I own the full cycle.
Design, code, infrastructure. End to end. Full time or consulting.Companies call me when their product isn't shipping, their systems are tangled, or they need someone to take an ambiguous feature to production without handoffs.
I'm a builder who owns the full stack. That means I don't hand off designs and hope for the best. I design it, I code it, I deploy it, I monitor it. If something breaks, I fix it. If something needs to ship faster, I build the pipeline that makes that possible. I work full time or consulting.
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 own features from problem to production. I research, define, design, prototype, validate, build, QA, deploy, and iterate. Every role in that pipeline is me. I work with teams. I don't depend on them to cross the finish line.
Same Problems, Every Industry
Across every company, every industry, every project, the same problems 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's why I focus on booking flows, multi-step forms, onboarding sequences, and information architecture. The unglamorous stuff that actually moves metrics.
Full Cycle, One Person
I'm not a designer who dabbles in code. I ship production applications across the full stack. React, Next.js, Vue, Python, PHP. Docker, PostgreSQL, Supabase. I've rebuilt entire platforms from WordPress to modern stacks. I've debugged enough CSS and enough network latency to know what's realistic to build.
The difference is not that I can code. The difference is that one person owns the entire lifecycle. No handoff tax between design and engineering. No translation loss between prototype and production. When I design a feature, I know how I'm going to build it. When I build it, I already know how I'm going to deploy it.
I use AI agents as force multipliers, not replacements. I direct them under my strategy and feedback. That means I can ship what takes most teams two weeks in two days, without cutting corners on thinking or judgment.
What this means in practice:
- I own features from vague idea to live deployment
- I design with the implementation already in mind
- I adjust scope based on real technical constraints, not guesses
- I build the deployment pipeline alongside the feature
- I debug at every layer from CSS to database queries
- I ship faster because there are no handoffs to wait on
What I Ship
I work across the full stack. Design, code, infrastructure. DevOps, AI pipelines, architecture, automation. I specialize in projects where the hardest part is figuring out what to build and how to make it fit together.
I've shipped across healthcare, fintech, ISPs, membership platforms, and technical infrastructure. The industry changes but the playbook doesn't: figure out what matters, design it, build it, ship it, iterate it.
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, Linux server management. I build deployment pipelines that let me ship without thinking about it.
AI Agent Workflows
Directing multiple AI agents to accelerate every phase of development. I research and design the foundation, then amplify the build with agents under my direction.
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 own the full cycle, so there is no handoff tax and no translation loss between design and code.
Security & Automation
Security audits across 20+ client sites. Vulnerability remediation, standards enforcement, AI-assisted code reviews. Security built in, not bolted on.
How I Decide
Shipping beats perfect. Deadlines sharpen judgment.
A shipped product with rough edges teaches you more than a polished one that never launches. Scope is a feature. The deadline is the forcing function.
Confusion kills conversion.
Every moment a user stops to think is a moment they might walk away. Clarity is the highest form of polish. Good UX guides, bad UX asks questions.
Clarity beats cleverness.
Users don't need to be impressed. They need to know what to do next.
Good UX reduces effort, not adds polish.
If users have to think hard about your interface, you've already lost. The best experiences don't announce themselves.
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 take an ambiguous feature and drive it to production. Scope it, design it, build it, ship it, iterate it. Every step in that pipeline is mine to own. I work with teams, but I don't depend on a chain of handoffs to get things done.
I use AI agents to amplify every phase. I do the thinking, the strategy, the design, the direction. The agents accelerate the execution under my feedback. This lets me move at a velocity that most teams can't match without sacrificing judgment.
I'm direct about tradeoffs. I push back when something hurts the user or the architecture. I translate technical decisions into business language because a feature that ships is better than a perfect one that never launches.
Take ambiguous feature.
Ship production feature.
Scope → Design → Build → Deploy → Iterate. One person, full cycle, no handoff tax.
What I'm Looking For
I'm not looking for a role where I design screens and hand them off. I'm looking for a role where I own the outcome. Features from problem to production. Full cycle, every layer, any stack.
Let's Talk
If you need a Senior Product Engineer who can take a feature from vague idea to live deployment without handoffs, or a consultant who can untangle a stalled system and get it shipping again. Let's talk.
Based in California. Open to remote or hybrid roles at product-focused companies. Also available for consulting engagements.