Engineering Organization Design and Hiring
Team Topologies (stream-aligned, platform, enabling, complicated-subsystem), Conway's law, team sizing, career ladders, hiring strategy and scaling from 20 to 500 engineers.
Executive explanation
Software architecture mirrors the communication structure of the organization (Conway's law). Org design is therefore an architecture decision: design teams around the system you want, with clear ownership and minimal hand-offs.
Team Topologies (Skelton and Pais)
| Team type | Purpose |
|---|---|
| Stream-aligned | Owns a value stream/product end to end (most teams) |
| Platform | Provides internal services that reduce stream teams' cognitive load |
| Enabling | Helps teams adopt new capabilities (e.g. SRE, security, AI coaching) temporarily |
| Complicated-subsystem | Owns a part requiring deep specialist knowledge (e.g. pricing engine, ML ranking) |
Interaction modes: collaboration, X-as-a-service, facilitating.
flowchart TB S1[Stream: Checkout] --> P[Platform: cloud, CI/CD, observability] S2[Stream: Search & discovery] --> P S3[Stream: Seller tools] --> P S2 --> CS[Complicated subsystem: ranking ML] E[Enabling: security & SRE] -. facilitates .-> S1 & S2 & S3
Business scenario
A scale-up grows from 40 to 200 engineers in two years. Teams are organized by technology (frontend, backend, QA, DBA), so every feature needs four teams; lead time is 6 weeks.
Changes: cross-functional stream-aligned teams of 5–9 per product area, a platform team, embedded QA practices, product managers per team, engineering managers with 6–8 reports, staff/principal engineers for cross-team technical leadership, clear career ladder with parallel IC and management tracks.
Hiring strategy
- Hire for the capabilities in the strategy (e.g. data/ML, platform) and for leadership capacity ahead of growth.
- Structured interviews with job-relevant exercises and calibrated rubrics.
- Balance seniority (avoid all-junior or all-senior teams); invest in onboarding (time to first production change as a metric).
- Location strategy: hubs vs remote; consider talent markets and time zones.
CTO interview questions and model answers
How do you structure engineering for a company moving to microservices?
Align teams to bounded contexts/value streams first, give each team ownership of its services and data, create a platform team to provide paved roads, and avoid reorganizing more often than every 12–18 months unless necessary.
What does a good engineering career ladder include?
Levels with clear expectations across technical scope, impact, collaboration and leadership; parallel IC and management tracks up to senior levels (staff/principal/distinguished); promotion processes calibrated across teams.