Software Platform Engineer, Insurance Infrastructure
Role details
Job location
Tech stack
Job description
We're looking for a Software Engineer with 3+ years of experience to join the GRID team and own a critical piece of Insify's core platform. This is platform engineering at its hardest: turning genuinely complex domain requirements - carrier contracts, regulatory rules, multi-jurisdiction edge cases - into abstractions that are clean, stable, and extensible across five carriers, four products, and six countries. The code you write becomes the foundation that every other team builds on.
It demands a particular kind of engineering mindset. Not the kind that reaches for a model and hopes it generalises, but the kind that can stare at a mess of carrier spec documents, extract the invariants, and design a data model that will hold up for the next three years. The kind that finds elegance in a well-designed configuration system more satisfying than novelty. The kind that understands that the best platform is one that makes every future problem simpler.
You'll use AI heavily in your daily workflow for coding, debugging, reviewing, generating test cases. But the architecture decisions here are still yours to make. This is one of the places in software where top-notch human engineering judgment creates outsized leverage, and where getting it wrong is expensive for the entire company. What you'll be doing
- Build and extend the GRID platform, Insify's core insurance infrastructure: policy issuance, mid-term adjustments, renewals, carrier integrations, and the back-office portal used by Operations daily.
- Design product configuration systems that allow new insurance products (DI, PnC, motor, legal protection) and new carriers to be onboarded without rewriting core logic. The goal: what used to require an engineering project becomes a config change, and you'll own the architecture that makes that possible.
- Own the policy administration layer that keeps Insify's domain model clean regardless of what's underneath.
- Build renewal and migration tooling at scale: automated renewal workflows, portfolio migrations between systems, and the operational tooling that makes large-scale policy moves safe and auditable.
- Implement underwriting and product configuration logic: raters, field mappings, underwriting rules, product wordings, and the SPC (Scalable Product Configuration) graph engine that determines what a customer can buy and at what price.
- Partner with Operations, Product, and Insurance to translate carrier spec documents and regulatory requirements into clean, testable platform capabilities.
- Set the engineering bar for the GRID domain: correctness, configurability, observability, and backward compatibility. Platform bugs affect every product and every market at once.
- Own incidents and operational health. When GRID has an issue, operations stops. You treat that responsibility seriously.
Requirements
- 3+ years of professional software engineering experience, ideally with TypeScript and AWS (Lambda, DynamoDB, event-driven architectures).
- A strong instinct for abstraction and platform design. You can identify the right data model and API contract that will hold up across five carriers, four products, and six countries.
- Solid fundamentals in distributed systems, event-driven architecture, and API design.
- Comfort with multi-tenancy, configuration-driven systems, and the complexity that comes from operating in a regulated, multi-jurisdiction environment.
- Ownership instinct. You think of the platform as yours and take responsibility for its stability and extensibility.
- Clear communicator. You can work with Operations and Insurance to understand a carrier contract and turn it into a system design.
- AI in your workflow. You actively use AI for coding, debugging, and tooling to move faster.
Nice to have:
- Experience building insurance, fintech, or SaaS platforms with multi-tenant product configuration.
- Familiarity with policy administration systems or insurance product configuration.
- Experience launching products into new markets or countries, including regulatory and localisation complexity.
- Background in building internal back-office platforms used by operational teams.
- Strong observability instincts (Sentry, Datadog) and a track record of operating production systems at scale.
Benefits & conditions
- Competitive compensation that reflects responsibility and impact.