AI Innovation Engineer
Free to start · No card · 5 credits the moment you sign up
Job description
Who are we?
We are the leading online platform for comparing and buying business insurance.
Not to toot our own horn, but we’re shaking things up in the SME business insurance market! We’re all about making it easy and efficient for small businesses to get the perfect coverage they need to stay protected. Say goodbye to headaches and hello to hassle-free insurance!
Location: Sydney, NSW (Hybrid)
Employment Type: Full-time, permanent
Level: Mid-level (3–5 years’ experience)
Team: Technology
The role
We're building an AI-first engineering team. We want an engineer who builds with agents and builds agents: someone who comes up with ideas, proves them fast with POCs, and ships the winners to production, safely, in a regulated insurance environment. You'll work within our guardrails, and when you see a better way, you're free to propose it and build it.
What you'll do
- Build and prove: Build POCs quickly with LLMs, agents and MCP. Define success metrics up front and use evals to show quality, cost and business value before anything scales.
- Engineer spec-first: Write requirements → design → tasks, hand execution to AI coding agents (Claude Code, Kiro) under human review, and keep specs, steering docs and CLAUDE.md in sync with the code.
- Build reusable agent tooling: Package workflows as skills, subagents, hooks, plugins and MCP servers the whole team can reuse. Use hooks, not prompts, for rules that must always hold.
- Orchestrate agents: Pick the right pattern (orchestrator/worker, pipeline, fan-out, routing), or one agent when one will do. Handle state, retries, token budgets and human approval gates, and run agents headless in CI/CD.
- Ship and govern: Turn POCs into tested, observable services and RAG pipelines. Protect personal information, enforce permissions, keep audit trails and set agent autonomy boundaries.
- Improve the framework: Spot bottlenecks and pitch stack changes backed by evidence.
What you'll bring
- 3+ years in software engineering, including shipping LLM-powered applications.
- Agentic coding: Daily use of AI coding agents in real delivery work. You know when to use a skill vs a subagent vs a hook vs MCP.
- Spec-driven delivery: You've written specs an agent executed and reviewed its output critically.
- Agent orchestration: You've built at least one multi-step or multi-agent workflow and know how agents fail.
- Strong fundamentals: Python and TypeScript/Node, API design, testing, CI/CD and AWS (or another major cloud).
- RAG, evals and LLMOps: You've built a retrieval system and an eval harness, and instrumented tracing, cost and latency.
- Security mindset: You design against prompt injection, data leakage and excess agent permissions, and you're sceptical of complexity for its own sake.
Nice to have: our stack
You don't need experience with all of these, they're what we use today, and you'll learn them fast.
AI Coding Agents: Claude Code, OpenHands SDK
Spec-Driven Delivery: Kiro, GitHub Spec Kit, AI-DLC
Models & Agent Runtime: Claude via AWS Bedrock, Bedrock AgentCore, Strands Agents, LangGraph
Tools & Guardrails: MCP, Cedar Policies, Bedrock Guardrails, n8n
Data & RAG: Snowflake (including Cortex), dbt, Fivetran
Evals & Observability: Langfuse, LangSmith, Braintrust, OpenTelemetry, CloudWatch
Platforms: .NET 8, Next.js 15, Salesforce, Atlassian, Terraform / AWS CDK
Bonus points: published skills, Kiro Powers or MCP servers; experience in a regulated industry (APRA CPS 234/230, Privacy Act 1988, ISO 27001, SOC 2).
- Hybrid working model with flexibility to work from home 2 days and the 3 days in the office
- Exciting and rewarding team culture
- Quarterly recognition awards
- Business Casual dress code
- Rewarding Employee Incentive Program
- Employee benefits package
- Growing company with progression opportunities
We are an equal opportunity employer and we do not discriminate on the basis of race, color, religion, sex, sexual orientation, gender identity, national origin, age, disability, or any other protected status. We encourage applications from people of all backgrounds, identities, and perspectives. We are committed to creating a diverse and inclusive workplace where everyone can thrive and grow.
Prepare your application
Use the description above to assess your fit for BizCover. This checklist is guidance from Resumize, rather than additional requirements from the employer. Imported listings can be shortened or change after collection, so confirm the complete description and current availability before sending an application.
Match requirements to evidence
Identify the responsibilities and skills the employer explicitly names. For each important requirement, choose one example from your work, education, training, or projects. Explain what you did, how you did it, and what changed as a result. Include a measurable outcome when you can support it. If you lack a requirement, describe related experience accurately instead of adding an unfamiliar skill to your resume.
Put the most relevant examples near the top of your resume. Keep job titles, dates, qualifications, and contact details consistent across your application materials. Use the employer’s terminology when it describes your experience accurately; a copied list of keywords does not explain your contribution. A short, specific bullet is easier to review than a paragraph that mixes several unrelated duties.
Check the working arrangement
Confirm the location, schedule, employment type, and any eligibility requirements on the employer’s site. A remote label does not establish worldwide eligibility or flexible hours. If compensation, benefits, equipment, travel, or contract duration are missing from this listing, write down your questions for the recruiter. Do not assume details from another opening at the same company apply to this role.
Review before submitting
Follow the employer’s requested file format and application instructions. Open your exported resume and check that its text is selectable, its sections read in order, and its links work. Proofread names, dates, and contact information. Share confidential work samples only when you have permission, and use an anonymized example when necessary.
Submit through a trusted employer or recruiting destination. If the original listing has disappeared, search the employer’s careers page for the title rather than assuming the vacancy remains open. Save the application date, job reference, and the version of your resume you sent. Those details help you prepare for a later conversation and avoid submitting conflicting information through several job boards.
Review your resume for writing and readability feedback, or browse other openings if this opportunity is unavailable.