Business Test Analyst in Haywards Heath

The purpose of the Business Test Analyst role is to validate the functional behaviour, accuracy and business correctness of data solutions delivered by the Insurance Data Squad. The role focuses on testing how data solutions actually behave end to end — from ingestion and transformation through to outputs such as journals, extracts and reports — ensuring they meet agreed functional and business expectations. This role does include functional testing, but it is not a traditional QA or QA engineering role. It does not own test automation frameworks, and does not sit outside delivery. Instead, the Business Test Analyst works embedded within the squad, partnering with Product, Analysis and Engineering to surface issues early and support confident, informed release decisions.

Key Responsibilities

• Functional & data testing
  • Test functional behaviour of data solutions, validating that data flows, transformations and outputs behave as expected against requirements and business rules.
  • Execute structured test scenarios covering data ingestion, transformation logic, edge cases and downstream impacts.
  • Validate data accuracy, completeness and consistency, including reconciliations between source systems, transformed data and outputs.
  • Identify defects, data issues and unexpected behaviour, clearly documenting findings and supporting resolution with engineers and analysts.
  • Retest fixes and changes to confirm expected behaviour has been achieved.
• Collaboration & early engagement
  • Work closely with Product Owners, Analysts and Engineers to understand intent, data logic and expected outcomes.
  • Participate actively in Three Amigos sessions, backlog refinement and sprint planning, helping define test scenarios before build starts.
  • Challenge unclear or incomplete requirements early, reducing rework and late-stage surprises.
  • Act as a business and data focused lens within the squad, ensuring delivered solutions align with real business usage.
• UAT & confidence building
  • Manage and coordinate end-to-end User Acceptance Testing (UAT) for data and reporting outputs, including defining UAT scope, managing timeframes and helping business users understand what to test and why.
  • Review UAT results and outcomes, consolidating feedback, triaging and tracking defects through to resolution and confirming readiness from a functional data perspective.
  • Provide Product Owners with clear insight into functional behaviour, known limitations and residual risks ahead of release.
• Documentation & transparency
  • Maintain clear documentation of functional test scenarios, data checks and outcomes.
  • Ensure functional and data issues are visible, understood and tracked through to resolution.
  • Contribute to improving shared understanding of what “good” looks like for data functionality and behaviour within the squad.

Knowledge, skills and experience required

• Experience performing functional testing within data, reporting or analytics environments.
• Strong ability to understand and test business rules, data logic and functional outcomes.
• Experience validating end to end behaviour, not just isolated components.
• Comfortable working with large datasets and identifying functional discrepancies.
• Working knowledge of SQL or similar tools to interrogate and validate data behaviour.
• Experience working in Agile delivery teams, embedded alongside product and engineering.
• Strong communication skills, able to explain functional issues and risks clearly to both technical and non-technical stakeholders.
• Experience working with data lakes, data warehouses or reporting platforms.
• Exposure to financial or insurance data, including understanding of downstream impacts and sensitivity.
• Experience supporting UAT or business sign off for data or reporting solutions.
• Knowledge and experience of using PowerBI.

Behaviours & ways of working

• Detail focused and analytical, with a strong interest in how systems actually behave.
• Comfortable asking “does this do what the business expects?” rather than just “does it technically work?”.
• Collaborative and pragmatic, focused on enabling delivery rather than blocking it.
• Confident challenging assumptions constructively and early.
• Calm and methodical when investigating functional issues or unexpected outcomes.