About the Role
<p>Searoutes makes the emissions data that shippers use to run and reduce their<br>logistics. It is an operational problem before it is an environmental one, and<br>in our hands it is mostly an engineering one.</p><p></p><p>We are hiring a <strong>senior engineer</strong> who works across our web frontend and our<br>infrastructure — the same two codebases, in the same week. Someone who ships a<br>product screen on Monday, changes an identity-provider flow on Wednesday, and<br>considers those the same job.</p><p></p><p>We are looking for a broad profile rather than a specialist. The next year is<br>mostly platform work with a user-facing edge — <strong>user management, API gateway</strong><br><strong>management, payments, SEO, and a great deal of compliance, GDPR and ISO 27001.</strong></p><p></p><p>If you are passionate about the environment, proactive and pragmatic in getting<br>things done, and love to work in a complex but fascinating industry where you<br>learn every day — then this is the place for you.</p><p></p><p><strong>The work in front of us</strong></p><p></p><p>Some of the items on our tech roadmap for the coming year. Bets are picked a<br>cycle at a time and shared out, so you would take the ones that suit you and<br>grow into the rest.</p><p></p><ul><li><strong>Product and marketing UI in React</strong> — multi-brand, WCAG AA, strong on<br>technical SEO, fast enough to hold a performance budget.</li><li><strong>User management and identity</strong> — Keycloak realms, organisation hierarchies,<br>partner brokering, and the entitlement model in the app.</li><li><strong>API gateway work in APISIX</strong> — routes, plugins and auth policy as code.</li><li><strong>Payments and billing.</strong></li><li><strong>ISO 27001 and GDPR</strong> — access control, change management, audit logging,<br>observability and alerting, consent and retention.</li><li><strong>The infrastructure underneath</strong> — Pulumi in TypeScript, Docker Swarm on<br>Hetzner, Cloudflare at the edge, Tailscale for all engineer and CI access.</li><li><strong>Third-party integrations</strong> — usually the seam between two systems that were<br>never designed to meet.</li></ul><p></p><p>Nobody arrives fluent in all of that, and we are not expecting it. We want<br>someone strong across a good part of it, comfortable being new to the rest, and<br>used to working things out — with a team and with agents, rather than alone.</p><p></p><p>Also in daily use: Postgres and PostGIS, Valkey, ClickHouse; Vite, Tailwind and<br>Radix; Jest and Playwright; GitHub Actions; HAProxy. Most of what we write is<br>TypeScript, strict — though our core API is Java and Spring, and the identity<br>layer has Java in it too, so how far you go into that side is up to you.</p><p></p><p><strong>How we work</strong></p><p></p><p><strong>LLM-native, in the codebases you would work in.</strong> They are built around<br>agent-assisted development rather than merely tolerant of it — the conventions,<br>the tooling and the review gates all assume it. Agents do most of the<br>implementation and much of the review; humans design, verify and approve. What<br>we are really hiring for is <strong>judgement over output you did not write by hand</strong>:<br>knowing what to specify, what to check, and what to throw away. The bar did not<br>move when the tooling did.</p><p></p><p><strong>Shape Up, and you own what you take.</strong> Roughly three weeks of building, then a<br>week of cooldown, with bets chosen at a betting table. We are small enough that<br>an area becomes yours quickly — you make the calls inside it and you answer for<br>how it turns out. We hand out problems, not the steps that solve them.</p><p></p><p>Remote first, with most of the team in Europe and everyone together in person at<br>least twice a year. Significant technical decisions get written down, and a<br>green build is never on its own enough to merge.</p><p><strong>Requirements</strong></p><p>You'll thrive here if you have…</p><p></p><ul><li><strong>Senior full-stack experience</strong> — you have owned features from the browser to<br>the machine they run on.</li><li><strong>A track record of taking something and running with it</strong> — a domain, a<br>migration, a subsystem you took on, decided and stayed accountable for.</li><li><strong>Taste.</strong> You can tell a good design from a merely plausible one, and you<br>will reject work that functions but is not right — your own, and an agent's.</li><li><strong>React beyond the client</strong> — server rendering, static generation, data<br>loading and hydration; you know what runs where and why it matters.</li><li><strong>TypeScript at strict</strong> — typed boundaries, and an instinct for when types<br>are carrying real weight.</li><li><strong>Infrastructure as code</strong> — Pulumi ideally; Terraform if you are ready to<br>pick up Pulumi.</li><li><stron