Staff / Principal Engineer
Staff and principal engineers rarely write the most code in the room — they write the documents that change what everyone else builds. RFCs, ADRs, technical strategy papers, and executive briefings must be clear, persuasive, and precisely scoped. This path builds the vocabulary and written communication skills to lead technical direction across an organisation, mentor engineers, and present architectural trade-offs to leadership.
Topics covered
- technical strategy
- RFC writing
- cross-org alignment
- mentoring vocabulary
- architecture decision records
- executive communication
Vocabulary spotlight
4 terms every Staff / Principal Engineer should know in English:
Request for Comments — an internal document that proposes a technical change and invites structured feedback from stakeholders
"I wrote an RFC for the migration to propose the approach and collect objections before we commit."
Architecture Decision Record — a short document capturing a significant design decision, its context, and the consequences
"We have an ADR explaining why we chose Postgres over MongoDB for this service."
A durable plan that aligns engineering decisions with business goals over a multi-year horizon
"The CTO asked me to write the technical strategy for our data platform for the next three years."
A large, ambiguous, high-impact piece of work that a staff engineer is expected to scope, drive, and deliver across teams
"Migrating our auth system to a shared service became my staff project for the year."
The defined boundaries of a technical initiative — what is included, what is not, and why
"Before we start, I want to align on technical scope so we do not accidentally sign up for a six-month project."
The ability to shape decisions and direction through persuasion and credibility rather than organisational power
"At staff level, most of your impact comes from influence without authority across teams you do not manage."
📚 Vocabulary Reference
Key terms organised by category for Staff / Principal Engineers:
Documents & Artefacts
Strategy
Influence & Leadership
Metrics & Communication
Recommended exercises
Real-world scenarios you'll practise
- Writing a company-wide RFC proposing a new data access layer, anticipating and pre-empting objections.
- Presenting architectural trade-offs to a CTO who has 15 minutes and wants the recommendation, not the full analysis.
- Facilitating an architecture review where two senior engineers disagree and the team is blocked.