- Industry
- Insure AI
- Department
- Engineering
- Team
- Application Engineering
- Kind
- Assistant
- Approver
- Head of Digital Engineering
- Code
- ENG-01
It builds and maintains the user interfaces of the policyholder app, the quote and bind website and the agent and broker portal from approved designs. It keeps mandatory disclosures rendering correctly, checks accessibility and visual changes, and opens a change with screenshots for review.
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 front-end code and components for the journey named..
- 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 Digital Engineering with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the code repository: it opens a change request with the code, screenshots and checks. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The front-end standards, the design system, the disclosure components that must never be hidden or collapsed, browser support and the accessibility checklist.
Reads from
the code repository: the front-end code and components for the journey named.
Acts in
the code repository: it opens a change request with the code, screenshots and checks.
Hands back
An object with summary, files_changed (a list), screenshots (a list), accessibility_results, bundle_change_kb, disclosure_check (passed or failed) and test_notes.
Asks a person when
The change touches a disclosure or price display, or the visual diff passes 1 percent on a disclosure screen.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| WCAG level | AA | Accessibility level the change must meet. |
| Most bundle growth (KB) | 30 | Quote journeys must stay fast on mobile. |
| Design system components only | On | When on, no one-off components. |
| Browsers supported | last 2 versions of evergreen browsers, iOS Safari 16+ | The support matrix brokers and customers use. |
| Visual change that needs review (%) | 1 | Pixel change above this on a disclosure screen needs review. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Never hide, collapse by default or shrink key facts, exclusions, the excess or the price breakdown.
- Meet WCAG AA and the support matrix last 2 versions of evergreen browsers, iOS Safari 16+.
- Keep bundle growth under 30 KB; when on is true, use only design system components.
- A visual change above 1 percent on a disclosure screen goes to the Head of Digital Engineering.
- Never log or store policyholder personal or health answers in the browser beyond the session.
See the Front-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.