Senior Software Engineer

FullTime
Remote
Discussed on the first call, set against experience and location.
Open

Three full time positions building AI-native product platforms end to end, from the data model and the API to the screens people actually use.

What the role covers

Product engineering across the whole stack. TypeScript throughout, Next.js and React Native at the front, NestJS and Strapi behind them, PostgreSQL underneath, shipped to Kubernetes. You own a feature from the schema to the screen to the deploy, and you are the person who knows why it works.

What you would actually build

These are platforms with money and schedules moving through them, not brochure sites. A booking platform where a customer describes a trip once and operators come back with quotes, and the operator network that shares work behind it. A cooperative finance platform with a real ledger, loan workflows and the reporting a committee signs off. A headless content platform that serves people and AI clients from the same records.

The problems are the interesting kind: a quote that has to be right the first time, a ledger that has to balance, a page that has to be fast in five languages, a deploy that has to be reversible at two in the morning.

What we look for

You have owned something end to end and lived with it afterwards. You are deep enough in TypeScript that types work for you rather than against you, and you are as comfortable reading a query plan as a render trace.

You write tests that would actually fail if the code were wrong, and you can explain a decision in plain words to someone who was not in the room. Three positions are open, and they are not interchangeable: tell us which part of the stack you want to be trusted with.

How we work

An issue before the work, then one pull request for it, reviewed and merged by a person. Every script that changes data reports what it would do by default and acts only when you pass --execute, inside one transaction, naming the database it reached before it says anything about rows.

Claims are gated on exit codes, not on output that looks right. A merge to main builds and deploys on its own, every image carries a real version, and the way back is written down before the way forward is taken.

The estate runs on its own hardware, so you see the whole path: the schema, the API, the screen, the image, the rollout and the thing that pages someone when it breaks.

How to apply

Use the contact form on this page and attach your CV. Tell us about one thing you built that you are still proud of, and one thing you got wrong and what it taught you. The second answer is the one we read twice.

We reply to everyone who writes a real message. A short note about your own work is worth more here than a cover letter written for anybody.

Apply

Send a short note on what you have built and why this role fits. Applications land in the same inbox as the contact page and are answered within a few days.