Skip to content

Engineering Manager (Years 8–12+) — Deep Dive

Build teams. Develop people. Align with business. Scale the org.

What "Engineering Manager" Actually Means

An Engineering Manager is:

  • Responsible for people — hiring, developing, feedback, compensation
  • Owns team delivery — on-time shipping, quality, team health
  • Represents engineers — advocates for team to leadership
  • Makes hard decisions — sometimes firing, restructuring, prioritization
  • Culturally important — sets tone for how team works

Key insight: You're a manager of people, not projects. Projects change; people are your focus.

Your First Year as Manager (Years 8–9)

What changes:

  • You stop owning features → you own team delivery
  • You code 10–20% → strategically (unblocking team, not shipping)
  • You meet 1-on-1 → weekly with each report (5–8 people)
  • You care about team happiness → as much as shipping

Your responsibilities:

  • Hiring: Source, interview, offer engineering
  • Onboarding: Get new engineers productive in 4 weeks
  • 1-on-1s: Weekly growth conversations with each report
  • Goals: Set team OKRs aligned with business
  • Performance: Feedback, evaluations, promotions
  • Culture: Shape how team collaborates
  • Execution: Unblock team, manage dependencies
  • Communication: Translate leadership goals to team, team needs to leadership

Skills you need:

  • Emotional intelligence: Understand what motivates people
  • Hiring: Build a strong bench
  • Communication: Clear, kind, frequent feedback
  • Judgment: When to push, when to support
  • Business acumen: How does engineering affect business?
  • Resilience: People problems are hard

Years 8–12: Growing as Manager

Year 1 (First Time Manager)

Focus: Master the basics.

  • Hire and build core team (5–8 people)
  • Establish 1-on-1s and feedback cycles
  • Ship first few projects on time
  • Build team culture and trust

Success metrics: - Team members say you're fair and supportive - You ship on time and with quality - No surprises (you communicate well) - Low turnover (people want to stay)

Years 2–3 (Growing)

Focus: Develop people. Scale impact.

  • Grow team to 8–15 people (or hiring for growth)
  • Promote 1–2 engineers within team
  • Represent team in cross-functional projects
  • Mentor other managers

Success metrics: - Engineers from your team get promoted to Senior - Team tackles harder problems - You influence decisions beyond your team - Leadership listens to your input

Years 4+: Senior Manager

Focus: Strategic leadership.

  • Manage multiple teams or large team (15+)
  • Hire and develop other managers
  • Set technical strategy for crew/division
  • Influence org culture and values

Success metrics: - You're known for developing great engineers - Your crew ships quality product - Other teams ask for your help - Leadership values your strategic input

The Hard Conversations

As manager, you do things you don't want to do:

Performance issues: - Engineer isn't growing → you give feedback - Performance doesn't improve → you put them on performance plan - Still doesn't improve → you fire them

Compensation: - Engineer thinks they deserve 40% raise, market is 10% → you have hard conversation - Someone is underpaid → you fight for budget to fix it

Conflict: - Team members disagree → you mediate and decide - Engineer doesn't like manager of other team → you have conversation - Someone is toxic → you address it

These hurt. They're still your job.

Promotion to Director/Senior Manager

What they're looking for:

✅ Scope: Are you managing multiple teams or a large team?
✅ People development: Have you promoted engineers or managers?
✅ Strategic thinking: Do you think about bigger org problems?
✅ Business acumen: Do you understand revenue and customer impact?
✅ Credibility: Do other managers and leaders trust you?
✅ Execution: Does your org deliver consistently?
✅ Communication: Do you communicate clearly up/down/across?
✅ Resilience: Do you stay calm during crises?

Interview for Director includes: - "Tell me about going building a team from scratch to X people" - "How do you handle a talented engineer who's checked out?" - "Describe your approach to hiring" - "Tell about a time you had to let someone go; how did you handle it?"

The Manager Pitfalls

Pitfall 1: Micromanagement

You tell people how instead of what.
Fix: Set goals, let them figure out execution.

Pitfall 2: Avoiding Hard Conversations

Performance issues don't get addressed.
Fix: Have 1-on-1, be kind, be clear, be firm.

Pitfall 3: Playing Favorites

Someone gets more interesting work because you like them.
Fix: Fairness over likability.

Pitfall 4: Coding When You Should Be Managing

You get distracted shipping features instead of developing people.
Fix: Your job is people, not features. Delegate coding.

Pitfall 5: Burning Out

People problems are emotionally taxing.
Fix: Get support (manager, coach, peers). Take vacation.

Compensation at Manager

Typical FAANG-adjacent (2026): - Base: $180–280K - Bonus: 20–30% - Stock: $100–200K/year - Total: $250–450K

Similar to Senior IC, often slightly lower.

Books to Read as Manager

  1. An Elegant Puzzle: Systems of Engineering Management — foundational
  2. Radical Candor — care personally, challenge directly
  3. The High Growth Handbook — practical guide
  4. The First 90 Days — onboarding playbook
  5. Good to Great — building great orgs
Can I go back to engineering after being a manager?

Yes, but it's harder. You'll likely be Senior Engineer, not Senior+. Doable if you want it.

How many direct reports should I have?

5–8 is ideal. 10+ gets hard. Less than 5 is underutilized.

When should I try management?

When you love mentoring and want to scale impact through people. Not because it's "next" or sounds prestigious.

Next: Director of Engineering or Tech Lead.