Hiring the right Business Analyst can be difficult because job titles do not always tell you what someone has actually done.
Two candidates might both have “Business Analyst” on their CVs while having very different experience. One may have spent most of their career documenting requirements. Another may have worked across complex transformation programmes, challenged existing processes and helped shape the solution.
For employers, assessing Business Analysis experience therefore requires more than matching keywords on a CV. The focus should be on what the candidate has delivered, the problems they have solved and how they have worked with stakeholders.
Look Beyond the Job Title
Business Analyst roles can vary significantly between organisations.
Some positions focus heavily on requirements gathering and process mapping. Others involve strategy, technology implementation, business change, data, product development or large-scale transformation.
The job title alone cannot tell you which type of experience a candidate has.
When reviewing applications, look for evidence of the candidate’s responsibilities and outcomes. A strong CV should give you an indication of the environments they have worked in, the complexity of the projects they supported and the stakeholders they worked with.
This is particularly important when hiring for transformation roles, where experience in a similar environment can be more valuable than simply having held the same job title.
Assess the Complexity of Their Experience
Not all Business Analysis experience carries the same level of responsibility.
A candidate who has worked on a small internal system change may have useful skills, but their experience may not transfer directly to a major technology transformation.
Consider the scale and complexity of previous projects. What systems or processes were involved? How many teams were affected? Did the candidate work across multiple business functions? Were there competing requirements or difficult stakeholders?
These questions help establish whether someone’s previous experience matches the demands of the vacancy.
Look at What They Actually Delivered
A strong Business Analyst should be able to explain the contribution they made to a project.
Rather than simply saying they “gathered requirements”, candidates should be able to explain what they discovered, how they analysed the problem and what happened as a result.
For example, did their analysis lead to a redesigned process? Did they help define requirements for a new system? Did they identify a problem that changed the direction of a project?
The distinction matters because employers are ultimately hiring people to solve business problems, not simply to complete a list of activities.
Assess Stakeholder Management
Business Analysts often sit between business and technology teams. Their ability to communicate with different stakeholders can therefore be just as important as their technical knowledge.
Candidates may need to gather requirements from senior stakeholders, challenge assumptions, resolve conflicting priorities and explain technical concepts to non-technical colleagues.
During an interview, ask candidates about situations where stakeholders disagreed or where requirements were unclear. Their answers can reveal how they approach difficult conversations and whether they can move a project forward when there is no obvious solution.
Skills England’s 2026 research identifies problem-solving, decision-making, communication, collaboration and adaptability as important capabilities across digital and technology roles.
Test Their Problem-Solving Approach
Business Analysis is not simply about documenting what people tell you.
Good analysts investigate why a problem exists, challenge assumptions and consider different ways of addressing it.
Interview questions should therefore give candidates an opportunity to demonstrate their approach to a problem.
You might ask them to describe a situation where the original requirements were incomplete, contradictory or technically difficult to deliver. Their response can show how they investigate problems, work with stakeholders and reach a practical outcome.
This can be more revealing than asking whether they consider themselves a “good problem solver”.
Understand Their Technical Knowledge
The level of technical knowledge required from a Business Analyst varies considerably.
A role supporting a software implementation may require an understanding of systems, integrations and data. A Business Analyst working on a digital transformation may need to understand how technology affects wider business processes.
That does not mean every Business Analyst needs to be technically specialised.
Instead, employers should define the level of technical understanding the role actually requires before assessing candidates. This prevents businesses from rejecting strong analysts simply because they cannot demonstrate skills that the job does not genuinely need.
Assess Their Requirements Experience
Requirements analysis remains a core part of many Business Analyst roles, but employers should look at how candidates approach requirements rather than simply whether they have experience gathering them.
Strong candidates should be able to explain how they identify requirements, validate them with stakeholders and manage changes throughout a project.
It’s also useful to ask how they deal with requirements that conflict with business objectives, technical constraints or project timelines.
These situations provide a clearer picture of a candidate’s judgement than a list of requirements-management tools on a CV.
Look for Adaptability
Digital transformation projects rarely remain exactly as they were at the beginning.
New information can change requirements. Technology can introduce new possibilities. Business priorities can shift.
A Business Analyst therefore needs to adapt while maintaining a clear understanding of the project’s objectives.
This is becoming increasingly relevant as AI changes technology and business processes. UK Government research published in 2026 shows that employers need different levels of AI capability across their workforces, from people who use existing AI tools to those who implement or develop AI systems.
For employers, the question is not necessarily whether a Business Analyst has used every new AI tool. It is whether they can understand new technology and assess how it could affect the business.
Use the Interview to Validate the CV
A CV should start the assessment, not finish it.
If a candidate claims experience with a major transformation programme, ask them to explain their role in it. What problem was the organisation trying to solve? What did they personally do? Which stakeholders did they work with? What changed because of their analysis?
Strong candidates should be able to explain their experience clearly and consistently.
This approach can also help distinguish between candidates who genuinely owned significant responsibilities and those who worked within a large programme without having direct responsibility for the areas described on their CV.
Define the Right Requirements Before You Recruit
One of the biggest recruitment challenges comes from creating a Business Analyst specification that tries to cover everything.
Requiring experience across multiple industries, methodologies, technologies and transformation environments can dramatically reduce the available candidate pool.
Instead, employers should identify the capabilities that are genuinely essential for the role. From there, they can separate requirements that a candidate must already have from skills that could be developed after joining.
This creates a more realistic candidate profile and makes the recruitment process easier to assess consistently.
What Makes a Strong Business Analysis Hire?
The strongest Business Analyst is not necessarily the candidate with the longest list of qualifications or tools on their CV.
Relevant experience, analytical thinking, stakeholder management, communication and the ability to understand business problems all matter.
For employers, the key is to assess what candidates have actually done, rather than relying on job titles or keyword matches.
A clear understanding of the role, combined with evidence-based interviewing, can make it much easier to identify Business Analysts who have the experience needed to contribute to a transformation programme.
Ultimately, good Business Analysis recruitment starts with a clear question: what problem does this person need to solve, and what evidence shows they can solve it?
