TheDesigner&Engineerwhobuilds.

It depends on the problem, but I don't disappear and come back with a final design. I explore a few directions early, share them with my team before I'm precious about anything, and iterate based on feedback.

Before I even open Figma, I'm checking if there's existing data, user feedback, or analytics that should inform the direction. I also think about what we're actually trying to achieve and how we'll measure success.

Once we ship an MVP, I'm watching how users engage with it and using that to guide the next iteration.

I prefer being embedded with the team rather than working in isolation. Daily standups, sprint planning, async feedback, whatever the team needs. I share work early, even when it's rough, because surfacing problems sooner saves everyone time.

I'm not precious about my ideas. One PM I worked with said I'm "always happy to scrap what I've done and go back to the drawing board" and "can step back and see the bigger picture of what the product team is trying to achieve."

I'd rather get to the right solution than defend my first instinct.

I design and build. I've made over 1,600 GitHub contributions across web and mobile, so when I hand something off, I already know it's feasible.

But beyond the code, I think about the business side. Not just "is this good UX?" but "does this move the needle?" At Bondex, I'd ask about conversion metrics and A/B testing before designing a feature. At Web3.Career, we redesigned the post job flow specifically to increase revenue.

Our QA lead once told me "this kind of quality ownership from a designer is rare." For me, it just makes sense. If I'm designing something, I want to know it actually works the way I intended.

I've been coding since 2015, but AI tools like Cursor have pushed what I can do to a different level. I work in Angular and TypeScript for web, Ionic for mobile, and I built Designjobs.careers from scratch.

My years of experience mean I can read, review, and debug anything being written, even when AI is accelerating the build. I'm not replacing engineers, but I can jump into the codebase to help ship what I designed, catch issues before QA, and have real conversations about technical constraints.

Nothing gets lost in translation between Figma and production.

Product Designer, Design Engineer, or anything hybrid where I can do both design and development. I'm open to any industry.

What matters is working on real problems with a team that ships. I like being close to the product, close to the code, and useful at every stage.