Top 7 Org design Interview Questions
Browse 7 real-world technical and behavioral interview questions about Org design. Review scenarios, edge cases, and architectural best practices.
Your managers each have twelve reports and nobody is sure who owns what. Redesign the organisation.
Fix ownership before span of control. Map every service to one owning team, cut teams around what they can ship alone, then size management to fit, adding a layer only if your own span demands it. Price the new manager roles, move people in waves, and involve HR early, as obligations vary by country.
You must reduce the engineering organisation by fifteen percent. How do you decide, and how do you lead the people who stay?
In layoffs, decide what work stops before which roles go, apply criteria agreed with HR and legal because the process varies by country, and never start from names. Tell people individually and with dignity, then cut the roadmap to match the smaller team so those who stay do not carry the same work.
Take-home: our engineering managers each have twelve reports and nobody is sure who owns what. Send us a written org design with the before, the after and how you would get there.
A strong written org design starts from an ownership map, cuts teams around product domains a team can ship alone, fixes span of control without moving the overload up a layer, and staffs every new manager seat by name or by hire. Worked below: 96 engineers, 8 overloaded managers becoming 15, moved over 16 weeks.
Two departments share ownership of a critical service and blame each other after every incident. How do you fix it?
Shared service ownership means nobody is accountable, so the blame is a symptom of structure. Give one team ownership with matching authority, make the other department a customer with an interface and an SLO, write incident management and escalation down, and have both department heads visibly back the change.
When do you create a platform team, and how do you stop it becoming the bottleneck it was meant to remove?
Create a platform team when several stream-aligned teams keep solving the same undifferentiated problem and it measurably slows them. Stop it becoming a bottleneck by running it as a product with real users, making self-service the standard, keeping adoption voluntary, and measuring the waiting it removes.
How do you execute the Inverse Conway Maneuver on a 200-person engineering org that accidentally built a distributed monolith mirroring their dysfunctional silos?
A pragmatic guide to dismantling component teams, breaking database monoliths, and surviving the political fallout of organizational restructuring. Use this engineering leadership answer to show the decision, trade-off, and evidence rather than a memorised definition. It also connects org design to the point an interviewer is testing.
You have twenty-five engineers in three teams and almost every feature needs all three of them. You have been asked to re-cut the organisation. How would you do it, and what does the change itself cost?
Measure where the coupling actually is before moving anybody, then cut boundaries around what a team can release without waiting on another. Price the transition honestly, name what your design makes worse, and be willing to say the coupling is architectural and no org chart will fix it.