Google lays off its Python team
Google’s decision to lay off much of its internal Python language team and rebuild it in lower-cost regions such as Munich has triggered broader concerns about offshoring, wage arbitrage, and the erosion of job security in big tech. Commenters argue that the team was small but critical infrastructure, supporting a massive internal Python ecosystem and upstream CPython itself, making the move look like short‑term cost-cutting at the expense of long‑term capability. The thread expands into debates over protectionism vs. free trade in software work, the limits of U.S.-style capitalism and corporate governance, and whether unions or regulation can realistically counter these trends.
What happened
- Google laid off most or all of its core internal Python team, then began building a new Python team in Munich.
- Several commenters say this fits a broader pattern: whole teams dissolved or merged, with equivalent roles re-created in lower‑cost locations.
- Some related language/tooling teams (e.g., Kythe/Grok, Flutter) were also reportedly hit in this wave.
Offshoring, costs, and locations
- Many see this as offshoring or “defragging” Google’s global footprint: shifting work to Munich, Bangalore, Mexico City, etc.
- Discussion of geo‑based comp: US pay tiers differ by city; Europe, India, and Eastern Europe are generally cheaper than US hubs.
- Some are surprised Munich was chosen (a high‑cost, high‑protection market); others argue it’s still cheaper than US metros and culturally closer than India.
- Debate over whether this is smart: some say offshoring often cuts quality and is a “false economy,” others say quality tracks pay, not country.
What the Python team did
- They maintained Google’s internal Python runtime (migrating from 2.7 → 3.11), ensured the monorepo built, and fixed or coordinated all breakages.
- Ran large‑scale dependency management for thousands of third‑party packages and maintained custom linting/formatting, build rules, C++ bindings, and pytype (a static type checker) plus automated refactorings across hundreds of millions of lines.
- Acted as internal experts and upstream CPython contributors / leaders; several see this as high‑leverage “infrastructure” work now at risk.
Python’s role at Google
- Conflicting views: some claim Python is relatively small vs C++/Java/Go; others say there are “tons” of critical Python, especially in SRE, CI/infra, testing, ML tooling, and YouTube.
- Consensus that most ML model development is in Python, while large‑scale serving often uses C++.
Labor policy, unions, and capitalism
- Long subthread on how to “protect” domestic jobs: tariffs, tax incentives, restrictions on offshoring, but also concerns about competitiveness and corporate flight.
- German layoff law is described as strict, making existing German employees hard to fire.
- Opinions split on unions at Google: some urge joining the Alphabet union; others criticize it as ineffective or culture‑war focused.
- Broader arguments over capitalism: some see these layoffs as predictable shareholder‑driven behavior; others say highly paid FAANG workers criticizing capitalism are being hypocritical.
Morale and industry impact
- Many describe Google as drifting toward “IBM‑like” behavior: risk‑averse, cost‑cutting, and demoralizing.
- Some think this will hurt recruiting and long‑term technical quality; others argue Google can still easily hire due to prestige and comp.