What Coding Agents Teach Us About the Future of Work
Software engineering is the first knowledge-work domain where agents deliver verifiable output. It previews what happens everywhere else.
Ask an engineering leader what changed in the last eighteen months and the answer is not that code got written faster. It is that the shape of the job moved. Engineers spend less time typing and more time describing what they want, reviewing what came back and deciding whether to trust it. The keyboard is still there. The centre of gravity is not.
Software went first for a structural reason. Code can be tested. An agent that changes ten files can run the suite, see what broke and fix it before a human ever looks. Version control makes every action reversible and every change reviewable. Most knowledge work has no equivalent: there is no test suite for a contract clause or a marketing plan. Where verification loops exist, agents thrive. Where they do not, agents drift.
What changed inside engineering teams
- Multi-file autonomous changes with test verification became routine rather than experimental.
- Code review load rose, and review quality became the limiting factor on throughput.
- Security teams started asking what credentials agents hold and what they can reach.
- Headcount plans began to be modelled around agent throughput rather than only hires.
- Junior roles shifted from producing code to supervising and validating it, which is harder to learn.
How an engineer's week is shifting. Writing code: 2023 45%, 2024 38%, 2025 28%, 2026 20%. Specifying & designing: 2023 15%, 2024 20%, 2025 26%, 2026 30%. Reviewing & verifying: 2023 15%, 2024 20%, 2025 28%, 2026 34%. Other: 2023 25%, 2024 22%, 2025 18%, 2026 16%.
The entry-level problem
The work that agents take first is the work juniors used to learn on. If the ladder's bottom rung disappears, organisations have to build a new one: structured supervision, explicit review training and deliberate exposure to problems agents get wrong. Companies that ignore this will find in five years that they have no mid-level engineers.
Where verification loops exist, agents thrive. Where they do not, agents drift.
What this previews for other professions
Finance has reconciliation and audit trails. Law has precedent and citation checking. Operations has policies and service levels. Each is a partial verification loop, and each is where agents are being deployed next. The playbook from engineering transfers: define the task precisely, give the agent a way to check its own work, make actions reversible, and put a human in the review seat.
What happens next?
- Verification tooling emerges for non-code domains, starting with finance and legal.
- Organisations formalise 'agent supervision' as a taught skill and a job level.
- Engineering headcount plans increasingly blend hires and agent capacity.
Related topics
Sources & references
- 01Developer tooling vendor documentation and usage disclosures — Frontier labs and developer platformsprimary
- 02Research on AI-assisted software engineering productivity — Academic and industry studies; see Sources pageresearch