Job Title: Business Analyst

Department: Product

Reporting to: Director of Product

Location: Hybrid / HQ / Remote

Role Purpose and Key Responsibilities:

Role Purpose:

We are looking for a Business Analyst to sit at the critical point between product intent and development execution. How well a product project goes is largely decided before development starts. Clear requirements mean accurate estimates, fewer mid-sprint surprises, and teams that can move fast with confidence.

The right person will be:

• Meticulous with requirements. Developers should be able to estimate and build from what you write without needing to chase clarification

• Comfortable working directly with developers, asking the right questions, and resolving ambiguity without needing a PM in the room every time

• Proactive in spotting gaps before they become blockers. You read the product well enough to know when something doesn't add up

• Fast-paced and organised. Multiple workstreams running simultaneously, without dropping the detail

• Trusted by both PMs and developers as the person who keeps requirements sharp

Key Responsibilities:

Requirements and specifications

• Translate product decisions into clear, detailed specifications that give development everything they need to estimate accurately and build without ambiguity

• The quality of your requirements directly determines how predictably a project lands

• Avoid scope creep by analysing and investigating all potential edge cases, gap analysis and full scope playback with stakeholders and developers before development starts

Backlog refinement

• Keep the backlog sharp and sprint-ready

• Work with developers to surface and resolve gaps before they become blockers mid-sprint

Discovery support

• Work alongside PMs on research, data pulls, and stakeholder interviews to build the evidence base for product decisions

• Contribute to the thinking, not just the write-up

Delivery coordination

• Track where features are, what's blocked, and what needs a conversation

• Keep things moving so the team isn't chasing answers mid-sprint

Key Outputs (What Success Looks Like)

• Development squads can estimate and plan with confidence because requirements going into sprints are complete and unambiguous

• Projects landing closer to plan: fewer mid-sprint surprises, less rework

• A working knowledge of the sportsbook product, the key stakeholders, and how the team operates

• Trusted by both PMs and developers as the person who keeps the detail right

Specialist Skills and Experience Required:

• Experience as a BA or in a similar requirements and analysis role in a digital product environment - you write specifications that developers can actually build from

• Domain knowledge required. You need to understand the product and competitors well enough to spot a gap in a requirement before it hits a sprint

• Comfortable working directly with developers, asking the right questions, and resolving ambiguity independently

• Able to work at pace and manage multiple workstreams simultaneously without dropping the detail

• Experience supporting more than one product team at the same time would be an advantage

• Familiarity with agile delivery: sprint ceremonies, backlog management, story refinement would be an advantage

• Experience in a remote or distributed team would be an advantage