A quick frame before the recap, because this is running on our public site and not everyone reading it is inside the panel.
CXR runs research panels a few times a year. Small group, closed forum, four to five weeks of structured async discussion on one topic, then a closing call. This one is on candidate fraud in hiring. Roughly two dozen TA leaders and heads of talent in the room, plus a handful of identity and verification specialists to keep us honest on the tech side. The four weeks map out as Landscape, Detection, The AI Complication, and What Needs to Change. We just closed Week 1.
Co-facilitating with me on this panel is CXR member, @Alex Murphy, CEO of JobSync. Full disclosure the same way I'd give it inside the forum: Alex and JobSync helped shape the framing on this one, and JobSync sits in the talent tech market. Panelists aren't paid to participate. Never have been. That's how CXR runs these. @Barb Ruess is project managing, @Hannah Vanderpool is our platform admin, and the panel itself lives over at www.cxr.works/research.
Now to what actually happened.
Meanwhile, the wider community weighed in
Alongside the panel, we ran two quick polls out to the broader CXR community and select recruiting audiences. Non-scientific, but the shape is worth naming.
43.9% of respondents said their organization is actively dealing with candidate fraud right now. Another 34.2% have seen isolated incidents. Only 14.6% said it hasn't surfaced as a concern yet.
That's roughly 4 in 5 already living with this in some form.
On the funnel question, Application and Sourcing led at 52.6%, with Screening and Assessment second at 36.8%. Two things stood out. Post-offer, pre-boarding, and onboarding pulled 21%, higher than Interviews at 15.8%. That maps directly onto the stories panelists already surfaced (@Ben Martin's identity-theft catch at I-9, @Andrea Johnson's flag about employees clocking in for each other) and it tells me the "who actually shows up Day 1" problem deserves its own beat later in the panel.
And 15.8% said "we just don't know yet." Same fog the panel is sitting in.
Week 1's word was intent
I went in thinking we'd spend most of the week fighting about where the edges of "candidate fraud" actually are. We didn't. The group aligned on the center faster than I expected, and it wasn't the definition I'd have written on a whiteboard on Day 1.
@Ryann Wingeier at Assurant put the frame down early: "a candidate is not who they say they are, with nefarious intent." The intent is what separates fraud from ordinary embellishment. A software engineer stretching toward Sr. on their resume is not the same thing as an entry-level IT hire posing as a Senior SWE. Both might be dishonest. Only one is fraud.
That distinction matters more than it sounds.
A lot of what gets flagged internally as "fraud" right now is really just noisy, AI-assisted, over-polished application behavior. If we can't sort the noise from the actual bad actors, we're going to burn recruiter time chasing the wrong signals. And we're going to hurt good candidates in the process.
@Adela Schoolderman at Edwards added the sharper version of this, and I keep coming back to it: using an AI tool isn't fraud. Using one to misrepresent your identity, your skills, or your work in a way that changes the hiring decision is. That framing is going to matter a lot when we hit Week 3.
It's a spectrum. Not a category.
The second thing that kept surfacing: "candidate fraud" isn't one thing.
It runs from resume polishing on one end to state-sponsored infiltration on the other. Every point on that line carries different risk, different detection cost, different consequences. You can't build one control that catches all of it.
Several of you said versions of the same thing. Prioritize by impact and access. Not by tactic.
That's the frame I want to carry into Week 2.
The label is too small
@John Gotham at Newell pushed on the term itself. His argument, which I think holds up: "candidate fraud" is too narrow for what we're seeing. He offered "Recruiting Fraud" as the better container.
Because it's also:
- Employer impersonation scams (fake recruiters phishing job seekers)
- Pay-per-applicant models incentivizing junk submissions
- Direct-deposit bank-draining schemes at the offer stage
- LinkedIn identity theft targeting our own recruiters
The whole hiring process is getting worked from multiple sides at once. "Candidate fraud" doesn't cover most of it.
@Alex Murphy summed it up nicely by saying that the casualty is trust. Between employers and candidates, yes. Also, between recruiters and the tools we're supposed to be able to lean on.
One to come back to in Week 4.
Remote is where we see it. That doesn't mean remote is the problem.
Third prompt of the week: is fraud really just a remote hiring issue?
Almost nobody said yes.
The responses landed together. Role and access drive real risk more than mode of work does. A fully remote warehouse coordinator is a different exposure profile than an on-site engineer with production system access. Several of you shared on-site examples too. Murphy's 2006 case of an in-office developer quietly outsourcing his own work overseas is the one I keep coming back to. That's twenty years old.
There was also a hard reaction against the "everyone on-site Day 1" reflex as a fraud response. @Amy Ho at Adobe made the case cleanly. Targeted friction beats blanket mandate. An in-person laptop pickup, one required in-person interview - that's a different move than shutting down your remote and hybrid talent pool.
Where I land: remote is where fraud is most visible right now, because that's where we've built up the most first-hand experience spotting it. That's not the same as remote being where the real exposure lives.
Where Week 2 goes
Detection. Prompts are up.
@Linellis Santiago at Land O'Lakes said something in Week 1 that ran under the surface across most of the threads: "we don't know what we don't know." Several of you said versions of that in your own words. That's the ground we're walking into Week 2 on.
We'll work through what you actually have in place today, what you wish you had, whose budget it's coming out of, how you're risk-tiering when exposure varies this much, and how you're really navigating the speed-versus-scrutiny tradeoff inside your org.
I'll be honest. I think Week 2 is where this panel gets a little uncomfortable. Defining the problem is the easy part. Talking about what you're spending money on, what's actually working, and where you know you have gaps is where the daylight between organizations starts to show up.
That's the point. Benchmarking against each other, not against a whitepaper or for an analyst.
If you're a panelist and you haven't posted in Week 1 yet, the threads are still open. Jump in this week. If you're reading this from the wider CXR community and you want in on the next research panel, the way in is the same as it's always been: participate in the polls, show up in the forums, come to a Colloquium. That's the pool we pull from.
#CandidateFraud
#candidateexperience
#leadership
#research