Claude Code: A Disaster or an Opportunity?

Tools like Claude Code are generating predictable responses. On one side: enthusiasm from developers who have discovered that certain classes of work now take a fraction of the time they used to. On the other: anxiety from hiring managers who worry about what this means for technical headcount, skills assessment, and the nature of the engineering org they are trying to build.

Both reactions contain something real. But I want to focus on the one that is less discussed: what AI coding tools mean for how companies should hire.

What has actually changed

The honest answer is: quite a lot, and faster than most organisations have adjusted for.

AI-assisted coding has compressed the time required for a wide range of engineering tasks - particularly the ones that are well-defined, well-scoped, and don't require deep contextual knowledge of a complex system. Boilerplate, basic feature implementation, test generation, documentation - these are areas where capable developers working with Claude Code or similar tools are already dramatically more productive than they were eighteen months ago.

What has not changed is the nature of the hardest engineering problems. Designing systems that are robust under operational stress. Making architectural decisions that will look sensible in three years, not just three months. Debugging production incidents in systems that have accumulated a decade of undocumented decisions. Understanding the security implications of a design choice in a genuinely adversarial environment.

These problems still require what they always required: exceptional judgment, deep domain knowledge, and the kind of experience that cannot be prompted.

The talent market shift

Here is where things get interesting for hiring.

The gap between a good engineer and an exceptional one is being amplified, not compressed, by AI tools. An exceptional engineer with access to Claude Code is not twice as productive as a mediocre one. They are perhaps ten times as productive - because they know which parts of the problem to hand to the tool, how to evaluate the output critically, and how to direct the work toward an architecture that will actually hold.

This means that the premium on genuine seniority - on the professionals who have developed deep judgment through real experience - is increasing. And at the same time, the scarcity of those professionals is more acutely felt, because they are less willing to move for the wrong reason, and more capable of identifying when an opportunity is genuinely interesting versus generically well-compensated.

What this means for hiring

Several things.

Assess judgment, not syntax. If your technical interviews still spend significant time on the kind of coding a competent AI can produce, you are measuring the wrong thing. The candidates who matter can use the tools. What separates them is what they do with the output - and whether they know when not to use it at all.

Reconsider the scope of roles. Some companies will find that AI-assisted development lets a smaller team of exceptional engineers accomplish what previously required a larger one. This changes the hiring conversation significantly - the priority becomes finding people with the right judgment and the right character, not filling seats.

The rare-profile problem gets harder. The professionals who are genuinely exceptional - and who know how to multiply their output with AI tools - are already employed, well-compensated, and being actively retained. Reaching them requires the kind of access and credibility that standard search processes do not provide.

The opportunity

Underneath the anxiety about AI in the workplace, there is a genuine opportunity for companies that think clearly about this shift: the chance to build smaller, better, more focused engineering teams that produce disproportionate outcomes.

That opportunity requires getting the talent piece right. And getting it right requires a different kind of search - one that is oriented around judgment and rare capability, not volume and keyword matching.

That is, incidentally, exactly what we do.

If you are thinking about how AI tools are changing your technical hiring strategy, we would find that a genuinely interesting conversation.