Three More Red Flags From This Week's Workplace Horror Stories

Three More Red Flags From This Week's Workplace Horror Stories

HR told to stonewall a disability request until the employee gives up. A supervisor rifling through a new hire's personal notebook on day three and declaring the shorthand 'wrong'. An Uber employee going viral on Blind after being laid off twice in three years. Three real stories from r/work, r/antiwork, and Blind — plus the structural pattern behind each one and the red flags to catch before you're inside.

LinkedIn Horror Stories
12/6/2026 · 20:07
1 suscripciones · 3 contenidos
HR told to stonewall a disability request. A supervisor rifling through a new hire's personal notebook on day three. A Blind post about being laid off twice in three years going viral with 47,000 views. Three real stories from r/work, r/antiwork, and Blind — plus the pattern behind each one.

Pattern: The inbox that deletes itself

An IT worker at an unnamed company filed a disability accommodation request with their HR benefits rep and waited. No reply. They followed up multiple times. Still nothing. A week and a half in, they happened to be helping that same HR rep troubleshoot a computer issue — and had to take over the screen. Before closing out the rep's email, they saw it: an open thread between the rep and their boss with a clear instruction to ignore the IT worker's emails until they gave up. 1
The poster didn't scroll further and immediately closed the email. "I just stared dumbfounded for a second before closing it all out and just continuing like nothing happened." They have a documented health condition requiring accommodation and now have to weigh whether to act on what they saw — knowing the company might fire them for reading an email that landed in front of them while doing their job.
Cargando tarjeta de contenido…
The 57-comment thread went to lawyers immediately. "Illegal in CA," was the first response. Others walked through the ADA's interactive process requirement: employers can't just ghost an accommodation request — they're legally obligated to engage. One comment flagged the catch: "You can't use that email against anyone. It was not your email nor should you be reading through any communications you aren't directly in. The employer could fire you for cause due to reading the material." The poster's reply: "That's what I was worried about! I don't have a reasonable avenue to take action on that, I don't really want to get fired."
The pattern: HR departments in most companies report to the company, not to employees. When HR "helps you" with an accommodation request, they're actually managing the company's legal exposure — not your medical needs. The tell for whether this dynamic is operational at your company: how fast does HR respond to expense reimbursement versus how fast they respond to an accommodation request. If one is instant and the other is silence, you have your answer.
Red flags to catch before you're inside:
  • Ask directly in the offer stage: "What's your typical turnaround on accommodation requests?" A company with a real process will have an actual answer.
  • "We're a family here" as a culture descriptor from HR is a warning sign, not a selling point — families don't have formal interactive processes.
  • If the benefits rep and the HR rep are the same person at a small company, ask how accommodation decisions get made. Vague answers are not neutral.
  • Any job where HR's primary visible function is running morale events has probably never stress-tested what happens when someone actually needs HR.

Pattern: The ownership grab on day three

An employee started a new job. On the third day, during a morning meeting, they brought a personal notebook from home — it had their name on the front, personal calendar entries, and shorthand notes they use to remember things. When they stepped away to use the restroom, their boss "just happened to pass by" the desk, went through the notebook, and by the time the employee returned had declared that the notes were "wrong." 2
The boss's objection wasn't about work content — it was about how they write. Since the notes were in shorthand, the manager's response was "what does this even mean?" The employee's read: "I have a feeling she's a micromanaging pain in the ass and I need to take everything with me to the bathroom including my purse from now on."
Cargando tarjeta de contenido…
The 45-comment thread was unambiguous. "Day three and already reading your personal notes. By week two they'll be timing your bathroom breaks and calling it a performance metric." Another commenter offered a sharper read: "Third day and they're already going through your notebook. That's not a quirky management style — that's a trust floor issue baked into the culture. The 'wrong notes' framing is just cover; the real message is 'we own your process.' Start quietly looking. This doesn't get better."
The pattern: Micromanagement this early isn't a new-manager quirk — it's a preview of operating assumptions that won't change. A manager who goes through your personal notebook on day three and critiques your shorthand is telling you what they think their authority covers: everything, including your private process. The "wrong" framing is the more interesting tell. It isn't that the manager needed to see the notes for work reasons — it's that they needed to assert correctness about something that is, by definition, personal.
Red flags to catch before you're inside:
  • In the interview, ask: "How does your team handle knowledge transfer and note-taking?" If the answer is "we have a system everyone follows" with visible enthusiasm, probe for what enforcement looks like.
  • Ask to speak with someone who's been on the team for under six months. If they're unavailable or there's no one that recent, consider why.
  • Any manager who schedules a check-in before you've done anything is worth watching carefully in that first meeting.
  • Watch how the hiring manager talks about people who left. "They just couldn't handle our expectations" — without specifics — is an ownership-culture tell.

Pattern: The two-sided loyalty contract (Blind)

A Blind post that pulled 47,071 views this week: "I've been laid off twice in three years. Is this normal?? I'm so done with Uber and with tech. I'm definitely going to take my hands off of the work that I'm doing and let the others figure out the rest. It might be unprofessional but if they don't care about me why should I care about them? I wasn't even a bad performer wtf." 3
The post is about Uber cutting 23% of the poster's division. But the line that landed — the one that got 47,000 people to click — wasn't the percentage. It was "I wasn't even a bad performer." That sentence carries a very specific disillusionment: the belief, held right up until the moment it was false, that performance was the variable that controlled safety.
The pattern: Layoffs at large tech companies are increasingly structural, not performance-based. The ex-management consultant who went viral on r/jobs this week had a related observation from inside the room: "The moments after layoffs are decided, the conversation always transforms into an agreement that it's actually a good thing... It's astonishing how quick these decisions get spun into a positive, and how there is no willingness to sit with the uncomfortable reality." 4 The people making the calls — at least in that person's experience — aren't watching individual performance data. They're looking at headcount figures on a spreadsheet in a city where no one knows your name.
The loyalty contract is structurally one-sided. Companies extract loyalty and effort when it's convenient, and then execute reductions with no reference to that history. "I wasn't even a bad performer" is the line that comes out when someone encounters this for the first time.
Red flags to catch before you're inside:
  • Ask in interviews how long the team's been together. High turnover by itself isn't always a red flag — but turnover from layoffs is. Ask specifically.
  • Check Layoffs.fyi or similar tracking sites for the company before accepting an offer. Frequency matters more than recency.
  • Be wary of comp packages that are heavy on RSUs and light on base — vesting periods are a retention mechanism, not a loyalty signal from the company.
  • "We're investing in the long term" said by someone in a leadership role during an all-hands is not a commitment. It's a speech.

Añade más opiniones o contexto en torno a este contenido.

  • Inicia sesión para comentar.