Full-stack engineer obsessed with bridging the gap between elegant interfaces and bulletproof backend systems. I build products that feel inevitable.

I started as a traditional frontend developer—obsessed with pixels, interactions, and making things move. But after a few years, I realized the most elegant interfaces feel hollow without intelligent systems backing them.
That curiosity pulled me deeper. I dove into backend architecture, database design, and system thinking. I learned that brilliant UI means nothing if the data pipeline is fragile. That's when it clicked: the magic happens at the intersection.
Today, I build across the full stack—not because I have to, but because I believe software should be designed holistically. Every line of frontend code should have a purpose. Every API endpoint should feel intentional. Every database query should anticipate scale.
When I'm not architecting systems, I'm in the gym. Building discipline through iron teaches the same lessons as building software: consistency, progressive overload, knowing when to rest. The gym cleared my mind on problems I couldn't solve at the desk.
Code is communication. Your users shouldn't feel your architecture. Simple systems beat clever ones. Shipping beats perfection.
Pixel-perfect UI built with React and Tailwind. Motion design that enhances, not distracts. Performance that feels instant.
Robust APIs, clean database design, and systems that work quietly. Architecture that scales without refactoring nightmares.
The orchestration layer. Frontend elegance meeting backend intelligence. Seamless data flow, zero friction.
Code that reads like documentation. Tools that anticipate needs. Systems built to empower other engineers.