Build things thatstay built
We are a small studio, so everyone here is close to the work and to the client. That means more responsibility than a large agency would hand you, and a shorter path between an idea and something running in production.
Real ownership of the work
You are on the call with the client, not receiving tickets second hand. You will know why you are building something, not just what to build.
Range, not one narrow lane
A store one month, a booking system the next. You will work across CMS platforms and custom stacks rather than maintaining a single codebase forever.
Code review as teaching
Every pull request gets read by someone more senior. Reviews explain the reasoning, because the point is that you write the next one better.
Sane delivery
We quote fixed scope so nobody has to absorb a bad estimate with a weekend. If a project slips, we fix the plan rather than the hours.
Open roles
We have no roles open at the moment.
We still read every application. If you write good code or design good interfaces, send us something you have built and tell us what you did on it. We reply to everyone, and we keep good applications on file for when a role opens.
Send an open applicationHow we hire
- 1
You send your work. A repository, a live site, or a case study. We care more about something you finished than a formatted CV.
- 2
A conversation. Around 45 minutes on what you have built, what you would do differently, and what you want to get better at.
- 3
A short paid exercise. A small, realistic task close to the work you would actually do. We pay for your time on it.