About Revvable
Revvable is the CRM and website platform for powersports dealerships: motorcycles, side-by-sides, ATVs, marine. We run the software dealers use to sell, and we build the websites their customers shop on.
Apex is our website product. Think Shopify for powersports: thousands of dealer websites, all managed from inside the CRM, built on Astro and Tailwind and deployed to Cloudflare.
The Role
We are hiring a web engineer who is genuinely excellent at HTML and CSS and who builds with AI coding agents every day.
You will own the template system that every Apex dealer site is built from, and you will launch dealer sites onto it. That means writing clean semantic markup, holding a strict design system, getting SEO right on sites that have real traffic to lose, and moving fast because you work with Claude Code as a matter of routine.
This is not a React job and it is not a design job. It is a job for someone who loves the browser platform, has strong opinions about markup and CSS, and has figured out how to go several times faster with an AI agent without ever shipping something they cannot explain.
What you will do
- Build and extend our template system: page layouts, reusable content blocks and their variants, and the brand-token system that lets every dealer look different inside a fixed structure.
- Launch new dealer websites, including migrating dealers off a legacy CMS without losing their search rankings.
- Own correctness on every site we ship: page titles and meta tags, canonical URLs, structured data, redirect maps, accessibility, and Core Web Vitals.
- Work in Claude Code daily, and write what you learn back into the repo (docs, conventions, lint rules) so it applies to everyone after you.
- Extend our automated browser test coverage so site launches stop being checked by hand.
- Work directly with the founder and a small engineering team. Short feedback loops, no layers.
What we are looking for
- Deep, hand-written HTML and CSS. Grid and flex without guessing. Custom properties, container queries, cascade layers, stacking contexts. You can open devtools on a layout you have never seen and find the problem.
- Semantic markup by reflex. You know why heading order, landmarks, and label association matter, and what a screen reader does with each.
- Real SEO and performance experience on sites where a regression would have cost someone money. LCP, CLS, INP as numbers you have actually moved.
- Fluency in a terminal and with Git. Command line, branches, reading a diff before you commit.
- A working practice with AI coding agents, and clear opinions about where they fail. You read what the agent produces, you verify in a real browser, and you know when a three-line hand edit beats another prompt.
- Comfort inside constraints. This is high-volume production work in a tight design system. No raw hex colors, no freeform fonts, no inventing a new pattern when one exists.
- You verify before you claim it works. You open the page, check the console, take the screenshot.
Nice to have
- Astro, especially the difference between prerendered and server-rendered pages
- Tailwind at config level, not just class recall
- Cloudflare Pages or Workers, DNS and domain cutovers
- Alpine.js, HTMX, or any background in adding behavior to server-rendered HTML
- Template languages such as Liquid, Handlebars, or Jinja
- CMS migration experience: dotCMS, WordPress, Shopify themes, Webflow at scale
- Automotive, powersports, or marine dealer websites. You know what a vehicle detail page is and why dealers care about it.
- Playwright or other browser automation
- Figma literacy: you can match a comp without asking for redlines
Please send resume
