Gig Economy vs IT Jobs: Which Exploits You More?

2 AM. A Zomato delivery guy named Ramesh is parked outside a building in Koramangala, Bengaluru. His phone shows a 2.1 rating from last week when a customer marked the order late. He wasn't late. The restaurant was. The algorithm doesn't care who was late. His incentive payout for the month has already dropped because of it. He takes another order.

Two floors up, a senior software engineer at a mid-sized product company is on a call. The sprint is behind. The client is in a different timezone. It's a "quick sync." It won't be quick. He opened his laptop at 9 AM. It is now 2 AM. He has not logged overtime because the company doesn't have that concept. He is a salaried professional. He is, by every visible marker, doing well.

Same exhaustion. Different costume. Different story each of them tells himself about why he is still awake.

Section 1: How the Gig Economy Exploits

The gig economy in India is not a new phenomenon with a few rough edges. It is a system built on the deliberate removal of accountability. The companies at the top, Zomato, Swiggy, Ola, Uber, Urban Company, have built billion-dollar valuations on the back of workers they legally don't employ.

That legal distinction is the entire architecture of exploitation. Because Ramesh is a "delivery partner" and not an employee, Zomato owes him nothing. No provident fund. No gratuity. No sick leave. No accident insurance that actually pays out. No minimum wage guarantee in a bad month. The relationship looks like freelancing. It functions like bonded labor with a ratings dashboard.

In 2022, Zomato and Swiggy both faced significant backlash after delivery workers in multiple cities organized informal strikes over slashed incentive structures. The companies had, over several months, quietly reduced per-delivery payouts while increasing the distance thresholds required to earn bonuses. Workers who had joined on the promise of earning Rs 25,000 to 30,000 a month found themselves clearing Rs 12,000 to 15,000 for the same hours. There was no contract to violate. There was nothing to dispute.

Ola and Uber driver-partners have documented how surge pricing, which customers assume benefits drivers, often doesn't. The platform takes a larger cut during surge periods in many configurations. Drivers figured this out the slow way: by doing the math after years of driving.

The rating system deserves its own examination. It is presented as a quality control mechanism. It functions as a behavioral compliance tool. A delivery partner who declines orders too frequently gets deprioritized by the algorithm. One whose ratings dip below a threshold faces account suspension, which in this context means job termination without any of the legal protections that word implies. The customer who rates poorly because their food was cold, because the restaurant sealed the bag badly, has effectively fired a worker. They will never know this. The worker knows it with every delivery.

Urban Company service professionals, who book appointments through the platform for plumbing, cleaning, beauty services, have reported similar patterns. Platform fees have increased over time. Cancellations by customers hurt the professional's metrics. Disputes about damaged goods or unpaid invoices go through a resolution process where the platform is simultaneously judge and financially interested party.

The gig economy is not capitalism with rough edges. It is a system that deliberately offloads all risk onto the worker while retaining all pricing power for the platform. The worker provides labor, uses their own vehicle, pays their own fuel, absorbs their own downtime, and gets paid per completed transaction. The platform provides an app and takes 20 to 30 percent of every transaction for doing so. If you designed this relationship from scratch to maximize extraction, you would design it exactly this way.

Section 2: How IT Exploits

The IT sector exploitation is harder to see because it wears better clothes.

The 70-hour work week became a public conversation in India after N.R. Narayana Murthy of Infosys made his statement in late 2023 suggesting young Indians should work 70 hours a week for national development. The statement was widely criticized. What was less discussed is that 70-hour weeks were already happening, quietly, across most mid-to-large product and service companies. Murthy didn't invent the culture. He just said it out loud.

Invisible overtime is the foundational mechanism. Salaried IT employees in India have no legal overtime protections under most employment contracts. The contract specifies a role, a compensation number, and vague language about "hours as needed." The "as needed" part is interpreted entirely by the employer. A 9-to-9 culture at a company doesn't show up on a payslip. It shows up as exhaustion, as missed family dinners, as the slow erosion of the person the employee was before they joined.

The bell curve performance review system, used historically at Infosys, Wipro, TCS, and many product companies, is a structural weapon. It requires a fixed percentage of employees to be rated below average regardless of the actual distribution of performance. In a team where everyone performed adequately, someone still gets a 3 out of 5, misses the promotion cycle, and is quietly told they need to improve. This is not performance management. It is a mathematical guarantee that a portion of your workforce feels inadequate every year. It suppresses salary costs, justifies attrition without severance, and creates perpetual anxiety that makes employees easier to control.

The moonlighting crackdowns of 2022 were revealing. Wipro fired 300 employees for working second jobs outside of office hours. Infosys issued stern warnings. The implicit message was clear: your employer owns your productive capacity, including the parts you're not being paid for. An employee who works 60 hours a week for a company and consults for two hours on weekends is apparently in breach of loyalty. The 60-hour company's claim on those remaining hours is somehow legitimate.

The EMI compliance trap is perhaps the most elegant piece of the system. A software engineer in Pune or Hyderabad earns a salary that sounds large in absolute terms and is genuinely comfortable relative to most Indian incomes. They buy a flat. They get a car loan. They take an education loan for an MBA they're not sure they needed. Within three years of their first job, their monthly obligations are structured so that losing employment means genuine crisis. The company doesn't force this. The system produces it reliably. A worker with a 40-lakh home loan and a school fee due in two months is not going to push back on an unreasonable deadline. He is going to take the call at 2 AM.

Section 3: The Key Difference

Ramesh knows he is being used. He is not confused about the nature of the transaction. He signed up to deliver food for money. The money got worse over time. The conditions were always precarious. He has no illusions about the company caring about him. He delivers food. He gets paid. The relationship is transactional and he knows it is transactional.

The software engineer two floors above him has been told a different story, and he believes it. He is "building a product." He is "part of a team." His company has a mission statement. There is a ping-pong table in the office. The onboarding deck talked about culture and values. He thinks of his identity as partially constituted by where he works. His LinkedIn says "Senior Software Engineer at [Company Name]" and he would feel the loss of that description as a personal diminishment, not just as a financial setback.

This is the key difference. The gig worker is being exploited and knows it. The IT worker is being exploited and has been given a narrative that makes the exploitation feel like participation.

The sociological term for this is false consciousness, drawn from Marxist theory but applicable well beyond it. It describes the condition where a person identifies with the interests of the system that extracts from them, rather than with their own material interests. The delivery worker has no false consciousness about Zomato. He is not rooting for Zomato to succeed. He is trying to make rent. The IT employee is often genuinely invested in the company's stock price, the company's product reviews, the company's public reputation. He has been absorbed into the institution's identity.

This distinction matters because it shapes what each person is willing to accept and for how long. The gig worker will strike, complain, switch platforms, organize informally, because he has no psychological investment in the platform's narrative about itself. The IT employee will stay in a bad situation for years because leaving feels like failure, because the sunk cost of the career path is enormous, because his sense of who he is has become entangled with where he works.

Section 4: Which Is Worse

The correct answer is the IT sector is worse. Here is why.

The gig economy exploits the body and the bank account. It is brutal and it is visible and it needs to be fixed urgently. But it does not colonize identity. The delivery worker retains the knowledge that he is separate from the platform, that the platform owes him more than it gives, that the arrangement is unjust. This clarity is a form of dignity, even inside the injustice. He can organize around it. He can feel righteous anger about it. Anger is useful. It points outward.

The IT sector exploits something harder to name and harder to recover from. It appropriates years of a person's life under the cover of career, and it does so with the employee's enthusiastic cooperation. The psychological mechanism here is what Leon Festinger described as cognitive dissonance reduction. When you have invested five years, a postgraduate degree, your social identity, your family's pride, and your financial stability in a career path, you cannot easily acknowledge that the path is extracting more from you than it returns. The mind will not tolerate that acknowledgment. So it makes the extraction feel like ambition. It makes the 2 AM call feel like dedication. It makes the forced bell curve feel like a fair meritocracy.

The sunk cost fallacy operates at scale in the IT workforce. The engineer who has spent eight years at a company and built his identity around the title, the stock options, the perceived prestige of the sector, is deeply resistant to the information that the deal was bad. Each year he stays, the evidence he would need to overcome to change his mind gets larger. He is not being held by chains. He is being held by the story he has been telling himself, and which the industry has been carefully telling him, about what his choices mean.

The status trap is the final layer. In Indian middle-class families, an IT job carries specific social weight. The salary makes parents proud. The designation sounds serious. The campus placement was competitive. To leave this and acknowledge it wasn't worth it, or that it damaged you, requires a kind of social bravery that most people cannot muster when every family dinner confirms the original story. The gig worker's family does not celebrate the Zomato uniform. There is no status to protect. There is only the money, and if the money isn't there, there's nothing to pretend about.

Physical exploitation heals, or at least it ends when the shifts end. Psychological exploitation that has been accepted as identity doesn't end when you quit. It follows you into the next job, and the one after that, because you have learned to perform the extraction on yourself.

The Zomato delivery guy at 2 AM knows he is being cheated. The software engineer at 2 AM thinks he is winning.

That is not a minor distinction. That is the whole game.