The senior developer is the person a team turns to when the specification is ambiguous, the change is risky or nobody remembers why the system does what it does. When AI generates the first draft of most changes, three things that the team has relied on the senior for become more important and harder at once. Review becomes the place where a change is first understood by anyone but its generator. Design decisions become the main constraint on what may be generated. Knowledge of why the system is as it is becomes the one input that no assistant can retrieve from the repository. This chapter concerns D2 Design, D4 Prove and D5 Steward as they fall on the person with the most context: what the senior's work consists of, why review capacity becomes the bottleneck of AI-assisted delivery, how a role charter protects professional judgement without making the senior a veto, how seniors are made when the entry-level work that made them is done first by machines, and what changes for staff and principal engineers whose scope spans teams.
A senior developer is an experienced individual contributor whom the organisation trusts with ambiguous work, review of risky changes and the mentoring of others. Staff and principal engineer name roles whose scope extends beyond one team, to design, standards and technical direction across several. Organisations draw these lines differently. The tech lead and the engineering manager are the subject of Chapter 15, and the junior developer of Chapter 13.
Four jobs make up the senior's work, and they are worth separating because AI changes each differently. The senior reviews, mentors, takes technical decisions and keeps context. None of the four is mainly typing.
Primary topics explored
- The senior's work
- Leverage and the review bottleneck
- Professional judgement
- The pipeline of seniors
- Staff and principal engineers
- Across the degrees of delegation
About AI Developer
AI Developer is Book 12 of The Transformed Architecture. It takes the developer as its subject and asks what happens when AI is used broadly in software development: the five developer functions (frame, design, build, prove, steward), the delegation ladder and the Level 4 prohibitions, the stewardship principle (name, understand, revert), verification as the scarce skill, the junior pipeline, adoption and productivity as claims that need evidence, regulation (the AI Act, the Cyber Resilience Act, the Product Liability Directive, NIS 2, DORA, the GDPR), ethics, intellectual property and sovereignty in the toolchain, and the developer as a person, for European enterprises and public authorities.
It builds on the conclusions of Architecture as Code, AI Governance, AI Platform and Security, AI Red Team, AI Threat, The Transformed Security Architect, AI Boss, AI Blue, AI Purple, AI Operations and AI Leader.
developers at every level, tech leads and engineering managers, architects, platform engineers, site reliability engineers and testers, product owners and designers, leaders who decide on developer tooling, heads of public-sector IT and procurement, works councils and unions, educators, and supervisors and auditors.
Gunnar Nordqvist
Conceived, directed and published the books of The Transformed Architecture.
Continue with the full chapter
Chapter 14: The Senior Developer, Staff and Principal Engineer in AI Developer gives the detailed explanations, practical examples and implementation patterns behind this summary.
This whitepaper belongs to “Developer Roles Across the Organisation” and is one of 37 drawn from the manuscript.