I've spent 4 years learning that technology is never the hard part.

How I started

I didn't come to engineering through a love of code for its own sake. I came to it because I liked solving problems — and software turned out to be the most powerful lever I could find. Early on, working with clients on Upwork, I learned the lesson that still shapes everything: the brief is never the whole story. The client who asks for an app usually needs a business outcome. My job is to find that outcome and build toward it.

Why I work across so many domains

Mobile, AI, IoT, automation, backend — on paper that's a wide range. In practice it's one discipline: match the technology to the problem, not the other way around. I follow the problem wherever it leads. That curiosity is why a hardware company trusted me with a custom BLE protocol the same year I shipped an AI automation pipeline. Different tools, same instinct.

The CertifyCrafter moment

Building my own SaaS product changed how I think. As a founder you feel every decision — the cost of the wrong abstraction, the value of shipping early, the weight of a churned user. CertifyCrafter taught me to think like an owner, not just an engineer. Now I bring that lens to client work: I care about your unit economics and your roadmap, not just your sprint.

Why I take confidentiality seriously

Most of my work is under NDA, and I treat that as a professional standard rather than a limitation. When you hand someone your idea, you're trusting them with something fragile. I'd rather show you fewer screenshots and keep every client's trust intact — that discipline is exactly what you'd want protecting your own project.