[!NOTE] Engineering Managers are evaluated on one fundamental question: Can you build and maintain a high-performing team? This means hiring the right people, growing them, having hard conversations when needed, and sometimes letting people go. These are the hardest parts of management — and the most commonly tested in interviews.
Hiring: Building the Team
The #1 interview question for EM candidates: "How do you hire great engineers?"
The Hiring Bar Framework
- Define what "great" means for THIS role: A startup SSE is different from a FAANG SSE. Write down 3-5 non-negotiable skills AND 3-5 nice-to-haves before you start interviewing.
- Structured interviews beat gut feelings: Google''s internal research showed that structured interviews (same questions, consistent rubrics) predict job performance 2x better than unstructured interviews.
- Hire for slope, not intercept: A candidate with rapid growth trajectory and strong fundamentals will outperform a senior engineer who has plateaued. Look for learning velocity, not just current knowledge.
Real-World Example: Netflix''s "Keeper Test"
Netflix asks managers: "If this person told me they were leaving, would I fight hard to keep them?" If the answer is no, they proactively manage the transition. This is controversial, but understanding it helps you answer EM interview questions about team quality.
Managing Underperformance
The question interviewers ALWAYS ask: "Tell me about a time you had to manage an underperforming engineer."
The Performance Improvement Framework
- Diagnose before acting: Is it a skills gap, motivation issue, personal problem, or wrong-role fit? Each requires a different approach.
- Have the direct conversation: Use SBI (Situation-Behavior-Impact). "In the last 3 sprints, your velocity has been 40% below the team average. I want to understand what''s happening and how I can help."
- Create a clear plan: Specific, measurable goals with a timeline. "Over the next 4 weeks, I''d like to see you complete 2 features per sprint with production-quality code reviews."
- Provide support: Pair programming, mentoring, reduced scope — show genuine investment in their success.
- Follow through: If performance doesn''t improve after genuine support, have the honest conversation about fit.
Example Answer (Strong)
S: "A mid-level engineer on my team was consistently missing deadlines and producing code that required multiple review cycles."
A: "I first had a private 1-on-1 to understand the situation. I discovered they were struggling with our microservices architecture — they came from a monolith background. I set up twice-weekly pairing sessions with a senior engineer, adjusted their sprint load for 6 weeks, and gave them a focused project that would build their distributed systems skills incrementally."
R: "After 2 months, their velocity matched the team average and their code review feedback improved dramatically. They eventually became one of our strongest contributors on distributed tracing. The investment paid off — hiring a replacement would have cost us 3-4 months of productivity."
Having Difficult Conversations
Engineering Managers must navigate: layoffs, PIPs, team reorganizations, and delivering bad news. The secret: radical candor — care personally while challenging directly.
Kim Scott''s Radical Candor Framework
- Radical Candor: Care personally + Challenge directly = Best outcomes
- Ruinous Empathy: Care personally + Don''t challenge = Problems fester
- Obnoxious Aggression: Don''t care + Challenge directly = People leave
- Manipulative Insincerity: Don''t care + Don''t challenge = Toxic culture
[!TIP] Interview insight: When discussing a difficult conversation, show both the empathy (you cared about the person) and the directness (you didn''t avoid the hard truth). Answers that show only empathy sound weak. Answers that show only directness sound harsh. The combination is what gets offers.