Customer Support
Full-time · Remote (Alberta preferred)The person a foreman reaches when a ticket won't submit at 6am.
Our customers are contractors and mine operators. When they contact us it's usually because something is blocking work or blocking payment, and they don't have time for a ticketing system that answers in three days.
You'd be the whole support function: answering the messages, working out what actually went wrong, and telling engineering what keeps coming up. A lot of the job is translating between someone in a truck and someone in a codebase.
You'd probably like this if
- ·You've worked in or around heavy industry, or you're willing to learn what an LEM and an AFE are in the first week.
- ·You can tell someone their problem isn't a bug without making them feel stupid.
- ·You'd rather fix the cause than close the ticket.
Apply for Customer SupportSoftware Engineer
Full-time · Remote (Alberta preferred)Backend and product work on a system that handles other people's money.
TypeScript, Next.js, Firebase. You'd work across the whole thing — the ticket pricing engine, approvals, invoicing, the AFE and PO logic that keeps a contractor's numbers matching their client's.
The unusual part of this job is the consequences. A rounding error here is a real invoice that doesn't match a real signed record. We test the money logic adversarially and we write down why a decision was made, because someone will need to reconstruct it later.
You'd probably like this if
- ·You've built something where being wrong was expensive.
- ·You reach for a transaction before you reach for a retry.
- ·You can explain a tradeoff you made and what you gave up.
Apply for Software EngineerFrontend Engineer
Full-time · Remote (Alberta preferred)Interfaces used outdoors, in daylight, on a cracked screen, at −30, with no signal.
React and TypeScript, with real constraints: our users are outdoors, often with no signal, and in a hurry at the end of a twelve-hour shift. A form that's fine in an office is unusable at a tailgate.
You'd own how the product feels on a phone at 6am and on a laptop in an accounting office at 5pm — two audiences with almost nothing in common.
You'd probably like this if
- ·You care what happens on a bad connection.
- ·You've argued for removing a feature to make something clearer.
- ·Accessibility is something you do by default, not a ticket.
Apply for Frontend EngineerUX Engineer
Full-time · Remote (Alberta preferred)Design the flow, then build it. Not one or the other.
Industrial software is famously bad, and the reason is rarely the visual design — it's that nobody watched someone try to use it in the field. You'd do both halves: work out what the flow should be, then implement it.
That includes talking to actual foremen and actual accountants, and being willing to throw out a design you liked because it added a step to somebody's morning.
You'd probably like this if
- ·You've shipped, not just handed off.
- ·You'd rather watch one person use it than read ten survey responses.
- ·You can defend a decision without being precious about it.
Apply for UX EngineerNone of these, but you want in?
We're small enough that a good person is worth making room for. Tell us what you'd want to work on.
Get in touch