Careers
Five engineers.Occasionally, a sixth.
We have no verified open positions today, so this page does not list any. Open applications are read by the founders, and the disciplines we hire into are below.
5
Engineers
the whole studio
5
Systems live
in production now
5
Client regions
BR · AU · IN · US · EU
—
Open roles
awaiting verified score
Open roles
None posted right now. We do not keep evergreen listings open to collect résumés. When a seat exists it appears here with a scope and a salary band.
Disciplines
What we hire intowhen we hire at all
Backend / AI engineering
Python and FastAPI, retrieval pipelines, model gateways, and the data modelling underneath them.
- Python
- FastAPI
- PostgreSQL
- pgvector
- AWS
Full-stack product engineering
Next.js and TypeScript across multi-tenant platforms, with real ownership of the surface you build.
- TypeScript
- Next.js
- React
- Node.js
- Tailwind
Mobile engineering
Flutter and native Android, offline-first sync, and store release engineering.
- Flutter
- Dart
- Kotlin
- Firebase
DevOps / platform
AWS architecture, containerisation, CI/CD, and the observability that makes an on-call rota humane.
- AWS
- Docker
- Terraform
- GitHub Actions
How we work
Small enoughthat your work is visible
Six things that are true of working here, including the ones that will not suit everybody.
You own a system — Not a ticket queue. You take a system from scope to production and stay on it afterwards.
You talk to clients — There is no account layer between you and the person using what you built.
Five people means visible work — Nothing you ship disappears into a monorepo nobody reads. It is in front of a client within weeks.
Review is written — Reasoning goes in the pull request, so decisions are inspectable months later.
Documentation is the job — Runbooks and handover docs are in the estimate, not squeezed in on a Friday.
Timezones overlap deliberately — We work across five client regions and agree the overlap rather than pretending it is free.
Hiring process
Four steps,and the exercise is paid
Send code we can read — a repository, a package, anything you actually built.
Conversation
Forty-five minutes with an engineer about what you built and why you chose it.
Paid exercise
A small, scoped piece of real work. Paid at our normal rate, and yours to keep.
Decision
A yes or a no with reasons, within a week. No silent pipelines.
The studio
Photographs pendingrather than stock photography
Apply
Send something you built and why you built it that way
A repository beats a résumé. One paragraph on a decision you would now make differently beats a cover letter.