Should engineering managers write code?

First-line EMs with 4-6 reports: 10-30% of time. Directors: 0-10%. VPs and above: 0%. EMs who insist on 50%+ coding time typically underinvest in their reports; EMs who go 0% at the first-line level typically lose team respect. Both failures are common.

IC track vs management track?

Both must exist as legitimate senior paths (Staff, Principal, Distinguished Engineer). If management is the only path to seniority, you push your best engineers into management they don't want and lose them within 2 years. Compensation parity between senior IC and management levels is table-stakes at Series B and above.

How large should teams be?

Standard rule: 5-9 engineers per team (two-pizza teams). Below 5, undersized for meaningful ownership. Above 9, coordination overhead dominates and the team splits itself informally. Teams too large is the more common failure at growth-stage startups.

Engineering Management for Startups: Structure, Cadence

Engineering management is where velocity and quality either compound or degrade.

Engineering Management: How to Build the Function That Determines Whether You Ship

Engineering management is the discipline of turning individual engineers into a compounding system that ships high-quality software. Below 10 engineers, a technical founder can hold the function together informally. Between 10 and 100, deliberate management structure is the difference between accelerating and stalling. The pattern that fails: hiring engineers faster than you build the management practices to support them, and discovering at ~30 engineers that velocity has decreased despite the team doubling.

The first engineering manager

Signals it's time: 6-10 engineers reporting to the CTO, the CTO is spending >50% of time on people rather than product, engineers are asking for more direction than they're getting. First EM profile: senior engineer with prior EM experience OR an internal senior engineer with strong communication skills who wants to try management. Team size: 4-6 direct reports. Reports to CTO/VP Eng. Explicit: still writes code (10-30% of time) at this stage. Managers who go 0% technical too early lose credibility with their team.

Structure as you scale

10-25 engineers: 2-3 EMs reporting to CTO. 25-60: EMs plus a Director layer, possibly team leads. 60-150: multiple Directors, functional VPs (Platform, Product Eng), tech leads on each team. Above 150: staff engineering track, principal engineers, engineering operations. The failure mode is adding management layers preemptively — every layer of management costs velocity through information degradation. Add layers when spans-of-control break, not before.

Cadence

Weekly EM 1:1s with each report (30 min, protected). Weekly team standup (15 min, blockers only). Biweekly sprint planning (60 min). Biweekly sprint retro (30 min). Monthly EM sync with peer EMs and VP (60 min). Quarterly planning (2-3 days across the whole eng org). Skip any of these and you'll notice within a quarter; skip the retros and quality degrades within two.

What to measure

DORA metrics (deployment frequency, lead time for changes, change failure rate, time to restore service) as team health indicators, not individual metrics. Team-level throughput trends over quarters, not sprints. Onboarding time (days to first PR merged, days to on-call). Retention and internal transfer rates. Explicit anti-metrics: lines of code, hours worked, tickets closed. Measuring these produces the metric and destroys what actually matters.

The performance conversation engineering managers avoid

The under-performer who's a nice person, well-liked, been there a while, and delivering 40% of what peers deliver. Engineering culture is often conflict-averse; EMs delay this conversation for quarters. The cost: the rest of the team notices, standards degrade, top performers leave. Rule: performance-manage inside a quarter of noticing, or the team will performance-manage you by leaving. This is the single most common EM failure at growing startups.

Frequently asked questions

Should engineering managers write code?: First-line EMs with 4-6 reports: 10-30% of time. Directors: 0-10%. VPs and above: 0%. EMs who insist on 50%+ coding time typically underinvest in their reports; EMs who go 0% at the first-line level typically lose team respect. Both failures are common.
IC track vs management track?: Both must exist as legitimate senior paths (Staff, Principal, Distinguished Engineer). If management is the only path to seniority, you push your best engineers into management they don't want and lose them within 2 years. Compensation parity between senior IC and management levels is table-stakes at Series B and above.
How large should teams be?: Standard rule: 5-9 engineers per team (two-pizza teams). Below 5, undersized for meaningful ownership. Above 9, coordination overhead dominates and the team splits itself informally. Teams too large is the more common failure at growth-stage startups.

Related fundraising guides (40)

Investor directory · Fundraising library · Articles A–Z · Company funding database