Answer “where do you see yourself in five years” with a level and a track. Name the level you want on the company’s own ladder. Say whether it sits on the engineering track or the management track. Then name one piece of work in this role that moves you toward it. A software engineer who says “a senior engineer leading a team” has mixed two tracks in one sentence. The interviewer will usually ask the next question, “Do you want to manage people?” Answer it with a choice and a reason from work you have already done. “Maybe someday” leaves the question open. “Not yet, but here’s how I’d test it” answers it. If you don’t know where you’ll be, that’s normal. Nobody is grading a forecast. The interviewer is checking that this job is on your path. They also want to see that you know which path that is. The rest of this post builds one Android engineer’s answer, follow-up included.
Where do you see yourself in five years asks if this job is on your path
The question asks for a prediction. The interviewer wants three other things from it. First, does this role fit what you want next? Second, will you still want it in two years? Third, do you understand how growth works in engineering?
The third point is where the follow-up comes from. Engineering ladders split at a certain level. An answer that ignores the split tells the interviewer you haven’t looked. So they ask about it directly.
Rhea’s draft mixed two career tracks in one sentence
Rhea is a senior Android engineer with six years on a fitness app. She is interviewing for a senior Android role on a larger team. Her prepared answer went like this.
In five years I see myself as a senior engineer leading a team. I want to keep growing technically and take on more responsibility.
Nothing in it is false. But “leading a team” could mean two different jobs. It could mean a tech lead who still writes and reviews code. It could also mean an engineering manager who runs one-on-ones and hiring. The interviewer can’t tell which one Rhea wants. She is also already senior, so “senior engineer” in five years sounds like standing still. The answer invites a follow-up that Rhea hasn’t prepared for.
Above senior, many ladders split into an engineering track and a management track
GitLab’s public handbook describes this split plainly. Its organizational structure page calls it a dual career path. It lets people move up without becoming people managers. The page says the fork comes “generally above the Senior level.” Past that point, someone who wants to progress has to pick a track. The same page says the pay bands for the two tracks align in most cases.
GitLab’s engineering management career guide goes further. For senior developers, it calls technical or professional leadership the most important career question. It also says not every team member will want to become a staff developer or a manager.
That is one company’s handbook. Will Larson’s StaffEng guide is undated online. It notes that a few companies have no staff-level technical path at all. They push experienced engineers toward management. Where the split exists, a senior candidate is expected to know which side they’re heading for.
Name the kind of staff role you already do in small pieces
“Staff engineer” alone is still vague. Larson’s guide sorts staff-level roles into four types. A tech lead guides one team’s approach and execution. An architect owns direction and quality in a critical area. A solver digs into hard problems wherever they are. A right hand extends an executive’s reach across a large organization.
Pick the one you already do in small pieces. That gives the interviewer evidence they can ask about. Rhea led her app’s move from one Gradle module to feature modules this year. She wrote the plan and split the work across four engineers. She reviewed every migration pull request. That is a small tech lead job. She can defend every part of it.
Then name the gap honestly. Rhea has led one team’s work. She hasn’t set direction across several teams. Saying so shows she knows what the next level asks for.
Tie the gap to work this team actually has
The gap is only useful if this job can close it. Read the job description and the team’s engineering blog for one concrete piece of work. Rhea’s target team owns a shared design system. Three app teams build on it. Owning part of that system would give her the cross-team work she lacks.
This is also what keeps the answer from sounding like you’ll leave. A five-year goal that this team can feed reads as a reason to stay. Our post on the why do you want to work here answer uses the same move. It builds from one real detail about the company.
Answer “do you want to manage people?” with something you’ve tried
There are three honest answers. Yes, no and not yet. Each one needs a reason drawn from something you’ve done.
A “yes” needs a taste of the job. Maybe you ran hiring loops, or covered one-on-ones while your manager was away. A “no” needs the same kind of evidence, pointed the other way. Rhea covered for her manager for two months last year. She was competent at it. But she missed the design work every week.
A “not yet” needs a test. Name the small step you’d take first. Mentoring formally counts. So does running an interview loop. GitLab’s structure page says a manager can let someone try tasks from both tracks before choosing. So “not yet” comes with a next step.
Moving between tracks later is normal too. Charity Majors argued this in “The Engineer/Manager Pendulum”, a 2017 essay. She wrote that “you can only really improve at one of these things at a time.” So picking one track now leaves the other open later. It tells the interviewer what you plan to get better at next.
Rhea’s full answer, with the follow-up
In five years I want to be a staff engineer on the Android side, not a manager. Usually that’s the step after senior. The kind of staff work I’m drawn to is tech lead work.
I already do a small version of it. This year I led our move from one Gradle module to feature modules. I drafted the plan, split the work across four engineers and reviewed every migration PR. Clean build times dropped from eleven minutes to six.
What I haven’t done is set direction across several teams. Your team owns the design system that three app teams build on. Owning part of that in my first two years is how I’d close the gap.
Then the interviewer asks, “Do you want to manage people?”
Not in the next five years. Last year I covered for my manager for two months. I ran one-on-ones and sprint planning. I was fine at it. But the module review was the part of each week I looked forward to. If that changes, I’d ask to mentor formally first and see how it feels before switching tracks.
We made Rhea up for this example. Her build times are made up too. Swap in your own work and your own numbers.
Every claim in the answer points back to something already in this post. “Staff, not manager” picks a side of the fork. “Tech lead work” names the type. The module migration is the evidence. The design system is the gap this job fills. The follow-up answer rests on two months she actually spent doing the other job.
No published ladder? Look for staff job postings at the same company
Many companies don’t publish their ladder. Their careers page often shows it anyway. Search it for “Staff Android Engineer” or “Staff Software Engineer.” Current or past postings mean the engineering track goes past senior. The posting’s responsibilities also tell you what that level does there. Borrow that wording for your gap.
If you find only senior roles and engineering managers, the track may stop at senior. That changes the answer. Ask the interviewer how senior engineers grow on this team. If the reply only describes moving into management, a staff goal won’t fit this team. Weigh that before you accept an offer.