Full Stack Developer

We are hiring for aptitude and attitude rather than a checklist of technologies, and we expect to spend real time bringing you up to speed. You would start with well-scoped, well-supported work and grow into owning features end to end. In time, and at whatever pace suits you, there is a route into backend work in Kotlin and into our Rust services if that’s of interest.

We’re flexible on whether this is a full-time or part-time position. Our goal here is to find the right person. The rest we can shape around the individual.

There is plenty to go at: a new forms engine at the centre of the application, a redaction toolkit for the SPA, and a new public-facing portal. All three are cool things to get to work on this early in a career.

We are prepared to consider candidates with little previous commercial experience.

Personal projects, coursework, an apprenticeship, open source contributions or a career change all count.

• Solid JavaScript fundamentals. You understand functions, scope, asynchronous code and the shape of the language, rather than only recognising framework idioms.
• Some React, and enough of an idea of how a component-based UI fits together to explain what you built and why.
• Some exposure to TypeScript, or clear enthusiasm for working in a typed language. Everything we write is typed.
• Comfortable with git - branches, commits, and resolving a conflict without panicking.
• Comfortable at the command line. We develop on macOS and Linux. Windows is not used anywhere in our development stack, and this is not negotiable - WSL included. You would be working in a predominantly bash-based environment: shell, git, package managers, build tools and containers all driven from the terminal. You do not need to be an expert, but you should be at home there rather than reaching for a GUI by default.
• Evidence that you learn things. Something you built and finished, a technology you taught yourself, a problem you chased down. We care far more about this than about which technologies you have already used.
• Working knowledge of LLM tooling, and the judgement to use it well. We use it daily and we expect you to. What matters is that the use is tactical rather than total: knowing which problems it is genuinely good at, recognising when the output is confidently wrong, and being able to explain and defend every line you put your name to. Reaching for it to move faster is fine; reaching for it instead of understanding is not.
• Suited to a small team. We are informal, with very little hierarchy and a happy-to-chat culture: if you want ten minutes with someone, you ask for it. It works best for people who are comfortable speaking up and getting on with things without much ceremony around them.
• Clear written communication. We are a remote team, so most of what you communicate will be written, and describing a problem preprecisely matters.

Everything below is something applicable to how we do things here. It is a description of the environment, not a filter.

• TypeScript in anger, including generics
• Modern React patterns - hooks, context, composition
• Vite, or any modern build tooling
• Testing with Vitest, Jest or similar
• JSON Schema, XML, or any experience of configuration-driven or dynamically rendered UI - anything where the thing on screen is described by data rather than written by hand
• Any exposure to designing an API or a library that other developers consume, however small
• Experience of an agentic coding tool on a real project, and an opinion about where it helped and where it got in the way
• Any backend experience at all, in any language - Kotlin, Java, C#, Python, Go, Rust, Node
• SQL and relational databases
• Docker, Kubernetes, or CI/CD pipelines
• Working with designers, or an eye for interface detail and accessibility

Note that the salary range indicated is subject to experience, and freelance day rates will be discussed subject to initial candidate vetting.