AI for your role

AI for Staff Engineers

Spend less time on the mechanical work and more on the decisions that matter.

Get the Staff Engineer brief
The shift

How AI is changing the Staff Engineer role

In 2026, AI handles much of the first-draft work a Staff Engineer used to do by hand: reading large codebases, summarizing design docs, drafting RFCs, and triaging incidents. It speeds up code review by flagging risky changes and suggesting tests, and it pulls together context across services so you can reason about system behavior faster. The role shifts toward judgment, trade-off analysis, and steering teams, with AI doing the gathering and drafting.

What AI can take off your plate

  • Drafting first versions of RFCs, design docs, and postmortems from rough notes
  • Tracing how a feature works across a large or unfamiliar codebase
  • Generating unit tests and catching obvious issues in code review
  • Summarizing long design threads and meetings into decisions and open questions
  • Writing migration scripts and repetitive refactors across many files

What stays distinctly human

  • Deciding which trade-offs are acceptable given business context and timelines
  • Building trust and alignment across teams with competing priorities
  • Setting technical direction and knowing which problems are worth solving
  • Mentoring engineers and giving feedback that accounts for their growth
  • Owning the consequences of architectural bets that play out over years
Tools

Five AI tools for Staff Engineers

GitHub Copilot
A Staff Engineer uses it to scaffold boilerplate, write tests, and get inline suggestions while reviewing or refactoring large modules.
Try it →
Cursor
Used to navigate and refactor across an unfamiliar codebase by asking questions about how components connect and making multi-file edits.
Try it →
Claude
A Staff Engineer drafts and pressure-tests design docs and RFCs, asking it to argue against a proposed architecture before review.
Try it →
Sourcegraph Cody
Used to search and understand a large monorepo, tracing how a function or API is used across many services.
Try it →
Notion AI
A Staff Engineer summarizes long design threads and meeting notes into decisions, owners, and open questions for the team.
Try it →
Prompts

Five prompts to try today

Paste these into Claude or ChatGPT and replace the bracketed parts with your own details.

1. Design review critique
You are a skeptical senior reviewer. Here is a design doc for [system/feature]: [paste]. List the three weakest assumptions, the failure modes under [scale/load condition], and questions I should ask the author before approving.
2. Codebase onboarding
Explain how [feature/request flow] works in this codebase. Trace it from [entry point] to [data store], list the key files and functions involved, and note any surprising indirection or coupling.
3. Trade-off analysis
Compare [option A] versus [option B] for [problem] given constraints: [latency, cost, team size, deadline]. Give a table of trade-offs and a recommendation with the conditions under which it would change.
4. Incident summary
Here are logs, timeline, and chat from an incident: [paste]. Write a blameless postmortem draft with timeline, root cause, contributing factors, and concrete action items with suggested owners.
5. RFC first draft
Draft an RFC for [proposal]. Include problem statement, goals and non-goals, proposed approach, alternatives considered, migration plan, and risks. Keep it under [length] and flag where I need real numbers.
The playbook

Every AI play for Staff Engineers

The full library of tools, prompts, and tricks for your role — updated every week. Tap any card for a step-by-step walkthrough and examples.

✦  New tools, prompts, and tricks are added every week — and go straight to subscribers in their morning brief. Skip the scrolling and get yours delivered free. Get my free brief →
Loading the library…

A day in your inbox

This is the kind of brief a Staff Engineer gets, every weekday morning.
Monday morning
✦ Personalized for: Staff Engineer
Today's Tool
Use Cody to map an unfamiliar service
Point Sourcegraph Cody at the repo and ask how a request flows from the API edge to the database. It surfaces the files and call paths so you can review a design without reading everything first.
👍 More like this·👎 Less like this·★ Save
Today's Prompt
Make the AI argue against your design
Paste your design doc and ask it to take the position of a skeptical reviewer who wants to reject it. The objections it raises are the ones your real reviewers will raise, so you can address them early.
👍 More like this·👎 Less like this·★ Save
Today's Trick
Ask for the conditions that flip a decision
When weighing two options, ask the AI not just for a recommendation but for what would have to be true for the other option to win. This keeps the choice tied to assumptions you can revisit later.
👍 More like this·👎 Less like this·★ Save
Today’s three are just the start — go deeper on your role.
Browse all playbooks →

Get the Staff Engineer brief

One AI tool, one prompt, and one trick for Staff Engineers, every weekday morning. Free.

You’re in! We just emailed your first brief — it should land in a minute. Add [email protected] to your contacts so it never hits spam.
Free forever. Unsubscribe anytime. We use your role only to personalize your brief.