Goodfit

How to hire a Business Analyst

Business analysts connect business teams and technical teams. They gather requirements, design processes and analyze data. They make messy problems easy for stakeholders to understand. In IT services and product companies, the BA often works with more teams than anyone else.

Screen BA applicants
BA

Free · Email code to start · Uses your mic · Up to 3 minutes

On this page

What does BA stand for?

BA stands for Business Analyst.

A Business Analyst (BA) works out what a business really needs. Then they turn it into something a technical or operations team can build. Stakeholders often describe a solution when they should describe the problem, so the BA interviews them to find the real need. The BA maps how a process really works, which is often different from what the manual says. They write requirements clear enough to build and test. And they stay involved during delivery to answer the questions the spec did not foresee.

Also called
Systems Analyst, Functional Analyst, Business Systems Analyst
Function
Business analysis, between business and technology
Level
Entry to senior individual contributor
Reports to
BA Lead, Program Manager, or a business or IT function head
Next step
Senior BA, Product Owner, Product Manager, Consultant, or Program Manager

The hiring challenge

Good business analysts are hard to find because the job needs two skills that rarely come together. The first is careful analysis: can they break a complex process into clear steps? The second is talking to stakeholders: can they explain their analysis to a VP who will not read a 40-page document? Most candidates are strong in one and weak in the other.

What to look for in a Business Analyst

Three traits matter. Structured thinking: do they break a messy problem into clear parts before diving in? Clear requirements: can they write requirements that engineers can build from? A vague wish list is no use. Adjusting how they explain: can they present the same analysis to a developer and to a VP? Do they change the depth and words for each?

For IT services companies, check three more things. Are they comfortable with clients? Many BA roles face clients. Do they write usable documents, such as process flows, user stories and acceptance criteria? And do they know your industry? BFSI, healthcare and retail each have their own BA needs.

How to structure the interview

A strong BA interview has three parts. First, a requirements exercise. Give the candidate a vague business need, like "we want to improve customer onboarding." Ask what questions they would ask to turn it into clear requirements. Score the quality of the questions. The number of questions matters less. Second, an analysis walkthrough. Ask them about a project where they studied data or a process and made a recommendation. Listen for how they structured the work and whether they can explain why it mattered. Third, a stakeholder conflict scenario. Describe two stakeholders who disagree on requirements. Ask how they would settle it.

Common mistakes when hiring Business Analysts

Hiring for fast documents over good analysis. Some BAs write documents quickly but do not understand the business problem underneath. They create more confusion.

Not testing how they manage stakeholders. BAs work in the gap between business and technology. If they cannot juggle different stakeholders who want different things, they slow everything down. Their job is to connect the two sides.

Assuming SQL skills. Many BA job posts list SQL as required. But many strong BAs have never written a query. Decide up front whether your BA must pull their own data or will work with a data team.

Key skills for a Business Analyst

  • Structured thinking
  • Requirements elicitation
  • Process documentation
  • SQL basics
  • Stakeholder communication
  • Data storytelling
  • User story writing
  • Cross-functional coordination

What a great interview looks like

Scenario

"Two stakeholders disagree on the requirements for the same feature. How would you settle it?"

Voice

"Walk me through a project you analyzed. What data did you use, what did you find and what did you recommend?"

Voice

"Tell me about a time you got vague requirements. How did you turn them into something the team could act on?"

Scenario

"A product manager asks you to write requirements for a feature you think is not needed. What do you do?"

Voice

"How do you decide how much detail to put in a requirements document?"

You can use these questions in Goodfit as they are, or edit the questions and the scoring for your team.

Recommended interview process

  1. 1

    Round 1: AI Voice Interview15 to 20 min

    A requirements exercise, an analysis walkthrough and a check on how clearly they explain things.

  2. 2

    Round 2: Case Study30 min

    A live requirements exercise from a vague brief. It is graded on the quality of their questions and their structure.

  3. 3

    Round 3: Hiring Manager Interview30 min

    Talk about your industry, stakeholder scenarios and team fit.

In Goodfit, the AI interview runs the first round for every applicant. Skill tests, coding tests and roleplays can run in Goodfit too. Your team reads the scorecards and joins for the later conversations.

FAQ

BA hiring questions

What does a business analyst do?
They connect what the business needs with what the technical team builds. They run stakeholder interviews and workshops. They document the current process and design the new one. They write requirements or user stories with acceptance criteria. They draw process maps and data flows. They check the impact when something changes and support user acceptance testing. And they handle the talks that always come up when two stakeholders want things that cannot both happen.
What is the difference between a business analyst and a data analyst?
A business analyst works with people and processes to decide what should be built or changed. A data analyst works with data to answer questions about what happened. They overlap on reports. A BA may spell out what a report must show, and the data analyst builds it. The core skills are quite different. The BA gathers requirements and designs processes. The data analyst uses SQL and statistics.
What is the difference between a business analyst and a product owner?
A product owner sits inside a delivery team. They own and prioritize the backlog and can decide what gets built next. A business analyst is usually a specialist who gathers and documents requirements. They often work across several teams or projects and do not set priorities. In many companies one person does both. So in an interview, ask if the role can make decisions or only writes the documents.
What skills does a business analyst need?
They need to find the real need when stakeholders show up with a solution. They need process mapping, and the discipline to record what really happens instead of the official version. They need to write clear, testable requirements, which is rarer than it sounds. They need to manage stakeholders who want different things. They need enough technical knowledge to know what is expensive to build. They need data skills, usually including SQL. And they need the confidence to say a requirement contradicts itself before it gets built.
What documents does a business analyst produce?
A common one is a business requirements document. In agile teams, user stories with acceptance criteria take its place. BAs also make process maps of how things work now and how they should work. They draw data flow and system diagrams. They build a traceability matrix that links each requirement to its tests. They write gap analyses and impact reviews for proposed changes. The real value is that everyone ends up with the same understanding. Documents nobody reads are the most common way the role fails.
What qualifications do you need to become a business analyst?
A graduate degree in business, commerce, engineering or computing is typical. The field is also open to career changers from operations, support and industry roles, because knowing the subject is truly useful. Larger companies recognize certifications in business analysis or agile. Most employers care more about proven requirements work and industry knowledge than the certificate.
What interview questions should I ask a business analyst?
Play a stakeholder who asks for a specific solution. Score whether the candidate finds the real problem behind it. Give a requirement that is vague on purpose and ask what questions they would raise. Ask them to walk through a process they mapped and what surprised everyone. That is usually where the role adds the most value. Ask how they handled two stakeholders who wanted things that could not both happen. And ask what they do when a requirement changes late in delivery.
How do you screen business analyst candidates?
BA applicant pools are large. Resumes look alike because the documents BAs make are standard. The skill that sets candidates apart is drawing out requirements, and you can test it directly. Run a short roleplay where the candidate has to question a vague request. Score every candidate on the same rubric. It shows who just writes down what they are told and who finds out what is really needed.

Also hiring?

Data

Data Analyst

How to hire

Operations

Operations Manager

How to hire

Product and design

Product Manager

How to hire

Looking for Business Analyst jobs instead? Browse open roles on Goodfit Jobs

Try Goodfit with your own team

Goodfit talks with applicants and employees by phone or in a browser. Try it on one of your open roles.

Book a demoStart free
  • 20 free assessments, no card needed
  • Then $5 per assessment
  • No seats or annual contract
Book a demo