We came across a background check that’s hard to forget.
One candidate. 161 companies over eight years. At her peak, she was simultaneously employed at 10 organizations — enterprises, startups, MNCs, across sectors and cities. The timeline tells the story starkly: she joined 50 companies during the remote work boom of 2020, added 21 more in 2021, and kept building from there.
None of these were small, informal arrangements. These were real organizations with real onboarding processes, real payrolls, and real confidentiality agreements — all of which she was technically a part of, all at once.
Here’s the part that matters most for employers: almost every company that hired her ran a background check. And almost every one of those checks missed her. Because most employment verification is designed to confirm one job at a time. Nobody was looking at the full picture.
That’s the core problem with moonlighting fraud. It doesn’t hide inside a single check. It hides in the gaps between them.
Why Moonlighting Became a Structural Issue, Not a Fringe One
Moonlighting — holding more than one job simultaneously without disclosing it — isn’t new. What changed is the infrastructure that makes it easy.
Remote work and hybrid models removed the physical constraints that previously made dual employment difficult to sustain. When attendance was visible, geography mattered, and office hours were fixed, working two full-time jobs simultaneously required a level of coordination that limited how widely it could happen. Once work moved behind a screen and schedules became flexible, those natural checks disappeared.
The numbers reflect this. A four-times jump in dual employment investigations was recorded after 2019 as companies began noticing the pattern. And the discrepancies, when they surface, almost always show up in the same place — employment checks, not education or identity.
Moonlighting fraud sits in a specific category here: it’s not a candidate who lies about a single employer or inflates a job title. It’s a candidate — often a capable, experienced professional — who is simply working for multiple organizations simultaneously, in breach of their employment contract, without telling any of them.
What Moonlighting Fraud Actually Costs
The conversation around moonlighting tends to get stuck on productivity — the assumption that someone working two jobs can’t be fully present at either. That’s a real concern, but it undersells the actual risk profile.
Confidentiality and IP exposure is the more serious issue. An employee with access to proprietary systems, client data, unreleased product roadmaps, or pricing strategies — who is simultaneously employed by a competitor or adjacent business — creates a leak risk that is difficult to quantify and nearly impossible to remediate after the fact. Most employment agreements have single-employer and non-compete clauses precisely because of this. Moonlighting, by definition, puts those clauses in breach.
Conflict of interest compounds this. In sectors like BFSI, consulting, and technology, the overlap between what a person knows and who else they’re working for can create situations where their interests are structurally misaligned with yours — without anyone having made a deliberate decision to act against you.
Liability and compliance exposure is a quieter but growing concern. As employment law around dual employment and gig work continues to evolve in India, organizations that can demonstrate they had verification processes in place are in a meaningfully better position than those that simply didn’t check.
Why Standard Checks Don’t Catch It
This is the part HR teams often find frustrating when moonlighting fraud surfaces: the candidate passed verification. A reference was confirmed. An employer was contacted. The check came back clean.
The reason standard employment verification misses moonlighting is structural. A typical employment check is designed to validate one role — confirm the dates, the title, the exit status. It answers “did this person work here?” It doesn’t ask “what else were they doing at the same time?”
When a candidate lists their primary employer and that employer confirms the details, the check is considered complete. The three other companies running payroll for the same person during the same period don’t appear anywhere in that report.
This is why moonlighting fraud is uniquely suited to surviving conventional background screening. It’s not about falsifying a document or creating a fake employer. The information the candidate provides is often technically accurate — it’s just deliberately incomplete.
What Employers Can Actually Verify
The shift that changes this is moving from point-in-time verification to timeline verification.
Instead of confirming whether a candidate worked at Company A between these dates, an Employment History Check reconstructs the full employment timeline — and looks for what doesn’t fit. Overlapping tenures. Concurrent employment at multiple organizations. Gaps that don’t match the narrative in the resume. PF contribution records that show multiple employers crediting into the same account during the same period.
UAN-based verification — using the Universal Account Number linked to EPFO records — is one of the most reliable signals available for this. Because PF contributions are tied to actual payroll, not just to what a candidate chooses to disclose, concurrent employment often leaves a trace in EPFO data that a candidate has no easy way to scrub.
This doesn’t catch everything. Not every employment relationship generates PF contributions — particularly short-term contracts, freelance arrangements, or roles that fall below the threshold. But it closes a significant portion of the gap that standard verification leaves open, and it shifts the check from “what did they tell us?” to “what does the record show?”
The candidate in our opening — 161 companies, 10 simultaneous employers — would not survive an Employment History Check. The overlaps alone would surface immediately.
The Hiring Context Where This Matters Most
Moonlighting fraud isn’t evenly distributed across industries or roles. It concentrates where three conditions overlap: remote or hybrid work arrangements, access to sensitive information or systems, and roles where output is measured asynchronously rather than through real-time presence.
That profile covers a large portion of white-collar hiring in India today — technology, consulting, financial services, product, research, legal, and operations functions where work-from-home is still standard for part of the week.
If you’re hiring at scale into any of these functions, or managing a distributed team where you can’t directly observe output rhythms, the verification gap is worth closing — not as a mistrust signal toward candidates, but as a basic accountability structure that protects the organization and everyone in it who’s playing by the rules.
The honest reality is that most people are not running 161-company moonlighting operations. But the ones who are can do significant damage, and the verification tools to catch them exist. The question is whether the process is designed to use them.
OnGrid’s Employment History Check is built to surface overlapping tenures, undisclosed concurrent employment, and timeline inconsistencies — giving hiring teams the full picture, not just a single-job confirmation.
Leave a Reply