“Where do you see yourself in 3 years?” How to answer

"Where do you see yourself in three years" feels like a formality until you are the one being asked. In tech it is usually worded differently. In the Sobes question bank it is "How do you see your further career development?" and "Do you have a career track? Do you want to grow technically or toward management and team lead?". The second wording was recorded after interviews at 6 companies, and a similar one in the iOS section, about choosing between a technical role and leadership, at 4.

Almost nobody has a precise three-year plan, and the interviewer knows it. Two answers fail: "I haven't thought about it" and "I want your job". The first shows you don't care where you are heading. The second sounds like a joke from a twenty-year-old advice book.

What they want to know

• Whether you will leave in six months. If you want ML and the role is billing support, both sides are better off finding out now.
• Whether your track matches what the company can give. A team of five with no growth plans won't produce a team lead position. A company with no staff grade has nowhere for a senior who doesn't want management to grow.
• Whether you think about your development at all. A person with a direction learns faster and is easier to manage: it is clear which tasks to give them.

The answer doesn't need promises or job titles. A direction and a next step are enough.

How the answer is built

Three parts, about thirty seconds:

1. Direction: technical depth, architecture, managing people, product, an adjacent field.
2. The next step for the coming year or year and a half, specific: which tasks you want to take on, what you want to learn.
3. The link to the role: why that step can be made here.

Phrase it through tasks and responsibility, not job titles. "I want to own a service's architecture end to end" can be checked and discussed. "I want to become a senior" means something different at every company: what actually separates the grades is covered in Middle vs senior developer: the difference in an interview.

Shorten the horizon freely. Give three years one sentence and the coming year the detail.

Junior

Over the next year I want to get to the point where I take tasks end to end: from clarifying requirements to release, without constant help. For that I need code review from strong developers and real production, not study projects. In about three years I see myself as a confident middle backend developer. Whether I go deeper into databases or infrastructure, I'll figure out along the way.

An honest "I'll figure it out along the way" is fine for a beginner. What matters is that there is a near goal and it is clear what you need from the team to reach it.

Middle

I want to grow toward design. Right now I'm good at doing tasks inside an existing architecture, and the next step for me is designing services myself and owning them in production: monitoring, incidents, load. Your job description mentions splitting services out of a monolith, and that's exactly that kind of experience.

It names what you can already do, what is missing, and where the job description has it. The interviewer doesn't have to guess whether the work will suit you.

Senior

I'm interested in influencing decisions beyond one team: standards, shared platform pieces, things that make life easier for several teams at once. I also want to grow people more: mentor two or three developers. Whether that's called staff or something else doesn't matter much to me. What matters is that the company has a need for that kind of work.

A senior is expected to think about impact, not the next line in the grade table. The sentence about the company's need doubles as a question: it is natural to ask right then whether they have such a role.

I want to be a team lead

I want to try leading a team. For the past year I've informally led three people: breaking down tasks, doing reviews, onboarding newcomers. I like it, and it works. I also understand I'm not joining you as a team lead right away: first I want to learn the product and show results as a developer. How do team leads usually appear here, do they grow from inside or get hired?

The answer works for two reasons. The wish is backed by experience, not just by "I want". And the candidate doesn't demand the title at the door but asks how it works. If you are applying for a lead position directly, the preparation is different, and the article on the team lead interview covers it.

Be careful if the team already has a lead and that person is sitting across from you. Talk about a growing area of responsibility, not a particular chair.

I don't want management

I don't want to go into management. I tried being a team lead for six months and found that calls and planning come harder to me than engineering work. I want to grow as an engineer: hard technical problems, performance, architecture. I'm happy to mentor, but I don't want direct reports. Do you have a technical growth track?

A direct answer beats an evasive one here. The wordings from the bank show that companies themselves ask about the choice between a technical and a managerial track, and "I don't want to manage" is a workable option for them. The only thing that sounds bad is "I don't want to be responsible for anything".

If you really don't know

Name what you do know and the choice in front of you:

I don't have a precise plan. I know two things interest me: working with data and system reliability. For the next year I want to work where they meet and see which is closer to me. That's why your team interests me: you have both.

That is more honest and more convincing than an invented title.

What not to say

• "I want my own business" or "I'm planning to relocate". It may be true, but the interviewer will hear the date you leave.
• "I want your job."
• A plan that has nowhere to come true at this company: ML on a team that has none.
• Different plans at different stages. The recruiter, the manager, and the CTO in the final round compare notes.

Check the answer against the rest of your story

Plans for the future should continue what you say about the past. If in your "tell me about yourself" you spent three years moving toward architecture and then answer the plans question with "I want to be a product manager", you will need an explanation. Your reason for leaving should line up with the plan too: if you are leaving for lack of growth, say what kind of growth.

Write the answer in three sentences and say it out loud together with your self-introduction and your reason for leaving, back to back, the way a screening goes. You can run the whole sequence in the HR mode of the mock interview. And at the end of the real interview, ask a question of your own: "How have the people who joined in this role two or three years ago grown?" The answer will tell you whether your plan can come true here.