Operations & Finance

Business Analyst Job Description

A Business Analyst (BA) uncovers, documents, and communicates business requirements so that solutions — whether technology implementations, process improvements, or organisational changes — genuinely address the underlying need rather than a symptom. Great BAs are intellectually rigorous questioners who can translate ambiguous stakeholder wishes into precise, testable requirements. They sit at the intersection of business and delivery, ensuring that what gets built is what was actually needed.

Key skills

Requirements elicitation and documentation (user stories, use cases, BRDs)Process mapping and gap analysis (BPMN, swimlane diagrams)Data analysis and SQL queryingStakeholder facilitation and workshop designAcceptance criteria definition and UAT supportBusiness case developmentWireframing and UX prototyping for requirements communicationAgile and waterfall delivery methodology

Responsibilities

  • Elicit, analyse, and document business requirements through stakeholder interviews and workshops
  • Produce clear and testable user stories, process maps, and functional specifications
  • Conduct gap analysis between current state and desired future state
  • Support the prioritisation of requirements against business value and feasibility
  • Collaborate with developers, testers, and project managers throughout the delivery lifecycle
  • Define acceptance criteria and support user acceptance testing
  • Develop business cases with cost-benefit analysis for proposed initiatives
  • Maintain a traceability matrix linking requirements to delivered solutions

Requirements

  • 3+ years of business analysis experience on technology or process improvement projects
  • Demonstrable ability to produce high-quality requirements documentation independently
  • Proficiency in process modelling and ability to facilitate cross-functional workshops
  • Working knowledge of Agile delivery — able to write clear user stories and contribute to sprint planning
  • Analytical skills including data analysis using Excel, SQL, or a BI tool
  • Strong written communication — requirements must be unambiguous and testable

Nice to have

  • BCS, IIBA CBAP, or equivalent business analysis certification
  • Experience with the specific domain (e.g. financial services, healthcare, e-commerce)
  • Familiarity with product discovery techniques and UX research methods
  • Experience running structured JAD or requirements workshops with mixed technical and business stakeholders
  • Familiarity with process-mining or workflow-automation tools that surface where a process actually breaks

What to look for in a great Business Analyst

The hallmark of a great BA is the quality of their questions, not just their documentation. In an interview, watch how they probe for underlying need rather than accepting a stated requirement at face value — do they ask 'why?' enough? Ask to see a sample of their requirements documentation: it should be precise, unambiguous, and testable. Strong BAs are also comfortable in conflict — when a stakeholder's requested feature contradicts another's need, they surface and resolve it rather than silently documenting both and letting development discover the inconsistency.

Where to source Business Analyst candidates

Consulting graduates who have spent time in business transformation or technology consulting are a strong pipeline — they arrive with structured thinking and stakeholder management experience from complex environments. Operations roles that have grown an analytical component (operations analyst, process improvement specialist) are another fertile source. Data analysts who want to move closer to business change are increasingly common career changers with relevant analytical rigour. BCS, IIBA, and Agile community events surface practitioners who invest in their craft.

Interview questions to ask a Business Analyst

Present a vague requirement ('The business wants a dashboard') and ask them to walk through how they would scope and clarify it — this is the most revealing exercise you can run. Follow with 'Tell me about a project where the requirements changed significantly mid-delivery and how you managed it.' Ask 'How do you handle a stakeholder who cannot agree on what they want?' to probe facilitation and conflict resolution skills. Finish with a technical angle: 'Walk me through a piece of analysis you did recently — what did you look at, what did you find, and what decision did it inform?'

Red flags when hiring a Business Analyst

Watch for candidates who jump straight to a solution before they have understood the problem — a strong analyst stays in the problem space long enough to map the current process and quantify the pain. Be wary of anyone who cannot show a real artefact: a BRD, a BPMN diagram, a set of user stories with acceptance criteria, or a gap analysis they actually produced. Vague answers about stakeholder conflict are another warning sign, because reconciling contradictory requirements is the daily reality of the job. Finally, distrust an analyst who has never touched data directly; if they cannot query a table or interrogate a spreadsheet, they will take every requirement at face value rather than validating it against what the numbers say.

How an ATS speeds up hiring a Business Analyst

Business analyst pipelines fill quickly with adjacent titles — data analyst, project coordinator, systems analyst — so the screening burden is real. With Pitch N Hire you can post the role to multiple boards at once and use structured screening questions to confirm the fundamentals early: requirements documentation, process mapping, and SQL exposure. Scorecards let each interviewer rate the same competencies — elicitation, stakeholder facilitation, and business-case reasoning — so you compare candidates on evidence rather than gut feel. Because a good BA interview usually includes a written or whiteboard exercise, keeping notes, ratings, and artefacts attached to the candidate record in one place stops feedback getting lost between rounds and shortens the time from first screen to offer.

Hiring a Business Analyst? See Pitch N Hire on your roles.

FAQ

Hiring a Business Analyst — FAQs

What does a Business Analyst do? +
A Business Analyst identifies and documents what a business needs from a change initiative — whether a technology project, a process redesign, or an organisational change. They elicit requirements through interviews and workshops, produce clear documentation, support solution design, define acceptance criteria, and help ensure delivered solutions match the original business need. They work across the full project lifecycle, from discovery to UAT.
What skills does a Business Analyst need? +
Requirements documentation, process mapping, facilitation, data analysis, and clear written communication are core technical skills. Equally important are critical thinking — the ability to challenge assumptions and identify unstated needs — and interpersonal skills for navigating competing stakeholder priorities. Working knowledge of Agile methodologies and proficiency with at least one modelling or diagramming tool are standard in most contexts.
How much does a Business Analyst earn? +
BA salaries vary by sector, project complexity, seniority, and geography. BAs in regulated industries such as financial services or healthcare typically earn more than those in less regulated sectors. Holding a recognised certification (BCS Practitioner, CBAP) and demonstrable experience on large-scale transformation programmes can increase earning potential. Contractor day rates differ substantially from permanent salaries. Current local market benchmarks are the best reference.
What should a Business Analyst job description include? +
State the domain and the delivery methodology up front, because a BA in a regulated financial-services shop works very differently from one in an agile product team. List the concrete deliverables — BRDs, user stories, process maps, gap analyses — and the tools involved, such as SQL, BPMN or Jira. Name the stakeholders they will facilitate and whether the role leans towards requirements, data analysis, or both. Adding a short brief on the current initiative helps candidates self-select, which raises the quality of your applicant pool.
How many candidates should I interview for a Business Analyst? +
For a mid-level role, a shortlist of four to six candidates through to interview is usually enough for a confident decision. Because the craft is hard to judge from a CV alone, include a practical exercise — a short requirements-gathering scenario or a process-mapping task — for two or three finalists rather than relying on conversation. If you interview well past six without a clear front-runner, the cause is usually an underspecified brief or a screen not filtering on the domain and methodology you need.
Built for recruiters & hiring teams

Ready to hire a Business Analyst?

Post this role to multiple job boards and screen, interview and decide — all in one AI-native platform.

Prefer to talk? Book a demo · View pricing

Free 1-user plan · No credit card · Talk to a real hiring expert

One Hiring Infrastructure.
Zero Tool Chaos.

Demos are consultative. We respect privacy and enterprise
governance. No lock-ins.

Start free Book demo