Explainer

Your Boss Is an Algorithm: Inside the Gig Economy's Invisible Manager

For millions of gig workers, the manager is not a person but a system — one that hires, ranks, pays and fires without ever explaining itself. Here is how the invisible boss works.

Somewhere in your city right now, a delivery rider is staring at a phone, waiting for the next ping. When it comes, they will not be told who decided to send it, why the payout is what it is, or how to argue if it feels wrong. There is no shift supervisor to catch in the corridor, no manager whose door they can knock on. The manager is algorithmic management — software that assigns the work, sets the pay, ranks the worker, watches every movement, and, on a bad day, switches the account off. It is the most consequential boss most gig workers will ever have, and it does not have a face.

I’ve spent a long time tracing a single pattern in how technology reshapes power, and gig work is where you can see it in its cleanest, cruellest form. A tool arrives promising freedom. Quietly, it keeps the control. That’s the move, and once you learn to spot it you cannot unsee it. So let me walk through what algorithmic management actually is, how it feels from the seat of a scooter or the driver’s side of a hatchback, why it is sold to us as flexibility, and — the part that matters most — what pushing back actually looks like.

What algorithmic management actually is

Strip away the app-store gloss and a gig platform is doing exactly what a traditional employer’s middle management once did. It is just doing it in code, at scale, and mostly in the dark. Break the manager’s job into its parts and you can see the software has quietly absorbed every one of them:

  • Assigning work. The algorithm decides which rider gets which order, which driver gets which trip. Accept too few and your future offers may thin out. That’s dispatch, automated.
  • Setting pay. Fares and delivery payouts are calculated per task by a pricing engine that can shift with demand, distance, time of day, and factors the worker never sees. The number simply appears. There is no negotiation and often no itemised breakdown.
  • Ranking and rating. A running score — built from customer stars, acceptance rates, cancellations, on-time percentages — sits over every worker. That score is not cosmetic. It gates access to the better-paying work and, past a threshold, to any work at all.
  • Monitoring. Location, speed, route, screen taps, how long you take at a restaurant, whether your phone moved when it should have — all of it is logged continuously. The workplace is a data stream.
  • Discipline and firing. When the numbers drop below a line, the account gets “deactivated.” No meeting, no notice period, often no human on the other end. The livelihood ends with a push notification.

Put those together and you have a complete manager. What’s missing is everything that used to make management accountable: transparency about the rules, a person who can explain a decision, and any real route to appeal. The system decides; the worker complies or drifts out of the flow of work. This is not a bug in how these platforms are built. It is the design.

How it feels from the worker’s side

Read the platform’s marketing and you’d think a gig worker is a free agent choosing their own hours. Sit with the daily reality and it looks very different. Riders and drivers describe a working life shaped by four pressures that a salaried employee would never accept.

Incentives that move under your feet

One week a set of trips pays a certain rate; a bonus is dangled for completing a run of deliveries by a cut-off. The worker organises their whole day around it. The next week the target has crept up or the bonus has thinned, and the earnings that felt reliable are gone. Reports from gig workers across Indian cities describe exactly this — the sense that the ground keeps shifting, that the harder you chase the number the further it moves. Because the pay logic is opaque, you can never quite tell whether you’re being rewarded or quietly squeezed. You just pedal faster to stay level.

The system decides; the worker complies or drifts out of the flow of work. This is not a bug. It is the design.

A rating you can’t see the inside of

The score is the whip. A handful of one-star ratings — for a cold meal the rider didn’t cook, for traffic they couldn’t clear, for a customer who was simply having a bad day — can drag an average down far enough to matter. And the worker rarely gets to see why, or to contest a single rating. They only see the consequence: fewer good offers, longer waits, the slow starvation of their access to work. When your income depends on a number you cannot audit, every interaction carries a small dread. You are always being marked, never shown the marking scheme.

Being watched the entire shift

Traditional jobs have breaks, blind spots, moments the boss isn’t looking. Algorithmic management closes those gaps. The tracking is constant and granular, and the worker knows it, which changes behaviour in the way all surveillance does — you self-police, you don’t stop, you treat every minute as measured because it is. The freedom to be unobserved, which is most of what “flexibility” should mean, is precisely what’s taken away.

Deactivation without a face

The sharpest edge is the ending. Workers describe accounts being frozen or deactivated with little explanation — flagged by fraud-detection systems, or dropped below a performance line, or caught in an error no human reviewed. For someone whose rent depends on that account, this is being fired. But there is no manager to plead with, no HR, often only an in-app help form that answers in templates. The relationship was intimate enough to track your every move and impersonal enough to end without a word. That asymmetry — total visibility of the worker, total opacity of the system — is the whole story in miniature.

Why “flexibility” is the bait

Here is where the pattern I keep returning to snaps into focus. Every one of these platforms leads with the same promise: be your own boss, work when you want, nobody’s watching over you. Flexibility is the pitch, and it isn’t entirely a lie — the ability to log in around a class, a second job, a child, is real and valuable to many workers. But look at what’s handed over and what’s held back.

The worker gets flexibility over one thing: when to make themselves available. The platform keeps control over everything that determines whether that availability is worth anything — what you’re paid, which jobs you’re offered, how you’re ranked, and whether you keep working at all. Flexibility over your schedule; total control over your economics. You’re free to choose your hours and unfree in every way that touches your income.

That’s the capture move, and it’s the same one I’ve traced everywhere technology remakes work. A tool arrives dressed as liberation and quietly retains the levers of power. I’ve written before about how technology gets captured — the recurring pattern where a genuinely useful innovation is structured so that its benefits flow up and its risks flow down. Gig platforms are the textbook case. The flexibility is real enough to recruit you and marginal enough to cost the company nothing. The control is the part that makes the money, and that’s the part they never share.

Ask the three questions I always come back to. Who takes the value? The platform, through its cut of every fare and its command of the pricing engine. Who pays the cost? The rider, in fuel, in vehicle wear, in unpaid waiting time, in the risk of a sudden deactivation. And who gets to fight back? Under pure algorithmic management, almost nobody — which is exactly why the answer to that last question is where all the interesting action is.

What pushing back looks like

The hopeful part of this story is that the faceless manager turns out to be far from all-powerful. Around the world, and increasingly in India, gig workers are refusing the premise that a piece of software gets to be an unaccountable boss. The pushback runs along four tracks, and the strongest results come when they reinforce one another.

Collective organising

The oldest tool still works. When riders coordinate — through unions, informal messaging groups, or app-off strikes during peak hours — the individual worker’s powerlessness against the algorithm becomes a collective bargaining position the platform can’t ignore. India has seen delivery and ride-hailing workers organise around exactly the grievances above: opaque pay changes, arbitrary deactivations, the erosion of per-order rates. A single rider can’t argue with a dispatch algorithm. Ten thousand riders declining to log in on a Friday night is a language the system understands. The algorithm is designed to manage individuals; solidarity is the one input it wasn’t built to handle.

Regulation with teeth

The law is beginning to catch up with the fiction that these workers are pure independent contractors owed nothing. India’s move to bring gig and platform workers into a social-security framework, and various state-level efforts around welfare and fairer treatment, point toward a floor beneath the algorithm — the idea that whoever the boss is, worker or not, some protections don’t switch off just because the manager is software. Good regulation here isn’t about banning the technology. It’s about insisting that automated authority carries the same duties any other authority would: notice, reasons, a way to appeal.

Transparency and the right to an explanation

A quieter but crucial demand is simply the right to understand the machine you work for. If an algorithm sets your pay, you should be able to see how. If a score gates your access to work, you should be able to see it and challenge it. If you’re deactivated, a human should review it and tell you why. None of this dismantles the platform model; it just drags the hidden manager into the light where it can be held to account. Opacity isn’t a technical necessity — it’s a choice that happens to favour the house. Forcing transparency is how you take that advantage back.

The algorithm is designed to manage individuals; solidarity is the one input it wasn’t built to handle.

Owning the algorithm outright

The most radical answer changes who the algorithm works for in the first place. If the software is going to run the show, why shouldn’t the workers own the software? That’s the premise of platform cooperatives — driver- and rider-owned platforms where the surplus flows back to the people doing the work and the rules of the algorithm are set by them, not extracted from them. It’s harder to build and slower to scale than a venture-funded app, but it resolves the capture at its root. When the workers own the manager, the manager can’t be turned against them. The faceless boss becomes accountable because it finally belongs to someone who has to answer for it.

None of these tracks is a silver bullet, and it would be dishonest to pretend the fight is close to won. But the history of workers facing down a new and seemingly unbeatable form of power should give us some nerve. I keep coming back to how India’s farmers won — a movement that looked hopelessly outmatched against entrenched interests and prevailed through sheer organised persistence. The lesson travels. Concentrated power looks permanent right up until enough people decline to accept it.

The manager was always a choice

The thing to hold onto is that there is nothing natural or inevitable about any of this. An algorithm assigning work, setting pay, and firing people without explanation is not a law of physics — it’s a set of decisions someone made, in a boardroom, in favour of a particular distribution of power. The same technology that runs an opaque, extractive manager could run a transparent, accountable, worker-owned one. The code doesn’t care. The people who write it, and the people who tolerate what it does, are the variable.

So the next time you see a rider waiting for a ping in the rain, understand what you’re looking at. Not a free agent enjoying their flexibility, but a worker managed by a machine they can’t see into, sold a small freedom in exchange for a large surrender of control. That trade was designed. And anything that was designed can be redesigned — by workers organising, by laws that insist on fairness, by transparency that ends the secrecy, and, most durably, by workers coming to own the very algorithms that manage them. The boss is software now. The question that decides everything is simply: whose software, and answerable to whom?

Kenney Jacob is the author of Captured, a history of who takes, who pays, and who fights back.

Frequently asked questions

What is algorithmic management?

The use of software to do the work a human manager once did — assigning tasks, setting pay, monitoring performance, ranking workers and even ending their access to a platform — often with little transparency and no one to appeal to.

How does algorithmic management affect gig workers?

It can mean shifting pay and incentives, opaque ratings that decide who gets work, constant tracking, and deactivation without a clear reason or a person to challenge. Flexibility is offered up front while a great deal of control is quietly retained by the platform.

Can workers push back against an algorithmic boss?

Yes, though it is hard. Collective organising, transparency and gig-work regulation, and worker-owned platform cooperatives are the main routes — all aimed at giving workers a say in the system that governs them rather than only being governed by it.

← All articles