Engineering first, then teams, then architecture, then design. Every step added a reason to stay close to how things get built.
Computer engineering, then straight into building. Front end, back end, whatever the project needed. The habit of asking how a thing actually gets made started here and never left. It is still the first question I ask about any design.
Led a developer and video team and rebuilt the university website, adding online grading, kiosk subject lists, and an e-voting system. Running a team taught me that the bottleneck is almost never how fast anyone types.
I led UI/UX for embeddable e-commerce widgets: shoppable photos, videos, and video ads. This is the point where I stopped waiting for someone to hand me a screen to build, and started deciding what the screen should be.
I led a developer team and owned solution architecture across complex projects while designing the responsive logistics web app and its admin portal. Wearing all three hats stretched some timelines, but it is where I learned to write a spec a developer can actually build from.
Promoted from Senior Software Developer to Solutions Architect to Lead Product Designer. I now partner with the CEO and VP from first idea to shipped build, across the Management Portal, AI candidate matching, the recruitment pipeline, the employee portal, and two mobile apps.
Six products designed and vibe coded on my own: marketing sites, a Shopify app, and two mobile app concepts. Same obsession, new tools. Building them myself is what keeps the specs I hand developers honest, and it means I know the cost of every idea before I propose it.
Every engagement includes all of this.
No design-to-development handoff
No front-end contractor after me
No one translating the spec into code
No agency layer between you and the work
Pick the one closest to where your project is. If your situation sits between two of them, say so and I'll shape one that fits how your team runs.