Note: The job is a remote job and is open to candidates in USA. Dalton Mills is the AI operating system for the trades, providing a platform that allows contractors to build the software their business needs without coding. The Principal Product Designer will own the product's UX and visual identity, designing and building industry-specific experiences while ensuring quality and consistency in the component library.
Responsibilities
- You'll own the experience, the identity, and the visual language of the product
- You own the product's UX and visual identity, the component library the product is built from, and the industry-specific experiences that make it feel native to each kind of business we serve
- In practice: you don't just spec the component library, you build and maintain it in code
- You don't just mock up a feature, you take it as far toward production as you can, with tools like Claude Code and Cursor, so engineering extends your work instead of rebuilding it
- You stand up our industry experience templates, the base flows and defaults that make the product feel native to a pest control company versus an HVAC company, as living, reusable systems, not static screens
- We measure the work by what's in customers' hands, not what's in Figma
- You don't need to be a full-stack engineer
- You do need to already be building
- Past the curious stage: you've used AI build tools like Claude Code, you've worked directly in code like React, and you treat shipping as part of the craft, not someone else's job
- You won't have deep engineering chops, and that's fine, we'll help you go deeper
- But 'I design it and I ship it' should already describe how you work, not how you'd like to
- What you'll own: Product UX and identity: how the product works, feels, and is experienced end to end
- The component library: the reusable building blocks the product is built from, owned in code, kept clean and consistent so engineering ships fast without breaking the bar
- Industry-specific workflows: the templates, defaults, and flows tailored to each industry we serve, pest control, HVAC, and beyond, built as living systems so each new customer starts from something purpose-built for their world
- Visual and craft quality: setting the standard for the product and raising it over time
- Shipping: taking your own work toward production, not handing it off at the mockup
- What success looks like: Week 1: your first design is live in the product
- Day 30: you own the design of a major product surface end to end, the component library is taking shape in code, and you've stood up the first industry template
- Day 90: the product feels noticeably better than the day you joined, the component library is yours, the first industry experiences are live, and you're shipping your own work, not just specifying it
Skills
- Exceptional design taste. A strong point of view on what good looks like, and a portfolio that proves it
- You already build. You've used AI build tools like Claude Code to take work toward production, and you've worked directly in code like React. You don't hand designs over the wall, you carry them forward yourself
- Design-system experience. You've built or maintained a design system or component library, and you know what it takes to keep one clean, consistent, and usable by engineering
- Ownership of ambiguity. You can take a broad, open problem, like 'what should the HVAC experience be?', and turn it into a system others can build on
- A high bar and thick skin. You welcome direct feedback because you care about the result more than the ego, and you want to raise the quality bar over time
- Comfort with early-stage speed. You're energized, not paralyzed, by a blank canvas and a fast pace
- Deeper engineering skills beyond the front-end (back-end, mobile)
- Experience designing for home-services or field-services verticals
- Exposure to vertical SaaS or operations-heavy software
Company Overview