Engineering managers are the hardest role in tech to hire well. They need to be technical enough to earn engineers' respect, empathetic enough to develop people, strategic enough to align with business goals, and resilient enough to handle the constant tension between those demands.
Getting this hire wrong is expensive. A bad senior engineer affects their own output. A bad engineering manager affects an entire team's output, morale, retention, and growth trajectory. After participating in over 150 engineering manager hiring processes at SmithSpektrum, I've developed a framework that consistently identifies great EMs—and filters out the candidates who interview well but manage poorly[^1].
The Three Pillars of EM Excellence
Every engineering manager needs strength across three dimensions:
People Leadership (40% weight): Can they develop, retain, and grow engineers? This is the core job. Technical skills and execution ability mean nothing if the team falls apart.
Technical Credibility (30% weight): Can they make sound technical decisions and guide architecture? They don't need to be the best coder on the team, but they need to earn engineers' respect and make good judgment calls.
Execution & Strategy (30% weight): Can they deliver results and align with business needs? Great people managers who can't ship don't last.
The most common hiring mistakes ignore this balance. Companies hire their best IC and promote them—but management is a different skill set. Companies over-index on charisma—but charisma without substance burns teams out. Companies skip thorough reference checks—but EMs often interview far better than they manage.
The Interview Process
A complete EM evaluation requires 5-6 hours of interviews with diverse perspectives:
| Stage | Duration | Focus | Who Conducts |
|---|---|---|---|
| Recruiter screen | 30 min | Basics, motivation | Recruiter |
| Hiring manager deep dive | 60 min | Leadership philosophy, fit | VP/Director |
| Technical interview | 60 min | Technical depth, credibility | Staff+ engineer |
| People management deep dive | 60 min | Management scenarios | EM peer |
| Cross-functional interview | 45 min | Collaboration, communication | PM + Design lead |
| Team interview | 45 min | Culture fit, day-to-day | Potential reports |
| Executive close | 30 min | Strategic alignment | CTO/VP |
The team interview—having potential reports meet the candidate—is critical and often skipped. The people who will work for this manager every day have instincts about whether they'll thrive under this leadership.
People Leadership Questions
This is where you spend the most time. If they can't lead people, nothing else matters.
Developing Engineers
"Tell me about an engineer you developed from mid-level to senior. What was your approach?" Listen for methodology, not just outcomes. Did they have a deliberate development approach, or did growth just happen? Probe on specific actions, timelines, and what they learned about developing talent.
"How do you handle an engineer who's technically strong but struggles with collaboration?" This tests coaching ability and nuance. Easy answers ("I'd talk to them about it") aren't enough. You want to hear about diagnosis, tailored approach, and persistence.
"Describe your approach to career conversations. How often? What format? What content?" Intentionality matters. Great EMs have a system. Mediocre EMs "do career conversations when there's time" (meaning rarely).
Follow-up probes: "What specific actions did you take?" "How did you measure progress?" "What would you do differently?"
Performance Management
"Tell me about a time you had to manage someone out. Walk me through the process." This is the hardest conversation in management. How they handled it reveals everything about their judgment, courage, and empathy.
Red flags: Has never managed anyone out (possible at early stages, concerning for experienced EMs). Only describes "easy" performance situations. Blames HR for inability to act. Shows no empathy for the difficulty.
"How do you differentiate between performance issues and wrong role fit?" This tests diagnostic ability. The answer matters for the individual and the team. Managing out someone in the wrong role rather than finding them the right role is wasteful.
Retention and Engagement
"What's your retention rate been? How do you explain it?" Self-awareness is the signal here. Everyone loses people. The question is whether they understand why and learn from it.
"Tell me about someone you lost who you wish you'd kept. What did you learn?" Candidates who can reflect on retention failures without being defensive are rare and valuable.
"How do you identify when an engineer is disengaging before they resign?" Proactive managers spot the signs early: reduced initiative, declining output, withdrawn behavior, sudden concern about work-life balance. Reactive managers learn when the resignation lands.
Technical Credibility Questions
EMs don't need to pass a Staff engineer technical bar, but they need Senior-level fluency and the judgment to guide technical decisions.
"Tell me about a technical decision your team made recently. What was your role?" The right answer depends on the team and situation. Sometimes EMs should be deeply involved; sometimes they should delegate. You're assessing whether they chose appropriately.
"How do you stay technically current while managing?" Great answers include deliberate practices: reading RFCs, attending design reviews, doing occasional coding, paired sessions with senior engineers.
"When do you roll up your sleeves and code versus delegate?" Look for self-awareness about when hands-on contribution helps versus when it undermines the team's ownership.
"How do you evaluate technical decisions when you're not the expert?" This meta-skill matters more than deep expertise. Can they ask the right questions, identify risks, and make judgment calls in unfamiliar territory?
For technical assessment, I recommend a 45-60 minute session with a Staff+ engineer that includes:
| Component | Format | Time |
|---|---|---|
| System walkthrough | Whiteboard their current system | 25 min |
| Technical decisions | Discuss past architecture choices | 20 min |
| Trade-off discussion | Probe on build vs. buy, debt vs. features | 15 min |
Execution Questions
"How do you approach roadmap planning with your team?" Process matters. You want to hear about stakeholder input, engineer involvement, estimation approaches, and flexibility for unknowns.
"Tell me about a project that went significantly over timeline. What happened?" Everyone has timeline misses. The question is whether they diagnosed root causes, communicated proactively, and improved for next time.
"Describe how you handle competing priorities from different stakeholders." This tests prioritization and stakeholder management. Great EMs negotiate, trade, and make explicit decisions rather than trying to do everything.
"What metrics do you track for your team? How do you use them?" Measurement approach reveals management philosophy. Too few metrics means flying blind. Too many means micromanagement. The right metrics focus on outcomes and health, not just activity.
Scenario-Based Questions
Present realistic management scenarios and probe how they'd handle them:
"Two senior engineers on your team have a persistent technical disagreement that's affecting velocity. How do you handle it?" Listen for: gathering context before acting, facilitating resolution rather than imposing it, knowing when to make a decision if facilitation fails.
"Your team just missed a major deadline. The CEO is upset. What do you do?" Listen for: taking ownership without throwing the team under the bus, communicating clearly, diagnosing root cause, preventing recurrence.
"A high performer tells you they're considering leaving for another offer. What's your approach?" Listen for: honesty about whether you should try to keep them, understanding their real motivation (often not money), not making promises you can't keep.
"An engineer reports that another engineer made an inappropriate comment. What do you do?" Listen for: taking it seriously, knowing HR and legal implications, protecting the reporter, thorough investigation, decisive action.
Score scenarios on a 1-4 scale. A 4 response shows systematic approach, considers multiple stakeholders, includes actionable steps, and acknowledges uncertainty. A 2 response is vague or single-dimensional. A 1 response reveals concerning judgment.
Reference Checks for EMs
Reference checks matter more for EM hires than any other role, and you need references from reports, not just peers and managers.
Questions for Former Reports
"How did they help you grow in your career?" Tests whether development happened or was just talked about.
"How did they handle situations when you disagreed?" Reveals conflict style and receptiveness.
"What was their biggest weakness as a manager?" Validates self-awareness (compare to what the candidate said).
"Would you work for them again? Why or why not?" The most honest signal you'll get.
Reference Red Flags
Former reports are hard to find—may have burned bridges.
All references are managers, no reports—what do reports actually think?
Vague positive generalities—not memorable, or reference is covering.
Hesitation on "work for them again"—diplomatic concern.
Evaluation Rubrics
People Leadership Rubric
| Score | Indicators |
|---|---|
| 4 | Clear development philosophy; specific examples of growing engineers; handles difficult situations with empathy and effectiveness |
| 3 | Solid people examples; reasonable management approach |
| 2 | Generic answers; limited specific examples; may avoid difficult situations |
| 1 | No evidence of people development; concerning behaviors |
Technical Credibility Rubric
| Score | Indicators |
|---|---|
| 4 | Deep system understanding; appropriate involvement level; clearly earns technical respect |
| 3 | Solid technical knowledge; reasonable involvement; competent decisions |
| 2 | Surface-level technical understanding; over or under-involved |
| 1 | Cannot discuss technical topics credibly; engineers wouldn't respect |
Execution Rubric
| Score | Indicators |
|---|---|
| 4 | Clear planning process; handles adversity well; strong stakeholder management |
| 3 | Reasonable delivery track record; adequate communication |
| 2 | Vague on process; may blame others for misses |
| 1 | Poor track record; doesn't take ownership |
EM Archetypes to Watch For
Some EM archetypes consistently fail despite interviewing well:
The Hero does everything themselves. Watch for: "I just do it myself when needed." These EMs don't scale and burn out their teams.
The Abdicator fully delegates without accountability. Watch for: "My team handles that" with no visibility into the work.
The Politician manages up brilliantly but ignores down. Peers love them; reports leave.
The Process Fanatic talks about methodology, not individuals. Process matters, but people matter more.
The archetypes that succeed:
The Multiplier makes everyone better. They have specific stories of developing others.
The Shield protects the team and removes obstacles. Team-first language.
The Coach develops through questions and guidance. They'll ask about your team during the interview.
Compensation Benchmarks
Engineering manager compensation in 2026 (US market):
| Level | Base Salary | Equity (Annual) | Total Comp |
|---|---|---|---|
| EM (first role) | $180K-230K | $40K-100K | $220K-330K |
| Senior EM | $220K-280K | $80K-180K | $300K-460K |
| Director | $260K-340K | $120K-300K | $380K-640K |
EM compensation should match IC compensation at equivalent levels. EM equals Senior/Staff Engineer. Senior EM equals Staff Engineer. Director equals Principal Engineer[^2].
If you're paying ICs more than EMs—or vice versa—you're incentivizing the wrong career moves.
The right engineering manager transforms a team. The wrong one destroys it. The investment in thorough assessment pays for itself many times over in retention, productivity, and engineering culture.
References
[^1]: SmithSpektrum EM hiring analysis, 150+ processes studied, 2019-2026. [^2]: Levels.fyi, "2026 Engineering Manager Compensation Report." [^3]: Fournier, Camille. "The Manager's Path." O'Reilly Media, 2017. [^4]: Google re:Work, "Manager Behaviors Research," 2023.
Hiring engineering managers? Contact SmithSpektrum for customized EM interview design and assessment support.
Author: Irvan Smith, Founder & Managing Director at SmithSpektrum