Careers
A small technical team, doing work that is actually used.
We build production systems for businesses that depend on them, and we co-build ventures with founders. Both mean real data, real infrastructure, and real consequences when something breaks.
What the work is
Scope, and the accountability that comes with it.
You work on systems people use to run their business, not on internal tooling and not on a proof of concept that gets shelved. That is the appeal and it is also the catch: when something you built is wrong, somebody's Tuesday goes badly, and you are the one who finds out.
Because the team is lean you get the whole shape of a project — the architecture argument, the build, the deployment, the conversation where a client tells you the thing you designed does not match how they actually work.
Remote, based in Canada
Small enough that everyone knows what everyone else is working on, without a standup to enforce it.
Several domains a quarter
Healthcare one month, operations software the next. If you want to spend three years on one codebase, this is the wrong place.
Client contact from week one
You will be in the room when someone describes their business. That is where the real requirements are, and it is not a skill you can delegate forever.
No layers
Nobody between you and the decision. That means the scope is real and so is the accountability when something you chose turns out wrong.
What we look for
Three things, and none of them is a framework.
Production mindset
You think about error handling, observability and the edge cases before they turn into incidents. A demo is not a system, and you have been on the wrong end of the difference.
Integration thinking
You understand that AI is only worth what it connects to, and that the interesting problems are usually in the data path rather than the model.
Breadth with depth
Strong fundamentals somewhere specific, and genuine curiosity about the rest of the stack. Not precious about job titles or about which language wins.
Open roles
None at the moment.
We hire slowly and only when there is work that needs a person rather than a quarter that needs a headcount. When that changes it will be posted here, and it will say what the job actually is.
That said: if you read the three things above and recognised yourself, write anyway. A speculative email from the right person has started more of our hires than a posting has.
Tell us what you have built and what went wrong with it. That is more useful to us than a CV, and considerably more interesting to read.