Police investigations and contemporary media reporting from Bangalore described a reported case of organised employment certificate fraud in India: over thousands of individuals reportedly secured jobs at Indian and multinational IT companies using fabricated work experience certificates, sold through a network of firms, some of which had no real business operations behind them.
At ProQuest, we regularly reference cases like this with clients because it illustrates, at scale, exactly the kind of gap our employment verification process is built to close.
What the Reports Describe
According to police investigations and reporting at the time, a network of recruitment adjacent firms in Bangalore sold experience certificates to job seekers for a fee, allowing them to claim work history at companies where they had never actually been employed. Authorities identified dozens of firms involved, and several individuals running these operations were arrested. Some of the firms named in these reports were reportedly non-operational entities that existed only to generate paperwork.
Why a Document Alone Cannot Establish Employment History
A certificate is, at its core, a printed claim. It carries no inherent proof that the issuing organisation is real, that the stated employment occurred, or that the dates and role described are accurate. This case illustrates that point at scale: thousands of certificates apparently passed initial review at hiring organisations before the underlying fraud was uncovered.
What We See in Practice
In our own verification work,one potential failure point is rarely the certificate's appearance. A fabricated certificate can look entirely professional. The failure point is almost always that the phone number or email listed on the certificate routes back to the same source that produced the fraud in the first place. When a verification process relies on candidate supplied contact details rather than independently sourced ones, it is effectively asking the fraud to verify itself.
The Gap Between "Looks Legitimate" and "Is Verified"
A certificate on letterhead, referencing a named company, with a phone number and address, can satisfy a cursory glance. What it cannot do on its own is confirm that the company is an active, functioning business rather than a shell created for this purpose. That distinction is the core function employment verification is meant to serve.
What Employment Verification Is Designed to Catch
Confirming the Employer Is a Real, Operating Entity
Verification involves establishing that a named employer actually exists as a functioning business, using sources independent of what the candidate or their certificate provides.
Sourcing Contact Details Independently
This is a critical step in ProQuest's verification process: employer contact information is sourced independently rather than relying solely on the details provided on the certificate. This helps reduce the risk of relying on misleading contact details, although independent sourcing alone cannot guarantee that every fraudulent employment claim will be detected.
Checking Consistency of Role, Dates, and Responsibilities
Fabricated employment histories often contain inconsistencies once cross-checked against other details a candidate has provided elsewhere, such as tenure length, designation, or timeline overlaps with other claimed roles.
What This Case Suggests for Hiring Practices
The reported scale of this case indicates that fraud of this kind is not necessarily rare or unsophisticated. It can be organised, priced, and repeated across a large number of candidates before detection. This does not mean every unverified certificate is fraudulent, but it does mean that treating a certificate as sufficient proof, on its own, carries a measurable risk that grows with hiring volume.
We generally advise clients to ask a simple question when reviewing their own process: if a candidate's experience certificate referenced a company that did not actually exist, would the current hiring workflow catch it before an offer is made?
In Summary
Reports of this case describe employment fraud operating at an organised, large scale, sustained long enough for tens of thousands of certificates to reach hiring desks. Whatever the exact final figures, the pattern it illustrates is one we encounter regularly in our own screening work: a document referencing employment is not the same as confirmed employment. Genuine employment verification, as practiced through ProQuest's background verification services, exists specifically to close that gap, by checking the employer's existence, sourcing contact information independently, and testing the internal consistency of what a candidate has claimed.
FAQ's
Q. Is this kind of certificate fraud still a documented risk today?
Ans. Cases of fabricated experience certificates continue to be reported periodically, and we continue to encounter attempts of this kind in our own verification work, which suggests the underlying risk has not disappeared even where individual schemes have been shut down.
Q. Can a fraudulent certificate look identical to a genuine one?
Ans. Yes. A well produced certificate can be visually indistinguishable from a legitimate one, which is why verification relies on checking the underlying facts rather than the document's appearance.
Q. What is the most basic step in verifying an experience certificate?
Ans. Confirming that the named employer is an actual operating business, independent of any contact details supplied on the certificate itself.
Q. Does employment verification guarantee fraud will never occur?
Ans. No single process eliminates risk entirely, but independent verification substantially reduces the likelihood that a fabricated employment history goes undetected.
Q. Why do larger hiring volumes increase exposure to this kind of fraud?
Ans. Higher volume means more opportunities for a fraudulent document to pass through an under-resourced or surface level review process unnoticed.