Internal document: Google fired dozens of engineers between 2018 and 2020 for abusing their access to data and tools
Context & Ripple Effects
The firings were disclosed piecemeal as they happened: a November 2019 memo cited data-security violations when four employees were let go, weeks after Google put staffers on leave for sharing internal docs and tracking colleague calendars amid labor tensions over leaked employee information. What this internal document changes is scale and pattern — not four cases but dozens of dismissals across 2018–2020, all attributed to abuse of access to data and tools.
That matters because the period overlaps exactly with Google's most visible internal unrest, including 2018 claims that executives pressured an engineer over pro-diversity forum discussions. Read against the later NDA settlement with six engineers over the 2018–2020 anti-union campaign, the security framing and the organizing timeline are hard to fully separate.
First-order effects
- Dozens of former Google engineers are retroactively recast in company record-keeping from labor or speech disputes into data-access abusers — a framing that shapes any future arbitration or litigation they bring.
Second-order effects
- Organizers inside Google face a sharpened deterrent: access to internal docs and calendars is now documented grounds for termination, raising the personal cost of the cross-employee research that fueled earlier campaigns.
Third-order effects
- If the pattern holds, large tech employers will keep resolving internal dissent through security-policy terminations sealed by NDAs, leaving regulators and courts to test whether 'data misuse' can lawfully function as a labor-control mechanism.
The trend: Tech companies are increasingly invoking data-security policy as the formal grounds for dismissing activist workers, with confidential settlements closing off the underlying disputes.