The conversation about moonlighting in Indian IT has been running, in various intensities, since Wipro terminated 300 employees for undisclosed dual employment in 2022. For three years, the discourse has been driven primarily by corporate statements, anecdotes, and pundit opinion. Hard data on prevalence has lagged.
In 2025, that began to change. A combination of background verification industry analyses, employee survey data, and academic research has produced a clearer picture of what is actually happening in Indian IT employment relationships. The picture is more concerning than most leadership teams have publicly acknowledged — and the operational implications are sharper than the policy statements have addressed.
The Prevalence Picture
Several recent data points are worth examining together.
Randstad India’s research suggests a 25–30% increase in moonlighting activity across the IT sector over the past three years. The methodology aggregates self-reported moonlighting in surveys with secondary indicators from employer disclosures and industry reporting.
Cutshort, a tech recruiting platform, surveyed 3,000 tech professionals in 2023 and found that approximately 23% had moonlighted at some point, with 7% actively moonlighting at the time of the survey. The survey was anonymous, which addresses some of the typical underreporting concern with sensitive employment behaviour.
Indeed India’s research identified the primary drivers as low salaries relative to workload, rising inflation impact on real wages, post-pandemic job insecurity that motivated income diversification, and entrepreneurial ambition expressed as side projects.
The most operationally relevant data, however, comes from background verification industry analysis. AuthBridge’s Workforce Fraud Files 2025, analysing background verification data from October 2024 to March 2025, found:
- A 9.46% overall discrepancy rate in the IT/ITES sector
- A 6% discrepancy rate among white-collar hires more broadly
- Among the most common findings: inflated job titles, exaggerated tenures, and employers that could not be verified
The discrepancy rate in IT/ITES is approximately 1.5x the broader white-collar baseline. Translated into operational terms, nearly one in every five candidates entering an IT or ITES role has misrepresented some material aspect of their professional history.
The Drivers Are Structural, Not Episodic
Understanding why moonlighting has expanded requires understanding the structural drivers, not just the policy environment.
Wage compression in Indian IT. The pandemic-era hiring boom drove substantial salary increases at the top of the market — particularly for in-demand specialisations — but the median IT employee in 2026 is operating in a real-wage environment that has not kept pace with cost of living increases, particularly in major metro markets like Bengaluru, Mumbai, and Hyderabad.
Remote work normalisation. The pre-pandemic moonlighting market was constrained by the practical impossibility of physically being in two offices simultaneously. The post-pandemic remote work norm in IT has eliminated that constraint. A skilled developer can credibly hold two full-time roles, executing both, with neither employer in a position to physically observe the conflict.
Platform proliferation. Freelance and contract platforms — Upwork, Toptal, Fiverr, and dozens of Indian-specific platforms — have made secondary engagement easy to find, easy to monetise, and easy to keep informal. The infrastructure for moonlighting has matured dramatically.
Entrepreneurial culture. Indian IT has a strong startup-adjacent culture in which side projects, advisory engagements, and bootstrapped ventures are aspirational. The line between “personal interest project” and “secondary employment” is genuinely ambiguous, and the cultural norms tend to give the employee the benefit of the doubt.
The legal grey area. Indian labour law does not clearly prohibit moonlighting for IT professionals. Section 60 of the Factories Act, 1948 prohibits same-day dual employment in factories but does not extend to IT or supervisory roles. State-level Shops and Establishments Acts vary widely, and several were written before remote knowledge work existed. The legality of moonlighting in India rests almost entirely on employment contracts and company policy — which means detection, not statutory law, determines enforcement.
These drivers are not going away. The wage compression is structural. Remote work is the norm in IT. Platforms continue to expand. Cultural norms favour flexibility. The legal framework is unlikely to clarify quickly. The conditions that have driven moonlighting growth will continue to drive it.
Why Companies Care: The Business Case for Detection
The corporate concern about moonlighting is sometimes framed dismissively — as an outdated insistence on exclusive employment, or as paranoia about productivity. The actual business case is more substantial.
Productivity dilution. An employee holding two full-time roles is not bringing full attention to either. The first-order productivity loss is real and measurable in delivery quality, response times, and engagement metrics.
Confidentiality and IP risk. Moonlighting at a competitor — or at a client of the primary employer — creates direct exposure to confidentiality breaches, intellectual property leakage, and conflict-of-interest situations. The risk is not theoretical; documented cases of code, design assets, and client information moving across moonlighting relationships are a recurring feature of IT industry incident reporting.
Data security exposure. Employees with system access at multiple organisations create attack surfaces that security teams cannot effectively manage. The likelihood of credential compromise, accidental data leakage, or deliberate exfiltration rises substantially.
Compliance breaches. Many client contracts in IT services include exclusivity provisions — the IT services firm warrants that personnel assigned to the client’s engagement are not simultaneously working for competitors or in conflicting capacities. Moonlighting personnel can put the IT services firm in breach of those provisions, with significant commercial consequences.
Tax and regulatory complications. Moonlighting income creates tax obligations that are often unmet. The Indian tax authorities have been increasing scrutiny of multiple-source income that does not appear in employment reporting. Where moonlighting surfaces in tax investigations, it can pull the primary employer into the regulatory scope.
These risks are not equally distributed across the workforce. They are concentrated in roles with system access to sensitive data, roles assigned to client engagements with exclusivity provisions, and roles in competitive market segments where moonlighting at a competitor is plausible. A serious moonlighting governance programme prioritises monitoring in these higher-risk segments.
The Detection Gap
Despite the substantial business case for detection, the practical detection capability of most Indian IT employers has been limited. Several gaps account for this.
Pre-employment verification doesn’t catch moonlighting. BGV at the point of hire confirms what happened before — past employment, qualifications, criminal record. It does not confirm what happens after. An employee whose pre-employment verification is clean can begin moonlighting on day two of employment without triggering any verification signal.
Annual disclosures are weak. Where companies have implemented annual conflict-of-interest declarations, the practical signal value has been low. Employees engaged in undisclosed moonlighting are unlikely to disclose it on a form. The declarations function more as a procedural protection for the employer than as a detection mechanism.
Manager observation is inconsistent. In remote work environments, the indicators of moonlighting that managers might once have noticed — physical absence, distraction, late hours — are obscured. Some indicators do remain (avoiding in-person meetings, reluctance for shift rotations, defensive posture about work patterns) but they require active management attention to register.
Tip-offs are unreliable as a detection mechanism. Many incidents that surface do so through tip-offs from co-workers, ex-employers, or — increasingly — automated alerts from EPFO matching showing PF contributions from multiple employers. But relying on tip-offs as the primary detection channel means most cases never surface at all.
The detection environment has been changing in 2024 and 2025. EY India has built tools that identify moonlighting through public-source databases and social media analytics. Specialist BGV providers have introduced continuous monitoring services that re-verify employment status periodically. Internal HR analytics tools have started incorporating moonlighting-relevant signals into dashboards. The capability exists. The deployment has been uneven.
The Cultural Complication
A useful detail to acknowledge is that the moonlighting issue in Indian IT is genuinely contested at a cultural level. Randstad’s 2023 research found that nine in ten Indian employees said an employer was “much more attractive” if it permitted additional work. Swiggy’s industry-first moonlighting-friendly policy in 2022 was widely praised by employees. Public commentary from professionals frequently frames anti-moonlighting policy as outdated paternalism.
The corporate response has split. Some major IT services firms maintain strict prohibition. Others have introduced explicit permission-with-disclosure frameworks, requiring employees to formally declare and obtain approval for secondary engagement. A few have moved toward fully permissive policies for non-conflicting work.
The data suggests that strict prohibition without competitive compensation may push concealment rather than transparency. The companies managing this most effectively pair clear governance with fair opportunity and open dialogue, creating environments where employees see disclosure as the path of less resistance rather than the path of greatest risk.
This cultural complexity is part of why pure detection-and-discipline approaches have not solved the moonlighting problem. The detection capability matters. So does the policy framework that determines what gets detected and what happens next.
What the Numbers Mean Operationally
For Indian IT leadership in 2026, the prevalence picture suggests a few operational priorities.
The verification programme needs continuous capability. Pre-employment verification remains essential but is not sufficient. Continuous monitoring — periodic re-verification of employment status, AI-driven pattern detection on work behaviour, integration with regulatory data sources — is the architectural addition required to address the moonlighting reality.
Policy must be paired with detection. Anti-moonlighting contractual provisions without operational detection capability create the appearance of governance without the substance. Conversely, detection without clear contractual basis creates signal that cannot be acted on.
Differentiation by role risk matters. Universal monitoring is expensive and may damage trust. Targeted monitoring of higher-risk roles — those with sensitive system access, client exclusivity provisions, or competitive proximity — concentrates investment where it matters most.
Transparency about the framework helps. Employees who understand that their employer monitors for moonlighting and how — and what the consequences are — are less likely to engage in concealed dual employment than employees who perceive monitoring as covert and arbitrary.
The moonlighting question is not going to be settled by Indian labour law in the near term. It will be settled by employment contracts, corporate policy, and operational detection. The companies that take this seriously in 2026 will look meaningfully different from those that don’t.
AMS Inform provides background verification and continuous workforce screening services across India and 160+ countries globally. For organisations strengthening their anti-moonlighting verification frameworks, speak to our team at AMSinform.com.
