Fake experience letters and what actually stops them
Falsified employment history is the most common form of CV fraud — not because people are bold, but because almost nobody can check a letter.
Ask any background-verification analyst which part of a CV is most often falsified and the answer is immediate: employment history. Not qualifications, which can be checked with a university. Employment — because the only party who can confirm it is a previous employer with no obligation to reply.
Why it is the easy lie
A degree certificate has an institution behind it, usually with a records office and increasingly a digital repository. An experience letter has none of that. It is a Word document, exported to PDF, signed by someone who may have since left. There is no register, no central authority, and no cheap way to check.
So the three most common falsifications are all low-effort: stretching the dates to cover an employment gap, inflating the designation, and inventing a short stint at a company that will not respond to email.
How it survives screening
- The recruiter is not the verifier. Screening checks fit, not authenticity.
- Verification happens after the offer, when everyone is invested and a delay is expensive.
- Non-responses get waived. When a previous employer never replies, the check is often marked inconclusive and the hire proceeds.
- Documents are trusted at face value because there is no alternative on the table.
What does not work
Eyeballing fonts, calling the number printed on the letter, and asking the candidate for "proof" all fail against a competent forgery. The number on the letter is controlled by whoever produced it. Font analysis catches sloppy edits, not careful ones.
What does
Move the proof into the document itself. When a letter is issued through a verification platform, it carries a QR code and certificate ID pointing at a page hosted by the issuer, showing the name, designation and period of service recorded at the moment of signing. Editing the PDF does not change that page, and the mismatch is instantly visible.
The effect is asymmetric in the right direction: forging becomes hard while checking becomes trivial. Today it is the other way round, which is precisely why the problem persists.
