Small Team. Large Surface Area.
We are early, which means the work is broad and the decisions are yours to make. If you want to build products end to end rather than fill in tickets, this is a good place to be.
What the Job Actually Gives You.
The things that actually shape a career, not a list of snacks.
Career growth
A clear path from where you are now to where you want to be, reviewed openly every six months rather than whenever someone remembers.
Senior mentorship
Every pull request is read by someone more experienced, with comments that explain the reasoning rather than just the fix.
Real ownership
You take features end to end, from schema to release, and your name stays on the work after it ships.
Modern stack
React, Node, TypeScript, Python, AWS and Docker. We upgrade deliberately and pay down debt instead of talking about it.
Build real products
Not internal tools nobody uses. The things you build go live and are used by people who notice when they break.
Balance that is real
Sensible hours, protected weekends, and Friday afternoons kept for learning rather than for catching up.
Honest About Who Thrives Here.
A small team amplifies both fit and mismatch. Read both columns before you write to us.
You Will Do Well Here If
- You would rather ask a blunt question than guess quietly
- You read the error message before you paste it into a search box
- You care that the thing works for the person using it
- You can take a review comment without taking it personally
- You are curious about the parts of the stack that are not your job
This Is Probably Not for You If
- You want a fixed ticket queue and no contact with clients
- You prefer a large team where responsibility is shared thinly
- You are looking for a title more than the work behind it
- You want to specialise narrowly and never touch anything else
Five Steps, No Black Box.
Two to three weeks end to end, and you always know where you stand.
- 01
Apply
Send your CV and anything you have built. A person reads it, and you hear back either way inside five working days.
- 02
Intro call
Thirty minutes with an engineer, not a recruiter. What you have built, what you want next, how we work.
- 03
Technical conversation
Ninety minutes on real problems, no whiteboard puzzles. We look at your code and talk about the decisions in it.
- 04
Test task
A small, scoped piece of real work, done in your own time and reviewed like any other pull request.
- 05
Offer
Numbers, role and start date in writing within two days of the last conversation.
Nothing is open today. Tell us which of these fits you and we will come back to you first when it opens.
Write to Us Before a Role Exists.
Send what you have built and what you want to build next. One of the founders reads it.
Things People Ask Us.
Yes, and it is the best time to. We read every open application, keep it on file for six months, and reach out first when a role opens. Several of our conversations started this way.