Software Engineer focused on web, mobile, backend architecture, integrations, and operational reliability.
I build systems designed not only to work — but to remain coherent under scale, failure, retries, and real-world constraints.

I'm a developer who cares about what happens after the feature is shipped.

That means thinking about offline-first behavior, retry logic and idempotency, API consistency, and performance under real constraints — not as afterthoughts, but as first-class design decisions.

I'm drawn to problems where correctness matters more than hype, and where the difference between a good system and a great one shows up months later, under load, during an incident at 2am.

Turning ambiguous product problems into clear, predictable technical systems — that's where I operate best.

• Reliability-oriented backend systems and sync engines
• Offline-first mobile workflows with conflict resolution
• Payment and external API integrations with proper retry and idempotency
• Internal tools that eliminate operational friction
• Architectures where failure is expected and handled gracefully

Good software is not the code that works once.
It is the code that remains understandable, resilient,
and economically maintainable when everything starts going wrong.