Where do you see yourself in five years?
answer
- direction, not a job title
- the capability you want to be known for
- near-term step, concrete and dated
- link the goal to this role
- firm on direction, flexible on path
basics
~20 sTests whether your ambition is real, self-aware and satisfiable here. Answer with a direction and a capability rather than a title, one concrete near-term step, and an honest link to what this role actually offers.
how to answer
5 beats- state the direction, not the titleOpen with the capability or class of problem you want to be trusted with, phrased in one sentence. Titles are organisation-specific and tell the interviewer nothing; if you want a title, mention it later as a consequence of the capability, not as the goal itself.
- the evidence that you are already on that roadGive one piece of recent work that points in the stated direction and say what changed because of it. Evidence from the last year or so turns an aspiration into a trajectory, and a small concrete example outperforms a list of courses or certifications.
- the next step, near enough to be checkableName what you want to be doing within roughly a year or two — a system to own, a depth to reach, a first experience of leading something. Keep it a step you could plausibly take in this job, so the answer stays connected to the room you are in.
- how this role advances itSay in one sentence which part of the goal this specific role moves forward, based on something you actually know about it. If it only advances part of the goal, say which part; that reads as evaluation rather than as a mismatch you failed to notice.
- the revision conditionClose by naming what would make you change course — discovering you like a different kind of problem, or that you enjoy leading more than you expected. Being firm on direction and flexible on path is what separates a considered plan from a recited one.
your answer
5 story prompts- Write the capability you want to be known for in one sentence, with no job title in it.
- Name one piece of work from the last eighteen months that already points that way.
- Name one thing this role offers toward that goal that your current job cannot.
- Write the near-term step you want within a year, concrete enough to be checked.
- Say in one sentence what would legitimately make you change direction.
draft and rehearse your own answer in a learn session
go deeper
This probes motivation and retention fit: whether you have a direction of your own, whether your self-assessment is realistic, and whether what you want can plausibly be found in this role. A strong answer proves you have chosen a direction deliberately, are already acting on it, and have checked that choice against what the job actually offers.
Direction first: I want to be the person a team goes to for identity and access problems. I'm on an internal security engineering team at a large enterprise, and most of my first year has been triage work — dependency findings, quarterly access reviews, the queue nobody fights over. Somewhere in that I noticed access kept producing the same repeat findings, so I rebuilt the review checklist with a teammate and we went from twenty-three repeat findings on that workflow to six across two review cycles. That was the first time the work felt like engineering rather than paperwork, and it's the direction I want to keep walking. In the next year or two I'd like to own one access surface end to end rather than working a queue across all of them, and be deep enough to be the reviewer instead of the reviewed. Five years out, I'd want to be the engineer other teams pull into design reviews on that domain — and honestly, teaching it. I wrote the walkthrough that two new joiners used in their first fortnight, and I liked doing it more than I expected to. What draws me to this role is that the access work here sits with the team rather than in a separate audit function, so I'd learn it from the design side. I don't know yet whether I end up managing. Ask me again after I've led one project properly.
The signal carriers are the specific repeat-finding drop and the honest admission that the manager question is untested. A junior is not expected to have chosen a track, but is expected to point at real work that already leans one way. Vaguer wording — 'I want to keep growing in security' — with no owned example would downlevel this immediately.
I'm aiming at depth rather than a title: I want to be the engineer an organisation relies on for threat modelling of internal platform services, the person who is in the room before a design is committed rather than after an audit flags it. That choice came out of real work rather than a plan. On my current team of eight I took over the secure-review rotation, and instead of reviewing pull requests one at a time I ran a seven-week clinic where each engineer walked their own service through a threat model with me. Repeat findings per audit cycle went from thirty-one to nine, and more usefully, three of them now run their own sessions without me. That told me the leverage I care about is depth plus teaching, not headcount. Over the next couple of years I want to be doing that at a harder difficulty — services with real blast radius, designs where the trade-off between usability and control is genuinely contested, and ideally somewhere the security team is measured on what gets built safely rather than on findings closed. That is most of why I'm sitting here; this platform group owns its own controls, which is the setup I've been trying to work in. Five years is far enough out that I'd be inventing if I named a title. What I'm firm on is the domain and the depth. What would change my mind is discovering I get more out of building the team that does this than doing it myself — I've had a taste, and I'm honestly not certain yet.
This works because the direction is defended with a decision the candidate already made under real conditions, and the number is tied to a mechanism others now run without them. The explicit uncertainty at the end reads as self-knowledge at this level, not indecision. Dropping the clinic detail and keeping only the ambition would downlevel it to a junior answer.
Direction plus one concrete skill you are building now is enough; nobody expects a mapped career. It is fine to say you do not yet know whether you want to manage, as long as you can describe what good looks like at the rung above you.
By now a specialty should be visibly forming, and you should be able to point at work where you already chose it over an alternative. Make the ask from this role concrete: a system you own end to end, a domain you go deep in.
Talk in terms of scope and multiplier rather than skills: what you want to be accountable for, and how many people your decisions should touch. Show that you have tested a path, not just imagined it, and can name what you would trade for it.
Frame the answer as the capability you want an organisation to still have after you leave, and the kinds of bets you want to be trusted with. Be explicit about whether you are chasing title, mandate or influence, and how you would know you had it.
saying these in an interview costs you the question
- Naming a title and a date with no capability behind it
- Describing a five-year plan this role could never support
- Joking about wanting the interviewer's chair or running the company
- Pure growth language with no near-term step you are already taking
- Signalling the job is a short stop on the way somewhere unrelated
- Claiming certainty about a path you have never actually tested
- What would you need from us to get there?Answer with two or three specific, grantable things: exposure to a particular kind of problem, review from someone deeper than you, ownership of a system, a path to leading a project. Avoid asks that are really promises you want made about promotion or title, and avoid saying 'nothing, I'll figure it out' — that reads as either false modesty or an unwillingness to be coached.
- What are you doing right now to move in that direction?Name evidence from the last year, not intentions for the next one: work you volunteered for, a review rotation you joined, something you taught. One example with an outcome beats a list of courses. If your recent work genuinely points away from the goal you just stated, say so and explain the correction you are making — that is a stronger answer than pretending the line is straight.
- What if that path isn't available here in five years?Show the direction survives without one specific ladder. Explain which parts of the goal are portable — the depth, the kind of problem, the people you want to grow — and say you would raise it early rather than quietly disengage. Do not answer 'then I'd leave', and do not pretend you would never notice; interviewers read both as unserious.
## What the prompt is really asking This prompt survives in loops because it is cheap to ask and expensive to fake. It arrives in several wordings: - 'Where do you see yourself in five years?', - 'What are your long-term career goals?', - 'What does the next step look like for you?', - 'How does this role fit into your plans?' All of them are the same question: 1. is your ambition real, 2. is it self-aware, 3. and can it be satisfied here for long enough to be worth hiring you. ## Failure one: a title instead of a capability The most common failure is answering with a title. 'Senior engineer in three years, staff in five' tells the interviewer nothing except that you have read a ladder. Titles are local currency; they mean different things in different organisations, and a candidate who plans in titles usually cannot say what capability the title is supposed to represent. **Answer in capabilities instead**: - the kind of problem you want to be handed by default, - the thing colleagues should come to you for, - the blast radius you want to be trusted with. A title can then appear as a consequence rather than the goal. ## Failure two: aspiration with no step The second failure is the opposite — pure aspiration with no near-term step. 'I want to keep growing and take on more responsibility' is unfalsifiable and forgettable. The fix is a **two-part answer**: the direction, then the concrete thing you are doing about it now. Evidence from the last twelve to eighteen months is what converts a wish into a trajectory, and it does not have to be impressive; a review rotation you joined, a runbook you rewrote, a newer teammate you brought up to speed all work if you can say what changed as a result. ## Failure three: misalignment The third failure is misalignment. A candidate who describes a five-year plan the role cannot support has just told the interviewer the hire will churn. This is the part most people skip, and it is the part being scored hardest. Before the interview, decide which piece of your goal this specific role plausibly advances — a domain, a scale of system, a kind of user, an ownership model — and say it out loud in one sentence. If the honest answer is that the role only advances part of the goal, saying so is stronger than a fabricated fit, because it shows you evaluated rather than applied blindly. ## Weak versus strong A weak answer and a strong answer often contain the same ambition. - The **weak** one goes: 'In five years I'd like to be a staff engineer, maybe leading a team, somewhere I can keep learning.' - The **strong** one goes: 'I want to be the person a team trusts on this class of problem; the last year and a half has been me deliberately going deeper on it, here is what I did and what it changed; what would move me furthest next is owning a system of this shape, which is why this role interested me.' Same length, entirely different **evidence density**. ## How the bar rises The bar rises with seniority in scope, not in certainty. A junior answer may legitimately end with 'I don't know yet whether I want to manage.' A senior answer that ends there reads as passivity, because by then you have had the chances to find out. Close on the **flexibility line** either way — what would make you change course — since an ambition with no revision condition sounds rehearsed rather than held.