About
An engineer who likes systems that must survive contact with reality.
I am most comfortable when the work cuts across product shaping, implementation, deployment, and operational follow-through. That is the practical overlap between product engineering, full-stack delivery, and DevOps work.
- from UI to operations
- Full stack
- engineering decisions tied to outcomes
- Product aware
- active technical research habit
- Daily watch
What I optimize for
I like concrete work: products with users, tooling that reduces friction, and infrastructure choices that hold up under routine maintenance. I spend time on active technical watch because the useful part of engineering is often knowing which ideas are worth adopting and which are just noise.
My background has pushed me toward a product-engineering profile with a strong DevOps bias. I care about the code, but also about deployment surfaces, operational cost, release safety, and the shape of the system a few months after launch. In practice that means moving easily between Angular frontends, backend services, infrastructure, and the product decisions that connect them.
The portfolio reflects that on purpose: fewer generic statements, more evidence, and more writing about how real systems get built.