The Last 10%: Dario Amodei’s Vision for Engineers, Medicine and the AI-Native Enterprise

Artificial intelligence writing 90% of a company’s software sounds like the beginning of a mass layoff announcement. Anthropic CEO Dario Amodei sees it differently—at least initially. In his view, automating most of a job does not immediately eliminate the worker. It creates a productivity surge in which humans concentrate their time on the small portion the machine still cannot complete.

That distinction sits at the center of Amodei’s increasingly provocative argument about the future of work.

When Claude generates most of the code, engineers do not necessarily disappear. They become reviewers, architects, product designers, security investigators and managers of increasingly capable digital workers. The human contribution shrinks as a percentage of the production process, but the output of each person can rise dramatically.

The more unsettling question is what happens when AI masters the final 10%.

Amodei’s answer reaches far beyond software development. He imagines artificial intelligence becoming the cognitive core of companies, helping organizations reason, coordinate and execute at a level that makes the modern enterprise resemble a form of collective superintelligence.

It is an ambitious vision combining extraordinary productivity, accelerated medical discovery and potentially severe disruption to white-collar employment.

Writing Code Is Not the Same as Doing the Job

The percentage of code written by AI has become one of the most widely repeated statistics in the technology industry.

Amodei has said that Claude now produces most of the code written by some engineers inside Anthropic. In parts of the company, developers may no longer type significant amounts of code manually. They describe the intended feature, direct the model, inspect its output, test the implementation and intervene when something goes wrong.

This is a fundamental change in the interface between an engineer and a computer.

Traditional software development requires humans to translate ideas into precise instructions written in programming languages. AI coding agents can absorb much of that translation work. A developer can increasingly communicate at the level of goals, constraints and architecture while the model handles implementation.

But lines of code are a poor measurement of complete job automation.

Compilers already generate enormous quantities of machine code, yet their arrival did not make programmers unnecessary. Higher-level programming languages automated much of the work once performed manually, allowing developers to build larger and more complex systems.

Claude writing 90% of a codebase may therefore say less about the disappearance of engineers than it does about the abstraction level at which they work.

The remaining 10% can still contain the most difficult and consequential decisions. Someone must determine what should be built, understand the needs of users, choose between competing technical designs, identify security risks and decide whether the output is safe to deploy.

AI can generate a plausible implementation in minutes. Knowing whether it solves the correct problem remains a different challenge.

The Productivity Hump

Amodei describes a transitional period in which automation produces an enormous increase in productivity before it produces full replacement.

Imagine that AI can reliably perform 90% of the work involved in a software project. The engineer is still necessary because the final 10% requires human judgment, organizational knowledge or technical expertise. Yet the engineer can now spend nearly all available time on those remaining tasks.

In simplified terms, one engineer may become capable of supervising the volume of work previously handled by ten.

Companies could respond by reducing staff, but they could also build far more software. Projects previously rejected as too expensive could become viable. Internal tools that never reached the top of the development queue could be created quickly. Small teams could launch products that once required large engineering departments.

This is the productivity hump: the period in which humans remain essential but become dramatically more leveraged.

The economic consequences will depend on how much additional demand appears. When productivity rises, companies do not always reduce employment proportionally. Lower costs can create new markets, new products and new categories of work.

However, that protection has limits.

If AI advances from writing most of the code to completing nearly the entire software-engineering process, the remaining human bottleneck begins to disappear. The model would not merely implement a feature. It would identify the requirement, inspect the existing system, design the solution, configure the environment, run tests, diagnose failures, document the change and prepare it for deployment.

At that point, engineering becomes less about humans using better tools and more about humans assigning objectives to autonomous systems.

From Roughly 5% to More Than 77%

The speed of improvement in coding benchmarks helps explain Amodei’s confidence.

The original SWE-bench evaluation was designed around genuine software issues collected from public GitHub repositories. Instead of asking a model to write a small function or solve an interview-style coding puzzle, it required the system to understand an existing codebase and generate a patch that resolved a documented problem.

Early results were poor. Claude 2 resolved only a small percentage of the tasks under the initial evaluation setup. The result demonstrated how far language models still had to go before they could perform practical repository-level software engineering.

Later Claude models made rapid gains. Anthropic reported that Claude Sonnet 4.5 achieved 77.2% on SWE-bench Verified, a human-reviewed subset containing 500 software problems.

The figures should not be treated as a perfectly controlled comparison. The benchmark variant, model scaffolding, prompting strategy, tool access and evaluation methodology changed over time. A score on the original benchmark is not directly interchangeable with a score on the Verified subset.

Even with those caveats, the direction of travel is difficult to ignore.

AI coding systems have moved from solving only the simplest isolated issues to handling substantial portions of carefully selected real-world software tasks. They can navigate repositories, edit multiple files, execute commands, run tests and revise their own attempts.

Benchmarks still do not capture the complete reality of production engineering. Real companies have undocumented systems, conflicting stakeholder demands, legacy infrastructure and security requirements that cannot be represented by a clean test suite.

Yet the improvement suggests that the islands of work reserved for humans are becoming smaller.

A Medical Story With Larger Implications

Amodei has also used a personal family experience to illustrate how AI can identify patterns across complicated information.

According to his account, his sister and Anthropic co-founder Daniela Amodei developed an infection while pregnant. Several doctors believed the illness was viral. After her medical information was provided to Claude, the model suggested that the infection could instead be bacterial.

The anecdote is powerful because it captures a potential advantage of medical AI: the ability to process a large volume of records, symptoms and reference material without fatigue.

A doctor may have limited time with each patient and may receive information spread across laboratory reports, previous appointments, medication histories and specialist notes. A model can examine those records together and surface possibilities that deserve another look.

That does not make Claude a replacement for a physician.

A personal account is not a clinical trial, and an AI-generated suggestion should not be treated as a verified diagnosis. Language models can misunderstand records, overlook critical context or produce confident but inaccurate conclusions. Medical decisions also require physical examinations, professional accountability and an understanding of the patient that cannot always be captured in uploaded data.

The more realistic near-term role is that of a second reader.

An AI system can summarize a patient’s history, identify unusual combinations of symptoms, compare test results over time and suggest questions for a clinician. The doctor remains responsible for evaluating those suggestions and deciding whether further tests or treatments are appropriate.

The same productivity dynamic seen in coding could emerge in medicine. AI handles the information-intensive portion of the work, allowing medical professionals to spend more time on difficult judgments, procedures and patient relationships.

The stakes, however, are much higher. A coding error may break an application. A medical error can harm a person.

The Enterprise as a Collective Intelligence

Amodei’s broadest idea concerns the nature of the company itself.

An enterprise already behaves like a distributed intelligence. It collects information from customers and markets, stores institutional knowledge, assigns tasks, makes decisions and coordinates the actions of thousands of people.

Executives act as strategic planners. Managers distribute information and resources. Employees operate as specialized units. Databases and software systems function as organizational memory.

The result is more capable than any individual person.

Placing AI at the center of that structure could make the organization faster, more coordinated and more responsive. Instead of acting as a chatbot used by isolated employees, the model could become a shared reasoning layer connected to the company’s data, applications and operational processes.

An AI-centered enterprise might monitor sales activity, examine customer feedback, analyze product performance and recommend changes continuously. It could draft software updates, prepare financial forecasts, identify supply-chain risks and coordinate specialized agents responsible for different departments.

Human employees would establish objectives, approve sensitive decisions and intervene when judgment or accountability is required.

In this model, AI is not simply another application purchased by the information-technology department. It becomes part of the company’s operating system.

That prospect explains why enterprise AI is strategically important to Anthropic. Consumer chatbots attract public attention, but organizations control enormous collections of proprietary data and repeatable workflows. Connecting models to those systems could generate far greater economic value than answering standalone questions.

The New Bottleneck Is Judgment

As AI takes over execution, the value of human work may shift toward deciding what deserves to be executed.

A model can write a technically correct feature that customers do not need. It can optimize a metric that damages the wider business. It can confidently follow instructions that were badly designed from the beginning.

Greater execution capacity can therefore magnify poor judgment.

When software becomes cheaper to produce, companies may generate more unnecessary complexity. When reports become effortless to create, employees may drown in synthetic analysis. When autonomous agents can perform thousands of actions, a poorly specified objective can produce failures at extraordinary speed.

The most valuable workers may be those who understand systems deeply enough to direct AI effectively and recognize when its output is misleading.

That requires more than clever prompting. It requires domain knowledge, skepticism, taste and accountability.

Junior roles present a particular challenge. Companies traditionally develop senior experts by giving beginners routine tasks and gradually exposing them to harder problems. If AI absorbs the entry-level work, organizations may struggle to train the people eventually expected to supervise advanced systems.

A company cannot indefinitely remove the bottom rung of the career ladder while expecting experienced professionals to appear at the top.

Productivity and Displacement Can Both Be True

The optimistic and pessimistic interpretations of Amodei’s argument are not mutually exclusive.

AI can make engineers ten times more productive and still reduce the total number of engineers companies need. It can create new products while eliminating familiar roles. It can help doctors detect overlooked conditions while introducing new forms of diagnostic risk.

The outcome will not be determined by a single automation percentage.

It will depend on how quickly new demand develops, whether organizations reinvest productivity gains, how governments respond and whether humans can continue moving into new areas of comparative advantage.

The transition may also unfold unevenly. The strongest engineers could become dramatically more valuable because they can manage fleets of coding agents. Less experienced developers may face fewer opportunities. Large companies could become leaner, while small teams gain the power to compete with established organizations.

The result could be both democratizing and concentrating at the same time.

What Happens When AI Learns the Rest?

The most important part of Amodei’s argument is not that Claude writes 90% of the code. It is that the remaining percentage may not remain protected for long.

Today’s models still need supervision. They make mistakes, lose track of objectives and struggle with ambiguous organizational realities. Humans remain necessary because the final portion of the task contains uncertainty, responsibility and context.

But frontier AI companies are specifically working to improve reasoning, memory, tool use and long-horizon autonomy—the capabilities required to attack that final portion.

The productivity hump may therefore be temporary.

For now, AI allows one person to accomplish far more. The engineer becomes an architect. The doctor gains a tireless second reader. The enterprise acquires a new layer of collective intelligence.

Beyond that stage lies a harder question: not how humans work with machines, but what economic role remains when machines can carry an objective from conception to completion.

Amodei’s vision is compelling because it contains both possibilities. AI could become the greatest amplifier of human capability ever created. It could also advance so quickly that the new roles it creates are automated almost as soon as people learn to perform them.

The decisive battle will not be over the first 90%.

It will be over the last 10%.