Not all headcount is equal. Requesting the wrong type of engineer — even if approved — can be as damaging as not hiring at all. Before writing a business case, you must be precise about what kind of capacity you need.
Common Engineering Archetypes
Individual Contributor (IC) — Junior (L3–L4)
- Best for: Well-defined, repeatable work with clear acceptance criteria.
- Risk: Requires significant mentorship investment from senior engineers. Net-negative for 3–6 months.
- Cost: $80k–$130k fully-loaded.
Individual Contributor (IC) — Senior (L5–L6)
- Best for: Ambiguous, high-impact work that requires judgment and autonomy.
- Risk: Expensive. Hard to recruit. Will leave if the work is not challenging.
- Cost: $200k–$350k fully-loaded (including equity).
Staff / Principal Engineer (L7+)
- Best for: Cross-team technical strategy, architectural decisions, unblocking multiple teams.
- Risk: Very expensive. Requires organizational maturity to leverage effectively. Will be frustrated by bureaucracy.
- Cost: $350k–$600k+ fully-loaded.
Engineering Manager (EM)
- Best for: When a team exceeds 6–8 engineers and needs dedicated coordination, career development, and stakeholder management.
- Risk: Adding a manager to a small team creates overhead without proportional benefit. The rule of thumb: one EM per 6–8 ICs.
The Seniority Mix Problem
A common mistake is requesting all senior engineers because "we only want the best." In practice, a team of all seniors is expensive, creates ego conflicts, and leaves no one to do the well-defined execution work. A healthy team typically follows a pyramid structure: more junior and mid-level engineers doing execution work, fewer seniors setting direction, and one or two staff-level engineers handling cross-cutting concerns.