Most frontend engineers write components. I build the systems that make hundreds of components work together: design systems adopted across organizations, CMS tooling that takes marketing teams off the engineering backlog, performance overhauls that cut load times by 80%.
I've been doing this for over a decade, across startups (Winc, FightCamp), enterprise (Internet Brands), and specialized environments (The Library Corporation). The common thread: every engagement left the team faster and more autonomous than I found them.
Below is the full picture: the tools I use, the companies I've worked with, and the philosophy that ties it all together.
My journey began in frontend development, but I've grown into a full-stack engineer and technical leader who bridges the gap between engineering and business teams.
Frontend
Where I spend most of my time, building interfaces that are fast, accessible, and maintainable at scale.
Backend
Enough backend depth to own the full stack: auth, APIs, cloud infrastructure.
Tools
The ecosystem I use to ship with confidence: testing, CI/CD, monitoring, and design handoff.
Specializations
The deeper disciplines I bring to every project.
Autonomy over dependency.
The best thing I can build for your team is the ability to ship without me.
Proof over promises.
I measure outcomes: load times, adoption rates, engineering hours saved. Not effort.
Systems over heroics.
Good architecture means nobody needs to be a hero. I build the foundations that make everyone faster.
Let's figure out if I'm the right fit.
Tell me about your project. I respond within 24 hours, and I'll be upfront about whether I can actually help.
Response time: Usually within 24 hours