Business Analyst Associate
JOB RESPONSIBILITIES
• Elicit requirements through stakeholder interviews, process observation, workshops and document analysis — drawing out what the business actually needs rather than recording the first solution it asks for
• Analyse and translate those requirements into functional specifications, identifying dependencies and impacts before work begins
• Design the target process rather than automating the current one, challenging steps that exist only by convention and removing them before they are built into software
• Write clear, testable acceptance criteria that can be verified automatically, agreed before development begins
• Build applications using AI development tools, within the central data model and approved patterns
• Prepare and maintain functional specifications, process flows and data mapping documents
• Coordinate with business users, the data architect and the software engineer through delivery
• Prepare and support UAT, test scenarios, defect analysis and issue resolution
• Support go-live and post-implementation, including documentation and monitoring
• Report progress, risks and blockers early, with a proposed course of action
REQUIRED QUALIFICATIONS
• 0-3 years in any role requiring documented precision subject to review
• Clear written communication — the ability to document a requirement another person can act on without seeking clarification
• Ability to break a business problem into ordered, testable steps — the same thinking a developer uses, applied to process rather than code
• Willingness to question how something is currently done rather than accept it as the specification
• The habit of checking your own work against a defined standard before submitting it
• Willingness to declare uncertainty promptly rather than proceed without confirmation
• Demonstrated change in working practice following feedback; this carries the greatest weight in assessment
• Familiarity with e-commerce operations, marketplace platforms, finance processes or ERP systems
• Ability to read code or a SQL query and judge whether it does what the requirement asked, without needing to write it unaided
• Exposure to requirements elicitation techniques such as stakeholder interviews, workshops or process observation
• Prior use of AI development tools on work that others depended upon
• Exposure to agile delivery, user stories or backlog refinement