40% of Managers Met a Fake Candidate. Fix the 5 Mismatches That Flag You

If your name, phone number, city, or job dates differ between your resume, LinkedIn, and ID, an employer's fraud screen can read you as a fake candidate. Those checks now run on everyone, and they look for the same signals federal advisories use to describe fake applicants: a name that changes between documents, a Google Voice number, a city that doesn't match, dates that don't line up.

The numbers explain why. In Checkr's Hiring Hoax 2026 survey of 3,000 US hiring managers, run September 11 to 16, 2026, 40% said they had interviewed someone later found to be using a fake identity, up from 31% in 2025. Honest candidates who get flagged usually aren't caught lying. They get caught by small mismatches between documents, and most of those take minutes to fix.

Why are honest candidates getting flagged as fake?

Honest candidates get flagged because the checks look for inconsistency, and inconsistency isn't proof of lying. The red flags employers are told to watch for (mismatched names, VoIP phone numbers, conflicting addresses) also describe plenty of real people with untidy profiles.

Employers really are under pressure. 60% of managers now say AI has made virtual interviews harder to trust, up from 51% the year before. 65% say they have uncovered candidates who misrepresented their skills or experience, up from 60%. Pindrop CEO Vijay Balasubramaniyan has said that of 827 applications to one software developer job, about 100 were attached to fake identities.

Budgets are moving to match. In September 2026, Recruitics surveyed 159 talent acquisition leaders, all director level or above at US companies with 5,000 or more employees. Secondary coverage of that survey reports that 53% plan to increase spending on identity and fraud verification. In Recruitics' October 20 release, 70% said a recruiter loses six or more hours a week to applicants who turn out to be unqualified, duplicates, or misrepresenting themselves.

Read the Checkr figure with care. It's a vendor survey, and Checkr sells verification tools, so the company has a reason to make the problem sound big. Even so, the spending is happening, and the checks are going to run on your application.

The 5 mismatches that flag real applicants

The five mismatches worth fixing first are your name, phone number, location, employer history, and education. Fixing each one means picking one version and using it everywhere.

The red-flag lists behind these checks come largely from guidance on North Korean remote IT worker schemes:

• Skadden (2026): multiple or inconsistent addresses across identity documents, LinkedIn profiles, and home addresses, plus VoIP phone numbers.
• An older advisory: inconsistent name spelling, nationality, claimed location, contact details, education, or work history across profiles and portfolio sites.

None of these is unusual on its own. Put three of them on one honest applicant and that person looks a lot like the profile in the advisory.

1. Your name doesn't match your ID

A legal name mismatch happens when the name on your resume or LinkedIn differs from your government ID in a way software can't reconcile. If you're "Mike Chen" on LinkedIn and "Michael Y. Chen" on your passport and in the employer's HR system, an automated tool sees two names.

The fix: put your legal name in the places that get checked against your ID (the application form, background check consent, HR records). Add your preferred name on top, for example "Michael (Mike) Chen" on your resume header. Don't drop your legal name entirely.

2. Your phone number is VoIP

A VoIP number is a phone number that runs over the internet instead of through a mobile carrier, like Google Voice. Advisories flag them because they cost nothing to create and carry no location. Lots of careful job seekers use Google Voice to keep spam off their real number, and that habit makes them look exactly like the fake profile the advisory describes.

The fix: use a carrier-issued number on applications. If privacy matters, get a second line from a real carrier rather than a VoIP app.

3. Your location doesn't add up

A location mismatch is a gap between where you say you live and the address on your ID and other documents. Writing "United States" with no city makes this worse, because it gives a screener nothing to check against.

The fix: list a city and state on your resume and LinkedIn, and make sure it matches your mailing address. If you're moving, write "Relocating to [City, State], [Month]" instead of leaving the field blank.

4. Your employer names and dates drift

This is the classic resume LinkedIn mismatch on a background check. Your resume says you were at "JPMorgan" from 2021 to 2024, LinkedIn says "JPMorganChase" from 2020 to 2024, and the employment verification comes back with a third version. Each difference is small. Together they look like a story that was put together after the fact.

The fix: use the employer's official name, write month and year for every role, and use exactly the same dates on your resume, LinkedIn, and application forms. Tailoring for a posting should change which accomplishments you lead with, never the dates. This is the part that's tedious to manage across dozens of applications, and it's the work Refolk takes off you: it writes your resume from your own history once, then tailors it to each posting while employer names and dates stay exactly as they are.

5. Your education disagrees with itself

Education mismatches include degree names, graduation years, and schools that differ between your resume, LinkedIn, and portfolio sites. "BS Computer Science, 2018" in one place and "B.Eng, 2017" in another is enough to set off a flag.

The fix: copy the degree title from your diploma or transcript and use that same wording everywhere.

Why remote engineers draw the most scrutiny

Remote software engineers get the most scrutiny because state-sponsored fraud schemes go after remote IT jobs. In Refolk's index, they also have the vaguest profiles: they are the biggest remote group and the one most likely to leave out a city.

In Refolk's index, 233 US profiles have "Software Engineer" in the title and "remote" in the headline, compared with 113 for "Data Analyst". In a sample of 25 remote US software engineer profiles, 9 listed their location only as "United States". The equivalent analyst sample had 4 of 25.

The samples are small, so treat the percentages as a direction, not exact rates. The direction is still clear: the people applying to the most heavily screened jobs are the ones most likely to leave out the detail a screener checks first. Exact employer names matter here too. The most common current employers in the engineer sample are Google, Walmart, and JPMorganChase, and "JPMorgan" versus "JPMorganChase" is exactly the drift described in mismatch 4.

Specificity now works as a credibility signal. A named city, a carrier phone number, and dates that match to the month make a profile easy to verify.

When do the checks happen, and why does late hurt more?

Most identity checks still run late, so a mismatch often costs you an offer rather than a phone screen. Only 29% of companies verify identity at application, and 63% focus their fraud prevention on the pre-hire stage.

Hiring under pressure makes this less predictable. In Checkr's survey, 28% of managers said they had knowingly moved a candidate forward despite suspecting dishonesty because they needed the role filled. So a mismatch might get past a recruiter rushing to fill a seat, then get caught weeks later by the formal background check after your final round.

That's the worst case for an honest applicant. You spend weeks interviewing and turn down other conversations, then an employment verification comes back with a date range that doesn't match what you wrote. The offer stalls and nobody explains why. Most people in that spot never find out it was a dates problem.

Checks are moving earlier, though. Recruitics launched AdaptiveApply with ID.me to bring verified identity to the top of the hiring funnel, which puts ID verification before the interview, at the moment you apply. Once that becomes common, a mismatch stops costing you the offer and starts costing you the screen, and you're less likely to hear why.

What does a LinkedIn verification badge actually prove?

A LinkedIn identity badge proves that a verification partner checked a government ID and that LinkedIn matched it to the name on your profile, or to an alias it could confirm. It doesn't prove your jobs, schools, or photo are real.

The common mistake is to verify, see the badge, and assume you're covered. The badge certifies one connection only: the ID name to the profile name. If your profile says "Mike Chen" and LinkedIn couldn't confirm that as an alias, the employer's own check against your passport can still fail.

Two practical points:

• Verify your identity on LinkedIn, but do it after your profile name matches your legal name or a clear alias of it.
• Don't treat the badge as cover for your work history. Employers check that separately, against your resume.

What to do if a recruiter thinks you're a fake candidate

If a recruiter seems to think you're a fake candidate, ask which detail raised the flag and offer documents that resolve it. The FBI itself has warned that screening can catch honest people.

In an October 13, 2026 announcement about North Korean IT workers, the FBI said no single indicator reliably identifies a fraudulent worker, and warned that overly aggressive screening could wrongly affect legitimate employees and job applicants. It recommends an "identity in depth" approach, meaning several checks taken together rather than one red flag acting as a veto. That gives you a reasonable basis to ask for a second look instead of accepting a silent rejection.

How to handle it:

1. Ask directly and politely. "I want to make sure nothing in my application is unclear. Is there a detail I can verify for you?"
2. Offer proof that fits the flag. An offer letter or W-2 for dates, a diploma for education, a utility bill for address.
3. Offer a live, on-camera ID check. A real candidate can say yes to this easily.
4. Fix the source afterward. Whatever got flagged once will get flagged by the next employer too.

Keep the scale in mind. Gartner's survey of 3,000 job candidates found 6% admitted to taking part in interview fraud. Gartner predicts that by 2028, one in four candidate profiles worldwide will be fake, but that's a forecast, not a measured rate. Most applicants are honest. The checks just can't tell that from a messy file.

A quick audit before you apply

Run this audit once before your next application. It closes most of the gaps hiring fraud checks look for.

1. Name: Check that your legal name appears on your resume header, LinkedIn, and application forms, with your preferred name added, not swapped in.
2. Phone: Replace any Google Voice or other VoIP number with a carrier-issued one.
3. Email: Use an address based on your name, the same one everywhere.
4. Location: List city and state, matching your mailing address.
5. Employers: Use official company names, the same on resume and LinkedIn.
6. Dates: Write month and year for every role, identical on every document.
7. Education: Copy your degree title from your diploma.
8. LinkedIn badge: Verify only after steps 1 to 7 are done.

Step 6 is where tailored applications tend to go wrong. When you rewrite a resume twenty times, titles creep and date ranges get rounded. A good tailoring process changes the emphasis and keeps the facts fixed, which is how Refolk handles it: each version is rewritten for the posting, the cover letter is drafted from the same history, and the dates come from one record.

FAQ

Can a Google Voice number really get my application flagged?

Yes, it can. Fraud advisories list VoIP numbers as a red flag because they cost nothing to create and carry no location. One VoIP number usually won't sink you by itself, but alongside other mismatches it adds to a pattern. Use a carrier-issued number on applications.

Should I use my legal name or my preferred name on my resume?

Use both. Put your preferred name on top with your legal name visible, for example "Michael (Mike) Chen", and use your legal name on application forms and background check consent. That way identity tools can match you to your ID, and people still know what to call you.

Does a resume and LinkedIn mismatch fail a background check?

It can stall one. Employment verification compares what you said against what the employer or a database reports. Different dates or company names on your resume and LinkedIn give the reviewer a discrepancy to settle before signing off, and with checks often running after the final round, that delay can land right on your offer.

Is ID verification before the interview becoming standard?

It's growing but not standard yet. Only 29% of companies verify identity at application today. Still, coverage of Recruitics' survey reports that 53% of talent acquisition leaders plan to spend more on identity and fraud verification, and AdaptiveApply with ID.me is built to run the check at the moment you apply. Assume you'll be checked earlier and get your details in line now.