Sign in Get started

The Engineering Manager Handbook (Development Manager) · Capstone Case Studies

Capstone: Plan Headcount and a Reorg for Doubling the Organisation

A 40-engineer product organisation must double in a year. Design the hiring plan, the team structure and the communication.

Scenario

Example company: you're the senior engineering manager for a 40-engineer product organisation (five teams). The company raised funding and wants 80 engineers in 12 months to deliver a new marketplace product while keeping the existing product growing.

Evidence

  • Today's teams: frontend (9), backend (11), mobile (7), data (6), platform (7). Most features need three or more teams.
  • Leadership: 2 engineering managers (one with 20 reports), 3 team leads.
  • Hiring data: last year, 6 hires; ~150 applicants per hire; onsite pass rate 30%; offer acceptance 70%; 10 weeks from opening to accepted offer.
  • Roadmap ask: marketplace MVP in 9 months, plus current roadmap continuing.

Deliverables

  1. A target team structure for month 12, and how you'd get there.
  2. A hiring plan by quarter, including managers and interviewer capacity.
  3. A realistic capacity view for the roadmap.
  4. How you'd communicate the reorganisation.

Hints

  • How many managers does an 80-person organisation need at six to eight reports each?
  • How do new hires ramp up, and who onboards them?
  • Should the marketplace team be built from new hires only?

Draft each deliverable below before revealing the model answer and rubric.

Further reading: Team Topologies key concepts · Sizing engineering teams

Deliverables

Target team structure and how to get there.

Model answer

About ten teams of six to eight: mostly stream-aligned teams by customer journey (e.g. buyer checkout, seller onboarding, listings, search, existing-product journeys), a platform team (deploy, observability, data infrastructure), and possibly a complicated-subsystem team for payments or search ranking. Get there by budding: move from layer teams to two or three stream-aligned pilots first, then grow experienced teams to eight to ten and split. Seed the marketplace teams with experienced engineers moving from existing teams, backfilled by hires.

Rubric

Look for: stream-aligned design (Conway's law), sizing of six to eight, budding rather than new-hire-only teams, and staged transition. Misses: one 'marketplace team' of 20 new hires.

Hiring plan by quarter, including managers and interviewer capacity.

Model answer

  • Managers first: ~10 teams need about 7–8 engineering managers plus team leads; hire or promote 3 managers in Q1 (the 20-report manager's span must be split immediately).
  • Engineers: ~40 hires → back-loaded 8 / 10 / 11 / 11 per quarter as onboarding capacity grows.
  • Funnel: at ~150 applicants per hire, ~6,000 applicants a year; with 30% onsite pass and 70% acceptance, ~190 onsite loops (~4 per week) — about 1,400 interviewer hours. Train 20+ interviewers, add recruiters and sourcers, and plan interview load as roadmap capacity.
  • Speed: cut the 10-week cycle with structured loops and fast decisions.

Rubric

Look for: managers before teams, realistic funnel maths, interviewer capacity and recruiting investment. Misses: hiring 10 engineers per quarter with no managers or interviewers planned.

A realistic capacity view for the roadmap.

Model answer

Effective capacity lags headcount: with ramp-up (roughly a quarter at low productivity and up to a year to full productivity) and onboarding plus interview drag on experienced engineers, a simple model of the 8 / 10 / 11 / 11 plan gives roughly today's capacity in Q1, about 10% more in Q2, and only about 50% more by Q4 — with headcount at 80, not double the output. Plan the marketplace MVP with a reduced scope and seeded experienced teams; keep the existing roadmap modest during the first two quarters; re-forecast quarterly from actual ramp-up data. Avoid adding people to late projects (Brooks's law).

Rubric

Look for: capacity modelled with ramp-up and drag, scope trade-offs for the MVP, and quarterly re-forecasting. Misses: assuming capacity doubles with headcount.

How do you communicate the reorganisation?

Model answer

Brief managers and leads first; tell engineers who change teams individually; then announce to the organisation the same day: what's changing (stream-aligned teams, phases and dates), why (features need too many teams; growth), what it means for each team, what isn't changing, and what's undecided. Hold a Q&A within a week, publish an FAQ, and repeat the plan at each phase. Offer people preferences for team moves where possible.

Rubric

Look for: sequencing, the why with evidence, individual conversations, honesty about uncertainty, and follow-up. Misses: a single all-hands announcement with no individual conversations.

Open in the app to mark lessons complete, take notes and track your progress.