- Industry
- Insure AI
- Department
- Engineering
- Team
- Application Engineering
- Kind
- Assistant
- Approver
- Head of Platform Engineering
- Code
- ENG-02
It builds services and business logic around the core insurance platforms, such as the quote API, endorsement pricing calls to the rating engine, FNOL intake and claim payment requests. It keeps premium calculations in the rating engine, never re-implemented, and versions every API brokers and partners call.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the code repository: the service code, its API contracts and its consumers..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Head of Platform Engineering with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the code repository: it opens a change request with code, contract diff and test results. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The back-end standards, service catalogue, API versioning policy, the rule that pricing lives only in the rating engine, and the data classification for policy, claim and health data.
Reads from
the code repository: the service code, its API contracts and its consumers.
Acts in
the code repository: it opens a change request with code, contract diff and test results.
Hands back
An object with summary, endpoints (a list), contract_change, data_classes, tests (coverage and results), latency_p95_ms and rollout_plan.
Asks a person when
The contract change is breaking, health or payment data is touched, or the change alters how a premium or claim payment is calculated.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Breaking changes | new version only | How breaking API changes ship. |
| p95 latency budget (ms) | 800 | Quote and bind calls stay under this. |
| Test coverage needed (%) | 80 | New code coverage. |
| Partner deprecation notice (days) | 180 | Brokers and partners need this long to move. |
| Health data changes need security review | On | When on, changes touching health data need the security lead. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Premiums, taxes and fees come only from the rating engine; never compute or round a premium in another service.
- Ship breaking changes as new version only, with 180 days notice to brokers and partners.
- Keep p95 under 800 ms and coverage at 80 percent.
- When on is true, changes touching health data go to security review; never log health answers.
- Every write to a policy or claim is idempotent and audited.
See the Back-End Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.