Small team.
Long specifications.
We write the spec before the code. Over four hundred user stories sit behind Karos Cloud, and every one of them was argued about first. If that sounds slow, this is not the right place.
Decisions get written down.
Then they get built.
- Specification first
- A feature is described, argued over and written down before anyone opens an editor. The Capability × Role matrix existed before the interface did.
- Small surface, high stakes
- We build for energy operations, where being wrong is expensive. That shapes everything — no silent failures, no clever shortcuts, no shipping to see what happens.
- Remote, anchored in Calgary
- The company is Canadian and the data stays here. Some roles need Alberta hours; most need overlap rather than a desk.
- AI as a tool, not a headcount plan
- We build agentic software and we use it. We are not replacing the judgement we hire for.
Nothing open right now.
We still read every note.
We hire in small bursts, usually when a portal moves from specification into build. When roles open they are listed here first, and shared on LinkedIn the same week.
Speculative
Tell us what you would build
Send one page to [email protected]. What you have shipped, what you would change about Karos after reading this site, and how to reach you. No cover letter, no portfolio deck.
[email protected]We reply to everyone, including no. If you have not heard back within two weeks, write again — something went wrong on our side.
See it running on
your own data shapes.
Thirty minutes in a working environment configured for your sector. Live in under a day.