Do you see yourself staying hands-on, or moving into management?
answer
- answer the fork, do not hedge
- evidence: something you already tried
- what you value on the other side
- what you want from this role now
- when you would revisit the choice
basics
~10 sTests self-knowledge and whether the track you want exists here. Answer the fork directly, back the choice with something you have already tried rather than imagined, and say when you would revisit it.
how to answer
5 beats- answer the fork in one sentenceLead with your leaning, stated plainly, even if it is provisional. A balanced non-answer reads as evasion and gives the interviewer nothing to plan a role around; you can qualify it immediately afterwards.
- the experience the choice came fromCite something you have already done that resembles the track you are choosing or rejecting — a project you led, a rotation you ran, people you brought up to speed. Say what it produced, so the preference rests on evidence rather than on temperament.
- what you genuinely value on the other sideName one thing the path you did not choose gives you, and how you plan to keep some of it. This prevents the answer from sounding dismissive and shows you weighed a real trade rather than picking the comfortable option.
- what that means for this roleTranslate the preference into what you want from the next year here: the ownership, the scope, or the leadership exposure you are asking for. Keep it to something the role could plausibly provide, and acknowledge it if you are unsure whether it can.
- the revisit pointClose by naming roughly when and on what signal you would reopen the question. A choice with a review date sounds held; a choice presented as permanent sounds rehearsed, especially to interviewers who have changed tracks themselves.
your answer
5 story prompts- Name the closest thing to leading that you have already done, however small.
- Write one sentence on what you enjoyed in it and one on what drained you.
- Name what the path you are not choosing gives you, and how you keep some of it.
- Write the leaning as one plain sentence, with no hedge in it.
- Name the signal that would make you reopen this choice, and roughly when.
draft and rehearse your own answer in a learn session
go deeper
This probes self-knowledge and track fit. The interviewer needs to know whether the growth you want exists on this team, and whether your stated preference comes from experience or from assuming that leadership is the only ladder. A strong answer picks a side, defends it with something you actually tried, and names the conditions under which you would reconsider.
Hands-on, and I can tell you what that's based on rather than just how it feels. Last year my group in an enterprise security org needed threat modelling to stop being a bottleneck sitting with two people. I offered to run it as a shadowing rotation instead of doing the sessions myself: three engineers sat in with me, then ran one each with me in the room, then ran them alone. By the end of that review cycle open high-severity findings on the services they covered had gone from seventeen to five, and the queue stopped depending on me being available. What I noticed is that the part I enjoyed was the coaching, not the coordinating. Sitting with someone while they work out that an authorisation check belongs one layer down is the best hour of my week. The scheduling, the arguing about whose quarter it comes out of — I did it competently and it drained me. So the honest read is that I want the mentoring without the management, which as far as I can tell is what a senior individual-contributor seat actually is. For this role that means I'd want to own a technical area and be the person newer engineers are pointed at, and I'd happily take a tech-lead stint on a project if one comes up, because I'd rather test it than theorise. I'd revisit the whole question in about two years, or sooner if I found I was more interested in who is doing the work than in the work.
The strength here is that the preference is separated into components — coaching yes, coordinating no — and each is tied to something actually done. Offering to take a tech-lead stint shows willingness to test rather than assert. Saying only 'I prefer coding' with no rotation and no outcome would leave nothing for the interviewer to weigh.
I want the staff individual-contributor path, and I say that having tried the other one rather than having avoided it. In my current enterprise security group I built the security champions programme across four product areas — picking the engineers, designing what they were accountable for, running the review cadence. Findings per quarterly audit across those areas fell from forty-one to fourteen over three cycles, and I count that as the highest-leverage thing I've done. For one quarter I also line-managed two of those engineers while their manager was out: I did their one-to-ones, their goal setting and one difficult performance conversation. That quarter taught me the trade precisely. I was better at the people work than I expected, and I was measurably worse at my own: my design reviews got shallow, and I caught an authorisation gap two weeks later than I should have because I was reading calendars instead of code. Both things are true, and given the choice I'd rather be the person the architecture actually depends on and mentor through the work rather than through a reporting line. What I'd want here is the scope that goes with that — being accountable for how security is designed across a group rather than for one service, and being expected to grow the engineers who do it. If the honest answer is that the influence at that level only comes with a manager title here, I'd want to know now, because that changes what I'd be signing up for. I'd revisit the question if the org's shape made the individual-contributor seat toothless.
This is credible because the manager track was sampled, not imagined, and the cost is named out loud with a specific consequence. Asking directly whether the influence requires a title shows the candidate is evaluating structure, not just expressing preference. Removing the named trade-off would flatten it into an assertion.
You are rarely asked this yet, and 'I don't know' is an acceptable core, but say what you would need to find out — leading a small piece of work, running an onboarding, owning a rotation. Curiosity about both sides beats a confident guess.
This is the level where the question starts landing, and the expected answer is a leaning plus a first data point: a project you led, a rotation you ran, someone you brought up to speed. State the leaning even if it is provisional; pure hedging is the weak answer here.
You should be able to describe the choice as tested, not felt: something you did that resembled the other track, and what it cost you. Name the trade honestly — depth given up, or hands off the keyboard — because a senior who has never weighed the cost sounds untried.
Frame it as where your leverage lands rather than as a personal preference: which decisions you should be in, which you should be enabling others to make. Be clear about the mandate you need for either answer, and about what the organisation loses if you sit in the wrong seat.
saying these in an interview costs you the question
- Hedging both ways so the interviewer cannot tell what you want
- Choosing management as the only visible way to grow
- Dismissing the other track as beneath you or as not real work
- Claiming a preference you have never tested in any form
- Naming a track the role plainly cannot offer, without acknowledging it
- What did you actually like about leading that work?Answer with the specific mechanic rather than the feeling: unblocking someone, shaping a plan, making the priority call, watching a person become able to do it without you. Naming what you liked and what you found draining is stronger than pure enthusiasm, because it shows you were paying attention rather than performing an aptitude you think is expected.
- Would you take a management role here if we offered it?Do not answer purely to please. Say what conditions would make it a yes — the size of the group, whether you keep technical depth, a trial period with a way back — and what would make it a no. If the honest answer is not now, say not now and say why; an engineer who accepts a track they do not want is a predictable resignation.
- How would you know if you'd chosen wrong?Give an observable signal, not a mood: the work you look forward to shifting, your review quality dropping, months passing without you learning anything technical, or people around you stalling. Add what you would do about it — raise it early, ask for a change — so the answer shows a correction mechanism rather than fatalism.
## Why interviewers ask Interviewers ask this for two reasons, and they weigh differently depending on who is asking. - A **hiring manager** is checking supply and demand: if you want a management track and the team has no opening for one, or you want deep individual-contributor work on a team that mostly needs a lead, the hire has a short half-life. - A **senior interviewer** is checking self-knowledge — whether you have actually examined the fork or are repeating whichever answer you think the room rewards. ## The double hedge The first mistake is the double hedge. 'I could see myself doing either, I'm happy wherever I'm most useful' sounds cooperative and lands as evasive. It gives the interviewer nothing to plan around, and it usually means the candidate has not thought about it. A **provisional leaning stated plainly** is always stronger than a balanced non-answer: 'hands-on for now, and here is what would change that' is a complete answer. ## Management as the only visible ladder The second mistake is choosing management because it is the only ladder you can see. Many candidates arrive at the manager answer by elimination — the individual-contributor path in their current organisation stops at a certain rung, so growth must mean managing. That reasoning is visible from the outside, and it worries interviewers, because a manager who took the job to keep growing rather than to grow other people tends to hold on to the technical work and starve the team. If your reasoning really is about scope, say the scope thing directly and let the interviewer tell you what tracks exist here. ## Untested certainty The third mistake is untested certainty. Preference claims carry weight in proportion to the evidence behind them, and the useful evidence is almost always small: - a project you led, - an incident you coordinated, - a rotation you owned, - a newer colleague you brought to competence. What you learned from that experience — including what drained you — is the substance of the answer. A candidate who says leading a small piece of work was satisfying but that they missed being deep in the problem has told the interviewer something real. A candidate who simply asserts a fit has not. ## If you already lead There is a version of this question aimed at people who already lead: 'would you go back to being hands-on?' The same rules apply, inverted. 1. Answer the fork, 2. cite the experience, 3. name the trade. The trade is what makes it credible in both directions — every choice here costs something, and pretending otherwise is what makes an answer sound like a script. ## Fit with this specific role Finally, be honest about the fit with this specific role. If you want a management path and the posting is plainly an individual-contributor seat, you can still say so, framed as **a horizon rather than a demand**: what you want next is the deep work, and the leadership question is one you would want to revisit in a couple of years with whoever is running the team. That is a workable answer. Concealing the ambition and surfacing it three months in is not, and interviewers who have been burned that way ask this question precisely to avoid it. Close on a **revisit point** — a rough horizon and the signal that would prompt the conversation — so the answer reads as a considered position rather than a permanent vow.