We are a small, senior engineering studio that ships software teams depend on every day. If you care how software is built — not just that it shipped — and you want ownership, deep focus, and work you can point at for years, you will feel at home here.
Actively hiring right now
Teams currently growing
Of roles are remote or hybrid
Small teams, real ownership, and the time to do things properly. We optimise for engineers who want to think about the product, not just close tickets.
You own a problem from discovery to production and beyond. No throwing work over a wall — the person who designs it ships it and maintains it.
The people closest to the code make the technical calls. We argue with data and prototypes, not seniority, and we write down what we decide.
If it is not written down, it does not scale. We document architecture, decisions, and trade-offs so the team compounds knowledge instead of losing it.
Reviews are thoughtful, tests are real, and CI enforces the bar. We would rather ship a week later than ship something the next engineer dreads touching.
We ask why before how. Understanding the user and the business is part of the job, not something handed to us on a spec.
We build for the team who inherits the code, including our future selves. Long-term maintainability beats a clever shortcut every time.
These are not aspirations on a wall — they are how we review code, scope work, and decide what 'done' means.
We ship less, better. A smaller surface area of well-built software beats a sprawl of features nobody can maintain.
We design for the load and the team we will have in two years, not just the demo tomorrow — without over-engineering for scale we will never reach.
WCAG AA is part of our definition of done, not a later pass. Software that excludes people is unfinished software.
We set performance budgets and enforce them in CI. Speed is a feature, and it does not survive without being measured.
We think about the threat model early and treat secure defaults as table stakes, not a hardening sprint bolted on before launch.
We read, we write, and we share what we learn in the open. A studio that stops improving is quietly falling behind its own advice.
We keep the list short and real. These are the conditions we think serious engineers need to do their best work.
Work from wherever you do your best thinking. We are async-first and organise around outcomes, not hours at a desk.
Own your calendar. Deep work needs long, uninterrupted blocks, so we protect focus time and keep meetings deliberate.
A yearly budget for courses, books, and conferences — plus the time to actually use it. Growth is part of the job.
TypeScript end to end, current frameworks, and tooling we are proud of. You will not fight legacy to do simple things.
We contribute back and publish our own tools. Your best work here can be work you show the world.
A small studio means real scope early. As we grow, the people who built the foundations lead what comes next.
Five steps, and we tell you where you stand at each one. We respect your time, so we keep it tight and we keep you informed.
Send us the role you want and a little about your work. No cover-letter theatre — show us something you have built.
A real engineer reads every application. We reply either way, usually within a week, with a clear next step.
A conversation about how you think and build — not a whiteboard gauntlet. We talk through real problems, close to the work you would do here.
A wider chat about ways of working, expectations, and what you want next. Your questions matter as much as ours.
A clear offer with the details in writing. We want you to join with full information and zero pressure.
Filter by team to see the roles we are actively hiring for. Do not see a perfect match? Reach out anyway — we hire when we meet the right person.
Own the frontend of products used every day — from design system to shipped feature — with React, TypeScript, and a real bar for accessibility and performance.
Design and build the APIs, data models, and services behind our products, with an eye for correctness, observability, and long-term maintainability.
Shape products end to end — from problem framing and flows to a polished, accessible interface — working shoulder to shoulder with the engineers who build it.
Own the why and the what for a product area — discovery, prioritisation, and a roadmap the team believes in — close enough to the work to make sharp calls.
Tell the studio's engineering story to a developer audience — the journal, open source, and the work itself — with substance over hype.
Keep a small studio running smoothly — people ops, finance rhythms, and the quiet systems that let engineers focus on building.
Our internships are not coffee runs and busywork. You work alongside senior engineers on production code, with mentorship, code review, and a project you can point to afterwards.
You ship features that reach users, reviewed to the same bar as everyone else's — not a throwaway sandbox project.
A dedicated senior engineer guides you, reviews your code, and helps you level up deliberately, not by osmosis.
Strong interns are the first people we talk to about full-time roles. Many of our engineers started exactly here.
Ship real features on production software alongside senior engineers, with dedicated mentorship, thorough code review, and a project you can point to afterwards.
Learn product design on live work — flows, prototypes, and real interfaces — mentored by a senior designer and shipping to actual users.
Anything the page did not cover, ask us directly — a person who builds will reply.
Most are. We are remote friendly and async-first, and each role states whether it is remote, hybrid, or on-site. We work across time zones and care about overlap, not a shared postcode.
It depends on the role — each one lists an experience level. We hire from internship through staff, and we weigh how you think and what you have built far more heavily than years on a CV.
Reach out anyway. We are a small studio and we hire when we meet the right person, not only when a listing is live. Tell us what you do best and what you are looking for.
Five clear steps: apply, initial review, a technical discussion, a final conversation, and an offer. No trick questions or whiteboard gauntlets — we talk about real problems close to the work you would do.
Yes. Our internships put you on real, shipping software with a dedicated mentor, and strong interns are the first people we talk to about full-time roles.
A real engineer reads every application, and we usually reply within a week either way. If we are slow, it is because a person — not a bot — is giving it proper attention.
See where you fit, or just say hello. We hire when we meet the right person — so if the work resonates, we want to hear from you.