Careers
Small company, whole problems
Nobody here owns a slice of a feature. You own a service — its schema, its API, its deployment, and the question of why a balance looks wrong. That is demanding, and it is the reason the work is worth doing.
Open roles
None posted right now. We would rather say that than keep a role listed that we are not hiring for.
It is still worth writing. We read everything, we keep what is good, and the people we have ended up working with mostly wrote before there was anything to apply to.
Write to us anywayWhat we look for
Four things, and none of them is a language
We care much less about which stack you have used than about how you behave when something does not work.
You finish things
Most of what is hard about this work is the last twenty percent: the error path, the retry, the migration that has to run on real data. We would rather see one thing you took all the way than five you started.
You check instead of assuming
The costly bugs here are the quiet ones — a service returning success while doing nothing. We test credentials against a deliberately wrong key, because matching values prove nothing. That habit matters more than any particular language.
You can own a whole service
There is no team to hand a ticket to. Whoever works on the ledger owns the schema, the API, the deployment and the 2am question about why a balance looks wrong.
You write it down
Every part of this system is documented because the next person — often the same person, six months later — needs to understand it without asking. Code that only works while you remember why is not finished.
Working here
What you would be walking into
Small
Small enough that what you build is visibly yours, and nothing ships without you understanding it.
Remote-friendly
We are based in Cameroon and work the way the work needs. What matters is the thing being done, not where.
Deep, not broad
You will go a long way into one part of the system rather than a short way into all of it.
Real users
Everything here is in production, taking real payments from real people. Nothing you build is a demo.
The tools
What you would work with
Not a wish list — this is what is running in production today.
Services
- ASP.NET Core on .NET 10
- Rust for the real-time tracking path
- PostgreSQL 18 with PostGIS
- Redis for rate limiting
Applications
- Next.js and React 19
- Ionic React for the mobile builds
- Android via Capacitor
- TypeScript throughout
Running it
- Docker on Oracle Cloud
- Caddy, with automatic TLS
- Cloudflare for DNS, CDN and storage
- One machine, sixteen containers
How hiring goes
Short, and about real work. We do not run whiteboard puzzles — nothing here is solved by inverting a binary tree under time pressure.
- 01
You write
Tell us what you would want to work on and show us one thing you finished. A repository, a service, anything real.
- 02
We talk
A conversation about that thing: what was hard, what you got wrong, what you would do differently. It tells us more than any test.
- 03
A piece of real work
A small, scoped, paid task against the actual codebase. You find out whether you like it here, which matters as much as whether we like you.