Google workers fired for protesting Israeli contract file NLRB complaint
Scope of protest and Google’s response
- Protestors held sit-ins inside Google offices, including an executive’s office, and some livestreamed from inside.
- Many commenters see this as crossing a line from speech to disruptive occupation, unlike earlier actions (petitions, resignations, outdoor walkouts).
- Others dispute how disruptive it was, claiming the occupied space was otherwise unused and that some fired workers only briefly observed or chatted with protestors.
- Several note an “employer’s market” and ongoing Google layoffs, arguing the company has strong incentives to fire activists rather than tolerate disruption.
Legality, NLRB complaint, and at‑will employment
- Discussion centers on whether this qualifies as “protected concerted activity” about terms and conditions of work under the NLRA.
- Some argue sit‑down–style actions on private property are not protected, and that trying to force Google to drop a contract with Israel is more like an unlawful secondary strike.
- Others focus on allegations that people with minimal or unclear involvement were fired, which they see as potential retaliation.
- At‑will employment is noted as limited by prohibitions on certain kinds of retaliatory firing; disagreement over how far protections for political activity extend, and whether they apply on‑the‑job.
- Consensus among more legalistic commenters: complaint is unlikely to fully succeed, but a settlement and severance are plausible.
Workplace activism vs. quitting
- Many insist “don’t do it at work”: companies are not democracies, and deliberately disrupting operations will predictably get you fired.
- Others defend the workers as taking real personal risk over what they view as complicity in atrocities; see using NLRB and litigation as extensions of protest.
- Some argue resignations are easy for employers to ignore; disruptive protest and legal challenges are more visible, though outcomes here are seen as poor.
Change in Google culture
- Some view this as part of a long-running crackdown on internal activism and organizing since the 2018 walkouts.
- Others attribute the difference to:
- Smaller scale and less broad support this time.
- Contracts (cloud/AI) now seen as strategically vital, including with defense and allied governments.
- A harsher economic environment and shifting internal power toward revenue-generating units.
Israel–Palestine, antisemitism, and media framing
- Large subthread debates whether campus and corporate protests are primarily:
- Anti‑occupation/anti‑war and focused on high Palestinian civilian casualties, or
- Anti‑Israel/antisemitic, sometimes including praise for October 7 or slogans interpreted as calling for Israel’s destruction.
- Some attendees say they have not seen antisemitic behavior on the ground; others point to specific incidents (slurs, violence, certain chants/signs) and organizations with militant links.
- Strong disagreement over:
- Use of the term “genocide” for Israel’s actions vs. framing them as warfare against Hamas embedded among civilians.
- How many protestors support or excuse Hamas vs. a small fringe.
- Whether media and political actors systematically overstate protester antisemitism, or underplay it.
- These geopolitical disputes heavily color views on whether the Google protest was morally justified or reckless.
Free speech, “consequences,” and double standards
- Repeated arguments that free speech protections formally limit government, not employers; others stress a broader moral/ societal ideal that speech shouldn’t cost livelihoods.
- Some note past HN and tech‑community support for internal protests against China (Dragonfly) and US DoD work (Maven), and see current reactions (“don’t protest at work”) as hypocritical or politically selective.
- Others answer that China‑censorship protests were less disruptive and on an issue (censorship) the industry is unusually united against, while Israel/Palestine splits opinion and involves core government and defense relationships.