I’m a software engineer based in Seattle. My background is in computer engineering and robotics; I now work mainly on backend services, data systems, and infrastructure at Gradient.
What I’m looking for
What I’d like to work on.
I’m interested in software, infrastructure, and embedded systems roles where I can solve technically demanding problems. I bring experience across backend services, data pipelines, and GPU infrastructure, along with hands-on work in electronics and robotics.
At university I worked on analog circuits, embedded sensing, and digital logic—from amplifier and filter circuits to a processor in VHDL. Those projects gave me a foundation in building, measuring, and debugging physical systems.
My early professional work involved automated sorting machines: motion control, scanners, cameras, and operator tools. I later moved into the backend services and infrastructure supporting the wider platform.
These days I might be investigating a query plan, testing a model-serving configuration, or changing deployment infrastructure. I like having enough context to follow a problem between those areas.
WORKING PRINCIPLES
How I make engineering decisions.
01
State and ownership
I prefer systems where ownership, completion state, retry behavior, and recovery paths can be inspected directly.
02
Measurement before tuning
For performance work I rely on measured throughput, latency, GPU memory, query plans, and queue depth rather than estimates alone.
03
Infrastructure guardrails
I prefer environment, credential, and network boundaries that make common configuration mistakes fail early.
04
Abstraction boundaries
I use abstractions when they clarify ownership; shared mutable state or non-recoverable handoffs should stay visible until they are actually resolved.
TOOLS & LANGUAGES
Tools I’ve worked with.
Used across professional work, personal projects, and earlier electrical engineering studies.