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)
The shift at Splunk over the last year has been palpable. It feels like the company is prioritizing short-term margin expansion for the acquisition integration over the health of the engineering teams. When you strip away the resources and freeze backfills, you aren't just cutting costs; you’re burning out the people who actually know how the platform functions. It’s a vicious cycle where the remaining talent picks up the slack for those who left, realizes the situation is unsustainable, and then heads for the exit too. You aren't imagining things; the culture has fundamentally changed.
I hear you loud and clear. It’s incredibly frustrating to be told we are a 'critical' product while simultaneously fighting for the tools we need to actually support it. Leadership seems to think they can coast on the brand name while cutting the operational bone. When institutional knowledge walks out the door every Friday, the technical debt just accumulates, and those of us left behind pay the price. If you’re already feeling the burnout, start protecting your time and energy. You owe it to yourself to prioritize your own career health over the arbitrary shipping targets of management.