The Resume Is Dead, and It's Not Coming Back

I read a resume last month that was perfect. Quantified impact on every line, verbs in the active voice, a career arc that built to exactly the role I was hiring for. It was one of the best resumes I've seen in twenty years of hiring.

So were the other forty in the pile.

That's the whole problem in two sentences. The resume used to carry signal because writing a good one took effort, and the effort itself told you something. A candidate who could describe their work crisply, quantify their impact, and tailor the story to your role had already demonstrated a kind of competence. Now a model does all of that in eight seconds, for everyone, for free. The polish is still there. The signal is gone.

What actually died

Let me be precise, because "the resume is dead" gets said a lot and usually means nothing. The document still exists. People still send it. What died is every inference you used to make from it.

• Writing quality used to proxy for clarity of thought. Now it proxies for having an internet connection.
• Tailoring used to show genuine interest in your company. Now a model tailors two hundred applications an hour.
• Keyword fit used to be a rough relevance filter. Now it's the easiest thing in the world to game, and the people gaming it hardest are often the weakest candidates, because they need to.
• The cover letter used to be a work sample of communication. It's now the least trustworthy document in the whole process.

None of this makes candidates dishonest. Most of them are doing the sensible thing with the tools available, and honestly, an engineer who refuses to use AI for a writing task in 2026 worries me more than one who does. The point isn't that candidates are cheating. The point is that the artifact no longer measures anything.

The screening stack built on sand

Here's what makes this dangerous rather than just annoying. Most companies' hiring funnels are a stack of filters, and the resume is the bottom layer. An ATS scores it for keywords. A recruiter skims it for pedigree. A hiring manager decides in ninety seconds whether the phone screen happens. By the time a human has a real conversation with the candidate, three decisions have already been made based on a document a machine wrote.

When the bottom layer of a stack stops carrying information, everything above it inherits the noise. You're not filtering for engineering ability anymore. You're filtering for prompt quality, and you're doing it with a straight face.

I've watched this play out from the inside. A founder I work with ran a search for a senior backend role and got nine hundred applications in a week. The ATS shortlist looked immaculate. The first five phone screens were a massacre: candidates who couldn't explain a single line of the experience their resume described, because they hadn't written the description and, in one memorable case, seemed to be reading their answers off a second screen with a familiar latency.

What still carries signal

The good news is that real signal didn't disappear. It just moved. It moved out of documents and into anything a candidate has to do live, unrehearsed, with their actual judgment on display.

A real conversation about a real decision still works. Not "tell me about a time you showed leadership," which has a rehearsed answer, but "walk me through the worst technical decision you were part of, and what you'd do differently." People who lived the work can go infinitely deep. People who resumed their way in run out of floor in two follow-up questions. The follow-up question is the entire game now. Any first answer can be manufactured. The third layer can't.

Work samples still work, with one big change: you have to let the candidate use AI, because forbidding it tests a job that no longer exists. Watch how they direct the tools. Watch what they accept and what they push back on. An engineer who ships the model's first plausible answer is telling you exactly how they'll perform on your codebase.

And references, the most unfashionable tool in hiring, quietly became one of the most valuable. A fifteen-minute call with someone who actually worked beside the candidate is the one channel AI hasn't polished, at least for now.

What I do instead

When I recruit for a client, the resume gets me a name and a rough shape of a career. That's all I let it do. Every candidate who goes further talks to me, a CTO who has hired 75+ engineers for his own teams, in a real technical conversation with real follow-ups. The ones worth a client's time then do a working exercise with AI tools on the table, scored on judgment: what they questioned, what they caught, what they chose not to build.

It's slower per candidate than keyword filtering. It's also the only version of screening that still measures the thing you're buying. The resume was a shortcut, and it was a good one for fifty years. It's dead now. The companies that keep screening on it aren't saving time, they're just making their bad hires more efficiently.

If you're hiring engineers and the pile of perfect resumes is telling you nothing, that's exactly the problem I solve. Here's how I recruit engineering teams, or just get in touch →