Stay technical enough to make good decisions and review designs credibly, without putting yourself on the critical path. In practice that means reading pull requests, taking part in design review, occasionally picking up small non urgent work, and joining incidents as a coordinator rather than a hero. Team size drives the level: with five reports you can code a little, with fifteen you should not.
Why interviewers ask this
The interviewer is looking for self awareness about the tradeoff. Managers who stay too hands on become bottlenecks and take the interesting work from their team; managers who disconnect entirely lose the credibility to challenge an estimate or a design. They want a deliberate policy tied to team size and context, plus the mechanisms you use to keep judgment sharp without owning production critical code.
How to structure your answer
- Give the principle: technical judgment without being on the critical path.
- Name the specific activities that keep you current.
- Tie the level of hands on work to team size and context.
- Say what you deliberately do not take on and why.
Example answer
My rule is that I stay technical enough to have an opinion and never take work that blocks anybody. So I read pull requests most days, I am active in design reviews, and I will pick up things that are genuinely not urgent: tooling, a flaky test, documentation, work that can sit for a week when my calendar explodes. What I do not do is take a feature on the critical path, because the week that goes sideways is always the week I have three interviews and a reorg conversation, and then I am the bottleneck and I have also taught my team not to trust my commitments. With six reports I probably write code a few hours a week. When I ran a group of sixteen across two teams I wrote almost none and stayed sharp through design documents and incident reviews instead. During incidents I join as a coordinator and a shield, not as the person typing, because that is the fastest way to make the actual experts wait on me.
Walking into this interview soon? GhostPilot listens to your live call, spots the question the moment it is asked, and puts a structured answer on your screen in real time. Try it on your next mock, or grab a $29 Session Pass, no subscription, for the real thing.
See how it worksFollow-up questions to expect
- How do you keep credibility with senior engineers if you are not coding?
- What happens to your technical skills over five years of managing?
- How do you avoid overriding your team just because you could do it yourself?
Related engineering manager questions
Your interviewer will ask their own version of this. Paste your actual job description into the free Question Predictor and get the 20 questions that role is most likely to ask, with what each one is really probing.
Predict my questions