EU remote
Senior Backend Engineer (TypeScript / Nest.js / AWS)
About this role
Full-time B2B | Remote EU / Poland | US Insurance Context | Start October 2026 We are an AI-native data and technology partner for private capital and healthcare. Founded in 2010 and headquartered in Warsaw, we work with leading PE firms, VC funds, and healthcare organizations to build proprietary data infrastructure, deploy AI solutions, and drive AI-native transformation. Our clients manage a cumulative $1.2T+ in assets.
Our average engagement runs five years. Our NPS sits above 80. We don't need to claim credibility - we can show it. We've also done to ourselves what we now do for clients. We've restructured our own company around AI - tools, policies, roles, delivery models. This isn't a pitch. It's a playbook we've already run, and we're hiring the engineers who will run it for others. The Opportunity Our client is a US insurance carrier building a platform business on top of its own paper: a set of operational services it offers to the specialist insurers (MGAs) it underwrites for.
The first service is claims - the carrier is becoming the claims administrator for its partners, running their claims in a shared instance of a modern claims platform. That platform only knows how to talk to one policy system, and every partner has their own. The missing piece is a multi-tenant policy gateway , and it is the blocking dependency for the first partner's go-live at the start of 2027. You'll be the engineer who builds it.
You'll work in a small pod with our tech lead and directly with the client's staff engineer, engineering manager and claims domain expert, in their codebase and on their AWS. We already run the data platform for the client's first partner, so you join a team that knows both ends of the integration. The environment is fast-moving and the spec is a PRD, not a design - we're expected to propose, decide and deliver, not wait for tickets.
What you'll be doing The core of the work is a greenfield Nest.js / TypeScript service that sits between the claims platform and N external policy systems: it authenticates the incoming webhook, resolves which tenant a request belongs to, fetches the policy (live API call or from a policy store fed by daily file extracts), maps it through a canonical policy model and returns it in the claims platform's schema - with hard data isolation between tenants, because a misrouted policy is a cross-tenant data leak.