Careers
Build software that ships and then keeps running
We run B2B SaaS in production and build it for other companies. If you want scope, ownership, and the discomfort of being on call for your own code, this is a good place to work.
Open roles
What we are hiring for
Senior Full-Stack Engineer
Own client products end to end — architecture through production — and stay on call for what you ship.
Product engineeringRemoteFull-timeSeniorAI Engineer
Take AI features past the demo — evaluations, routing, fallbacks, and cost you can actually measure.
AI integrationRemoteFull-timeMid to seniorPlatform & Reliability Engineer
Own the delivery pipeline, the edge, and the observability that lets a client's team run what we built.
Cloud and platformRemoteFull-timeMid to seniorProduct Designer
Design B2B software that respects the person using it, and ship it in the browser rather than in Figma.
Product engineeringRemoteContract or full-timeMid to senior
The work
What it is actually like
You own things end to end
The person who writes the feature deploys it, watches it, and answers for it. There is no separate ops team to hand it to.
Real leverage, real scope
Carrying a partner portfolio and client builds at once only works because we invest hard in shared infrastructure. Improving that layer is the highest-value work here.
Breadth is the point
In one quarter you might touch genomics tooling, a music generation pipeline, and a multi-tenant workspace. It is not a monoculture.
Written over verbal
Decisions get written down. It is how we stay coherent across many codebases without living in meetings.
Hiring process
Short, and mostly about real work
No whiteboard algorithms. We look at what you have built and then build something small together.
- 01
Send your work
A repo, a shipped partner, a write-up. Whatever best shows how you think.
- 02
Conversation
45 minutes on what you have built and what you want to own next.
- 03
Paid work sample
A small, scoped, paid piece of real work on a real codebase.
- 04
Decision
A yes or a no within a week, with reasons either way.
What we look for
Signals that matter to us
- You have shipped something people actually use
- You can explain a tradeoff you got wrong and what it cost
- You write clearly — decisions, docs, and commit messages
- You are comfortable owning a system in production
- You would rather delete code than add an abstraction
No listing that fits? Write anyway.
We hire when we meet the right person, not only when a requisition is open. Tell us what you would want to own here.