Quick answer
A suspicious application is not a verdict. Treat it as a reason to inspect a specific claim, compare the evidence with the role requirements, and ask a focused follow-up question. A fair workflow records what triggered review, uses the same verification step for comparable cases, and keeps the final decision with a human recruiter or hiring team.
How we compiled this guide
Treegarden publishes recruiting software, so this guide may lead readers to request a demo. We reviewed current FTC job-scam guidance and the FBI Internet Crime Complaint Center's 2025 Annual Report on September 12, 2026. They establish that employment-related fraud and interview impersonation are real risks. They do not prove that any individual applicant is fraudulent or authorize automatic rejection.
Separate a review signal from proof
Applications can look inconsistent for many ordinary reasons: a changed surname, an inaccessible portfolio, an outdated profile, a resume drafted with writing assistance, or a recruiter working across languages and locations. A risk signal can justify a closer look. It cannot establish that the person is fake or that a claim is deliberately false.
That distinction matters because a shortcut can exclude strong candidates and leave the team unable to explain a disputed decision. Write down the signal, verify the claim that matters to the role, and record the response. The workflow should be explainable to the candidate, the hiring manager and an internal reviewer.
Signals worth reviewing in context
| Signal | What to check | What not to conclude |
|---|---|---|
| Career history conflicts with a public profile or application answer | Ask for clarification about dates, title, employer or project scope. | That a mismatch alone proves intentional misrepresentation. |
| Portfolio, identity or contact detail cannot be verified | Confirm the source link or alternative proof relevant to the job. | That a sparse online footprint makes someone ineligible. |
| Experience sounds polished but lacks operational detail | Use a structured follow-up: problem, constraints, decisions, evidence and result. | That a well-written resume was generated dishonestly. |
| Interview identity or voice does not match the stated person | Pause the process and use a documented identity-verification or rescheduling step appropriate to the role. | That technical issues on a call are proof of deception. |
The FBI's 2025 IC3 report specifically describes voice spoofing or potential voice deepfakes in online interviews and notes that its Employment category included AI-involved employment-type scams. That is a reason to design a consistent escalation path for material identity concerns, not a reason to make an interview environment hostile to every candidate.
Use a calm, repeatable review workflow
- Identify the exact claim or signal that requires review. Avoid labels such as "fake candidate" in routine recruiter notes.
- Compare it with the written requirements for the role. Verify only what is material to the decision.
- Ask a concise, role-relevant clarification question or request an alternative source of evidence.
- Use a structured interview or work sample to explore claimed experience where it would matter on the job.
- Record the evidence reviewed, the candidate's response, and the human decision.
- Escalate an identity, access or security concern through the company's existing process rather than improvising a separate investigation.
A candidate may use a writing tool to improve clarity. The hiring question is whether their experience, credentials and work claims are accurate and can be verified through a fair, role-relevant process.
Treat interview identity concerns as a process question
When an interview creates a material identity concern, stop and document the observation. Do not accuse the candidate in the moment based on a single technical issue. Decide which verification step is suitable for the role and local policy: rescheduling with an approved identity check, asking a role-specific question that requires first-hand explanation, or escalating a possible security concern.
Keep the same threshold for comparable candidates. The goal is to protect the organization and the candidate experience, not to turn unusual communication, disability accommodations or ordinary video problems into automatic flags.
This is different from fake recruiter messages
Inbound candidate-review risk is separate from a scammer pretending to be the employer. If someone reports a fake recruiter or job post using your company name, direct them to the official careers site and follow the company's external incident process. Our employer job-scam prevention guide covers that candidate-protection workflow.
Keep the review record with the recruiting workflow
An applicant tracking system can keep application notes, structured interview feedback and approval context together. It should support the reviewer; it should not label someone as fraudulent or make an unexplained automatic rejection. For a related boundary, see our guide to candidate fraud versus AI writing assistance.
Frequently asked questions
Does a suspicious signal prove that an applicant is fake?
No. A suspicious signal is a reason to review an application in context. It should not be treated as proof of fraud or used as the sole reason to reject a candidate.
How should recruiters review a suspicious application?
Record the specific signal, verify the underlying claim using a consistent process, give the candidate a reasonable opportunity to clarify a material mismatch, and keep a human reviewer responsible for the decision.
Should employers automatically reject AI-assisted applications?
No. Writing assistance is not the same as a false claim. Evaluate whether the application accurately represents the candidate's experience and use role-relevant follow-up questions to verify important claims.
Primary sources used
- FBI Internet Crime Complaint Center: 2025 Annual Report
- Federal Trade Commission: job scam guidance
- This guide intentionally does not use a fraud-rate benchmark to determine whether an individual candidate should be rejected.
Support fair, organized candidate review
Use Treegarden to keep recruiter notes, interview feedback and approval context in the same hiring workflow.
Book a demo