Careers · Engineering · Mobile
Mobile Engineer
The roadmap is explicit: iOS and Android ship with the web, not after it. The truck phone is half the product, and it's being built now, alongside the operating loop, so the technician's day works on launch day. This role owns that app.
- Remote · US & Canada
- React Native
- Offline-first
- SQLite
- Expo
The work
What this role actually does.
Build the truck phone
The React Native app, with Expo, for iOS and Android. The next stop full screen, the property's history one tap deep, the quote from the book, payment in the driveway.
Make offline the default
Offline-first on SQLite. A basement with no signal is a normal workplace, not an edge case. The job record keeps working, and sync reconciles cleanly when the truck finds bars.
Design for the wall, with design
Big targets, one thumb, readable in sunlight, because the other hand is holding a flashlight. You'll push back on anything that assumes a desk.
Close the job on site
Photos, notes, time, signature, and payment before the truck leaves. Done means done, and nothing follows the tech home.
Prove it in the field
Test against real conditions (dropped signal, gloves, a phone at arm's length on a ladder) and bring what you learn back into the sync model.
What matters here
What you bring.
01
Respect for sync
You have shipped offline-capable software, or you understand deeply why conflict resolution is a product decision, not a library import.
02
Empathy for the person on the wall
The user wears gloves and is mid-job. You measure your work by whether it survives that, not by how it demos.
03
Ownership of the whole surface
One app, your name on it. Problems belong to a name here, not a standup.
04
No trade background required
Direct field-service exposure is welcome and teachable. Monthly customer calls put the truck in the room either way.
The first ninety days
How the role starts.
Weeks 1-2
Ride the flows
Run the current builds, walk a technician's day through the app yourself, join a customer call, and ship a small fix.
Weeks 3-6
Own an offline path
Take one flow (the stop brief, or the on-site quote) and make it work in a dead zone with a sync story you can defend in writing.
Weeks 7-12
A full day, no signal
A technician's day runs end to end offline: briefed at the first stop, quoted in the driveway, closed from the truck. That's the launch bar you own.
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.