About Artificial

Help shape the future of specialty insurance

At Artificial, we’re building the next generation of technology for the specialty (re)insurance market. Our mission is to transform how brokers and carriers operate in complex markets by removing operational barriers and enabling smarter, faster decision-making. We use modern technology to solve real challenges for some of the world’s leading brokers and insurers. By automating the repetitive and structuring the complex, we help our partners unlock new opportunities for innovation and growth. You’ll be joining a collaborative team that values curiosity, ownership, and continuous learning. We work in an environment where ideas are heard, support is built-in, and outcomes matter. Everyone here has the chance to make a tangible impact on our products, our customers, and the industry. We've just raised $45M (£33M) in Series B funding from lead investor CommerzVentures, new investor Move Capital, as well as all existing shareholders. This investment round gives us the room to grow with confidence, continue to innovate, and ensure that Artificial remains the first choice for brokers and carriers seeking a smarter way to trade digitally. Join us, and take the chance to be a part of something that will change the landscape of insurance for generations.

About the Role

We are looking for a Quality Engineer to own test automation across Artificial's product platform. This is a hands-on technical role: we already have a substantial automated test suite - roughly 680 Playwright tests alone, plus extensive backend coverage - but it's grown quickly without a dedicated owner, and needs real structure, consolidation, and meaningful metrics built on top of it. You'll start on Platform, bringing structure to what exists and establishing standards for what gets added next, then extend automation into Transform/customer-configuration testing over time - an area with no automated coverage today, only manual execution by our existing testers, in work that's highly specific to each client.

Key Responsibilities

• Reorganisation and consolidation: Bring coverage, completeness, and integrity to our existing ~680-test Playwright suite (plus extensive backend coverage) - identifying and removing duplication, fixing or removing flaky tests, and establishing clear structure and naming conventions where the suite has outgrown its original organisation
• Meaningful metrics: Build real, trustworthy metrics off the back of the existing suite - coverage mapped to actual product routes and features (today's closest proxy, Playwright page objects, doesn't map cleanly to routes), pass/fail trends over time, and flaky-test tracking
• Ongoing addition and maintenance: Own the suite as a living asset, not a one-off clean-up - adding new automated coverage as features ship, maintaining existing tests as the product changes, and keeping the suite healthy on an ongoing basis
• CI pipeline scaling: The suite has grown 40% in three months (470 to 680 tests) and is now regularly hitting CI resource limits, with an 8-shard stress-test job approaching a 4-hour timeout. Work collaboratively with the QA Lead and Engineering on a real scaling plan for our existing CI pipeline (Buildkite) - this can't just mean adding more runners indefinitely. You'll be closely involved in shaping this, with full ownership expected to grow over time
• Clarifying automation boundaries: Work with Engineering and FDE teams to establish a clear, documented relationship between platform-level automated tests and FDE "golden tests," removing current ambiguity about what covers what; also align with the performance testing work already underway so load/performance results sit in the same reporting picture rather than a separate silo
• Mentorship: Support QA Engineers with automation as they need it - helping them write and troubleshoot tests, sharing what you know, and building their confidence over time
• Reporting integration: Work with the QA Lead to integrate automated test results into the wider test management approach, so a test failure automatically generates a structured bug report linked back to Linear, rather than issues being created manually on an ad-hoc basis as they are today
• Cross-team collaboration: Work closely with Engineering (who currently own significant existing automation) to agree a clear, documented handover and ongoing collaboration model, avoiding duplicated effort or unclear ownership
• Building Transform/config automation from scratch: Once Platform is on a solid footing, extend automated coverage into FDE/customer-configuration testing - an area that has no automated coverage today, only manual execution by our existing testers. Unlike the Platform work above, this genuinely starts with nothing, in an area that's highly specific to each client rather than standard across the platform