Show You Lead People, Not Just Projects
The hardest EM interview questions aren't about technical systems — they're about the people you've managed. How did you handle an underperformer? How did you grow someone into a senior engineer? What did you do when a strong engineer wanted to leave? These questions separate managers who know how to manage from ones who actually do it well.
Be specific and honest about hard situations. Interviewers can tell the difference between a rehearsed "difficult conversation" story and one where you actually had the conversation.
Average compensation increase for Askia EM clients
Askia client outcomesAverage time to first EM interview with optimized positioning
Askia client dataOf EM clients receive multiple offers
Askia client dataIs this guide for you?
Use this Good fit if you…
- ✓You're targeting EM, Senior EM, or Director of Engineering roles
- ✓Behavioral rounds on people management are where you stumble
- ✓You've led teams but haven't rehearsed your management stories
Skip Not the right fit if…
- ✗You're a new manager with less than 1 year of direct reports
- ✗You're targeting Staff+ IC roles
- ✗Your interviews are purely technical
The playbook
Five things to do, in order.
Build a story bank of 5 management archetypes
Prepare one story each for: the underperformer, the high performer you retained, the team conflict, the person you promoted, and the person you had to let go. These 5 cover 90% of people management questions.
Show the coaching, not just the outcome
"I put them on a PIP and they left" is a fact. "I gave monthly feedback, noticed the pattern wasn't changing, had a direct conversation about fit, explored alternatives, and ultimately transitioned them out" is a management story that shows judgment.
Quantify team health metrics
Attrition rate, eNPS, promotion rate, number of engineers leveled up under you. These data points exist — find them. "In 2 years managing this team, 3 engineers promoted, 0 regrettable attrition" is a powerful management thesis.
Name the structural changes you made
Great managers change the system, not just individual behaviors. "I introduced bi-weekly career conversations, not just annual reviews. That changed how quickly I could spot and address drift."
Show how you scaled yourself
At Director level, you manage managers. At EM level, you manage ICs but also develop tech leads. Show how you identified, developed, and delegated to people who could extend your reach.
See the transformation
"I managed a team of 6 engineers. One wasn't performing well so I gave them feedback and eventually they left."
"Inherited a team member who'd been missed in two promo cycles. In the first month, I found the real issue: no sponsorship and unclear expectations, not capability. Built a 90-day plan together, got them visibility on a cross-functional project, and advocated for the promotion. They're now a Senior Engineer and the highest-rated IC on the team. That's the story I look for before assuming underperformance is the person."
Questions people ask
How honest should I be about performance issues I've managed?
Very honest — with discretion. Don't name anyone. But do share the real texture of the situation. Sanitized stories read as fake. "It was a difficult conversation" is more believable than "it went smoothly."
What if I haven't managed anyone through a PIP or termination?
Lead with what you have. A story about early performance feedback, a career conversation that changed trajectory, or a team conflict you navigated shows the same judgment even without the hardest edge cases.
How do I show leadership scope without a large team?
Influence, not headcount. Show cross-team coordination, mentorship of engineers outside your direct report chain, and how your decisions affected other teams or the overall engineering org.
Ready to put this into practice?
Get personalized coaching for your Engineering Manager job search — resume, interviews, and offer strategy tailored to you.
