If you have applied for a BA role, prepared thoroughly, and then heard nothing, you are probably asking the wrong question. Most candidates ask: did I meet the criteria? The better question is: did I give the hiring manager what they actually needed to make a decision in my favour? Those are two very different things. Understanding how companies hire business analysts means recognising that the formal process and the real decision-making process are running in parallel, and they do not always line up.
Job advertisements are written by HR teams, often with rushed input from a hiring manager who is already stretched. What ends up published is frequently a blend of generic competency language, a wish list of tools, and a few vague sentences about the team. Almost none of it tells you what problem they are actually trying to solve by hiring someone. That problem is where you need to focus your energy.
The Three Layers Every Hiring Process Involves
In most organisations, particularly in government, utilities, and large enterprise environments, the hiring process for a BA role involves at least three distinct layers of influence. Each one is filtering for something different, and getting through all three requires a different kind of preparation.
- HR or talent acquisition: This layer manages the process and screens applications against stated criteria. The person reviewing your CV may not fully understand what a BA does. Getting past this stage is about your CV being legible to someone looking for keywords and threshold evidence, not nuance.
- The hiring manager: This is typically a delivery manager, programme manager, or senior BA. They have a specific problem. A project or programme needs analytical support, and they have probably been trying to fill this gap for weeks. They are not evaluating your certification status or your Confluence experience. They are asking one question: can this person walk into my environment and make progress quickly, with minimal hand-holding?
- The panel: Many organisations introduce a panel at interview stage, which adds perspectives from a business stakeholder, a technical lead, or an HR representative. Each of them is filtering for something slightly different, and a strong candidate needs to speak to all of them without sounding rehearsed or generic.
What Hiring Managers Are Actually Looking For
After 25 years sitting on both sides of this process, in government departments, water utilities, health systems, and enterprise transformation programmes, the pattern is consistent. Hiring managers are not primarily looking for a list of tools or a certification. They are looking for three things.
Evidence That You Understand the Problem, Not Just the Process
The candidates who stand out are those who can demonstrate that they understand what business analysis actually does in context. That means showing how your work connected to a business outcome, not just a project deliverable. There is a meaningful difference between saying “I wrote requirements” and saying “I worked with a team that was processing applications manually, identified that the bottleneck was in how information was captured at intake, and redesigned the process so that downstream teams had what they needed on first contact.” The second version shows problem framing, stakeholder engagement, and a focus on outcome. That is what a hiring manager needs to hear.
Confidence With Ambiguity
Most BA roles start with incomplete information. When a hiring manager describes a role in vague terms, it is often because the work genuinely is not defined yet. What they are testing, sometimes without realising it, is whether you are the sort of person who can walk into an unclear situation and start making sense of it without needing everything spelled out. Think about times when you joined a project mid-stream, or when the brief was poorly defined, and prepare to talk specifically about what you did in those first days and weeks to orient yourself and add value. If you want to build that confidence further before your interview, the guidance in Business Analyst Confidence: Interviews and Stakeholder Talks is worth reading alongside this.
Whether They Can Imagine Working With You
This is the factor that is least discussed and most decisive. Hiring managers are thinking about what it will actually be like to have you in the room with difficult stakeholders, in a planning session that goes sideways, or on a Friday afternoon when everything is urgent. Confidence, clarity, and the ability to communicate in plain language are evaluated constantly throughout the interview, whether or not there are formal questions designed to test them.
A Concrete Example: What the Panel Actually Discussed
On a digital transformation project for a utility organisation, Organisation A, the team was hiring a mid-level BA to support the build of a customer-facing self-service portal. Development industry customers were lodging applications through a legacy system, and the core challenge was that customers had no visibility of their application status once it was submitted. Three candidates made the shortlist. All three had relevant experience on paper.
The hiring decision came down to two factors that were never on the job description. The first was domain curiosity. One candidate had done no research on the organisation and answered every question in abstract terms. A second candidate had clearly looked at how similar organisations had approached the problem and referenced a comparable portal initiative, noting what had worked and what had created problems downstream. That candidate was not showing off. They were demonstrating that they think before they engage, which is exactly what a BA working across multiple internal teams and external customers needs to do.
The second factor was how each candidate described handling stakeholder resistance. The winning candidate gave a specific example of a situation where a business owner had been resistant to changing a paper-based process. Here is where the friction came: the hiring panel had initially assumed this would be a straightforward story about change management. Instead, the candidate described how they had pushed back on their own early assumption that the resistance was about attachment to paper. When they actually sat down with the business owner and listened properly, the concern turned out to be about audit trails. That reframing changed the solution design entirely. The panel remembered that answer long after the interview ended. The others they did not.
How to Position Yourself Before and During the Process
The comparison below shows the difference between how most candidates approach each stage of the process and what the hiring manager is actually hoping to see.
| Stage | What Most Candidates Do | What the Hiring Manager Wants to See |
|---|---|---|
| Reading the job description | Check whether they meet the listed criteria | Understand the underlying problem the role is designed to solve |
| Writing the CV | List responsibilities and tools used | Specific outcomes tied to real project contexts |
| Preparing for interview | Memorise answers to competency questions | Examples that reveal judgment, not just process compliance |
| Handling panel questions | Tailor answers to whoever is asking | Consistent clarity that speaks to all perspectives at once |
| Discussing stakeholder challenges | Describe a conflict and how it was resolved | Show that you listened deeply enough to reframe the problem |
Read the Job Description for What It Reveals, Not What It Says
Look past the list of tools and competencies. Ask what the role is actually for. Is this an organisation building something new, or stabilising something that has gone wrong? Is the BA role embedded in a delivery team or sitting at the interface between business and IT? The answers shape how you frame your experience, and getting this right before you write a single word of your application is worth the time.
Make Your CV Do Specific Work
Generic statements about requirements elicitation and stakeholder management are not memorable. Specific statements about the type of problem you worked on, the stakeholders you engaged, and what changed as a result are. If you are not sure how to write impact-focused CV content, the Business Analyst CV Impact Statements: A Practical Guide gives you a framework to work from immediately.
Prepare for the Question Behind the Question
Interview panels often ask scenario or competency questions that are really testing something more specific than the surface question implies. “Tell me about a time you managed a difficult stakeholder” is really asking whether you have good judgment about when to push, when to listen, and when to escalate. Prepare your examples with that second-order intent in mind, and check out the guidance on BA Interview Questions: How to Answer with Confidence and Clarity for additional structure.
Surface What Is Specific to Their Context
If the role is in a regulated environment, such as health, utilities, government, or financial services, then experience with compliance constraints, audit requirements, or multi-stakeholder governance is worth naming explicitly. These environments have specific BA challenges that generalist candidates often underestimate, and demonstrating awareness of those challenges signals that you will not need to be educated on the basics once you arrive.
The Referral and Network Reality
It would be dishonest to write about how companies hire business analysts without acknowledging that a significant proportion of BA roles, particularly contract roles but increasingly permanent ones too, are filled through networks before they are ever advertised. This is not about unfairness. It is about how hiring managers reduce risk. They would rather bring in someone who comes recommended by a trusted colleague than take a chance on a strong CV from an unknown candidate.
This makes professional visibility more important than many early and mid-career BAs realise. If you are actively looking, it is worth investing time in making your thinking visible, whether through LinkedIn posts, community participation, or simply having good conversations with former colleagues. The guidance on Business Analyst Networking covers this in more depth and gives you a practical starting point.
Treat every application as a problem-framing exercise, not a form-filling exercise. The organisation has a gap. Your job is to show them that you understand what that gap is, that you have relevant experience with similar problems, and that you are the kind of person they can rely on to do the work without being managed through every step of it. That is ultimately how companies hire business analysts: not by finding the person who most precisely matches the job description, but by finding the person who makes them feel most confident that the problem will actually be handled well.
Frequently asked questions
How do companies hire business analysts?
Most organisations use a combination of HR screening, hiring manager interviews, and panel assessment. The formal criteria filter the longlist, but the final decision is usually driven by whether the hiring manager believes a candidate can handle ambiguity, engage stakeholders effectively, and add value quickly. The formal and real decision-making processes run in parallel and do not always align.
What do hiring managers look for in a business analyst?
They look for evidence of problem-solving in context, not just a list of tools or techniques. They want to see that you can frame a problem, work through stakeholder complexity, and connect your work to a business outcome. Confidence in unclear situations and clear communication are consistently the most decisive factors.
Why do business analysts not hear back after applying?
Applications often fail at the initial HR screening stage because the CV does not clearly demonstrate relevant experience in terms the screener can recognise. Generic language about requirements and stakeholders is easy to overlook. Specific, outcome-focused examples tied to real project contexts are far more likely to get shortlisted.
Do you need a certification to get a business analyst job?
Certification helps at the screening stage and signals commitment to the profession, but it rarely determines the hiring decision. Hiring managers are more interested in what you have actually done and how you think than in whether you hold a CBAP or equivalent. Strong examples from real project experience carry more weight.
How important is networking for getting a business analyst role?
Very important, particularly for contract work but increasingly for permanent roles too. A significant number of BA positions are filled through referrals before being advertised. Building relationships with former colleagues and making your professional thinking visible can directly influence whether you are considered for roles that never reach the job boards.
Try Ash, Your Virtual BA
If you are preparing for a BA job application or interview right now, Ash can help you sharpen the thinking that hiring managers are actually looking for. Use Ash to explore BA concepts, stress-test your understanding of key methods, and work through the kind of problem framing that separates memorable candidates from forgettable ones. The more fluent you are in BA practice, the more naturally that comes through in every answer you give. Try Ash Virtual BA and start building that fluency today.
Further reading
- Business Analysis Blog | 3 Reasons Why Companies are Hiring Business Analysts | IIBA
- How Organizations Attract and Retain the Best Business Analysts | IIBA® Business Analysis Blog
Written by Sam Cordes, founder of the Business Analyst’s Toolkit.