[Hiring] Business Analysis @Career Bridge

Role Description

This is a remote position.

Simulation-Based Work Experience Programme — Founding Cohort

Business Analysts are frequently given messy problems rather than neatly documented requirements. Participants may enter a scenario where stakeholders disagree about the problem, existing processes are poorly understood, requirements conflict, operational pain points have not been investigated or somebody has already selected a solution without establishing the underlying need. The participant's job is to create clarity from ambiguity.

Workplace Responsibilities & Jobs to Be Done

• Problem investigation: Investigate the underlying business problem rather than automatically accepting the proposed solution.
• Stakeholder identification: Determine which individuals, teams or user groups are affected and assess their influence, needs and potential contribution to requirements.
• Requirements elicitation: Analyse stakeholder information, prepare elicitation approaches and identify questions required to uncover genuine business, user and operational needs.
• Requirements analysis: Evaluate collected requirements for clarity, completeness, consistency, feasibility, duplication and alignment with business objectives.
• Requirements challenge: Identify when stakeholders have presented solutions as requirements and reframe those requests around the underlying need.
• Current-state analysis: Investigate how an existing process, service or system operates and identify inefficiencies, bottlenecks, failure points and unnecessary complexity.
• Future-state analysis: Develop recommendations describing how a process or service could operate differently to achieve the intended outcome.
• Gap analysis: Compare current and desired states and identify capabilities, process changes, technology, data or organisational changes required to close the gap.
• Process analysis: Analyse workflows across multiple stakeholders or systems and identify opportunities for simplification, automation or improved control.
• User-story development: Translate requirements into structured user stories communicating user need and expected value.
• Acceptance-criteria development: Define clear, testable conditions establishing when a requirement or user story has been satisfactorily delivered.
• Requirements prioritisation: Determine which requirements are essential, valuable or deferrable when delivery capacity or budget is constrained.
• Conflict resolution: Analyse conflicts when stakeholders have incompatible requirements and recommend an appropriate resolution.
• Impact assessment: Evaluate how a proposed change could affect people, processes, systems, data, policies and operational responsibilities.
• Solution assessment: Compare potential solution approaches against agreed business needs and provide an evidence-based recommendation.
• UAT and readiness support: Determine how a proposed solution should be validated and whether the organisation is sufficiently prepared for implementation.

Requirements

• Business Requirements Document: Define the business problem, objectives, stakeholder needs, requirements, constraints and expected outcomes.
• Requirements Catalogue: Create an organised set of functional, non-functional, business and user requirements with appropriate prioritisation, categorisation and traceability.
• User Stories and Acceptance Criteria: Develop structured user stories accompanied by clear, testable acceptance criteria demonstrating how each requirement can be validated.
• Current-State Process Analysis: Document how an existing process operates and identify pain points, bottlenecks, inefficiencies, control weaknesses and operational risks.
• Future-State Process Design: Propose a future workflow demonstrating how identified problems could be addressed and desired outcomes achieved.
• Gap Analysis: Compare current and desired states and identify required changes across processes, technology, people, data or organisational capability.
• Stakeholder Analysis: Assess key stakeholders, their needs, influence, interests and likely concerns and recommend an engagement approach.
• Options Assessment: Compare potential solution approaches against defined criteria, analyse benefits, risks and constraints and provide a reasoned recommendation.
• Change Impact Assessment: Evaluate how a proposed solution or change will affect organisational areas and identify preparation, communication or mitigation required.
• UAT Scenario or Acceptance Plan: Produce a structured approach for validating that delivered functionality satisfies agreed requirements and user needs.

Capabilities You Can Demonstrate

• Requirements Engineering
• Stakeholder Analysis
• Process Analysis
• Problem Solving
• Requirements Elicitation
• User Stories
• Acceptance Criteria
• Facilitation
• Business Change
• Critical Thinking
• Communication
• Solution Assessment

Who Should Apply?

• Aspiring Business Analysts
• Junior Business Analysts
• Career changers
• Product or Project professionals developing BA skills
• Graduates
• Career returners
• Trained Business Analysts seeking stronger applied evidence