Example · DevOps / Platform Engineer
Your value is in answering for each production change.
25 of your 40 hours still need you
- 14 stay yours
- 11 faster with AI
- 15 tools could take
A typical week at the middle pace. Your plan uses your own tasks.
Is DevOps a dying career?
By our task-by-task count, 25 of a typical 40-hour week as a DevOps engineer still need a person. Tools could already take about 15 hours. A model already does 37% of your week well, and that is the part you were hired for. That includes the Terraform module from a ticket, the pipeline workflow, the runbook and the access request queue.
Read more
If you have let an AI agent draft a module, you have seen it. The tags and parameters come out cleaner than yours. You may also have seen it propose a security group open to the world.
That second part is now the core of the job. Someone has to read the plan before it applies and say go on a production change with their name on the approval record. Someone has to decide at 3 a.m. whether to roll back, and tell finance why the bill went up and what to do about it. The work the model does well is cheap to produce and expensive to get wrong, and you are the person who knows where the bodies are buried in those accounts. The night page and the access queue are often the things people in this role dread most. They are also the most protected things you do. This report helps you take charge of those two areas.
The hard truth
AI was supposed to cut your toil, and toil rose.
In Catchpoint's 2025 survey, toil rose for the first time in five years. More tools and faster changes can mean more to run and clean up.
Sources (2)
- Median time on operations work, often synonymous with toil, rose from 25% to 30%, the first rise in five years. Catchpoint, SRE Report 2025, 2025
- AI adoption still has a negative relationship with software delivery stability. Google Cloud, 2025 DORA Report, 2025-09
What stays yours
Deciding at 3 a.m. whether to roll back, fail over or wait
Someone must be reachable, authorized and willing to be wrong in public. An agent can propose a fix, but it cannot be paged, and no company yet lets one hold production write credentials unattended. The on-call rotation is the last place where a named human is required.
Approving a production change and being the name on the record
SOC 2 (a common security audit) has a change-management criterion (CC8.1). It requires that changes be authorized, tested and approved before they reach production, with evidence. Your auditors need a named approver. Today that is often your lead. The plan is about making it you.
Catching the open-to-the-world rule in a generated plan
A wrong infrastructure plan looks like a right one until the breach. The reviewer who reads the diff and knows what an open-to-the-world network range costs is the constraint on every infrastructure agent.
Knowing which cluster a service actually runs in, and why the dependency map is wrong
Past migrations, exceptions and "we'll fix it later" live in your head and nowhere else. A model can read the code, but it cannot know about the service that was moved by hand and never codified.
Explaining the bill and deciding what to do about it
The monthly cost number is read by finance. Rightsizing a cluster means knowing which workloads are latency-sensitive and which teams will object. A model can rank candidates, but a person has to choose and answer for it.
What's next for a DevOps or platform engineer?
Plan A is your best move inside the work you do now. Most sessions in the 13-week plan build toward it.
- A
Become the named production change and incident owner
Why it fits
Why you. If you already say "roll back" at 3 a.m. and already catch the open-to-the-world rule, a record of production changes and incidents handled is standing nobody else at your level has. The gap between what you do and what your title says is the smallest of the three moves.
The gap. Most teams have no written severity ladder. The approval record names your lead, and incident command falls to whoever is on call. There is usually no plan-review checklist and no automated policy check.
The trade-off. You become the person blamed, in writing, when a production change goes wrong. The dread is the same, but you have more authority on paper. You will also merge fewer modules for a quarter, and someone will count.
Other moves that fit
These are also good bets in this field. Read them if Plan A doesn't suit you.
Own the bill: the platform cost seat
Why it fits
Why you. If you are already the person who can explain why the bill went up, you are halfway there. The cost review is the one durable task where finance is the audience, and finance is where headcount decisions get made.
The gap. No monthly cost memo exists yet, and your lead presents to finance. Tagging is not good enough to tie spend to teams, and finance makes commitment decisions without engineering input.
The trade-off. Expect spreadsheets, and a quarter of being the person who tells squads to use less. It sits close to your lead's territory; if they want it, you need the change and incident owner move more than this. A company can still buy a FinOps (cloud cost management) tool. The plan makes that a worse deal than keeping you, though it is still possible.
The portable hedge: build a paper trail you can take with you
Why it fits
Why you. Incident write-ups, a change-risk standard and a cost memo are proof that travels. "Ran incident command, owned change approval under SOC 2 (a security audit standard), cut the bill" is a résumé line that gets interviews at any company whose product runs on a cloud.
The gap. You have no public proof of your work yet, and no idea what the market pays for a named incident or change owner.
The trade-off. Leaving resets the asset this report says protects you. Your first year anywhere new is your most exposed: context starts at zero and module-writing is all anyone can measure.
What's a plan B for DevOps engineers?
Plan B is a job AI is creating that these skills already fit. One session a week in the plan trains you for it, so it is ready if your job shrinks or you want a change.
BPlan B, picked for this role
Agent reliability and quality engineer
Answering for production changes and running incidents is the heart of this role, so shipping one agent workflow gets you most of the way.
Other options
AI cost and vendor analyst
Since you already own cloud cost and tagging, adding model and GPU spend to the bill you defend is a natural extension.
Developer AI enablement lead
Platform teams already shape how other engineers ship, and rolling out coding agents across your org is the proof this role asks for.
In your own plan you can switch to any of the 47 roles.
The first two weeks
The first 2 of 13 weeks. Most weeks have three sessions of 45, 60 and 90 minutes, plus one 40-minute Plan B session. In Weeks 4 and 8 your Friday on-call shift replaces the long session, so line those weeks up with your rotation, and Week 12 has no third session. By week 13 you'll have a plan-review checklist and severity ladder in use, a one-page memo with your ask for a Senior title, and a published write-up on agent reliability.
- Week 1: Measure your week
What you do
- ATrack one week of your work against the task list on this page. Write down roughly how many hours went to each task.
- APull the last 90 days of production changes. Count them, note who approved each one and count how many were rolled back.
- AReopen your last ten AI-drafted infrastructure plans, or draft ten now in a tool your security owner has approved. Sort each one as safe, needed a change or would have caused harm.
- BTake Anthropic's free AI Capabilities and Limitations course. For each limit, write one way an AI agent could break a deploy.
- Week 2: Check the rules
What you do
- AAsk your lead in writing which accounts and environments an AI agent may change, and who decided that.
- AFind who owns the change-management control, the written rule for approving changes. If you are audited under SOC 2, a common security audit, ask for last year's control description.
- ACompare the control text with what really happens during a production deploy.
- BTake AI Fluency: Framework & Foundations, a free Anthropic course. Write your own rules for what an agent may run and what needs a person.
Three courses from the plan
Checked 2026-10-11.
- AWS Certified DevOps Engineer - Professional (DOP-C02)AWS Training and Certification · $300
Not during the plan. It certifies the exposed rows. Sit it only if the postings you want ask for it three times.
- AWS Certified Solutions Architect - Associate (SAA-C03)AWS Training and Certification · $150
Only if you have no AWS cert at all and an HR screen needs one. It tests vocabulary more than judgment.
- HashiCorp Certified: Terraform Associate (004)HashiCorp · $70.50 plus tax; no free retake
It is cheap and harmless, though it won't protect your job. If you sit any exam, sit this one.
Risks beyond AI: moderateCost-center risk
Platform teams are an engineering cost center and were trimmed with everyone else in the 2023 tech layoffs. Pulling the other way, cloud spending keeps growing and the bill needs an owner. This risk does not outrank the AI risk for you, but it decides when a thin platform team gets thinner.
Where this could be wrong
- On-call may be more exposed than we scored. Our score assumes no vendor lets an agent roll back production unattended. If your company adopts automated rollback when a service misses its reliability target (its SLO) and trusts it, on-call becomes more exposed and the need for a person on the pager shrinks. The change and incident owner move then rests on change approval alone.
- We assumed the approval record names your lead. If a release manager or squad leads already sign and you only apply the change, the change and incident owner move is "join the approval," not "own it," and owning approvals protects you less.
- The access queue may already be on its way out. If your company adopts just-in-time access with automated approval, the access queue shrinks on its own and the access standard in Week 8 is moot. Spend that week on the cost memo instead.
- A staff engineer could take the change and incident owner move quickly. A senior engineer who already holds the agent's guidelines has a strong claim to it. If they want it, focus on the cost seat and the portable hedge.
Also matched: devops engineer, platform engineer, cloud engineer. Research checked 2026-10-11. Page updated .