What three months of applications show about verification signals
Application verification signals
How many flags to plan for
24flags at the median account rate (8%)
15 to 39across the middle half of accounts (5% to 13%)
Each dot is one application. Yellow dots are flags at the median rate.
On this page
At the median account, 8% of job applications screened by Findem’s Authenticity Suite between August and October 2026 had a suspicious flag. Rates varied widely across accounts, from 1% to 49%.
A flag isn’t a finding of wrongdoing. It means something in an application doesn’t match other sources, such as a company that can’t be verified or employment dates that conflict with a candidate’s online professional profiles. Many flagged details have ordinary explanations. A flag shows a recruiter where to look and what to ask.
Here’s what the signals showed.
Rates vary widely by account
Most accounts fell in a narrower band than the full range suggests. The middle half of accounts saw between 5% and 13% of applications flagged. A small group sat well above the rest, which is why we report the median account rather than a single rate across all applications.
Application verification signals
Range of flag rates across accounts
At the median account, 8% of applications had a suspicious flag.
Remote roles were flagged more often
Applications for roles listed as remote were flagged at a rate about 65% higher than applications for all other roles.
Application verification signals
Flag rate for roles listed as remote, compared with all other roles
65% higher
The data shows where flags concentrate, but not why. Teams hiring for remote roles may want to plan for more flags to review and decide in advance which of those roles require identity verification before an interview.
Work histories that don’t line up
Three of the signals relate to the work history itself. The figures below are shares of flagged applications. An application can show more than one signal, so they overlap.
Application verification signals
Share of flagged applications showing each signal
Work history
Contact details and documents
14 in every 100 flagged applications
About 14 in every 100 flagged applications showed work history that conflicts with professional profiles.
14% of flagged applications showed work history that conflicts with professional profiles. Profiles aren’t always current, and some people leave short roles off. This signal is a reason to ask, not a conclusion.
10% showed unusual employment overlaps. Some overlap is normal, since contract work, side businesses, and notice periods all produce it.
7% showed employment dates that don’t match company records. A renamed or acquired company can trigger this check, so each flag includes a plain-language explanation the recruiter can verify.
Contact details and documents
6% of flagged applications showed contact details with little history. That can be associated with a borrowed or synthetic identity. It can also reflect a candidate who set up a separate address for a job search.
3% showed hidden content in the resume. Hidden text is one way applicants try to get a resume past AI screening.
What a flag should lead to
At the median rate, a recruiter reviewing 300 applications for one role would see about 24 flags. That’s enough to need a clear process.
A flag should start a review, not end one. Authenticity Suite doesn’t advance or reject any applicant automatically. Recruiters see a plain-language explanation for each flag, check it, speak with the candidate where needed, and make the decision. If a question remains, Authenticity Suite Pro lets a recruiter send a short, consent-based identity verification session before an interview is scheduled.
The harder question is who owns a flag once it appears. It helps to agree on three things in advance:
- Who reviews a flagged candidate, and what they can decide
- When a concern moves from TA to Security or Legal
- Which roles require identity verification before interviews
About the data
These figures are based on job applications screened by Findem’s Authenticity Suite between August and October 2026. Account figures exclude accounts with no flags recorded. Signal shares are percentages of flagged applications. Because an application can show more than one signal, they don’t sum to 100%. Flags point to inconsistencies that warrant review. They don’t confirm wrongdoing.












