Team Design for Engineering Managers
Team design is how engineering work and people are organised into teams. Team topologies describes patterns such as stream-aligned, platform, enabling and complicated-subsystem teams, clear ownership of services reduces handoffs, and remote or hybrid work needs deliberate communication habits and written decisions.
Stage: Hiring and Teams · Part of the Engineering Manager roadmap · Last reviewed 19 November 2026
What to learn in Team Design
- Describe the four team types in Team Topologies and when each fits
- Assign clear ownership of services and code so incidents have an obvious responder
- Size teams to keep cognitive load manageable and communication paths short
- Set remote and hybrid norms for meetings, documentation and overlap hours
- Spot when Conway's law shows up in a system and adjust the team structure
Team Design interview questions
What is Conway's law?
It states that organisations produce system designs that mirror their communication structures. If three teams build a compiler, you get a three-pass compiler. Managers use it deliberately by shaping teams around the architecture they want, sometimes called the inverse Conway manoeuvre.
What is a stream-aligned team?
In Team Topologies it is a team aligned to a flow of work from a business domain, such as a product or user journey, able to deliver changes end to end with minimal dependence on other teams. Other team types exist mainly to support such teams.
Where Team Design fits in the Engineering Manager roadmap
Team Design belongs to the Hiring and Teams stage (advanced level), which takes about 5 hours. Build the right team.
Other units in this stage
Back to the full Engineering Manager roadmap