Recagn
Sign in

Guide · Anti-cheating

Fake experience on a resume: what to check, and which check settles what

Fake experience comes in three kinds: a job that didn't happen, dates stretched to fit, and real work that grew in the telling. Documents settle the first two. Only questions test the third. What a mismatch means stays your call.

Part of Interview cheating: how candidates cheat, what tools can detect, and what to do

What is a fake experience resume?

A fake experience resume claims work the candidate didn't do. It comes in three kinds: an employer or role that never existed, real jobs with dates stretched to add years or cover a gap, and a real job whose work grew in the telling. Each kind needs a different check.

Fake experience is one of several ways a candidate's claims can fail to hold up, from the CV through to the interview; the others are in the guide to interview cheating. The warning signs usually show first when you build a shortlist, which the guide to shortlisting candidates from CVs covers.

KindWhat it looks like on the CVThe check that settles it
A job that didn't happenAn employer you can't find, a role with no one to call, a gap filled with a company nameThe employer's own records: HR, the relieving letter, the PF record
Stretched dates"8+ years" in the summary over roles that add up to five; two full-time roles at once; a gap the summary skipsThe dates on documents the candidate shares, then a question
Work that grew"Led" for someone who was on the team; years with a tool longer than they used it; a scale they didn't runOnly questions about the work

Source: this guide's reading, 17 Nov 2026

The third kind is the hardest to settle, because the dates pass. A real job at a real company, for the years stated, can still carry a claim the person can't back up.

How do you spot fake experience on a resume?

Read the CV against itself before you read it against anything else. Add up the years from each role's start and end dates, look for overlaps and gaps, and check whether titles, scale and tools fit the time spent. A mismatch is a question for the candidate, not proof.

Red flags worth a question

  • Summary years that the roles below don't add up to.
  • Two full-time roles at once, with neither marked part-time.
  • A gap the summary skips, or a role filling it with no detail.
  • An employer with no website, or a reference on a personal email address.
  • A title well above what the years usually carry.
  • Years with a tool longer than the role it sits under.
  • A skills list longer than the projects that use it.

Each one is a reason to ask. People round up dates, count internships and list a notice period as time in the job, so ask before you decide.

An illustration, not a real CV: the summary says "8+ years". The roles below run from Sep 2021 to Aug 2023 (2 years) and from Sep 2023 to the present (about 3 years 2 months by mid-November 2026). Together that is about 5 years 2 months, so the summary claims nearly three years more than the roles hold. Ask which years the summary counts.

How do you verify work experience?

Check employers and dates against records the candidate shares and people you reach yourself: the relieving or experience letter, a reference call to a manager you identified, and the candidate's PF service history. Ask for consent first. These settle where someone worked and when; they don't tell you what the person did there.

CheckWhat it settlesWhat it can't settle
Relieving or experience letter, payslipsThe employer, the title on paper, the last working dayWhether the paper is genuine: confirm with the employer's HR on a number you find yourself, not the one on the letter
A reference call to a past managerThe role, the team, what they were trusted withIndependence: a reference the candidate supplies can be a friend, so find the manager through the company
The candidate's PF service history, which they can download with their UAN and share with youEmployers and dates on their PF recordWhat they did there; a job missing from it is a question to ask, not proof
A background-check provider, with the candidate's consentThe same records, collected for youWhat they did there; cost and turnaround vary by provider
Degree certificatesThe issuer's records, or DigiLocker, a platform for storing, sharing and verifying documents and certificates, where the issuer uses itWhether the course covered what the role needs

Sources: DigiLocker's home page, read 17 Nov 2026; this guide's reading, 17 Nov 2026

Every check here runs on the candidate's own records. Tell them what you will check and why before you start, and collect only what the role needs.

Which order to run them in

Start with what costs nothing: the CV's own dates. Ask for the relieving letter and the PF service history once someone is on the shortlist, not at application, so you collect records only from people you are serious about. Call references last, after the interview, when you know which claims you want a past manager to speak to.

Questions to ask any background-check or screening vendor

Take these to any provider you are weighing, Recagn included:

  • Which records does it read for employment, and with whose consent?
  • Does it confirm what the person did, or only where and when?
  • What does it return when an employer isn't in the record?
  • Can a result reject a candidate on its own?
  • Does your client see the result?
  • What does it cost per candidate, and is that price published?

What do employment checks miss?

Employment checks miss the work itself: a PF record or a relieving letter confirms a job and its dates, not what the person did there. A CV line about that work can overstate it and still pass every date check. When the dates allow a claim, only questions about the work test it.

The claim the dates allow

An illustration, invented for this guide: a CV lists "5+ years of Kubernetes" under a role that started six years ago. Every date check above passes, and the claim can still be untrue if the team moved to Kubernetes two years ago. Ask when they started using it, what the team ran before, and what broke the first time.

How to ask about the work

Pick the three or four claims the role rests on. For each, ask for one specific: what they built, how big it was, what broke, what they would change. Follow up once on the detail they give. Then write each claim down as backed up, overstated or contradicted, with the answer beside it, so the next person to read the file can see why.

For the Kubernetes line above, ask what the team ran before Kubernetes and when the switch happened, then who was on call for the first outage after it. If the switch came two years ago, six years in the role and five with the tool can't both be right, and that is the gap to talk through.

When the worry is something else

How Recagn does this

Recagn is our product. Its CV claim check, which the product calls the Consistency Checker, sets the claims on a CV against the candidate's interview answers, criterion by criterion, once the interview is complete. Each finding is a corroboration, an inflation or a contradiction, and quotes the claim and the answer side by side.

Before the interview, Recagn reads each CV against the role's scorecard, which Recagn calls a rubric, and treats every line on it as a claim to test, not a fact; that read is part of Recagn's resume screening. The claim check then takes the skills, projects, education and experience on the parsed CV and compares them with the job description, the rubric and the candidate's answers, follow-ups included. What it tests is the work the CV describes.

Vikram S.'s CV claim check

Read what the CV says, then what he said when asked. Recagn counts what it found; the counts never change his score.

Vikram S. Senior Java full stack and platform engineer

  1. From the CV we wrote

    Designed the company's Terraform estate across AWS; 7+ years of Terraform in production.

    His answer · Describe a time you designed or optimised AWS infrastructure using Terraform or Ansible. What did you optimise for (cost, availability, security) and what was the measurable impact?

    I own our whole AWS Terraform estate and have done this for over seven years. I optimise for cost and availability. We use reserved instances and autoscaling, and everything is in modules. When I joined in 2019 we were still creating most things from the console, and Terraform came in later, but I led that move. The impact was significant savings across the board.

  2. From the CV we wrote

    Authored the internal developer portal on Backstage, including 15 custom plugins.

    His answer · Tell us about your experience administering Kubernetes or OpenShift clusters and, if applicable, building internal developer portal features with Backstage. What problems were you solving?

    I run a platform of twelve clusters on Kubernetes and OpenShift serving hundreds of microservices. I built our developer portal on Backstage with fifteen custom plugins. The main problem we solved was giving teams one place to see everything about their services. The plugins integrate with our tools across the stack.

Profile against interview: 1 contradiction, 4 inflations, 7 corroborations No effect on scores.

Your decision: not made yet

Scored by Recagn on 8 Nov 2026 · Senior Java full stack and platform engineer · invented candidate; the CV and answers were written for this example

Vikram S.'s current role runs from Apr 2019, so on the run date, 8 Nov 2026, it was 7 years 7 months old. "7+ years of Terraform in production" fits inside those dates, and a dates check passes it. It is a claim about years with a tool that the dates allow, and the interview question beside it is what tests it; the same goes for "15 custom plugins". The totals cover all his answers, not only the two shown. His CV was written for the example.

You read the findings in two places. On the interview, a "Consistency" fold lists each one: the criterion, the line quoted as Résumé: "…", the Answer: "…" and the reasoning. On the candidate's record, "Consistency history" keeps them, with the hint "Profile against interview. No effect on scores." The same counts appear on the Company Report you share with your client.

A finding changes neither the interview score nor Recagn's recommendation, and it never rejects anyone. Testing each claim against the answers comes off your plate. Checking employers and dates, and what a mismatch means for this client, stays yours. Recagn recommends. Only you can reject a candidate.

The claim check runs on the interview's credits, so it costs nothing beyond the interview. How it fits into screening is on Recagn's resume screening page.

Questions people ask

Can a candidate with fake experience pass a reference check?

Yes, if you call the reference they give you. A friend can play a former manager. Find the manager through the company, call the employer's HR on a number you looked up yourself, and ask about the work as well as the dates.

Can a background-check company like AuthBridge confirm a candidate's past employers?

For jobs on the candidate's PF record, going by its own page. Run with the candidate's consent, AuthBridge's UAN check lists the companies linked to the candidate's UAN, with dates of joining and exit (page shows no date; read 17 Nov 2026), and its price is not published. A record like that confirms where and when someone worked, not what they did there; the interview is where that gets tested (AuthBridge).

What does it cost to test a candidate's experience claims in the interview?

On Recagn, nothing beyond the interview. The check that sets a CV's experience claims against the answers runs on the interview's own credits: at most ₹50 for one text interview on Starter, before GST. Where it fits into screening is on Recagn's resume screening page.

Can Recagn tell whether a CV's experience is fake?

It tells you which experience claims the interview answers back up. Once an interview is complete, Recagn sets the skills, projects and years with a tool on the CV against the candidate's answers, criterion by criterion. It marks each finding a corroboration, an inflation or a contradiction, and quotes the claim beside the answer. Employers and dates are checked with documents and references, and that part stays yours.

See it run on one of your roles.