Example · Senior Software Engineer / Tech Lead
75% of your week as a senior software engineer is still yours.
AI agents now write much of the routine code. Reviewing it and signing off before it ships stays with you.
Make my planA typical week at the middle pace. Your plan uses your own tasks.
Are senior software engineers safe from AI?
In a typical week at the middle pace, 55% of this work needs your judgment and 20% is work you do using AI. AI could do about 25%. Routine code now comes from agents. Google's CEO said in April 2026 that 75% of the company's new code is AI-generated, and Sonar's January 2026 survey of 1,100 developers put the share of committed code at 42%.
Read more
That is the part of your week a model already does well: well-specified feature work, tests, refactors and PR descriptions. It adds up to about 25% of your week.
The rest holds, and some of it is getting heavier. After a run of outages in early 2026, Amazon told junior and mid-level engineers they would need a senior engineer to sign off on AI-assisted changes (Financial Times, March 10, 2026; Amazon disputes that AI caused the outages). New Relic's 2026 survey found 86% of tech leaders saying senior staff spend more time fixing code. Your bigger risk is a layoff round, or two years as the unpaid bottleneck for other people's agents. The plan turns review from a pile into a policy with your name on it.
The week, task by task
Who does each hour of a typical 40-hour week.
See every task
Needs your judgment.
- Architecture and technical direction: deciding, refusing, sequencing12%
- Incident command, on-call escalation, postmortems10%
- Debugging production when the cause is unclear8%
- Mentoring, pairing, growing reviewers8%
- + 3 smaller tasks17%
AI does the slow parts. You still own it.
- Drafting design docs and RFCs: options, tradeoffs, diagrams14%
- First-pass code review: style, obvious bugs, missing tests6%
AI could do most of it.
- Writing feature code on well-specified work, including directing an agent through it14%
- Tests, boilerplate, mechanical refactors, dependency bumps6%
- PR descriptions, ticket updates, status notes, routine docs5%
Why some tasks still need a person
Deciding the architecture: what to build, what to refuse, what has to stay reversible
This takes context and accountability. The tradeoffs depend on history, team skill and money nobody wrote down, and a wrong call shows up a year later, which makes it expensive to check.
Signing off on risky changes: live-data migrations, auth, money movement
Someone has to answer for these changes. Companies are formalizing that a senior approves AI-assisted changes. The protection is delegated by policy, so it holds inside the company but can be moved by a reorg.
Leading the incident and owning the postmortem
This takes context, and you hold the accountability informally. You know which graph lies at 2 a.m., and the organization needs one name on the timeline.
Finding the cause when it is unclear
This takes context. Agents read logs fast, but they don't know that a job double-runs after a failover, or which alert has been noisy since the last migration.
Growing the people behind you
This rests on relationships. Someone has to train the next reviewer, and an agent can't sit with a nervous engineer through their first incident.
Good to know
What is hard about this field, and what you can do about it.
The hard truth
More of your week will go to checking code.
AI writes a lot of code that is almost right. Someone has to catch the almost, and often that is you.
Sources (2)
- 66% of developers named 'AI solutions that are almost right, but not quite' as a frustration, the most cited. Stack Overflow 2025 Developer Survey, 2025-07
- 45% say debugging AI-generated code is more time-consuming. Stack Overflow 2025 Developer Survey, 2025-07
What's next for a tech lead?
Plan A is the best move inside the work you do now.
Grow in the job you have
The main focus. Most weekly sessions build toward it.
- Each week
- 4 sessions
- Ready in
- About 3 months
Why it fits
Why you. You already review the risky changes and carry the pager, so you know where agent output fails in your system.
The gap. You need a failure rate split by agent-assisted and other changes, a written review contract, and evidence that it changed something.
The trade-off. It makes you the official reviewer, which can mean more review at first. If the policy later moves into automated gates, the title can go with it.
2 other moves that fit
- Forward deployed or applied AI engineerReady in about 6 to 12 months
- Engineering managerReady in about one review cycle
What's a plan B for senior engineers?
Plan B is meant to be different from this job. It was picked because skills from this role carry over.
Get ready for a new kind of job
A second option. A newer job AI is creating that these skills already fit.
You already set reliability targets, review risky changes and lead incidents, and this role applies the same work to agents.
- Each week
- 1 session
- Outlook
- Hiring now
- Pay
- $200K to $485K a yearThree staff and principal engineer postings, Aug to Sept 2026; the top end is AI lab pay.
2 other options
- AI evaluation specialistYour code review judgment is exactly what turns into test sets and rubrics that say whether an AI system is ready to ship.
- Developer AI enablement leadYou already write your team's review rules for agent code and coach engineers through them, which is this job across more teams.
In your own plan you can switch to any of the 47 roles.
The 13 weeks
Small steps that add up. One plan for both: most sessions build Plan A, one a week builds Plan B.
By week 13 you will have
AFor Plan A
- A review contract and PR template your team uses
- Failure rates split by agent-assisted and other changes
- A memo asking for ownership of change safety
BAnd for Plan B
- A regression incident report
- A published agent reliability write-up for your portfolio
- 1Measure your week
- 2Draft a review contract
- 3Set terms for agent PRs
- 4Count agent failures
You finish withA one-paragraph draft note to your manager
- 5Start a decision log
- 6Practice incident response
- 7Train the next reviewer
- 8Write down hidden knowledge
You finish withA before-and-after comparison of agent output
- 9Work across teams
- 10Check the job market
- 11Share the work
- 12Make your ask
- 13Decide your next move
You finish withOne application with your write-up attached
Three courses from the plan
- Site Reliability Engineering, chapters 4 (Service Level Objectives), 11 (Being On-Call) and 15 (Postmortem Culture)Google · Free online
Yes, for Weeks 6 and 10.
- StaffEng guides: "Manage technical quality" and "Writing engineering strategy"staffeng.com · Free
Yes. Read those two guides only.
- State of AI-assisted Software Development 2025DORA (Google Cloud) · Free download (form required)
Yes, for framing the Week 12 memo.
Checked 2026-10-15.
The fuller picture
Risks beyond AI: highLayoff and offshoring risk
Layoff rounds and offshore engineering centers have moved more senior seats in 2026 than coding agents have. Software postings are well below their 2020 level, tech cuts are running ahead of last year, and US companies keep opening engineering centers in India. Being senior helps, since most of the postings that remain ask for experience, but it doesn't stop a round from reaching your team.
Where this could be wrong
- Approving changes could become automated. If automated review gets good enough that a CI gate, the automated check before merge, can sign off, the sign-off role shrinks faster than we scored it.
- Shares assume a tech lead at a product company. At an agency or consultancy, feature work is a bigger share and so is exposure.
- The 75% figure is a CEO's claim, and Semafor noted the timeframes are hard to verify. Amazon disputes the reporting on what caused its outages.
- We rate layoffs above the AI risk based on 2026 cut counts and posting data. If funding loosens quickly, that risk falls faster than the AI one.
Also matched: senior software engineer, tech lead, staff software engineer. Research checked 2026-10-15. Page updated .