Design Engineer. UX Engineer.
Product design, frontend engineering, and systems thinking. Full time or consulting.I work with teams when a product problem needs both interaction design and implementation judgment: unclear workflows, complicated systems, and features that need to make it into production intact.
I started in design and learned to code because implementation changes the experience. Today I design in Figma, contribute in code, and collaborate with product, support, and engineering to make the finished product work in the real world.
From Design to the Full Stack
I started designing websites in 2008. At the time, I was focused on how things looked, but I was always more interested in how people actually used them. Why someone clicked one thing and ignored another. Why small changes quietly changed behavior.
That curiosity pulled me toward UX and CX long before I had the language for it. In 2015, while working at ProBoards, I moved fully into UX and realized this was the work I cared about most. Not decoration, but understanding how people think, decide, and move through a system.
Over the years, that focus deepened through my work with Multimedia LLC, Aeries, Beetle & Frog, and now Member Splash. But something shifted along the way. I kept wanting to cross the line from design to build. Designing something and handing it off felt like stopping at the interesting part. So I started writing code. Then infrastructure. Then automation. Step by step, I became someone who doesn't just figure out what to build and how it should work. I build it and ship it too.
Today, I work across the boundary between product design and engineering. I help teams carry features from problem framing and interaction design through implementation, launch, and iteration, staying close to the technical and operational details that shape the experience.
Same Problems, Every Industry
Across different companies and projects, a few patterns keep appearing:
"People visit, but don't take action"
"Users start, but don't finish"
"The process feels confusing even though all the information is there"
"We're spending money on traffic, but conversions are flat"
These aren't design problems. They're decision problems.
Most of my work is about decisions, not screens. That is why I pay close attention to booking flows, multi-step forms, onboarding sequences, and information architecture: the places where people can lose their way or abandon a task.
Design with Implementation in Mind
I am a designer who also contributes in code. My experience spans React, Next.js, Vue, Python, PHP, Docker, PostgreSQL, and Supabase. I have rebuilt WordPress sites into modern stacks and investigated issues from CSS through network behavior, which helps me understand what is realistic to build.
The difference is not simply that I can code. It is that I understand how a design decision affects the component, state, API, deployment, and support work around it. That context helps me make better tradeoffs before a feature becomes expensive to change.
I use AI as a supporting tool for synthesis and repetitive implementation work. It does not replace collaboration, product judgment, or careful technical review.
What this means in practice:
- I carry feature context from early discovery through implementation
- I design with implementation constraints in mind
- I adjust scope based on real technical constraints, not guesses
- I contribute to the delivery path alongside the feature
- I can investigate issues from CSS through database queries when the work calls for it
- I help teams reduce rework by keeping design and implementation connected
What I Ship
I work across product design, frontend implementation, and the systems that support delivery. I specialize in projects where the hard part is figuring out what to build and how to make it fit together.
I have shipped work across healthcare, fintech, ISPs, membership platforms, and technical infrastructure. The context changes, but the work benefits from the same discipline: understand what matters, design it, build it with care, and learn from what ships.
Full-Stack Architecture
Architecting and building production systems across React, Next.js, Vue, Python, PHP, Supabase, and PostgreSQL. I pick the stack that fits the problem.
DevOps & Infrastructure
Docker, CI/CD, Cloudflare, Vercel, and Linux server management. I contribute to delivery paths that make releases easier to understand and maintain.
AI-Assisted Workflows
Using AI where it reduces repetitive work while keeping product judgment, technical review, and accountability with the people building the feature.
Workflow Orchestration
Automation pipelines, cron chains, n8n workflows. I wire systems together so processes run themselves instead of needing human babysitting.
Design to Production
From first Figma sketch to live deployment. I use implementation knowledge to make design decisions more concrete and easier for teams to ship.
Security-minded delivery
Security audits, vulnerability remediation, standards enforcement, and code review. I bring security considerations into product and implementation decisions early.
How I Decide
Scope creates room for learning.
A focused release can teach a team more than an overextended plan. I use deadlines to clarify the essential interaction, the known risks, and what should wait.
Clarity makes action easier.
When people cannot find the next step or understand the consequence, they hesitate. Clear language, hierarchy, and feedback reduce that effort.
Clarity beats cleverness.
Users don't need to be impressed. They need to know what to do next.
Good UX reduces avoidable effort.
The job is not to remove every decision. It is to make necessary decisions understandable and keep routine work from becoming harder than it needs to be.
I design and build for momentum. If a feature keeps shipping and users keep moving forward, the architecture is working. If it stalls, I want to know why.
Scope to Ship
I help take ambiguous features to production. I can shape scope, design the interaction, contribute implementation, and stay engaged after launch while working closely with the people who know the product, customers, and system best.
I use AI selectively to accelerate repetitive work, not as the centerpiece of the process. The differentiator is keeping product, interaction, and implementation judgment connected.
I'm direct about tradeoffs. I push back when something hurts the user or the architecture, then explain the consequence in terms the team can use to decide.
Take ambiguous feature.
Ship production feature.
Scope → Design → Build → Deploy → Iterate. Clear context across the work.
What I'm Looking For
I am looking for a role where design and engineering are close enough to inform each other, and where I can help carry features from problem framing through production.
Let's Talk
If you need a Design Engineer or UX Engineer who can help turn an ambiguous product problem into a clear, buildable experience, let’s talk.
Based in California. Open to remote or hybrid roles at product-focused companies. Also available for consulting engagements.