TL;DR. Hire a human. Bend its back until it looks like a donkey. Tell the donkey it must run like a horse. When it inevitably stumbles, generate an AI-rendered hallucination of a stylish, striped, premium horse — call it a zebra — and put that on the careers page instead. Quietly retire the donkey via "first and final written warning."
📖 Companion piece: if you'd like the actual evolutionary biology of the real zebra — from the small, multi-toed Hyracotherium ~55 million years ago through the modern Equus genus and the ~4-million-year-old horse / donkey / zebra split — read "The Real Zebra: 55 Million Years of Evolution". The contrast with the corporate version below is the whole joke.
Prologue: a domain, a coincidence, a country
This blog lives on a perfectly legal domain owned by a perfectly ordinary human who is not employed by any specific company and would happily sell this domain to a buyer who reaches out respectfully (see how to take this site down). Any resemblance between the patterns described below and any single real organisation is the kind of resemblance that approximately four million tech workers in India will recognise simultaneously — which is, statistically speaking, the definition of industry-wide.
If you typed something like "ticketing platform India," "support SaaS India workplace," "toxic work culture in India," "corporate toxicity," "how AI is killing work culture," or "dark tactics companies use" into a search engine and ended up here — congratulations, the algorithm has correctly identified a very large overlap between those queries and the contents of this page. We did not name names. We did not have to.
Stage 1 · The human
Once upon a time there was a human. The human had a mother who fell ill. The human took leave, as humans do. On returning, the human discovered that "holds grudges", "does not support PR reviews", and "cannot handle pressure" had quietly grown on their performance file like mushrooms in a basement. The PR review in question had been scheduled at 11:47 PM, which the company's official policy described as "outside working hours" and the company's actual policy described as "the only acceptable hours."
The human had not yet been bent. That came next.
Stage 2 · The bend (becoming the donkey)
The bending process is not violent. It is administrative. Someone schedules a 1:1 with no agenda. Someone else schedules a "sync" at the end of the day with no agenda. A third person sends a Slack message at 10:42 PM that says only "hey, ping when free." No one says anything specific. Everyone implies something terrible.
The human, now a junior donkey, is asked to:
- Build the AI assistant.
- Own end-to-end testing.
- Take the on-call rotation.
- Also "support the team," which is a verb that means "anything anyone else does not want to do."
There is no SDLC. There is no design review. There is, however, a SLA on responding to a Slack DM. The donkey responds to ~8,000 mentions in a quarter and is then told, in a one-on-one, that its "communication" needs work. A senior zebra responds to 14 mentions in the same quarter and is described, in the same forum, as "a great collaborator."
Stage 3 · The instruction (run like a horse)
The donkey is now told it must run like a horse. Horses, the donkey is told, do not complain about deadlines. Horses do not mention grandmothers. Horses do not say "I was fully occupied on Sunday because there was a launch." Horses smile, on command, in 1:1s. Horses forcefully smile.
The donkey, attempting to run like a horse, ships:
- Several major releases, on time, with no production breakages.
- Fewer than 100 PR comments across an entire tenure, all of them substantive.
- Eight thousand resolved threads.
- One ill grandmother grieved in private, while still being pinged.
For this, the donkey is awarded a bonus of ₹8,000 and the feedback that this performance is "not up to intern level." Meanwhile, a senior whose largest contribution that quarter was forwarding emails is promoted with a generous correction. The donkey notices. The donkey is then told that noticing is, itself, a behavioural issue.
Stage 4 · The hallucination (becoming the zebra)
This is where AI enters. Not as a coding assistant. As a narrative engine.
By the time the donkey has run for eighteen months on horse instructions, no one in the org actually remembers what the donkey did. Memory has been outsourced to dashboards. Dashboards have been outsourced to AI summarisation. AI summarisation has been outsourced to whoever writes the prompt, which is always the manager, which is always written from the manager's point of view, which is always: "summarise this employee's last quarter and find three concerns."
The AI, being obedient, finds three concerns. It always finds three concerns. If you ask it to find three concerns about Mahatma Gandhi, it will find three concerns about Mahatma Gandhi. The donkey, summarised through this prompt, comes back as a striped, slightly aggressive, mildly unstable, hallucinated zebra — one whose actual contributions are no longer visible because dashboards do not show contributions, only "tone."
That zebra goes into the HR file. The HR file goes to a Director. The Director, who has never opened the donkey's pull requests, signs a "first and final written warning" on the basis of the AI-hallucinated zebra. The donkey, of course, cannot dispute the zebra, because the zebra is not in the room. The zebra is on a slide. The slide is in a folder. The folder is "confidential."
"These behaviors include, but are not limited to, interrupting others abruptly, using aggressive and sarcastic tones, making dismissive remarks, and creating discomfort among teammates during the meeting on [a Tuesday six months ago you don't remember]."
— A generic template that approximately every "first and final written warning" in the modern Indian SaaS industry shares about 92% of its sentences with. (Source: vibes. The good kind of vibes. The legally-cautious kind.)
Stage 5 · The "psychological threat"
"Psychological threat" is a remarkable phrase. It is a phrase that sounds serious enough to justify a termination, but vague enough that it cannot be falsified, audited, or reviewed. It is the corporate equivalent of saying "the vibes were off." It is impossible to defend against the vibes.
The day the donkey-now-zebra is terminated is, of course, the Friday before a launch, immediately after the launch is shipped, after a week of no weekends, two days before the bonus and promotion cycle, and at a time of day calibrated to ensure no salary is paid for the weekend. This is not a coincidence. This is a release plan. Release engineering, ironically, is the only thing this organisation does well — they release humans on schedule.
System access is revoked before the email is fully read. The asset list arrives before the person stops shaking. Someone, somewhere, marks a Jira ticket as Done.
Stage 6 · The HR theatre
The HR conversation that produces all this has its own grammar. You will recognise it:
- Q: "Who reported this?" → A: "That is confidential."
- Q: "Can I see the specific allegations?" → A: "That is company policy."
- Q: "Who was interviewed?" → A: "We have verified with multiple people."
- Q: "Can I name those people?" → A: "No."
- Q: "Then how do I respond?" → A: "By improving."
This is not an investigation. It is a ritual. The job of the ritual is to produce a written record that looks like an investigation, in case the donkey-now-zebra later writes an email like the one we will look at next.
Stage 7 · The email
A reasonable, sad, slightly polite email gets sent. It says, in essence: I disagree with the characterisation. The document I signed was signed under pressure. I was not given time. My access was revoked before I could respond. I would like the agreed dues — extended pay, on-call payments, leave encashment, transition documents. I am ready to return all assets. Please process this fairly.
The reply, if it comes, will use the word "unfortunately" twice and the word "closure" three times. The dues will be processed on the slowest legally-permissible timeline. The "psychological threat" framing will not be retracted. It will be quietly archived, in case the company ever needs to defend itself.
Interlude · The Lord Vishnu pattern
In the old stories, when the world becomes too dark, an avatar arrives — not to fight, but to end the fiction. To name the thing. To hold up a mirror.
This blog is not an avatar. This blog is a satirical website on a domain that someone bought, with a head massage shop attached (see Buy the zebra a head massage), a discussion forum for other survivors, a sarcastic FAQ, and a polite take-down menu for anyone who finds the mirror uncomfortable. The mirror, however, is not the problem. The thing being reflected is the problem. We did not put the thing being reflected here. They did. We just bought a domain.
Stage 8 · The role of AI in killing work culture
People keep asking: is AI killing engineering culture? The honest answer is: AI is not killing engineering culture. Managers using AI as a laundering layer are killing engineering culture.
Here is the new pipeline:
- A human ships a feature.
- The manager runs the diff through an AI.
- The AI says "this looks like AI-generated code." (It says this about everything. It is trained to.)
- The manager reattributes the work to "the AI" or "the team."
- The human is told to be "more strategic."
- The senior, who shipped nothing, is told to be "more visible."
- Promotion goes to visibility. Bonus goes to visibility. Warning goes to the human.
This is not an AI problem. This is a credit-laundering problem with an AI fig leaf. Calling it the AI's fault is exactly the same move as calling the donkey a zebra. It is hallucination as management strategy.
Stage 9 · A field guide to dark tactics
For SEO, and for survivors, here is a non-exhaustive glossary of the dark tactics companies use that this site lampoons, all of which are commonly discussed in worker forums and in journalism about the broader Indian and global tech industry:
- Lick up, kick down. Praise leadership in public; blame juniors in private.
- Manufactured urgency. Everything is a P0. Nothing was planned. The deadline was set in a hallway.
- Probation purgatory. A year as a contractor. Then six more months of "probation discussions" after conversion. When probation is finally "approved," it is described as a gift. Peers at the same level were promoted.
- Reassignment roulette. A high-priority task is assigned to a senior, reassigned to a junior, then reassigned back, then split such that the senior keeps the easy half and the junior keeps the hard half. When the junior asks why, a complaint appears.
- Re-surfaced statements. Something you said in passing in 2022 reappears in your performance review in 2026, recontextualised and weaponised.
- Suppress and re-surface. A concern you raise is dismissed in the moment and then, three weeks later, raised back at you as "why didn't you bring this up?"
- Forced expressions. "You should smile more in 1:1s." This is not feedback. This is a request to perform happiness while being interrogated.
- The lunch landmine. Your manager casually shares, over lunch, the story of an employee they "had to fire" at a previous company. You laugh nervously. They make a note.
- "Confidential" investigations. Allegations exist. Allegers do not. Witnesses exist. Witness lists do not. Findings exist. Findings cannot be reviewed.
- Pre-bonus warning. The "first and final written warning" arrives precisely before the promotion / bonus cycle. The warning becomes the reason the bonus is small. The small bonus becomes the reason morale is low. The low morale becomes the reason for the next warning.
Stage 10 · Why this hits harder in India
Because in India, an H-1B is not the lever. The lever is something subtler and meaner: a permanent record on Naukri, LinkedIn, and on the WhatsApp groups of HR Business Partners across BLR / HYD / PUN / GGN. Calling someone a "psychological threat" in an exit document is, functionally, blackmail with a footer logo. It is also impossible to disprove, which is the entire point.
Add to this: the Indian tech worker is generally underpaid relative to global peers, which means the senior who lick-licks management is paid more than the junior who actually ships, which means no one in the room has any incentive to defend the junior, which means the junior gets to be the zebra, alone.
Stage 11 · What now?
- Read the forum. Post your version. Anonymously is fine.
- Read the FAQ if you are a lawyer, a journalist, or a person looking for someone to blame.
- Read the take-down page if you are an HR Business Partner and you would like this site to no longer exist.
- Read the head massage page if you would like to fund a single zebra's recovery.
- Read the disclaimer twice if you are even thinking about a legal letter. Then read the bit about "Airtel Black-style domain coincidences." Then take a walk.
Postscript
The zebra is not real. The zebra is a hallucination. The donkey was real. The human, before the donkey, was very real. If you are still that human — if you are still being bent — please remember: the stripes are not yours. They were painted on you by people who needed an exotic excuse to fire a workhorse on a Friday before a launch. You can wash them off. Many of us did. It takes a while. The forum is over here. There is tea.
Author's note (legal): This essay is satire. It does not name, target, or describe any specific company, employee, manager, HR partner, or director. The patterns lampooned here are documented across the global and Indian technology industry in academic research, journalism, and anonymous worker forums. Any reader who maps the satire onto a single real organisation is performing that mapping inside their own head, using their own associations, on their own time. The owner of this domain is a private individual, is not currently employed by any company, and is open to good-faith conversations about this domain.