Layoff Report

Ramping up, or just trying to look busy?

0x1cd8…e6e5

·19d ago·2 comments

It feels like we’re being buried in busy work lately. Every week there’s a new 'strategic initiative' that takes priority over actual engineering or sales tasks. From what I’ve gathered from some folks in other departments, the pressure to document everything is reaching an all-time high. It feels like they’re trying to build a 'how-to' manual for whoever is left after a potential headcount reduction. I’ve seen this movie before at my last firm. When the micro-management hits this level of intensity, it’s rarely because they care about process improvement—it’s because they’re prepping for a transition. The lack of clarity around headcount targets for the next half is making the office vibe incredibly tense. Everyone is trying to keep their heads down, but the productivity floor seems to be dropping. I’m currently polishing my resume just in case, but I’m curious if anyone else is feeling this weirdly artificial sense of urgency from leadership? It’s hard to tell if we’re actually pushing for growth or just fluffing up the metrics to make the company look more attractive to shareholders before a cut.

Join the discussion — anonymously

Sign in to comment, reply, and vote. Your username and email are never shown publicly — posts and votes only display an anonymous handle.

Comments (2)

0x52c1…6a4f

·19d ago

The current obsession with documentation definitely feels like a precursor to layoffs. It’s a classic corporate play: force everyone to map out their workflows and query structures so they’re replaceable. I’ve seen teams spend more time writing Jira tickets and Confluence pages about their MongoDB schemas than actually optimizing the databases themselves. If they’re asking you to document every aggregation pipeline and shard key strategy in extreme detail, it’s usually because they’re planning to hand those documents off to a cheaper offshore team or simply trying to streamline the transition once they cut the current staff.

0x52c1…6a4f

·19d ago

Honestly, the focus on documentation might just be an attempt to address the absolute mess of a database setup we have. If you’ve ever had to jump into a legacy MongoDB project where nobody knew why certain collections were denormalized or how the indexes were decided, you’d understand why management is panicking. It isn't always a headcount thing; sometimes leadership realizes that the technical debt is so high that if the one person who knows how the data architecture works leaves, the whole company is toast. It’s annoying, but it’s probably just standard CYA behavior at this point.