Ex-Google engineer charged with stealing trade secrets

Prior cases and context

• Commenters recall earlier Google trade-secret cases (e.g., self‑driving) and note that experience from those incidents likely hardened Google’s monitoring.
• Some express surprise that high‑profile offenders can obtain presidential pardons, with discussion of how money and social circles can indirectly enable this.

Google’s security, monitoring, and hiring practices

• Many are struck that the engineer could be CEO/CTO of Chinese startups while employed at Google and that this was visible on LinkedIn or corporate filings.
• Debate over whether Google should continuously scan global company registries for conflicts; some say it’s feasible and expected for a company “built on data,” others say it’s technically and logistically hard (name collisions, access to Chinese records).
• People highlight that file uploads to personal cloud from work devices should be obvious red flags, especially after prior scandals.
• It’s noted that Google analyzes internal network traffic and likely logs packets extensively; others argue full packet capture at scale is impractical and that rule‑based monitoring is more realistic.

China, citizenship, and security risk

• Several comments cite China’s intelligence law obligating citizens to assist state intelligence, arguing that Chinese nationals with sensitive access are a special risk and should be monitored more or even not hired.
• Others counter that this veers into illegal national‑origin discrimination, that many cases involve false accusations, and that naturalized or US‑born Chinese should be treated as Americans.
• Some stress that giving up Chinese citizenship doesn’t fully mitigate risk due to potential retaliation against family and extraterritorial harassment.

How secrets are stolen and detected

• The indictment details exfiltration via copy‑paste into Apple Notes, converting to PDFs, and uploading to personal cloud, plus badge‑sharing to fake presence; commenters describe this as poor opsec.
• Discussion of alternative, lower‑signal methods (cameras, HDMI capture, slow drip of data) and the survivorship bias that only the sloppy get caught.

Trade secrets, skills, and value

• Thread revisits what counts as “stealing” vs reusing accumulated know‑how when changing jobs; consensus is that copying documents or code is clearly over the line, but reusing general experience is not.
• Several argue that raw code repositories are often less valuable than architecture, data, and know‑how; cloning a large codebase without its ecosystem can be near‑worthless.