Topic
Engineering Leadership
Engineering leadership is the discipline of designing the team structures, delivery systems, and decision processes that let an engineering organisation scale beyond what one person can manage.
Engineering leadership is the discipline of designing team structures, delivery systems, and decision processes so an engineering organisation can scale beyond what one person can manage. It is architecture applied to people and process.
The playbook that works for ten engineers breaks at thirty and collapses at fifty. Not because the people change, but because communication overhead grows faster than headcount, and the structures that made a small team fast: everyone in one channel, one person holding the whole system in their head: become the bottleneck.
I lead a team of 20+ engineers across ERP development, full-stack engineering, integration architecture, and technical analysis, spanning internal staff and external partner teams in different timezones. Most of the hard problems are not technical. They are about who decides what, how work is sequenced, and what happens when two teams need the same thing in the same sprint.
I write about this from inside it, including the parts that went badly. I moved from Senior Technical Business Analyst to Head of Engineering & Architecture in about two years, and I am building toward a CTO role, so this is a record made in progress, not a retrospective from the other side.
Key concepts
The vocabulary that comes up most in this area, defined.
| Term | Definition |
|---|---|
| Team topologies | Organising teams by the type of work they own: stream-aligned, platform, enabling, complicated-subsystem: rather than by technology. |
| DORA metrics | Deployment frequency, lead time for changes, change failure rate, and time to restore. The four measures that correlate with delivery performance. |
| Communication overhead | The coordination cost that grows with the square of team size. The reason a structure that works at ten fails at thirty. |
| Career ladder | An explicit statement of what each level requires. Without one, promotion decisions are relitigated from scratch every cycle. |
| IC track | A senior individual-contributor path with parity to management, so technical depth is not taxed by requiring a move into people leadership. |
Articles on engineering leadership
No articles on this topic yet. The first ones are in progress. Leave your email and I'll let you know when they land.
Frequently asked questions
Informal coordination, single-owner knowledge, and unstructured prioritisation. All three work at ten people and fail by thirty, because coordination cost grows faster than headcount.
Do the work of the role before you hold it: take responsibility for outcomes beyond your own code, make decisions others can follow, and build the systems that let the team operate without you. The title follows the work.
Sets technical direction, owns the architecture of the platform, structures teams around the work, and translates technology decisions into commercial terms for executives. Part architect, part organisational designer.
When the team can no longer hold one shared context: typically past eight to ten engineers, or when two workstreams have different cadences and stakeholders. Split along ownership boundaries, not technologies.
The four DORA metrics: deployment frequency, lead time for changes, change failure rate, and time to restore service: plus a qualitative read on whether engineers can ship without asking permission.