Technical Business Analyst Job Cape Town area,South Africa,Business

Your Purpose...

Is to “change people’s lives for the better through wellness”;
We deliver social wellness experiences that enable people to meet their personal wellness goals, through holistic physical, mental nutritional and social wellbeing.
To bridge Product intent and technical delivery: supporting Product with the evidence and analysis needed to shape clear outcomes and high‑level requirements, then translating those into detailed functional, process, system and data requirements so Engineering can build with clarity, and Product and Tech Leads can focus on leadership, decision‑making and stakeholder management.

Your Duties and Responsibilities...
Discovery Support

Supporting Product discovery with evidence, journey insight, data, and technical or process investigation where needed. Product remains accountable for defining the customer/business problem, opportunity and desired outcome

Requirements Definition

The heart of the role: translating high‑level Product requirements into detailed functional requirements, flows, stories, acceptance criteria, business rules, edge cases and NFRs in collaboration with Engineering.

Backlog ownership and refinement

Owning backlog detail: refining and sequencing stories with Product and Engineering Leads, and running refinement sessions with engineers, so each release enters development ready to build.

Business Process Mapping

Mapping current and future‑state process logic where it affects delivery: operational steps, hand‑offs, decisions, exceptions and change impacts. Primary working relationships are Product, Engineering, Architecture and Data, with clubs/contact centre/operations brought in for detailed process validation, and acting as the bridge between local/regional teams and the central product and engineering team so local needs are surfaced without fragmenting a shared platform.

Systems

Mapping

Tracing how changes move through systems, APIs and integrations — which system does what, where hand‑offs happen, and what each event triggers downstream — including specifying request/response contracts, sequence flows and non‑functional requirements, so implications are surfaced before build starts.

Data Mapping and Definition

Defining and tracing data requirements — fields, sources, ownership, where data is created and mastered, how it is transformed, consumed and passed into downstream processes, and the quality expectations that apply.

Impact and Gap Analysis

Identifying downstream impacts across systems, APIs/integrations, data, teams and processes. Flagging gaps, conflicts, dependencies and unowned areas to Product, Engineering and Delivery early.

Analysis for Prioritisation

Analysis to support Product decision‑making: quantifying volumes, failure points, options, trade‑offs and likely implications so Product can make informed prioritisation decisions. Product remains accountable for prioritisation.

Documentation as an Asset

Maintaining the definitive, current record of journeys, mappings, requirements, decisions and acceptance criteria so it is reusable by other squads rather than rebuilt each time

Validation

Ensuring test scenarios cover agreed requirements, business rules, exceptions and downstream impacts, and confirming that what was built matches what was defined.

Defect and Production Investigation

Investigating defects and production issues, reproducing behaviour and tracing root cause across app, API and downstream systems, so Engineering starts from an accurate diagnosis, not a guess.

Our

Minimum Requirements ...
We can’t live without…

Experience as a Business/Systems Analyst, technical BA or Product Owner in a squad-embedded, agile product team — at least 5 years overall, including 3+ years in a technical or systems analysis role.
Comfortable…