Is AI taking software engineering jobs?
The hiring data discussed with Greenhouse CEO Daniel Chait points to the matching layer breaking, not the jobs vanishing. Figures cited in the episode put applications up 239% since ChatGPT while 75% fewer reached the hire stage, and software engineers are the heaviest users of the automation driving that. Much of it is a signal problem, and each side makes it worse by responding rationally to the other. Separate research finds employment for young workers in AI-exposed occupations lagging their peers, a pattern its authors do not yet attribute to AI.
1. What the doom loop is
Daniel Chait runs Greenhouse, which more than 7,500 companies hire through, and he named the pattern. Candidates use AI to find and apply to more jobs and to tailor every resume to the posting. Recruiters, who may each be looking at four or five times the applications they saw a couple of years ago, point an off-the-shelf model at the inbox and ask which 20 of the thousand to call. That makes it harder to get seen, so candidates send more. Both responses are individually reasonable and jointly ruinous.
2. Engineers are the heaviest auto-appliers
By Greenhouse’s own data, software engineers automate applications more than any other group and send the most. Chait is careful that this does not make them the villains: they are early adopters doing what the tooling makes easy. It does mean engineering roles feel the signal collapse acutely.
3. The signal collapsed
Chait’s read is that more postings alone would not fix it. When every resume is tailored by a model to the job description, resumes converge, and a thousand near-identical applications carry less information than a hundred varied ones. Layer on the trust problem. A Greenhouse survey cited in the episode found 91% of recruiters have spotted candidate deception and 41% of candidates admit to using prompt injection to get past AI filters, and the episode cites resume hacks like white-fonting and injection up 500%. Screening turns more defensive in response, which attenuates the signal further.
4. The job did change, which is a separate claim
Chait grants the part that is real: software engineering looks different than it did three years ago, and different than it did sixty days ago. That is a change in what the work is, and it shows up in what teams hire for. It is a separate question from whether the roles exist, and conflating the two is what turns a matching failure into a story about replacement.
Whether AI is already costing young workers jobs is a separate, open question. A Stanford Digital Economy Lab update in August 2026 found employment for 22 to 25 year olds in the most AI-exposed occupations about 19% below where it would be had it kept pace with same-age workers in less-exposed ones. The authors describe that as a descriptive pattern and say they cannot yet show that AI is the cause.
Why it matters
If the problem were demand, the fix would be waiting. Because much of it is signal, the fix is anything that puts information back in the channel: a targeted application instead of a hundred automated ones, and a screening process that rewards evidence over keyword overlap. Both sides are currently optimizing against a system that stopped carrying information.
Hear it from the guest
“Ultimately, what it becomes is kind of a signal problem. It's like a matching problem”
“It's like you're sending in … a needle to an ever growing haystack, and you're making your needle look more like hay.”
Quotes lightly edited to remove filler words.
From the conversation
This explainer is drawn from these episodes — each carries its full transcript.