If you have applied for a job in the last two years and never heard back, you have probably wondered whether a person ever saw your resume. An internal document from Google DeepMind suggests that the people building the most advanced AI systems on the planet wonder the same thing about their own employer’s software.
The memo, reported by Bloomberg and picked up widely since, comes from DeepMind’s AGI Safety and Alignment Team. It tells prospective candidates to fill out a separate form, on top of the standard Google application, so that a real human being will definitely see that they applied. The reason it gives is unusually blunt for a corporate hiring document.
What the Memo Actually Says
Two lines are doing most of the work here. The first is the admission: “We have an applications system with a non-trivial probability your CV will be screened out incorrectly or take too long to reach us.” The second is the remedy: “Filling out this form makes sure that a real human on the team will get to see your application.”
Read that as an engineer would. “Non-trivial probability” is not hedging language for “rarely.” It is the phrase you use when the failure rate is high enough that you have to design around it. And the team designing around it is the one whose entire remit is making sure advanced AI systems behave the way their operators intend.
There is a third line worth noting, aimed at candidates who have started fighting fire with fire. The memo warns that the form is read by people, and that those people “get really tired of reading LLM answers, because they all sound very samey.” So the same team that cannot trust the machine to screen applications also cannot escape applicants using machines to write them.
Google’s Response, and the Gap Between the Two
DeepMind did not dispute the memo’s existence. A spokesperson told Bloomberg that the hiring software is functioning correctly, and framed the form as a routing shortcut rather than a rescue mission: “This team set up a special form to go past the recruiter review, and get their resumes direct to the people on the team. But there are no shortcuts to getting hired.”
| The memo says | Google says |
|---|---|
| There is a non-trivial chance your CV is screened out incorrectly | The hiring software is working fine |
| The form exists so a human definitely sees your application | The form exists to skip recruiter review and reach the team directly |
| Please do not share this document widely | No comment on that part |
Both descriptions can be technically accurate at once, which is what makes the story stick. A form that routes around recruiter review is exactly what you build when you do not trust recruiter review. Whether the filter is a language model, a keyword matcher or a tired human with 900 applications in a queue, the fix is the same, and so is the implication.
Why Automated Resume Screening Keeps Getting It Wrong
Nobody outside these systems knows precisely how they rank candidates, and the vendors have every incentive to keep it that way. Publish the rubric and you invite gaming. But the failure modes are well understood by anyone who has watched them operate.
- Vocabulary mismatch. A posting asks for “cross-functional team leadership.” Your resume says you “ran projects with design and sales.” A human reads those as the same thing. A matcher tuned for precision often does not.
- Format fragility. Two-column layouts, tables, headers and graphics that look sharp to a person can parse into nonsense on the way in. Skills that never got extracted cannot be scored.
- Unusual career paths. Career changers, people with a gap, and anyone whose experience is real but oddly labelled get penalized hardest, because the model has seen fewer resumes like theirs. That is the same structural bias that has kept talented people out of fields like security, even as those fields insist they are finally opening up to candidates from non-traditional backgrounds.
- Volume tuning. When a role gets thousands of applicants, the screening threshold rises until the shortlist is manageable. Nobody decides that qualified people should be cut. The math decides it.
That last point is the quiet one. A screening system does not need to be broken to reject good candidates. It only needs to be calibrated for throughput.
The Arms Race Nobody Is Winning
Applicants worked out years ago that the first reader is a machine, and responded rationally by using machines to write for it. Generate a resume tuned to the posting, generate a cover letter, apply to sixty roles in an afternoon. The volume goes up, which pushes the screening threshold up, which makes AI-assisted applications more necessary, which pushes volume up again.
The result is a hiring pipeline where software writes to software and the humans at both ends are worse off. DeepMind’s own warning that reviewers “get really tired of reading LLM answers” is the same complaint platforms have been making from the other direction, and it is why LinkedIn declared war on AI slop across its feed. Detecting generated text at scale, reliably, is not a solved problem. Neither is screening it.
None of this is happening in a calm labor market. Tech hiring has spent two years contracting while the same companies talk up automation, a gap that shows up in the enterprise data too, where CTO confidence in scaling AI has now fallen for a third straight year. More applicants per opening means more aggressive filtering, which means more incorrect rejections, which is precisely the condition the DeepMind memo is describing.
What This Means If You Are Applying
| Do this | Why it works |
|---|---|
| Mirror the posting’s exact wording | Matching is literal more often than it is semantic. If they wrote “distributed systems,” write “distributed systems,” not “large-scale backend work.” |
| Use a plain single-column layout | Parsers mangle columns, text boxes and graphics. A boring resume that parses beats a beautiful one that does not. |
| Attach numbers to claims | Specific figures survive both filters. They are what a machine scores and what a human remembers. |
| Find the human route | A referral, a direct message to someone on the team, a supplementary form. DeepMind built one for exactly this reason. |
| Edit anything a model drafts | Use it for structure, then put your own specifics and voice back in. Reviewers are actively fatigued by generated prose. |
The Bottom Line
Automated screening was pitched as a fix for a genuine problem. A single opening can draw thousands of applications, and no recruiting team can read them all carefully. Something has to triage.
What this memo shows is the cost of that triage, written down by people with no reason to exaggerate it and every reason to keep it quiet. When the AGI Safety and Alignment Team at Google DeepMind decides the safest path to hiring good people is a side door with a human behind it, the honest reading is not that Google’s software is uniquely bad. It is that the current generation of hiring automation misses qualified candidates often enough that the experts have stopped pretending otherwise, at least internally.
Everyone else has been getting the automated rejection email for years without the explanation. Now there is one, and it came from the last place you would expect.
