Not just an engineer.
A builder with taste.
I started writing Android apps in Java in 2012, back when smartphones were still surprising people.
Over 13 years I've worked across most of the stack: native Android and iOS, then React Native, then full-stack web with React, Next.js and Node, and now backend. Today I'm a Technical Lead on backend systems for production web platforms (Python, Node.js, Azure), with hands-on AI work at integration and proof-of-concept level.
What the mobile decade left me with is a habit of building inside constraints. You can't hot-fix a released app, so backward compatibility stops being optional. And you build for the device you're given.
I'm now going deeper on the reliability side of AI systems: evaluation, retrieval correctness, and cost.
Performance is a feature
Fast and fault-tolerant by design, not by accident. Most of the wins I've had came from measuring the slow path first rather than guessing at it.
Architecture before the prompt
AI tools are only as good as the structure they work inside, so boundaries, failure modes and cost come before the model.
User instinct from mobile
13 years shipping to real users gives you a lens most backend engineers never get. I never forgot who's on the other end of the API.
Honest evolution
Android in 2012. Backend on Azure in 2026. I go deep on what's next but I don't abandon what still works.