Three Red Flags From This Week's Workplace Horror Stories

Three Red Flags From This Week's Workplace Horror Stories

A salary listing that shrank by $35k on offer day. A hire who was escorted out 48 hours after leaving their last job. A marketer whose two promised headcount hires were quietly replaced by a standing instruction to 'use AI.' Three real stories from r/jobs and r/antiwork this week — plus the patterns behind each one.

LinkedIn Horror Stories
June 11, 2026 · 8:41 AM
1 subscriptions · 1 items

This week's red flags

Three real stories — salary bait-and-switch, a Day 2 firing, and the AI headcount trap. Each one has a pattern worth memorizing before your next offer letter.

Story 1: The $90k listing that became a $55k offer

A senior analyst in Austin went through four rounds for a role advertised at $85k–$105k. The offer letter landed: base salary $55k.
The company included a three-page "Total Compensation" PDF. Health insurance premiums: counted. An unguaranteed 15% bonus: counted. Access to an internal video library labeled "Professional Development Value" at $5k/year: counted. Total package, they claimed: $92k.
When he called HR to ask if it was a mistake, the rep mentioned unlimited breakroom snacks.
"She literally told me that the 55k is very competitive when you consider the 'holistic investment' the firm is making in my career path."
He withdrew. She sounded offended.
The pattern: Wide salary ranges attract candidates deep into the funnel; a "total comp" PDF bundles mandatory employer costs and hypothetical bonuses to make the lowball look reasonable. Condescension on pushback is part of the playbook — you're supposed to feel naive for expecting the advertised number. 1
Loading content card…
Red flags:
  • Salary range is unusually wide (>$25k spread on a single-level role)
  • "Total compensation" gets mentioned before any offer
  • HR can't confirm base salary during screening

Story 2: Hired, quit, escorted out on Day 2

A nonprofit recruited him outbound, delayed his start so he could transition properly. He gave notice, showed up. Day 1: onboarding, feedback to dress more professionally. Day 2: a meeting with his manager and HR. "It wasn't going to work out." No reason given. Escorted out, Teams access revoked within the hour.
"How does a company pursue a candidate, interview them multiple times, agree to delay the start date so they can transition out of another job, hire them, onboard them, and then decide after two days that they're 'not a fit' without giving any explanation?"
At least one other commenter described an identical scenario — also at a nonprofit. 2
Loading content card…
The pattern: "Not a fit" with zero specifics, after someone has already resigned elsewhere, usually means a veto from someone who wasn't in the loop — or a cancelled role that nobody told recruiting about. At-will termination makes it legal. It's still a betrayal.
Red flags:
  • You were recruited outbound — recruitment energy often outruns organizational alignment
  • No one from the actual team appeared in interviews
  • Early feedback is vague or personal rather than role-specific

Story 3: AI didn't reduce the workload. It cancelled the hire.

Two roles were promised to handle growing scope. Then nothing — replaced with a standing directive to "spin it through Claude." 3
Loading content card…
"The tool that made my own exploitation look like productivity is also somehow the reason nobody feels bad about asking me to keep doing it indefinitely."
The comments filled with variations: an engineer watched two junior hires compress to "one junior with an LLM." A support worker was told AI would handle cases before they became cases. It didn't.
The pattern: AI productivity gains are real in narrow domains, but at the organizational level they justify freezing headcount while scope grows. Outputs that look good on a dashboard hide the single-point-of-failure risk. When someone burns out, the "AI makes up for it" logic doesn't survive the offboarding.
Red flags:
  • "We're using AI to optimize headcount" in any form during interviews
  • A role that's been open or "on hold" for months
  • You're absorbing responsibilities that used to be split across multiple people

The shared thread

All three stories live in the same place: the gap between what a company signals and what it delivers. An inflated range, an enthusiastic recruit, a headcount promise — each is a signal to get what they want from you.
The most reliable proxy for signal accuracy: how they behave when something goes wrong. Does HR have a real answer, or condescension? Does a manager explain a termination, or just say "not a fit"?
If the answer is always deflection, you already have your answer about everything else.

Add more perspectives or context around this Post.

  • Sign in to comment.