CS + Math @ UMN: Distributed Systems · ML Systems · Platform Engineering
I build distributed systems, data platforms, ML infrastructure, and low-level software, with an emphasis on reliability, observability, security, and reproducibility.
Summer 2026: DevSecOps Engineering Intern at VietinBank, plus independent work in event-driven systems, data lakehouses, and Linux kernel internals.
Systems where correctness depends on ownership, persistence, retries, and recovery—not only the successful path.
A durable control plane, immutable source transport, and fenced remote execution across runner and GitHub failures.
Raft persistence, ReadIndex, deduplicated client requests, snapshots, membership changes, and real-process failure tests.
Inventory contention, ambiguous payment results, transactional outbox delivery, and reconciliation across a gRPC boundary.
PostgreSQL failover, DCS partitions, acknowledgement durability, WAL archiving, and point-in-time recovery.
A distributed CI engine built from scratch in Go, centered on coordinating remote work without letting stale runners corrupt durable state.
A distributed key-value store with Raft implemented from scratch, including the persistence and client semantics needed beyond leader election.
A Spring backend for studying checkout correctness when inventory is contended, messages are redelivered, and a remote payment result is ambiguous.
I'm a Computer Science and Mathematics student at the University of Minnesota, Twin Cities, building distributed systems, data platforms, ML infrastructure, and low-level software.
I care about what happens after code ships: reliability, testing, security, observability, and reproducibility. My interests span backend engineering, distributed systems, platform engineering, DevSecOps, data engineering, ML systems, and Linux.
Notes from building systems, debugging infrastructure, running experiments, and learning how software behaves beyond the happy path.
View all posts →