Much of our work is replacing or extending systems that already carry a business. That means the interesting problems are rarely greenfield: they are about migrating safely, integrating with something old, and not breaking what people depend on today.
What you will be doing
Designing and building APIs in Node.js, with Python and .NET on some engagements.
Modelling data properly. Most performance problems we inherit are schema problems wearing a disguise.
Integrating with systems that were not designed to be integrated with, including ERPs and insurers' platforms.
Writing migrations that can be rolled back, because some of them will need to be.
Owning what you ship through to production rather than handing it over a wall.
What we are looking for
Around four years building and running back-end services.
Solid SQL. Not ORM familiarity, actual SQL, including knowing why a query is slow.
Experience with a real migration or cutover, and an honest account of what went wrong in it.
Security as a habit rather than a checklist: authn and authz, secrets handling, input validation.
Clear writing. Our clients read our design notes.
Nice to have
Infrastructure as code, containers, CI/CD pipelines you have actually maintained.
Event-driven or queue-based architectures.
Exposure to a regulated sector such as insurance, finance or healthcare.
How we work
Design is discussed before it is built, in writing, in a document anyone can argue with. Code review on everything. If a plan turns out to be wrong halfway through we change it rather than defending it.
Applying
Send a CV. If you can describe a system you built that is still running, and what you would do differently now, that is the part we will want to talk about.