Business Analyst - Entry Level

Role Overview

This is a junior business analyst role embedded in a banking technology programme, sitting squarely between the people who use the systems and the people who build them. Day to day you will run discovery conversations with business users, write up what you hear into requirements that others can act on, and help a change travel from an idea into something developers can build and testers can verify. The work matters because banking change programmes succeed or fail on the clarity of their requirements — a well-written user story, or a gap caught during analysis, prevents weeks of expensive rework later in the delivery cycle.

The portfolio you would support is broad: core banking upgrades and enhancements, mobile and internet banking, payments and transaction processing, system integrations and APIs, data migration and validation, reporting and business intelligence, process automation, customer onboarding journeys, lending systems, reconciliation, and regulatory or compliance-driven technology initiatives. Expect a mix of long-running platform work and shorter enhancements with faster turnaround.

Key Responsibilities

• Lead and capture discovery sessions — interviews, workshops, and requirement-gathering meetings — with business users and stakeholders, then convert those conversations into written requirements that both business and technical readers can follow.
• Produce and maintain the core analysis artefacts: business requirements documents, functional requirements documents, user stories with acceptance criteria, use cases, and process flow diagrams.
• Map current-state processes, identify gaps, inefficiencies, and missed opportunities, and propose practical improvements rather than simply restating the problem.
• Act as the bridge between business and technical language, working with developers and architects to confirm that what has been specified is what actually gets built.
• Brief QA and test teams early so that test scenarios and cases reflect the real intent of a requirement rather than just its obvious path, and stay involved through user acceptance testing to help business users validate the delivered solution.
• Keep requirements traceable end to end, so that when something changes, the knock-on effect on design, testing, and connected systems is visible, assessed, and properly recorded.
• Support defect clarification and resolution by giving technical teams the business and functional context they need to interpret an issue correctly, and carry out straightforward data analysis to back up recommendations and project decisions.
• Handle the project discipline that keeps a team aligned — minutes, action trackers, status updates, and document control — and support implementation, deployment, and post-implementation activities, including impact analysis when changes are proposed to systems already in use.

Requirements & Qualifications

• Bachelor's degree in Business Information Technology, Information Systems, Computer Science, Business Administration, Finance, Economics, or a comparable discipline.
• 0–2 years of experience in business analysis, IT, software development, testing, project support, or a similar technology environment. New graduates are considered where relevant academic projects, internships, or other hands-on technology exposure can be demonstrated.
• A working grasp of the software development life cycle and where analysis sits within it.
• Practical understanding of how requirements are elicited and how business processes are analysed, ideally evidenced by coursework, an internship, or a project you have helped deliver.
• Confident use of Excel, Word, and PowerPoint for analysis, documentation, and stakeholder updates.
• Advantageous to have: the ability to sketch process flows and workflow diagrams; familiarity with BRDs, FRDs, user stories, use cases, and acceptance criteria; basic SQL and database knowledge; a working idea of APIs, system integrations, and data flows; exposure to tools such as Jira, Confluence, Visio, or Draw.io; awareness of Agile/Scrum ways of working; and any familiarity with banking or financial services systems.
• Competencies that matter here: analytical rigour and problem-solving, close attention to detail, clear written and verbal communication, the confidence to listen carefully and ask the right clarifying questions, and the discipline to keep documentation accurate under time pressure.
• Able to move comfortably between business and technical audiences, manage your own time across parallel workstreams, contribute as part of a collaborative team, and stay composed in a fast-paced project environment.