Systems Engineer with a specialty in Database Systems: OLAP, Metadata Management, Storage, Query Engines & Processing.
I have a Masters in Computer Engineering from Carnegie Mellon, where I got inspired by databases and knew I wanted to pursue them as a career.
I spent ~5 years at Google working on BigQuery internals β the streaming layer, storage APIs, and the machinery that moves petabytes between query engines and cloud storage. I learned what it takes to build systems that work at massive scale: the engineering rigor, the failure modes you'd never predict, and the operational discipline to keep it all running.
- Storage engines β how data is laid out on disk and accessed efficiently
- Query engines β planning, optimization, and execution
- Streaming systems β high-throughput data pipelines that keep consumers fed
- Columnar formats β Parquet, Arrow, Vortex, and the tradeoffs between them
- Distributed systems β coordination, consistency, and the places where theory meets messy reality
- OLTP β interested in branching into transactional systems and exploring that side of the database world
Taking a short breather and looking for my next role. I believe the best way to understand a system is to build one, so I'm always tinkering on something. Recently:
- Apache Iceberg: Spec discussions on REST catalog read restrictions, materialized views, and table encryption
- Apache Gravitino: Governed Table Encryption for the Iceberg REST Catalog, Soft Delete, Materialized Views
- Strata: a SQL database engine in Rust, built from scratch
- mori: a worktree manager for running multiple coding agents
- mammoth-cache: a self-hosted build cache for Gradle, Maven, and Bazel
Iβm looking for my next engineering role in databases, data infrastructure, or distributed systems, at a company of any size with a strong engineering culture. Seattle preferred (remote or hybrid), open to relocating for the right fit. If that sounds like your team, Iβd love to chat.
π Resume π« nevzheng@gmail.com π LinkedIn π Blog