Scale an Engineering Team from 5 to 20

Diagnose what breaks when you add headcount

2–3 weeks. The interviews take one week. Writing the document takes another. The most important bottleneck is usually the one that takes longest to name — build in time to sit with the findings before writing.

Design the team structure for 20 engineers

2–3 weeks. The design takes a week. The team presentation and incorporating feedback takes another. The design will change based on the presentation — budget time for a second draft.

Hire five engineers without lowering the bar

12–20 weeks depending on the hiring market and role. Five hires at an average 4-week process each. Running processes in parallel is required — sequential hiring takes too long at this stage.

Build a team that works when you are absent

2 weeks of absence plus 1 week of preparation and 1 week of documentation on return. The preparation week is not optional — a team that is not briefed on the authority matrix before you leave will default to waiting for you regardless of what the document says.

Deliver a major project through two sub-teams

8–16 weeks depending on project scope. This milestone cannot be manufactured — it requires a real project with real cross-team complexity. If no such project exists in your current roadmap, that is information about whether your team structure is working.