Careers
Build the part everyone else skips.
Anyone can make a model write code. We are building the review gate, the isolated worktree, the health check and the rollback that make it safe to let it. That is the hard half, and it is the half we hire for.
What it is actually like
Six things that are true here and not everywhere
No table tennis. Here is what genuinely differs, including the parts you may not want.
You file requests into the product you build
Work on Capybari reaches Capybari's own board. You will plan a request, approve a plan, review an agent's diff and read its completion report before lunch. Every bad edge in the product is an edge you personally hit.
Written before spoken
A decision that is not written down has not been made. Proposals are documents, not slide decks, and they get read before the call rather than presented during it.
The gates apply to us
Nothing reaches our default branch without review, and anything touching deployment, credentials or the agent sandbox gets a security pass. Being in a hurry is not an argument that has ever worked here.
You will be near production incidents
We ship a product whose job is deploying other people's software. When ours misbehaves, engineers look at it — not a separate operations team. If that is not the job you want, this is the wrong company and we would rather say so now.
We publish our gaps in public
The roadmap says what we have not built. The pricing page lists what Enterprise buyers cannot have yet. You will be asked to write those sentences about your own area, and to resist the urge to soften them.
Small enough that scope is yours
You will own an area rather than a ticket queue, and you will do some of your own design, testing and support triage. Nobody's job title decides whose answer is right.
Benefits
What comes with the job
Everything below is PLACEHOLDER until finance and legal have confirmed it for your jurisdiction. We would rather show a draft than an empty section.
- Salary band published in the job description — no "competitive", no negotiation-by-nerve
- Equity for every permanent role, with the strike price and the vesting schedule explained in writing before you sign
- Remote-first, hired where you already live, within the supported time-zone band
- Four-plus weeks of paid leave, plus local public holidays, with a minimum you are expected to take
- A real hardware budget — the machine you want, replaced when it stops being fast enough
- Health cover appropriate to your country, arranged rather than reimbursed
- Learning budget for books, courses and one conference a year, with time to attend it
- Parental leave beyond the statutory minimum wherever we are permitted to offer it
- No core hours, but genuine overlap with your team on written work
- Two focus days a week with no internal meetings scheduled at all
Open roles
Where we need people right now
Each role links to a short application form. Tell us what you have built; a person reads every one.
The roles in one paragraph each
What you would actually be doing
Founding Engineer — Agent Runtime. Own the loop that turns a planned task into a finished branch: dispatch, the worktree lifecycle, dependency ordering, live run streaming, the mid-run question a specialist asks a human, and the structured report at the end. You will spend real time on failure modes, because that is where the product is judged.
Backend Engineer — Deployment & Operations. Own deployment targets and everything downstream of merge — the SSH transport, deploy phases, health-check types, diagnostics, automatic rollback to the last healthy commit, and the investigation that opens when a deploy fails. If you have carried a pager and have opinions about what should have been logged, we want the opinions.
Product Designer. Own the board, the plan view, the review gate and the investigation timeline. The brief is unusual: the interface must get quieter as the situation gets more serious. You will design dark and light as equals, work at 320px first, and be asked to delete more than you draw.
Developer Advocate. Write the guides, record the walkthroughs, run office hours in Discord, and answer the hard questions in public. This is a writing job first. If you cannot explain an isolated git worktree to a non-technical founder in three sentences, this will be uncomfortable.
Customer Engineer. Sit with new teams through their first request, first review gate, first deployment target and first rollback, then feed what you learn straight back into the product. Part support, part solutions engineering, part product research. The people who do this job well end up deciding the roadmap.
Security Engineer (part time or contract). Review the agent sandbox, credential handling, the read-only default on investigations and the write-access escalation path. Run our disclosure process. Tell us, in writing, what we are still getting wrong. We are pre-audit and say so on the pricing page; you would be the person who changes that.
Hiring process
Four stages, about three weeks, no surprises
We tell you the whole process at the start and we do not add stages to it afterwards. Timings below are targets, not guarantees, and are PLACEHOLDER until confirmed.
-
Application — you write, we read. Send the form, or email careers@capybari.com. No cover letter theatre; two paragraphs about something you built and what went wrong with it beats a page of adjectives. We reply within five working days, including when the answer is no.
-
Intro call — 30 minutes, with the person you would work with. Not a recruiter screen. We describe the role honestly, including the parts that are tedious, and you ask whatever you like about the company. Salary band and equity are discussed here, not at the end.
-
Paid exercise — about three hours, done in your own time within a week. A real, scoped problem from our backlog. We pay for your time at a fair contract rate whether or not we make an offer. You may use Capybari, or any other agent tooling, and we would rather you did — how you review what a machine wrote is exactly what we are trying to observe.
-
Two conversations — 60 minutes each, in the same week. One on the exercise: what you decided, what you rejected, what you would do with another day. One on working together: how you handle disagreement, ambiguity and the Friday-evening deploy you should not do.
Then a decision within three working days, with a written reason either way. References only after an offer, and only with your say-so.
We do not run whiteboard algorithm rounds, we do not ask for unpaid take-home projects, and we will not ask you to build a feature we intend to ship.
None of these fit?
Write to us anyway
Use the product before you apply
The free plan takes a few minutes and one repository. File a request, read the plan, and turn up to the intro call with an opinion about what we got wrong.
No card required · A person replies to every application