Amazon's Silent Sacking
Amazon’s move toward “silent sacking” — keeping roles technically employed while removing meaningful work and ratcheting up return‑to‑office and performance pressure — is portrayed as a way to shed expensive staff without headline layoffs or severance. Commenters link this to broader trends: aggressive offshoring of engineering and healthcare roles to lower‑cost countries, post‑pandemic reversals on remote work, and boards pushing short‑term profitability over employee loyalty, innovation culture and, potentially, long‑term reliability of platforms like AWS. Others counter that big‑tech engineers remain exceptionally well paid, that overhiring during the zero‑interest era made cuts inevitable, and that similar dynamics are now emerging across many large U.S. employers.
Offshoring, Remote Work, and Global Competition
- Several comments note a strong shift of software hiring to India (Hyderabad, Pune, emerging Indore) and Mexico, driven largely by cost savings.
- Remote-friendliness in Indian branches of many firms lets engineers earn $20–40k while living in towns where incomes are a fraction of that; some argue this validates warnings that remote-first makes tech globally more competitive.
- Others push back that Indian quality of life still drives many who leave to never return, and that higher Indian pay is not a “magic bullet” to destroy US tech salaries.
Amazon RTO, “Silent Sacking,” and Managing Out
- Multiple accounts describe Amazon dissolving teams, leaving engineers technically employed but with little or no work and told to find internal roles during hiring freezes.
- This is framed as “silent sacking”: making conditions unpleasant (RTO mandates, limited roles, PIPs) so people quit without severance.
- There is debate about severance: some report severance even after failing PIPs; others insist firing “for cause” would avoid it.
- People emphasize the psychological toll of being “managed out” via opaque PIPs and constant criticism, versus a clean layoff with severance.
AWS Reliability and Engineering Practices
- Some fear that headcount cuts, offshoring, and weaker culture will eventually hurt AWS reliability; others inside AWS say core EC2/VPC remain well staffed and cuts mainly reduce new feature work.
- Critiques focus on excessive microservices, confusing offerings, and hidden costs; defenders highlight Amazon’s data-driven A/B culture and “two-pizza team” model, though it’s seen as expensive and politically complex.
Tech Labor Market, Overstaffing, and Productivity
- Many argue big tech overhired during the zero-interest era and is now correcting; some claim 20–25% of engineers at companies like Amazon/Google could be cut without hurting output.
- Others counter that engineers aren’t just “running the train” but building future systems; layoffs and churn risk long-term capability.
- There’s tension between “software skills will remain valuable” and anxiety that globalization and AI will structurally depress high-end SWE pay.
Corporate Culture, Perks, and Power
- Several see a shift from employees as long-term investments (perks, 20% time) to employees as quarterly cost centers; Amazon is repeatedly cited as especially frugal and cutthroat, with short average tenure.
- Others note culture varies sharply by org; some teams are healthy and impactful, others are political and punitive.
- Discussions also touch on outsourcing in healthcare, skilled immigration backlogs, and whether governments should make offshoring economically painful, with no consensus.