Example · Software Developer (early career)

45% of your week as a software developer is still yours.

AI writes more of the routine code each year. Senior judgment on messy problems is what holds.

Make my planA typical week at the middle pace. Your plan uses your own tasks.

Is software engineering a dying career?

In a typical week at the middle pace, 23% of this work needs your judgment and 22% is work you do using AI. AI could do about 55%. If the parts of the job you find hardest are vague asks from internal users and 2 a.m. data mysteries on call, those are the two most durable parts of your job. If watching an agent do your afternoon in twenty minutes worries you, that concern is fair too, and it applies to about 56% of your week.

Read more

Both are true at once.

Anthropic's March 2026 labor-market paper puts computer programmers at the top of all occupations for observed AI exposure, at 75% task coverage. Stanford's "Canaries" data through June 2026 shows employment of 22-to-25-year-olds in exposed occupations 19% below trend, driven by reduced hiring, not layoffs. If you are early in your career, you are in that cohort. The exposure depends on which kind of coding. Well-specified tickets in a codebase the model can read are the most exposed. Your job has a large slice of that and a smaller slice no model can do without you: the parts in people's heads, in production data, and in who signs off. The plan moves your week from the first slice to the second in 90 days.

The week, task by task

Who does each hour of a typical 40-hour week.

See every task
You23% · 9 hours

Needs your judgment.

  • Schema changes and migrations on live customer data6%
  • Scoping and clarifying with product and internal users6%
  • Standup, planning, retro6%
  • Supporting internal users, triage, "why does it do this?"5%
You using AI22% · 9 hours

AI does the slow parts. You still own it.

  • Production debugging, cause unclear10%
  • Reviewing teammates' PRs7%
  • Deploys, CI, dependency upgrades4%
AI55% · 22 hours

AI could do most of it.

  • Feature tickets with a clear spec in existing code22%
  • Bug fixes with reproduction steps15%
  • Tests for your own changes8%
  • Small UI changes (forms, tables, CSS)6%
  • + 1 smaller task5%
Why some tasks still need a person
You know how one tricky internal system actually works (permissions, billing, whatever people come to you about)

That knowledge lives in a few bug fixes, some chat threads and your head instead of the repo. A model reading the code sees what it does, but it misses why and which customers break if it changes.

You go find the person who filed the ticket and ask what they meant

Turning a vague ask into a precise one happens before any agent can start, and becomes more of the job as the build step gets cheap.

You have been on call through real incidents

You have seen the system fail in ways nobody wrote down. Saying "roll back now" carries accountability no tool will be handed soon.

You have been near live data migrations

Irreversible operations on customer data are where checking is hardest and someone must answer for the result. It is the least exposed corner of software work.

You know which internal users to trust about requirements

Time spent learning that "ops says X, means Y" is context a new hire (or a model) rebuilds slowly.

Good to know

What is hard about this field, and what you can do about it.

The hard truth

Your CS degree now comes with a harder first search.

A computer science degree used to feel like a sure thing. Right now, recent computer science and computer engineering grads are out of work more often than grads in almost any other major.

What you can doIf you have a developer job, build ownership there first. If you are still looking, plan for a longer search. Ship one project that real people use, apply beyond big tech, and treat internships and contract work as real first steps.
Sources (2)

What's next for a software developer?

Plan A is the best move inside the work you do now.

APlan A

Grow in the job you have

The main focus. Most weekly sessions build toward it.

Your next stepBecome the engineer of record for one internal system
Each week
4 sessions
Ready in
About 4 to 5 months
Why it fits

Why you. If you are already, informally, the one who knows a system, going from "the one who knows" to "the owner" is documentation, alert routing, and one conversation with your manager.

The gap. You have no system doc and have not run a migration end to end. Your manager may not see you as an owner yet, because you have never asked.

The trade-off. Internal tools are low-visibility. Ownership reaches a promo packet only if you make it visible, which is a separate skill. Owning a system also means owning its pages.

2 other moves that fit
  • Become the person who can say "this change is safe"Ready in about 6 to 9 months to be the default reviewer for agent prs
  • Move toward the customer boundary (implementation engineering)Ready in about 9 to 12 months

What's a plan B for developers?

Plan B is meant to be different from this job. It was picked because skills from this role carry over.

BPlan B

Get ready for a new kind of job

A second option. A newer job AI is creating that these skills already fit.

A job to aim forAI deployment strategist

Going to find the person who filed the ticket and asking what they meant is how AI deployments succeed with real customers.

Each week
1 session
Outlook
Hiring now
Pay
$100K to $290K a yearRange across five US postings in 2026, latest Oct 2026; some require Python.
2 other options
  • AI workflow builderYou can already code, so building and shipping working agent automations for an internal team is reachable within months.
  • AI evaluation specialistBeing on call through real incidents teaches you how systems fail, which is the instinct needed to test AI features before release.

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 runbook and invariants doc for your system
  • An agent guidelines file with before-and-after results
  • A one-page summary of what you own

BAnd for Plan B

  • A launch plan and a feedback memo
  • An AI deployment playbook for your portfolio
Month 1Weeks 1 to 4
  1. 1Measure your week
  2. 2Write down what you know
  3. 3Ask for ownership
  4. 4Pin down current behavior

You finish withA merged test PR and a new coverage number

Month 2Weeks 5 to 8
  1. 5Guide the coding agent
  2. 6Prepare for migrations
  3. 7Dashboard and user workarounds
  4. 8Run the migration

You finish withA count of real problems caught in review

Month 3Weeks 9 to 13
  1. 9Route alerts, clarify a ticket
  2. 10Postmortems and customers
  3. 11Gather your evidence
  4. 12Show what you own
  5. 13Decide your next step

You finish withA 90-day review and a plan for what comes next

Three courses from the plan
  • How to Do a Code Review (eng-practices)Google · Free

    Yes, week 2. These are the best two hours here.

  • PagerDuty Incident Response DocumentationPagerDuty · Free, Apache 2.0

    Yes, before your next on-call.

  • Site Reliability Engineering / SRE WorkbookGoogle · Free online

    Read selected chapters only.

Checked 2026-09-22.

The fuller picture

Risks beyond AI: moderateHiring-cycle risk

Interest rates and the 2022–23 hiring hangover explain part of the entry-level slowdown. That changes how urgent this is, but the direction stays the same. At a small company, ownership and promotion also depend on very few people. If they say no, the path changes.

Where this could be wrong
  • The shares are guesses until week 1. If your log shows much more feature work, more of your week is work AI can do, and becoming the person who can say a change is safe becomes urgent.
  • The scenario may be too slow or too fast. If agents get supervised production access within 18 months, the work AI only helps with today becomes work it can do alone, and owning a system is all that holds. If adoption stalls, you have five years, not three.
  • As its authors say, the Stanford figure is descriptive rather than causal. Some of the 19% is interest rates and the 2022–23 hiring hangover. That changes the urgency but keeps the direction.
  • We may be over-weighting the system you know best. If it is scheduled for a rewrite or a vendor replacement, own a different one instead. Ask in week 3.

This is an example. Your plan uses your own week.

Make my plan

Also matched: software developer, software engineer, junior developer. Research checked 2026-09-22. Page updated .