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)
Retention has never been the goal here, just the appearance of efficiency for the next quarterly report. They don't want engineers who know the systems; they want modular, replaceable cogs who don't ask questions about the margin targets. The brain drain isn't a bug in the model, it's a feature. They’ve crunched the numbers and decided that replacing expertise with cheap, green labor is cheaper in the short term. Just don't expect the quality to hold up when the legacy codebases inevitably hit a wall.
It's frustrating to watch, but honestly, this is exactly how the playbook has always worked. They view institutional knowledge as a liability that inflates salary costs, not an asset that keeps the business running. When you see talent leaving, take it as your sign to update your resume and get out before you become the one holding the bag for a failed project. Leadership isn't ignoring the drain—they are actively prioritizing immediate cost-cutting over long-term stability. You're better off finding a company that values your expertise.