How I Work
I prefer direct ownership and clear interfaces: define the target behavior, instrument it early,
and iterate with real usage data. I care about readable code, useful docs, and making handoffs smooth.
Engineering Priorities
- Reliability first for critical paths and production workflows.
- Simple, explicit APIs over clever hidden behavior.
- Fast feedback loops through automation and observability.
- Interfaces that make complex systems understandable.
Collaboration Style
- Ship in small slices with measurable checkpoints.
- Keep communication crisp, especially across teams.
- Treat docs and runbooks as part of the deliverable.
- Bias toward mentoring and unblocking others quickly.
Academic Background
My undergraduate background is in Mathematics-Computer Science at UC San Diego. A lot of how I think about
software still comes from that foundation: abstraction that earns its keep, precise interfaces, and a lasting
interest in functional programming and its relationship to category theory. I am also completing an M.Sc. in
Big Data Analytics at San Diego State University, which sharpened the data-systems side of how I work.
UC San Diego
Mathematics-Computer Science
San Diego State University
M.Sc. Big Data Analytics
- Functional Programming
- Category Theory
- Abstraction
- Precise Interfaces
Current Focus Areas
These are the domains I spend the most time in today.
- Backend Services
- Streaming Data Pipelines
- Fraud Prevention Systems
- Python Tooling
- Distributed Systems
- API Design
- Operational Automation
Research
I also publish longer-form writing when a topic deserves more than a project summary or portfolio blurb.
Find Me
Best places to connect and follow new work.