Axel — design, code & growth
Founding Design Engineer at Axel (YC W19), building through the team's growth from 0 to 30M GMV and 100K+ users. I own product design and frontend delivery, shipping PRs alongside brand, campaign and email work that supports growth.
Visit live → helloaxel.com- Role
- Founding Design Engineer · Full-time
- Period
- Dec 2025 — Present
- Client
- Axel
- Themes
- Design engineering · Frontend PRs · Brand & growth

- 0M
Axel GMV · from 0 · team milestone
- 0K+
Axel users · from 0 · team milestone
- PRs
My primary deliverable
- 0
Transactional email templates
01
A founding role, from product decisions to production
Since December 2025, I've worked full-time as Axel's Founding Design Engineer, reporting directly to the CEO. I take product problems from early exploration through interface design, frontend implementation, testing and engineering review. My remit also covers the brand and the creative work that brings people into the product.
Product design
User journeys, interaction design and the details of booking and membership experiences.
Frontend engineering
Production React, reusable components, responsive layouts, interaction states and motion—delivered as PRs.
Brand & campaigns
Visual identity, core advertising campaign creative and the landing pages that connect them to the product.
Email & testing
Transactional email design and implementation, product QA and iterative testing.
02
Building through 0 → 30M GMV
Axel grew from 0 to 30M GMV and 0 to 100K+ users. My contribution spans the experience people discover, the product they use and the communications they receive: product design, frontend PRs, brand, campaigns and email. I work with the team to turn growth priorities into changes we can ship, test and refine.
03
I ship pull requests
My primary deliverable is a reviewable PR. I work in the frontend codebase, building the components, layouts, states and interactions needed to carry an experience into production. On helloaxel.com, that includes the landing experience, conversational interface and motion. A working preview lets the team review the actual behavior alongside the code.
- 01
Frame the problem
User need, business goal and engineering constraints
- 02
Design & prototype
Flows, visuals and interaction states
- 03
Implement & test
Production frontend, responsive behavior and QA
- 04
Ship a PR
Focused diff, working preview and review context
04
The collaboration runs both ways
I connect design and engineering in both directions. Design → engineering: I turn intent into components, interaction states and PRs that engineers can review. Engineering → design: I bring implementation feedback, real data and technical constraints back into the experience. Working with the lead engineer, I help keep the design and the running product aligned as both evolve.
Founding Design Engineer
Aspen
Lead engineer
Engineering
Focus either direction to explore the collaboration
| Direction | What I bring | What the team can review |
|---|---|---|
| Design → engineering | Flows, visual decisions, components and frontend implementation | A focused PR with a working preview and scenarios to check |
| Engineering → design | Constraints, data states, implementation feedback and QA findings | Updated interactions, states and design decisions |
05
Fast iteration with AI coding tools
I use AI coding tools throughout prototyping and implementation to move quickly from a design decision to a working change. The shared workflow with engineering gives that speed structure: focused PRs, clear review context and checks appropriate to the change. I stay responsible for the experience, the code I submit and the testing behind it.
Build quickly
Use AI to explore interactions, implement frontend changes and iterate in the product's existing stack.
Make review concrete
Pair the code diff with a preview and the user scenarios the change affects.
Match review to impact
Work with engineering on behavior, data and sensitive flows; verify visual and interaction details throughout.
06
One experience, from the ad to the product
I work across branding, visual identity and core advertising campaigns, carrying the same visual direction into landing pages and the product. That scope connects acquisition creative to what a traveler sees next. Within the product, my work includes booking and membership experiences, with attention to how people understand membership value and savings.
“I connect the brand people discover with the product they actually use.”
07
Email is part of the product
I design and maintain 28 transactional email templates in Customer.io and Liquid, from onboarding to cancellation. The work combines visual design with implementation: using real event data, handling missing values and checking how messages render. Email carries the same care as the interface because it is often where people learn what happened and what to do next.