Hacker News new | ask | show | jobs
by frollogaston 3 hours ago
Dunno about 20, but 7 years ago, they fired a security engineer for forcing in a CL for their internal Chrome extensions to put a disapproving banner on certain anti-union websites. Wasn't a very harmful change, but because she left a clear paper trail of circumvented code/release reviews, she couldn't be trusted anymore.
1 comments

That was a security engineer modifying internal security tooling without proper permissions/reviews.

The union piece was probably extra motivation but still you just do not do that to security infra, it should always be a firing offense unless it was a truly exceptional circumstance.

Conversely, this guy was in a DevRel role where it sounds like they released open source stuff all the time and the line was a lot more fuzzy (admittedly I've only heard one side of the story).