Hiring Engineering Managers: The Complete Guide

What Engineering Managers Actually Do

A Day in the Life

Engineering Managers are first and foremost people managers. Their primary responsibility is ensuring their team members are productive, growing, and engaged. When a team ships a major feature, the EM's contribution is often invisible—they cleared blockers, resolved conflicts, ensured the right people were working on the right things, and kept morale high through challenging moments.

A typical EM week might include: three or four 1:1 meetings with direct reports, a performance review write-up, a hiring debrief for a candidate they interviewed, a skip-level meeting with their manager's direct report, sprint planning with the team, and a difficult conversation with an underperforming engineer about expectations.

Core EM Responsibilities

People Management (Primary)

• Hiring: Writing job descriptions, reviewing resumes, interviewing, closing offers
• Performance: Setting expectations, giving feedback, writing reviews, managing PIPs
• Career Development: Helping engineers identify growth areas and opportunities
• Team Health: Monitoring morale, resolving conflicts, building psychological safety
• 1:1s: Regular conversations about work, growth, blockers, and life

Delivery (Secondary)

• Sprint/project planning and estimation
• Removing blockers that slow down engineers
• Coordinating with product, design, and other teams
• Escalating risks and timeline issues early
• Balancing technical debt vs. feature work

Technical Direction (Varies by Org)

• Some EMs own architecture decisions
• Others delegate to Tech Leads or Staff Engineers
• At minimum: technical credibility to earn engineer respect

Engineering Manager vs. Tech Lead

This is one of the most common questions in engineering hiring. The roles overlap but serve different purposes.

Tech Lead

Tech Leads own technical outcomes. They make architecture decisions, establish coding standards, review designs, and mentor engineers on technical skills. Tech Leads typically spend 50-80% of their time coding. They may conduct 1:1s focused on technical growth but don't own performance reviews or hiring decisions.

Tech Lead responsibilities:

• Architecture and system design decisions
• Code review standards and technical quality
• Technical mentorship for the team
• Hands-on contribution to complex features
• Technical representation in cross-functional meetings

Engineering Manager

Engineering Managers own people outcomes. They make hiring decisions, conduct performance reviews, have career conversations, and manage team health. EMs may understand the technical work deeply but their success is measured by team outcomes, not personal technical contribution.

EM responsibilities:

• Hiring, firing, and performance management
• Career development and growth conversations
• Team morale and psychological safety
• Process and team effectiveness
• Representing team in leadership meetings

When You Need Each

Many organizations have both roles working together. The Tech Lead owns "what to build and how," while the EM owns "who builds it and how they're doing."

The Player-Coach Problem

One of the biggest decisions when hiring an EM is whether you need a player-coach (codes part-time) or a full-time manager.

Player-Coach EMs

Best for:

• Teams of 3-5 engineers
• Startups where everyone needs to ship code
• Highly technical domains requiring hands-on leadership
• Teams that can't afford dedicated management overhead

The challenge:

• Coding suffers because management interrupts flow
• Management suffers because code deadlines create pressure
• Very few people excel at both simultaneously
• As team grows, the "playing" disappears but habits persist

Realistic expectations:

• A player-coach managing 5 people can code maybe 20-30% effectively
• Beyond 5 direct reports, the "player" part becomes unsustainable
• Great player-coaches are rare—most are better at one than the other

Full-Time Manager EMs

Best for:

• Teams of 6+ engineers
• Organizations with separate Tech Lead role
• Complex people situations (remote teams, growth challenges)
• Managers of managers

The challenge:

• Some engineers don't respect managers who don't code
• Technical credibility erodes over time
• May struggle to evaluate technical decisions

Making it work:

• Stay close enough to the code to have informed opinions
• Pair with strong Tech Lead or Staff Engineer
• Attend design reviews and stay involved in technical discussions
• Don't pretend to be more technical than you are

What Makes Great EMs

People Skills (Non-Negotiable)

Coaching and Feedback
Great EMs help engineers see blind spots and improve. They give specific, actionable feedback—not vague comments like "be more proactive." They can deliver hard messages with empathy and follow through on development plans.

Difficult Conversations
Every EM will face: an underperformer who needs a PIP, a high performer who's being difficult, a team conflict that's affecting delivery, a promotion request they can't grant. Great EMs don't avoid these conversations. They prepare, engage directly, and follow up.

Hiring Instinct
Strong EMs can spot engineering talent through interviews. They know what questions reveal actual ability vs. interview prep. They can sell their team to candidates authentically. They build diverse teams by expanding sourcing beyond the usual channels.

Technical Credibility (Necessary)

Engineers need to respect their manager's technical judgment, even if the manager doesn't code. Credibility comes from:

• Asking good questions in technical discussions
• Understanding trade-offs and constraints
• Not overriding technical decisions without good reason
• Admitting what they don't know

Business Awareness (Differentiator)

The best EMs connect engineering work to business outcomes. They can explain to their team why a feature matters, push back on unrealistic timelines with data, and make resource trade-off decisions that account for company priorities.

Where to Find Engineering Managers

Internal Promotion

The most common path to EM is promoting a senior engineer. Pros: they know the context, team, and codebase. Cons: management is a different skill set, and not all great engineers become great managers.

Signs a senior engineer might be a good EM candidate:

• Already mentoring junior engineers informally
• Takes interest in how the team works, not just their own work
• Shows empathy and emotional intelligence
• Handles ambiguity and conflict constructively
• Wants to amplify others, not just their own output

External Hire

When hiring externally, look for:

• Current EMs at similar-stage companies (startup EM → startup, not FAANG → startup)
• Tech Leads ready to move into management (must genuinely want people management)
• Second-time EMs who've learned from first experience

Where to source:

• Engineering leadership communities (Rands Leadership Slack, LeadDev)
• LinkedIn with specific searches for EM titles
• Referrals from your current engineering leaders
• EM-focused job boards and newsletters
• Conference speakers from leadership-focused events

Red Flags in EM Candidates

• Can't give specific examples of difficult people situations
• Only talks about technical achievements, not team outcomes
• Wants to be EM for the title/pay, not the work
• Badmouths previous direct reports or employers
• Can't articulate their management philosophy
• Never fired anyone (likely avoided hard decisions)

Assessment Challenges

Why EM Interviews Are Hard

Technical interviews don't work. A coding test tells you if they can code, not if they can manage people. System design shows technical thinking, not leadership ability.

Behavioral interviews are gameable. Any prepared candidate can tell the "tell me about a conflict" story they've rehearsed. The question is whether they actually handled it well or just tell it well.

References are often useless. Companies provide scripted references. Former managers give generic praise. The candidate picks their best advocates.

Better Assessment Approaches

Multiple, deep reference checks

• Talk to 3-4 former direct reports, not just managers
• Ask specific questions: "Tell me about a time they gave you hard feedback. What happened?"
• Look for consistency across references
• Pay attention to what's not said

Scenario-based discussions

• Present realistic management dilemmas from your context
• "You have an engineer who's technically strong but difficult to work with. The team is frustrated. What do you do?"
• Look for nuance, not textbook answers

Evidence of actual leadership

• What teams have they built? What happened to those teams?
• Who have they hired? What did those people go on to do?
• Who have they fired or managed out? What was the process?

Skip-level conversations

• If possible, arrange conversation with someone who reported to them
• This is the closest you'll get to real signal

Recruiter's Cheat Sheet

Resume Green Flags

• Clear progression: IC → Tech Lead → EM (not just "EM" suddenly)
• Specific team sizes managed (e.g., "managed 8 engineers")
• Hiring and growth language (built team from X to Y)
• Mix of technical and people accomplishments
• Tenure of 2+ years in EM roles (takes time to learn)
• Testimonials or recommendations from former direct reports

Resume Yellow Flags

• Very short EM stints (<1 year each)
• Only technical achievements listed, no people outcomes
• Vague claims like "led engineering efforts"
• No mention of hiring, performance management, or team building
• Title inflation without corresponding scope
• Missing team size or scope information

Questions to Ask in Initial Screen

• "How many people have reported to you directly?"
• "Tell me about someone you hired who worked out well."
• "Tell me about a time you had to give difficult feedback."
• "What's your approach to 1:1s?"
• "Have you ever had to let someone go? What was that process like?"

Technical Terms to Know