Probook is the AI Operating System for the home services industry, transforming how plumbing, HVAC, and electrical businesses operate.
Our impact is real. Dispatching the right technician to the right job can mean the difference between a $300 “band-aid” fix and a $20,000 system replacement. By automating previously high-touch workflows around-the-clock, Probook ensures a consistent customer experience without the need for 24/7 live staffing. We unify our customers’ processes into a single, scalable platform, giving businesses one place to run their entire dispatch operation.
The role
You are our first designer. You own how Probook looks, feels, and works across the web app, mobile, and Chrome extension, and you ship the frontend yourself.
That second part is not a stretch goal. Most of what you design, you will build and merge. If your process ends at a Figma handoff, this is not the role.
The software this industry runs on looks like it was designed in 2008. For a lot of our operators, Probook is the best-designed product they use at work. You set that bar from here.
What you’ll do
•
Own UI/UX quality across all three surfaces, end to end
•
Ship production frontend changes yourself — design through merge
•
Establish Probook’s visual and interaction language from scratch
•
Sit in on customer calls, watch operators work, and turn what you see into things that ship
•
Partner with engineers from spec to ship, and with the founders on product direction
•
Use Claude Code, Cursor, and similar to go from problem to multiple working flows in a day
What we’re looking for
Required:
•
4–6 years of product design experience, ideally 2+ years at startups
•
A track record of merging your own frontend code to production. We will ask for specifics and look at the work.
•
B2B or ops-heavy product background.
•
Strong portfolio of shipped product work
•
Turnaround in hours, not weeks, without dropping quality
What separates the top of the pool:
•
Taste you can’t switch off - you see the typographic inconsistency and you fix it
•
You can explain why a decision is right, not just show the artifact
•
You explore the problem properly before converging, then converge fast
•
You pick the important flow over the interesting one without being told