Nobody knows where they'll be in five years. The interviewer doesn't either, and they know you don't. So the question feels dishonest to answer sincerely and risky to answer honestly, which is why so many people produce something vague and forgettable.

The way out is to understand what's actually being asked. This is not a prediction test. It's a question about direction, commitment, and whether this specific job fits the trajectory you're on. Answer that, and you don't have to invent a five-year plan you don't have.

What They're Really Asking

Four concerns sit underneath it.

Will you stay long enough to be worth hiring? Hiring is expensive and slow. Someone who reads as a six-month stopover is a bad investment. This is the biggest driver of the question.

Does this role fit your direction? If your goals point somewhere this job can't take you, you'll leave — not out of disloyalty, but because the fit was wrong. They'd rather find that out now.

Are you ambitious in a way that works here? Growth-minded is good. Wanting the interviewer's job in eighteen months is not.

Do you think ahead at all? Someone with no sense of direction reads as passive, which is a real signal about how they'll operate in the role.

Notice that none of these require an accurate prediction. They require a plausible direction and evidence that this job is a sensible step in it.

The Structure That Works

Four parts, forty-five to seventy-five seconds.

1. Direction, not a job title. Describe the kind of work you want to be doing and the depth you want to reach — "leading data projects end to end," "the person the team relies on for architecture decisions." Naming a specific title is brittle; titles differ across companies and you may accidentally name one that doesn't exist there, or one above the person interviewing you.

2. Growth you want. What you want to get better at. This is where you can be concrete and honest.

3. The connection to this role. The essential part: why this job is a genuine step toward that. This is what turns a generic ambition into a reason to hire you, and it needs real research on the company to sound credible.

4. A note of flexibility. One line acknowledging that specifics evolve. This reads as mature rather than uncommitted, provided the direction itself was clear.

The order matters — direction first, connection third. Leading with "I want to be a manager" without linking it to their role is the most common way this answer goes flat.

Sample Answers

Mid-level, aiming for depth:

"In five years I'd like to be the person a team relies on for the hard analytical problems — not necessarily managing people, but genuinely senior in the craft, owning things end to end rather than picking up defined pieces. Getting there means working somewhere with real data complexity and people who are better than me at parts of it. That's most of why this role interested me; the problems you described in the posting are a step up from what I'm handling now. Whether that ends up being an IC path or something with more leadership in it, I'd expect to have a clearer view in two or three years."

Early career:

"Honestly, five years is further than I can predict with confidence, but I know the direction. I want to be genuinely good at this — the kind of person who's trusted with independent work rather than closely supervised. Practically, that means the next couple of years are about depth: getting strong in the core skills, learning how the business side actually works, and building enough judgement to make calls on my own. This role appealed to me because it's hands-on and the team is small enough that I'd see a lot. Where I specialise after that, I'd rather discover than decide now."

Career changer:

"Coming into this field from operations, my five-year picture is straightforward: I want to be fully established here, past the point where the transition is the interesting thing about my background, and using the operational experience as an advantage rather than an explanation. Realistically, the first two years are about proving I can do the work at the same level as people who started here. This role is the right entry point because it sits close to the operational side, so what I already know is useful from day one rather than being set aside."

Senior candidate:

"At this stage my goals are less about progression and more about scope and impact. In five years I'd want to have built something durable — a team, a function, a system that outlasts my involvement. I'm not particularly focused on the next title. What matters is whether the problems are hard enough and whether I'm given enough ownership to do the work properly. From what I've read about where you're heading, this role has both, which is what brought me to the conversation."

Mistakes to Avoid

"In your job." Meant as a compliment, heard as a threat — or at best, as poor judgement about how organisations work.

A different job. Describing goals this company can't support answers the question honestly and disqualifies you at the same time. If your real answer is a different field, either apply for that field or find the honest overlap.

"I don't know." Understandable and fatal on its own. Nobody knows the specifics; you're expected to have a direction. "I'm not sure" with nothing after it reads as passive.

Wildly unrealistic timelines. "Running the department" in five years, from a junior role, signals a misread of how progression works.

Something obviously rehearsed and empty. "Growing with the company and taking on more responsibility" is the answer everyone gives. It's the interview equivalent of a generic resume — technically fine, entirely forgettable.

Anything unrelated to work. Personal five-year plans belong elsewhere. They're asking about your career.

Overcommitting to a lie. Promising a decade at a company you're unsure about is a small dishonesty with a real cost — it usually shows in your tone, and it's the same instinct discussed in lying on your resume.

If You Genuinely Don't Know

Most people don't, and there's a version of that which interviews well.

The move is to be specific about the near term and honest about the far term. "I know what I want the next two years to be about — getting strong in X and Y. Beyond that I'd rather stay open, because the paths I find interesting keep changing as I learn more about the field." That's honest, shows direction, and shows self-awareness. What kills the answer is stopping at "I don't know" without the near-term specificity.

You can also anchor on capability rather than position: what you want to be good at rather than what you want to be called. Skills-based goals are easier to state truthfully and read as more thoughtful than title-chasing.

If you're mid-transition, changing industries or moving into tech, the uncertainty is expected — lean on the direction of the change rather than its destination.

How It Connects to the Rest of the Interview

This question rarely stands alone. It's checked for consistency against everything else you say, so your answers should tell one story.

It pairs most directly with why do you want this job — if your five-year goal doesn't connect to your stated reason for wanting the role, both weaken. It also has to be consistent with why you left your last job: if you left seeking growth, your goals should reflect that. And it feeds why should we hire you, where trajectory is part of the case.

Have supporting evidence ready. A goal backed by something you've already started — a course, a project, a portfolio — is far more convincing than a stated intention. That's the same evidence principle behind answering the strengths question and building a STAR story bank with the STAR method.

Then use it. When they ask if you have questions, asking how people in this role have grown over three to five years connects directly back to your answer and makes the whole thing read as genuine.

Fitting It Into Full Preparation

Rehearse this alongside tell me about yourself, the behavioural set, and your greatest weakness. Run a mock interview to hear whether your answer sounds directed or vague, and work through the complete prep guide. Adapt for video, panel, and second interviews, sort what to wear, and follow up afterwards. Then handle salary expectations and negotiation.

None of it matters if you're not getting interviews. That's upstream: a tailored, ATS-readable resume, checked with a free ATS score and improved where the keywords don't match. If you're waiting on responses, how long it takes to hear back sets expectations, and how many applications per day keeps the pipeline full.

How to Build a Direction Worth Describing

If the answer feels hard, that's usually a signal rather than a problem with the question. Some practical ways to develop a real direction — which also makes the rest of your search sharper.

Look at what you already gravitate toward. Across your roles, which tasks did you volunteer for? Which did you avoid? That pattern is more informative than any career quiz, and it tends to describe your actual direction better than a title would.

Talk to people two or three steps ahead. Informational interviews are the fastest way to find out what a path actually involves, and they often correct assumptions built entirely from job postings. Networking and referral conversations surface the same information.

Name capabilities, not positions. "I want to be genuinely good at systems design" is a goal you can pursue anywhere and defend in any interview. "I want to be a Senior Manager II" depends on one company's ladder.

Test it cheaply. A project or a portfolio piece tells you whether you enjoy the work before you commit a job to finding out. This is how most successful career changes start, whether that's into tech or non-tech into data — and a career-change portfolio is the proof that makes the story credible.

Let it change. Direction isn't a commitment. Reviewing it once a year is more useful than deciding it once.

A real direction pays off well beyond this one question: it makes your targeting sharper, your tailoring more focused, your summary more specific, and your whole search less scattered. It also protects you from the drift that sets in during long searches, where burnout and repeated rejection push people toward applying to anything.

Turning the Answer Into Leverage

Used well, this question is one of the few places you can shift the conversation in your favour.

It sets up the salary discussion. A candidate with a clear trajectory has a stronger position when salary expectations come up and when it's time to negotiate the offer, because you're being priced on where you're going, not only where you've been.

It gives you a real question to ask. "How have people in this role grown over three to five years?" is among the better things to raise when they open the floor — see questions to ask in an interview. Their answer tells you whether your goal is achievable there, which is information you genuinely need.

It's a fit check in both directions. If they describe a path that doesn't match what you said you wanted, that's worth noticing now rather than a year in — the same reason why you left your last job is worth being honest with yourself about.

It reinforces everything else. A consistent trajectory strengthens what are your strengths, why should we hire you, and your STAR examples, because they all point the same way.

Frequently Asked Questions

How do I answer "where do you see yourself in 5 years"? Describe a direction rather than a job title, name the growth you want, connect it explicitly to this role, and add one line acknowledging that specifics evolve. Around a minute is right.

What if I don't have a five-year plan? Almost nobody does. Be specific about the next one to two years and honest that the longer term stays open. Direction plus near-term specificity is what's being tested, not accurate prediction.

Should I say I want to be a manager? Only if it's true and the role plausibly leads there. Framing goals around capability — what you want to be good at — is safer and usually reads as more thoughtful than naming a title.

Is it bad to say I want to start my own company? Usually, in a standard hiring conversation, because it signals a fixed departure date. If it's genuinely central to you, focus on the skills you want to build, and consider whether this role is the right fit at all.

Can I say I want the interviewer's job? No. It's intended as ambition and lands as either a threat or a misjudgement of how progression works. Describe the kind of work, not someone's specific seat.

Putting It All Together

The question isn't asking you to predict the future — it's asking whether you have a direction, whether this job fits it, and whether you'll stay long enough to matter. Answer those three and the fact that you can't see five years ahead stops being a problem.

Give a direction rather than a title, name what you want to get better at, connect it concretely to this role, and allow that specifics will change. Keep it consistent with everything else you say in the room. And if you genuinely don't know, say what the next two years are about — that's a better answer than a confident invention, and interviewers can tell the difference.

Make sure you get the chance to give it: run your resume against the posting with a free ATS score and tailor it before you apply.