About Me
How I work
Start with the problem.
I begin by understanding what needs to change, who it affects, and what constraints actually matter before deciding what to build.
Design before I build.
I think through the domain, data, interfaces, failure modes, and trade-offs so implementation follows a clear technical direction.
Make complexity explicit.
Good architecture does not hide complexity. It gives complexity clear boundaries so systems remain understandable and changeable.
Engineering
Build for the next engineer.
I write code for the person who will maintain it after me: clear boundaries, intentional abstractions, and decisions that are easy to reason about.
Validate with evidence.
I test assumptions against reality through tests, measurements, observability, and real system behavior rather than relying on intuition alone.
Ship, learn, improve.
Engineering is ultimately about creating value. I prefer deliberate solutions that can ship, learn from real usage, and improve over time.
Beyond the code
I'm interested in the intersection of mathematics, engineering, and intelligent technology, especially where computation can be applied to problems that extend beyond software itself.
Curiosity beyond the code.

Mathematics

Artificial Intelligence

Optimization

Industrial Engineering

Robotics & Autonomy

Healthcare

Reliability & Systems

Digital Twins

Swimming
Get in touch
Open to new opportunities, collaborations, and interesting problems. Have something in mind? Let's talk.