Interview Primer — Staff

What to prioritize

Staff is judged on leverage, not output.

They probe for

Your archetype & scope
Framing ambiguous problems
Influence without authority
Org-level leverage stories

Bring evidence of

A cross-team initiative
A costly-to-reverse call
A project you killed/cut
Engineers you grew

1Staff archetypes & scope

0/4▶

Staff isn't "senior+1". Loops assess which archetype you are and whether you drive impact beyond your own code.

Know your shape

The archetypes: Tech Lead, Architect, Solver, Right-Hand — know which one you're interviewing as.

StaffEng — Archetypes.

Scope & impact: how your work moved an org/product metric, not just shipped a feature.

StaffEng — stories.

Your "staff project": the ambiguous, high-leverage effort you drove across teams.

Will Larson — Staff-plus.

Sponsorship vs mentorship; creating leverage through others.

Lara Hogan — Sponsorship.

2Technical vision & strategy

0/4▶

Staff engineers set direction. Expect "where should this system be in two years?" questions.

Set direction

Writing a technical strategy / vision doc that others can execute.

Will Larson — Eng strategy.

Reversible vs one-way-door decisions; sequencing a multi-quarter bet.

Werner Vogels — one-way doors.

Identifying leverage: what to build, buy, or kill.

StaffEng.

Balancing delivery now vs platform investment for later.

Fowler — Tech debt.

3Ambiguous system design

0/4▶

Prompts are deliberately open ("design our platform"). The skill is framing the problem and choosing what not to build.

Lead the room

Drive a staff-level system design: org-scale architecture, migrations, cost, DR.

Resources — System Design (Staff).

Frame vague prompts: define success, constraints, and non-goals first.

System Design Primer.

Multi-region, consistency at scale, cell-based architecture, blast radius.

AWS — Cell-based.

Cost as a design constraint; $ per request/storage/egress.

Well-Architected — Cost.

4Migrations & evolution

0/3▶

The hardest real work is changing a live system safely. Staff engineers own these.

Change without breaking

Strangler fig — old and new side by side, migrate consumers incrementally.

Strangler Fig.

Zero-downtime schema changes — expand → backfill → dual-write → switch → contract.

Stripe — Online migrations.

Deprecating a service used by many teams: comms, timelines, guardrails.

Strangler Fig.

5Influence & communication

0/4▶

At staff, you lead without authority. Executive communication and alignment are graded as hard skills.

Lead without authority

Aligning multiple teams; handling a senior stakeholder who disagrees.

Will Larson — Irrational Exuberance.

Executive communication: brief up, tailor detail to audience, lead with the decision.

StaffEng — Communicating.

Writing that scales: RFCs, design docs, strategy docs; getting buy-in async.

Design docs at Google.

Running a design review that reaches a decision, not just discussion.

StaffEng.

6Reliability & org leadership

0/3▶

You set the reliability strategy, not just the retry policy.

Own reliability at scale

SLOs & error budgets as a cross-team planning tool; when to freeze features.

SRE Workbook — Error budgets.

Incident response & blameless postmortems; reducing MTTR.

SRE — Managing incidents.

Disaster recovery: RTO/RPO, failover drills, chaos testing.

Principles of Chaos.

7Behavioral at staff

0/5▶

Stories must show leverage and judgement: you changed how the org works, or made a costly-to-reverse call well.

Leverage stories

A time you killed or de-scoped a project — judgement about what NOT to do.

StaffEng — stories.

Draft answer

Shape — "We were building [thing]; I looked at [data/cost/usage] and argued to stop or cut it to [smaller scope]."

Why it's senior — you traded ego for impact and freed the team for higher-leverage work: "that redirected [N] engineers onto [what mattered]." Judgement about what not to build is the signal.

A cross-org initiative you drove despite competing priorities.

Behavioral guide.

Draft answer

Shape — "[N] teams needed to align on [standard/migration/platform]. I wrote the proposal, ran the review, and got buy-in by [prototype / data / addressing objections]."

Result — org-level: "adopted by [teams], which [measurable outcome]." Show you led without authority.

A high-stakes technical call under ambiguity, and how you de-risked it.

Will Larson.

Growing engineers into senior/staff — concrete outcomes.

StaffEng.

Disagreeing with a leader's direction and how you handled it.

Behavioral guide.