Engineering Manager interview question · Most asked
How technical should an engineering manager be?
Summary
Technical enough to understand trade-offs, ask good questions, judge risk and earn credibility — but not the person making day-to-day technical decisions or writing critical-path code. Those belong to the tech lead and the team.
Longer Answer
Managers who code on the critical path become bottlenecks and neglect people work; managers with no technical depth can't evaluate designs, risks or hiring signals. Ways to stay current: reading design docs and incident reviews, joining design reviews as a listener, small non-critical contributions, and pairing occasionally.
Key Points
- Enough to judge risk and trade-offs
- Not the critical path
- Stay current deliberately
Deep dive: The Manager's Operating System
Explanation
What interviewers look for
Balanced view of technical credibility.
Red flags
- 'Managers shouldn't need technical skills'
- Still the main coder on the team
More most-asked Engineering Manager questions
- Tell me about a time you disagreed with your own manager or leadership.
- How do you measure your team's performance?
- How do you approach hiring for a new role?
- What makes an interview process fair and predictive?
- How do you help engineers grow their careers?
- How do you handle an engineer who has been underperforming for months?
- An engineer asks for a promotion you don't think they're ready for. What do you say?
- How do you retain strong engineers?