Careers · Design · System & UX
Product Designer
Pre-launch is when the screens get decided: the dispatcher's board on one display, the technician's next stop full screen on a phone. This role exists to grow the midnight design system across web and mobile, and to test it against real crews before launch makes the choices permanent. The product is built alongside real trade work. The research subjects are on ladders.
- Remote · US & Canada
- Design systems
- Field-service UX
- Research
The work
What this role actually does.
Grow the midnight system
One design system across the TanStack Start web app and the React Native truck phone. Components that survive both a dispatch board and a glare-lit driveway.
Design the board
Dispatch on one screen: every job, every truck, every change. The dispatcher's Tuesday outranks our aesthetic preferences, every time. Design for that sentence.
Design the truck phone
The technician's app is not a shrunk dashboard. Big targets, one thumb, wet gloves, sunlight. The flow is the stop, not the screen.
Run field research
Field-service UX research with real crews and monthly customer calls. Questions asked in the shop, findings written down, decisions that cite them.
Document the why
Design decisions live next to engineering decisions, with reasons. The system should let people ship correctly without you in the room.
What matters here
What you bring.
01
Systems discipline
You have built or grown a design system under shipping pressure, and you know when a new component is a solution and when it's a debt.
02
A research instinct
You would rather watch a dispatcher work for an hour than run a survey, and you can turn what you saw into a change that ships this week.
03
Taste that yields to the field
Strong opinions, honestly held, dropped without ceremony when the record from a real crew says otherwise.
04
No field-service background required
We can teach the domain. What we can't teach is empathy for operators. Bring that.
The first ninety days
How the role starts.
Weeks 1-2
Audit and listen
Read the midnight system as it exists, join a customer call, and ship one small refinement through the whole pipeline to production.
Weeks 3-6
Own a flow
Take one (estimate building, or the technician's stop) from field research through shipped screens on web and mobile.
Weeks 7-12
The system stands alone
The midnight system documented well enough that engineers ship correct screens without asking, and a monthly research loop with crews is running on a calendar, not on memory.
The terms, in the open
No surprises at the end.
Compensation, in the open
Compensation is discussed openly in the first call: the thirty-minute intro with the hiring manager, not the final round. You'll have the number in writing before the final interview, and the offer itself arrives in writing within five business days of it. No stage of this process exists to find out what you'll accept.
Five stages, about four hours
A person reads your application within two to three business days. Then the intro call, a sixty-to-ninety-minute technical screen on work like the work (no surprise algorithm puzzles) and three forty-five-minute conversations with the people you'd ship with. The written offer follows within five business days of the final interview. All told, about four hours of actual conversation.
The benefits, as stated
Comprehensive medical, dental, and vision with monthly wellness stipends; a minimum of three weeks PTO plus two company-wide recharge weeks; and an annual learning budget. Roles are remote-first across the US and Canada with quarterly onsites in rotating cities. We don't currently sponsor visas (reviewed annually), and we'd rather say that here than three interviews in.
Apply
One email. A person reads it.
Send your story to careers@thorbis.com. A résumé helps, but the judgment shows in how you describe the work you’ve shipped.