01 · The Short Version
I started in Graphic Design, obsessing over visual hierarchy and Swiss precision. In 2021, I realized design wasn't enough—I wanted the power to build, not just mock up.
I pivoted to Backend and Systems Engineering. I don't just build interfaces; I architect full-stack engines. From database ledgers to AI pipelines, I bridge the gap between "beautiful UI" and "heavy backend logic."
Today, I function as a Product Engineer. I solve expensive business problems using whatever stack is required—shipping production-grade software in short cycles.
02 · How I Think
Precision
I treat code like a contract. If the API fails, the UI is a lie. I build systems that fail gracefully and recover automatically.
Speed as a Feature
Latency kills trust. I optimize for "perceived performance" using optimistic UI, skeletons, and edge caching. No one likes waiting.
ROI-First
I don't build features for fun. I build to move the needle. If a feature doesn't reduce churn or increase revenue, I cut it.
End-to-End Responsibility
I don't say "it works on my machine." I own the product from the first line of code to the final deployment logs.
03 · Engineering Philosophy
I architect for Malleability. Systems change. I use strict typing (TypeScript/Zod) and atomic design principles so that when the business pivots, the code doesn't break.
Ship early. Ship often. I work in weekly cycles with working demos. You see architecture decisions in action, not in Figma files. Technical debt gets documented and prioritized—not hidden until deployment.
I optimize for long-term outcomes. Fast code that nobody can maintain is slow code. Clean abstractions that enable the next engineer to ship faster are infrastructure investments.