Engineering will grow from 50 to 250 people in 18 months. How do you design the organization?

Short answer

Align teams to business domains (stream-aligned teams of 5–9), add platform and enabling teams to reduce cognitive load, define engineering management spans and staff/principal IC roles, establish career ladders and hiring processes that scale, adapt architecture to team boundaries, and keep communication and decision-making explicit as layers are added.

Detailed answer

  • Structure: domains (e.g. 5 product areas) each with 3–6 stream-aligned teams, a group product manager and an engineering director; platform group; enabling teams (security, SRE, data/AI).
  • Leadership: hire managers ahead of need; staff/principal engineers per domain for technical direction; architecture council.
  • Hiring: structured process, calibrated rubrics, recruiter capacity, onboarding program (first deploy within days).
  • Architecture: align services/modules to team ownership; avoid shared ownership hotspots.
  • Operating model: quarterly planning with OKRs, written decision records, all-hands and engineering reviews.
  • Culture: engineering principles, on-call fairness, career growth.

What the interviewer expects

Team Topologies-style thinking, Conway's law awareness, attention to leadership and hiring capacity.

Common mistakes to avoid

Hiring without onboarding capacity, too many teams on a monolith without boundaries, managers with 15+ reports.