Business Analyst (Technical) - Agentics in Ipswich

WTW is building one of the most far-reaching investments in digital products in the risk and broking industry. At the heart of that investment is a Product team looking to grow by hiring four Product Analysts into one of the core product domains that together define how WTW’s digital business operates and grows. Product Analysts sit where product intent turns into working software. You will work hand in hand with your Product Owner and engineering team to shape and document requirements, turning PRDs into actionable, measurable deliverables – epics, user stories and acceptance criteria that engineers can build from with confidence. You will carry features through build, coordinate user acceptance testing, and stay close to the business and the users our products serve, so that what we ship reflects how the work actually happens.

The Product Domains:

• Client: How clients interact with and experience WTW’s digital products, services, and embedded AI.
• Colleague: How WTW colleagues use digital tools to work smarter, serve clients better, and operate more effectively.
• Market Connectivity: Integrations and connections to external markets, carriers, capabilities, and marketplaces.
• Payments: How money moves between clients, WTW and carriers – premium and claims payments that are accurate, timely and increasingly automated.

Requirements Shaping and Documentation:

• Work with your Product Owner and engineering team to shape ideas into clear, well-bounded requirements – running workshops, interviewing users and mapping processes to get to the real need.
• Turn PRDs and discovery outputs into actionable, measurable deliverables: epics, user stories, acceptance criteria, and the process and data flows engineers can build from without guesswork.
• Define how success will be measured for each deliverable – the acceptance criteria, the data to capture, and the evidence that will show a feature is used and creating value.
• Keep requirements current through build – capturing what was agreed, managing change, and making sure the documentation reflects what is actually being delivered.

Delivery and Backlog Support:

• Maintain a well-groomed backlog with your Product Owner – stories refined, estimated and ready ahead of the squad’s planning.
• Be the squad’s first stop for requirements questions during build, resolving ambiguity quickly so engineers keep their momentum.
• Support the squad’s ceremonies – refinement, sprint planning and reviews – with the user and business context that makes them productive.
• Track delivery against the intent of the PRD and flag early when scope, dependencies or timelines start to drift.

UAT and Release Readiness:

• Plan and coordinate user acceptance testing: define scenarios and scripts with the business, brief and support testers, and manage cycles through to sign-off.
• Triage defects and feedback with the Product Owner and engineering team, separating what must be fixed now from what can follow.
• Support release readiness – walkthroughs, training material and the operational checks that make a go-live land well.
• Feed what UAT reveals back into the backlog so every release improves the next.

Business and User Engagement:

• Build trusted working relationships with the business teams and users your squad serves – brokers, claims handlers and operations colleagues across regions.
• Spend time in the field: watch how the work actually happens, gather feedback on what we have shipped, and bring that insight back into requirements.
• Translate between the two worlds – business language into product requirements, and product direction back into terms the business recognises.
• Understand and translate business data requirements into actionable and consistent schemas – so the data our products capture means the same thing everywhere.
• Support adoption after release with walkthroughs and follow-up, so a deployment becomes embedded use.

Measurement and Continuous Improvement:

• Define and track the measures behind each deliverable with Product Operations – adoption, usage and the business outcome the feature was built for.
• Report progress with candour: what the data shows, what users say, and what should change as a result.
• Contribute to the Product Analyst cohort – shared templates, standards and practices that raise the quality of analysis across every squad.

Qualifications Skills and Experience Essential:

• Solid experience as a business analyst or product analyst on software delivery teams, with a record of taking requirements from ambiguity through to delivered, adopted features.
• Strong requirements craft: eliciting needs through workshops and interviews, writing clear user stories and acceptance criteria, and mapping processes and data flows.
• Hands-on experience planning and running UAT – scenario design, test coordination, defect triage and sign-off.
• Experience working directly with engineers in agile delivery, and the judgement to know when a conversation beats a document.
• A clear communicator and facilitator, as credible with a broker or claims handler as with a developer.
• Data literacy – comfortable defining measures, interrogating data to test assumptions, and using evidence to make the case for a change.
• Organised and self-directed, able to run several threads at once and keep them all moving.