shihang zhang

these days i build infrastructure for quantum computing at google — a hybrid cloud platform that lets quantum services live between GKE and the bare-metal datacenters (via GDC) where the hardware actually runs.

before that, six and a half years inside kubernetes identity at GKE. i designed and shipped GKE's kubernetes API frontend from prototype to GA — the data-plane endpoint that serves resource CRUD and the long-lived streaming connections (watch, exec, logs) that keep kubectl feeling alive — plus the GKE auth service alongside it. i also owned the kubernetes service account token roadmap end-to-end — KEP-1205, KEP-1855, KEP-2799: bound tokens, CSI driver tokens, and the long migration off secret-based tokens. the kubernetes project gave me a contributor award somewhere in there.

i'm also a google-wide readability reviewer for go and API design — which is a fancy way of saying i spend a non-trivial part of my week arguing about identifier names with people who care just as much as i do.

before infrastructure i was in machine learning — brown for grad school, rutgers before that, a stint TA'ing deep learning, and a year deep in pytorch when attention was still a paper and not a product. some of that brain still leaks into how i reason about distributed systems.

seattle, originally from chongqing. the most interesting infra problems live where unfamiliar hardware meets cloud-native software — quantum is just the newest place that's true.