A Culture of Constant Layoffs in an AI-First, People-Last Environment
Pros
- High-Impact Projects (depending on team): You can work on pretty big projects depending on the team you're working on. -Cross-Functional Collaboration: Work closely with other engineers, PMs, and stakeholders. - Compensation & Perks: Competitive salary, RSUs, benefits, and internal mobility are plusses
Cons
🔪 Layoff Culture & Job Insecurity Meta has become synonymous with repeated layoffs. If you're not consistently raising the bar every performance cycle, you're at risk—regardless of tenure or contributions. The environment can feel volatile, with a “perform or perish” undertone that fosters anxiety rather than growth. 🤖 AI-Led Future, Human-Optional While Meta promotes its AI initiatives heavily, the internal shift is even more intense. Software engineers—especially E3s and E4s—are increasingly seen as expendable as the company pivots toward an AI-managed engineering structure. The writing is on the wall: only a small “core” group will remain to maintain and scale AI systems. 🔥 Burnout & Scope Creep Ownership is great—until it becomes a euphemism for being overextended. If you’re not on a “high-impact” project, you’re overlooked. If you are, you're often under-resourced. Support and documentation are inconsistent, and many engineers are left juggling multiple priorities with unclear guidance. 💀 Competitive, Eroding Culture The cultural shift over the last three years has been sharp. What once felt like a collaborative environment now feels like a battle royale. Performance is stack-ranked against your peers, so you're not just trying to succeed—you’re trying to beat others to stay employed. The psychological toll of this constant comparison is wearing, especially in a post-layoff climate where everyone feels disposable.
