Moonlighting: When Workers Reclaim Their Hours, Employers Call It Theft

An engineer finishes her sprint, clears her queue, closes the laptop at seven, and then opens a different one to build something for a client of her own. Depending on who is describing it, she has just demonstrated initiative or committed fraud. The argument over moonlighting in India is stuck between those two readings, and it has been since remote work made the second laptop invisible. I want to separate the parts of that argument that are about real harm from the parts that are really about control — because they are not the same thing, and conflating them has cost people their jobs.

Let me say clearly at the start what this piece is not: it is not legal advice. Whether a particular second engagement is permitted depends almost entirely on the particular contract that person signed, the sector they work in, and facts I cannot see from here. Anyone with real stakes should read their own agreement and talk to a lawyer. What I can do is describe the shape of the dispute, because the shape is where most of the confusion lives.

How a quiet practice became a public fight

Second jobs are not new in India. Teachers have tutored, accountants have kept small sets of books, musicians and photographers and writers have always had a day job holding up the rest of their life. Nobody convened an ethics debate about any of it. What changed around 2022 was that white-collar work went home, and the supervision that used to happen by line of sight stopped happening at all.

The flashpoint came from the IT services industry. The chairman of one of the country’s largest software firms called the practice cheating, plainly and publicly. Other large firms followed with internal reminders that dual employment breached their terms, and there were widely reported terminations — one firm stated it had let go of a few hundred people on those grounds. Surveys at the time suggested a large share of IT employees personally knew someone doing it, which tells you the practice was not marginal.

But the industry did not speak with one voice. A consumer internet company published a policy that explicitly permitted outside projects, subject to disclosure and a check for conflict. At least one large services firm said it would look at framing something similar, tied to whether people were meeting their delivery norms. A union minister weighed in on the side of employees, roughly to the effect that companies should not be capping people’s ambitions. Four years on, the split has settled rather than resolved: some employers permit outside work with prior disclosure, most of the big services companies still prohibit it outright.

That split matters, because it demolishes the claim that this is a settled question of ethics. If moonlighting were simply theft, the companies that permit it under a disclosure policy would be institutionalising theft. Obviously they are not. What they have done is draw the boundary of employment in a different place.

What the legal position actually looks like

Here is where the public conversation goes wrong most often. People want a single answer — is it legal or not — and there isn’t one. With the usual caveat that this is general description and not advice, the position as I understand it runs roughly like this.

There is no blanket statutory ban on a private-sector employee in India holding a second engagement. What there is instead is a patchwork. Factory legislation restricts an adult worker from being employed in more than one factory on the same day, which is a workplace-safety provision written for shifts on a shop floor and does not transpose neatly onto a product manager working from a flat in Kochi. Standing orders and their state-level amendments can restrict dual employment for the categories of workers they cover, which in practice excludes a great many software professionals. Government service has its own rules entirely. None of this adds up to a general prohibition on evening work.

The real restriction, for most people reading this, is contractual. Exclusivity clauses are extremely common in Indian employment agreements — language committing you to devote your whole working time to the employer, not to engage in any other business or employment, not to take outside work without prior written consent. Indian courts have generally been willing to enforce restrictions that operate during the term of employment, which is a different question from post-employment non-competes, where the position is far less friendly to employers. If your contract says you need written permission and you didn’t ask, you are in breach of contract whatever you think of the clause. That is the blunt practical answer.

The more interesting pattern is what disputes have tended to turn on when they are actually litigated or arbitrated. From the reported material, the centre of gravity is not the mere existence of a second job. It is conflict of interest, misuse of the employer’s resources or confidential information, competing with the employer, concealment where disclosure was required, and demonstrable prejudice to the business. In other words, the question courts have gravitated towards is closer to what did you actually do to your employer than where were you at nine in the evening. I would not push that observation further than it can bear — outcomes are fact-specific, one clause can decide a case, and I am not going to claim a tidy doctrine exists where there is mostly a scattering of decisions and commentary. But the direction of travel is worth noticing, because it is not the direction the ethics rhetoric assumed.

The question that decides these disputes is closer to what did you actually do to your employer than where were you at nine in the evening.

The employer concerns that deserve a straight answer

It would be lazy to treat every employer objection as pretext. Several are serious, and anyone arguing for a worker’s right to a second project should be able to meet them without flinching.

• Client confidentiality. An IT services business runs on other people’s data and other people’s contractual promises. If an engineer with access to a bank’s systems is also working for someone else, the employer carries a risk it did not agree to carry and often cannot even describe to its client. That is a real exposure, not a feeling.
• Direct competition. Building the same product for a rival on the side is not a boundary dispute. It is a straightforward conflict, and no reasonable framing of employee autonomy protects it.
• Use of the employer’s resources. The company laptop, the company VPN, the company’s licensed tools, the company’s hours. Second work done on the first employer’s time and equipment is a different act from second work done on your own.
• Fatigue. Someone working seventy hours across two commitments will eventually deliver worse work to both, and the employer is entitled to care about capacity it is paying for.
• Concealment. Where a contract requires disclosure, hiding the engagement damages trust independently of whether the engagement itself was harmful.

Every one of those is answerable with a disclosure-and-conflict-check policy. That is precisely what the firms that permit outside work have built. None of them requires a blanket ban, and none of them requires the claim that an employee’s evenings belong to the company.

The claim underneath the claim

Which brings me to what I think this fight is actually about. A salary buys agreed hours and agreed duties. Nobody disputes that. The argument that a salary also buys your remaining capacity — your evenings, your weekends, your skills when nobody is paying for them, your right to be economically useful to anyone else — is a far larger claim, and it is being made mostly by implication rather than out loud.

Notice that the word chosen was cheating. Not breach, not conflict, not risk. Cheating is the language of an exclusive relationship, and it only makes sense if the underlying assumption is that all of you, not a defined portion of your time, has been bought. That assumption survived for years only because it was never tested. In an office, you were visibly present for your hours and invisibly off-duty after them, and neither side had to state what was being purchased. Remote work removed the visibility, and with it removed the polite ambiguity. The moment the employer could not see you, it had to say what it actually claimed over you — and what came out was much broader than most employment contracts had ever needed to argue for in public.

A salary buys agreed hours and duties. The claim that it also buys your evenings and your remaining capacity is a much bigger claim, and remote work is what forced it into the open.

This is the same boundary being contested everywhere in modern work, just under different names. It is what quiet quitting was actually about: not refusing to work, but refusing the unpaid extra that had quietly become the baseline. It is what campaigns for the right to disconnect are trying to codify — the idea that off-hours are a thing that legally exists. And it is why the response to remote work was so often bossware, keystroke logs and screenshot timers rather than output measurement, because the thing being defended was never really the deliverable. It was the claim on the person.

There is a pattern here that runs well beyond employment law, and I have written about it at length in how technology gets captured: a technology arrives with an obvious liberating use, and the fight that follows is not about the technology but about who gets to keep the surplus it creates. Remote work handed employees back their commute, their autonomy over the day, and the practical ability to sell spare capacity. Almost immediately, a serious effort began to reclassify all three as things they had been given by permission rather than things they had won.

Where I land

I do not think employees get to hide a second engagement when their contract requires them to disclose it, and I do not think anyone should defend moonlighting for a direct competitor or on a company machine. Contracts mean something, and the person signing one should read the exclusivity clause before assuming their evenings are their own.

But the honest policy position is not difficult. Require disclosure. Check for conflict of interest and for client-confidentiality exposure. Say no when there is one, in writing, with a reason. Say yes when there is not. Measure people on their output during the hours you pay for, which you should be doing regardless. That framework protects everything an employer can legitimately claim while conceding the thing an employer should never have claimed — that the hours it does not pay for are still, somehow, its property.

Until a firm is willing to say that second part out loud, it should stop calling the alternative cheating.