Policy administration
Product configuration, versioning, endorsements and renewal processing across long-lived books.
Platforms the market barely trains anyone for
Insurance runs on long-lived, heavily configured systems that few engineers encounter outside the sector. Policy administration, claims and underwriting platforms carry decades of accumulated product rules. Recruiting for them through general channels returns volume and very little relevance.
01 A narrow talent pool
Configuration knowledge is learned on the job, nowhere else
Nobody graduates knowing how a policy administration platform is configured, how product versioning interacts with renewal cycles, or why a claims workflow branches the way it does. That knowledge accumulates only through exposure — which means the people who hold it are few, already employed, and rarely answering job adverts. Sourcing for insurance is a search problem, not an advertising problem.
02 System areas
Where we source into
Claims automation
Intake, triage, straight-through processing and the exception paths that decide customer experience.
Underwriting workbenches
Rules engines, referral routing and the tooling underwriters work in every day.
Actuarial and analytics engineering
The data engineering around reserving, experience analysis and model inputs.
Distribution and agency systems
Broker and agent portals, commission calculation and the integrations behind them.
Legacy interfaces
The batch jobs, file transfers and interfaces that hold an older estate together during modernisation.
03 How we search
Direct approach, not advertising
For scarce insurance capability we map where the skill actually exists and approach people directly, including those not looking to move. That takes longer than posting a role, and we would rather set that expectation honestly than send you twenty adjacent profiles to appear responsive.
- Market mapping before sourcing, so we know how large the realistic pool is
- Passive approach to people already in comparable platform roles
- Deep assessment against your specific configuration and product context
- A realistic timeline stated up front, including when we think a requirement is hard
04 Adjacent capability
Sometimes the answer is a transferable background
Where an exact platform match does not exist in the market, we will say so and propose the nearest genuinely transferable profile — an engineer from a comparable rules-driven estate, with a realistic view of the ramp-up involved. You decide whether that trade is worth making. What we will not do is present an adjacent profile as an exact one.
Which platform and which skill?
Tell us the system, the product context and the seniority. We will map the market and tell you plainly how findable it is.
Share a Requirement