Recruiters now screen applicants against fraud checklists, and those checklists flag things honest people do every day: a profile rebuilt after a layoff, a location that just says "United States", AI-template wording, start dates that differ between documents. If you trip one, nobody tells you. Your application just stops moving.
The pressure behind this is real. Checkr's latest survey says 40% of US hiring managers have interviewed someone using a fake identity. LinkedIn Hiring Assistant 2 is rolling out to recruiters from November, and it puts your identity-verification status on the same card as your profile, screening answers and ATS history. Below are five flags you might trip by accident and how to fix each one before you apply.
What LinkedIn Hiring Assistant 2 shows a recruiter about you
Hiring Assistant 2 shows recruiters one candidate card with your LinkedIn verification status, ATS insights, pre-screening answers and experience all together. LinkedIn announced it between September 29 and October 1, 2026 (sources disagree on the exact day), and it is rolling out free to English-language customers from November.
Dan Reid presented it at Talent Connect 2026. LinkedIn verification has two parts. A government ID confirms your identity, and a work email confirms your current employer. LinkedIn reports 115 million verified members.
What matters is what the card leaves out. One source covering the launch warned that the system "can draw only on information candidates have included in their profiles." So whatever you put on LinkedIn is the evidence a recruiter has. If your profile, resume and ATS form disagree, the recruiter now sees that on a single screen.
LinkedIn's own August US survey found 64% of recruiting professionals say it's harder to know whom to trust. That's the frame of mind your application lands in.
How common is candidate fraud in 2026?
By managers' own account, very common. In Checkr's Hiring Hoax 2026, 40% of US hiring managers said they had interviewed someone later found to be using a fake identity, up from 31% in 2025. The survey covered 3,000 managers from September 11 to 16, 2026, and was published October 15.
Up from 31% a year earlier, per Checkr's survey of 3,000 managers.
The rest of the survey points the same way:
- Interview proxies. An interview proxy is someone who takes the interview in place of the real candidate. 67% of managers had confirmed (34%) or strongly suspected (33%) one.
- Skill misrepresentation. 65% had caught a candidate misrepresenting skills, up from 60%.
- Training. Formal fraud training on HR teams rose from 17% to 71%.
- Confidence. Only 23% of managers are "extremely confident" their process would catch a fraudulent candidate.
Gartner expects one in four candidate profiles worldwide to be fake by 2028. Checkr CPO Ilan Frank says polished resumes no longer tell "the whole story."
One caveat: Checkr sells verification tools, and at least one outlet has pointed that out. Read the percentages as a direction rather than precise figures. Recruiters have real reasons to be wary, though. On October 13, 2026, the DOJ charged 14 people in a North Korean IT-worker scheme and seized about 187 devices from more than 40 laptop farms in Texas. The scheme reached 70+ US companies and brought in about $3M. Operatives used VPNs and proxy infrastructure to look US-based. CrowdStrike has done work tracing these laptop farms, and the actors behind them are also known as Famous Chollima.
Why honest applicants get flagged as fake
Most screening happens before anyone checks an ID. Only 29% of companies verify identity at the application stage, and 49% wait until after at least one live interview. That means the first cut is a person comparing your profile against a fraud checklist.
Those checklists describe fakes by their shape: a new digital footprint, a vague location, generic wording and dates that don't line up. Honest candidates can match that shape for ordinary reasons. You rebuilt your profile after a layoff. You wrote "United States" because you're open to relocating. You used an AI template, as 79% of job seekers in a Kelly survey say they do in their applications.
A flag doesn't always end your application. Checkr found 28% of managers moved a suspected-dishonest candidate forward because the role needed filling fast. Read the other way, a flag turns your chances into a coin flip that depends on how busy the recruiter is.
The worst part is that nobody tells you. A recruiter who suspects a fake won't email you to say your location looked like a VPN. They move to the next card, and your application goes into the pile that never gets a reply. You could send application after application and never learn that a missing city was the problem.
The fix isn't to look more impressive. It's to be coherent, so that your profile, resume, ATS answers and verification status all tell the same story.
Why remote full-stack developers are the test case
Remote full-stack engineering is the role most exposed to fraud screening, because it is remote IT work, the kind the North Korean scheme relied on. Refolk's index shows how many honest profiles carry the same surface signals.
In Refolk's index of professional profiles, 21,848 US profiles have a current Full Stack Developer or Engineer title, compared with 41,275 in India. Only 46 of the US profiles put "open to work" in their headline. That's 0.21%.
| Segment | Profiles | What it means |
|---|---|---|
| US full-stack developers | 21,848 | Baseline |
| India full-stack developers | 41,275 | 1.89x the US count |
| US full-stack, "open to work" in headline | 46 | 0.21% of US profiles |
| US full-stack, location only "United States" | 3 of 25 | 12% (sample) |
| US open-to-work full-stack, location only "United States" | 6 of 25 | 24%, twice the baseline (sample) |
| India full-stack, location only "India" | 3 of 25 | 12% (sample) |
The profile counts cover the full population. The location rows come from 25-profile samples, so treat them as directional, not statistically solid.
Two things stand out. First, saying you're looking isn't the risk, because almost nobody does it. Second, the checklists care about whether your footprint hangs together. Ashby's fake-candidate guide flags connection counts that don't fit the length of a career and candidates who want remote work only. Each of those is fine by itself. Put several together and they start to look like a persona.
Five fraud flags honest candidates trip, and the fix for each
The five are a vague location, a profile younger than your career, wording that matches other applicants, dates that differ across documents, and an employer nobody can confirm. None of them takes money to fix. They take attention.
1. Your location just says "United States"
This is the flag job seekers trip most. In Refolk's index samples, open-to-work US full-stack developers were twice as likely to list only "United States" as full-stack developers overall.
Double the 12% baseline in Refolk's index samples (25 profiles each, directional).
Here's why it reads badly. The operatives in the DOJ case used VPNs to appear US-based, and a country with no city is what a masked location looks like. Job seekers do it to stay open to relocation. A recruiter running a checklist reads it as possibly hiding something.
Fix: name a real metro and use the exact same wording on your resume, LinkedIn and every ATS form. If you're flexible, write it as "City, State (open to remote or relocation)" so the city stays and the flexibility is still clear.
2. Your profile is younger than your career
Cadient's recruiter guide is direct about it: if a profile is under a year old but the resume shows a ten-year career, "ask why the digital footprint is so fresh." Many honest people deleted an old account, lost access to one tied to a former employer's email, or started over after a layoff.
Fix:
- Try to recover the old account before you open a new one.
- Reconnect with former managers and teammates so your connection count fits your career length.
- Ask for one or two recommendations from people at past employers. These are dated, named, third-party evidence.
- Link public work with its own history, such as a public code repository, talks or published posts.
3. Your resume reads like everyone else's
Wording copied from AI templates has stopped being only a style problem and become a fraud signal. LinkedIn says recruiters face a "sea of applicants" who look alike. When phrasing matches across applicants word for word, it can look like a coordinated set of fake personas rather than a shared template.
Fix: put specifics in every bullet that only you could have written: the system's name, the number, the team size and the tool. A bullet that names the system you changed, the metric you moved and the size of the team you did it with is something a template can't produce. "Drove cross-functional impact" is something it produces constantly.
If you reach for AI because writing from scratch is slow, Refolk writes the resume from your own history, so the bullets carry your actual systems and numbers rather than template phrasing, and then rewrites it for each posting you paste in.
4. Your dates don't match across documents
Hiring Assistant 2 puts ATS records next to the profile. If your resume gives one start month, LinkedIn another, and the ATS form you filled in from memory a different year entirely, all three now show up on the same card. To a recruiter who just read about laptop farms, that looks like a made-up history rather than a careless one.
Fix: keep one master record of every job with month and year, title and employer name, spelled identically every time (no "Sr." in one place and "Senior" in another), and copy from it. Don't type dates into an ATS from memory.
Tailoring is where the drift usually starts, because each new version of the resume gets edited a little. Refolk builds every tailored resume and cover letter from the same base history, so dates and titles stay the same in every version you send.
5. Your last employer is "Stealth Startup"
In Refolk's US full-stack sample, "Stealth Startup" was the second most common current employer. It's honest and common, and nobody can verify it. LinkedIn checks employers by work email, and "Stealth Startup" has no domain to check. Put it next to a new profile and it looks like a gap someone covered with a made-up job.
Fix: name the company if it's public now. If it isn't, describe it ("Seed-stage fintech, name under NDA") and back it up with something checkable: a reference who will confirm the role, a launch post, or a public repo.
How to verify your identity on LinkedIn before you apply
Go to Settings → Verifications, verify with a government ID, and add work-email verification for your current employer. It's voluntary, and one reviewer of Hiring Assistant 2 says recruiters shouldn't treat a missing badge as a red flag on its own. Still, it's the only fraud signal you control before a person judges your card.
Since 49% of companies don't verify identity until after a live interview, the badge does its work early, at the gut-check stage, when the recruiter has nothing else to go on. Expect more checks later on:
- Employer identity tools. Remote-hiring checklists recommend tools like Greenhouse Real Talent. If you get a verification link, complete it quickly. A delay looks like hesitation.
- Camera-on interviews. With 67% of managers having confirmed or suspected an interview proxy, expect interviewers to want to see who they're talking to. Turn your camera on, use a plain background and don't take offense.
- Follow-up depth. Expect detailed follow-up questions about your own work. If your bullets are specific, these questions help you.
Before each application, compare your resume, LinkedIn profile and ATS answers line by line: location, dates, titles and employer names. Hiring Assistant 2 shows recruiters all three together, so any mismatch is visible.
FAQ
Can a real person get flagged as a fake applicant?
Yes. Recruiter fraud checklists look for a new profile, a vague location, generic wording and mismatched dates, and honest candidates produce all four for ordinary reasons like layoffs, lost accounts and AI templates. Since only 29% of companies verify identity at application, a person makes the first call based on how your profile looks, and you're never told why you were passed over.
Should I verify my identity on LinkedIn before applying?
Yes, if you can. It's voluntary and takes a government ID through Settings → Verifications. LinkedIn reports 115 million verified members, and Hiring Assistant 2 shows verification status on the recruiter's candidate card. A missing badge isn't supposed to count against you by itself, but having one removes a question before anyone asks it.
Is using AI to write my resume a fraud red flag?
AI use isn't the problem. 79% of job seekers in Kelly's survey use it. The problem is wording that matches other applicants, because recruiters read duplicated text as a sign of coordinated fake personas. Keep the AI help and add specifics only you have: system names, numbers, team sizes and tools.
Will I have to prove my identity during interviews?
Likely, though usually not at the start. Only 29% of companies verify identity at application, and 49% wait until after at least one live interview, so expect a verification link from a tool like Greenhouse Real Talent or a camera-on interview later in the process. Complete any link promptly, keep your camera on, and know your own resume well enough to handle detailed follow-up questions. With 67% of managers reporting a confirmed or suspected interview proxy, those questions are coming, and specific bullets make them easy.