SeniorEngineerHandbook
title: Senior Engineer Competency Handbook type: technique created: 2026-05-21 last_updated: 2026-05-21 related: ["radar/techniques/StructuredPromptDrivenDevelopment", "radar/techniques/RequestForDiscussion"] sources: ["https://github.com/jordan-cutler/path-to-senior-engineer-handbook"] radar_quadrant: Techniques radar_ring: Assess radar_position: inner
A curated, structured resource map for progressing from mid-level to senior software engineer, organised by competency domain rather than technology stack.
The handbook (jordan-cutler/path-to-senior-engineer-handbook) organises resources across the core competency areas that differentiate senior from mid-level engineers:
| Domain | Focus |
|---|---|
| Technical skills | System design, architecture decisions, code quality |
| Communication | Writing, documentation, async collaboration, presentations |
| Execution | Estimation, project management, delivery under ambiguity |
| Leadership | Mentoring, code review culture, technical direction |
| Career navigation | Promotion processes, staff+ paths, levelling frameworks |
| Domain knowledge | Distributed systems, databases, observability, security |
Each section links to high-signal books, articles, talks, and courses — not a comprehensive list but a filtered set based on community consensus.
The handbook treats senior engineering as a set of learnable, definable competencies rather than an accumulation of years or a reward for technical output. This is a specific methodology: identify gaps across all domains, not just technical ones, and address them with targeted resources.
The communication and execution domains are consistently under-represented in technical reading lists but are the most common blocking factors for senior promotions in practice.
Several competency domains in the handbook overlap with blips already on the radar. Writing skills feed radar/techniques/RequestForDiscussion practice. Architecture knowledge is a prerequisite for meaningful radar/techniques/ArchitecturalDecisionRecords authorship. The competency map contextualises why these techniques exist.
Senior Engineer Competency Handbook sits in the Assess ring of the Techniques quadrant, at inner position. First studied via the GitHub repository (2023-11-27). The methodology of structured, domain-mapped competency development is the blip — the handbook is the primary reference resource for it. Inner position reflects zero setup cost (read and apply) and direct applicability to any engineer targeting a senior-level role or leading junior engineer development. Remaining gate is deliberate use of the competency map to identify and close a specific skill gap.
