About the Company
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. We've restructured our own company around AI - tools, policies, roles, delivery models.
The Opportunity
Our client is a US insurance carrier building a platform business on top of its own paper. 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.
Responsibilities
- Design and build the gateway service on the client's Nest.js-based internal framework and AWS, proposing infrastructure changes as Terraform PRs for their DevOps team to apply.
- Implement the webhook contract: HMAC authentication in application code with secrets in Vault, IP allowlisting, ISO-8601 date handling, policy-version-at-date-of-loss selection.
- Build the tenant router and registry with composite resolution and well-defined failure behaviour.
- Build the source adapter framework - a common interface with per-source auth, timeouts, retries with backoff and circuit breaking.
- Build the batch path: SFTP landing zones per tenant, file validation and quarantine, idempotent loads into a PostgreSQL policy store with snapshot retention and freshness monitoring.
- Define the canonical policy model and the shared canonical-to-target mapper; take the first partner's mapping tables through review with the client's claims expert.
- Ship per-tenant observability (structured logs, metrics, Grafana dashboard, freshness and error-rate alerts) and an onboarding runbook.
- Write isolation negative tests as a release gate, run failure-mode drills and end-to-end walkthroughs in the client's sandbox, and support their security review.
- Collaborate directly with client engineers and domain experts across time zones, largely async. Some availability in PT timezone would be required - not more than once a week.