How to hire a Business Analyst

Why this role is hard to hire

The hiring challenge

Good business analysts are structurally hard to find because the role requires two skill sets that rarely come together: analytical rigour (can they break down a complex process into clear steps?) AND stakeholder communication (can they explain their analysis to a VP who does not want to read a 40-page document?). Most candidates are strong on one and weak on the other.

What to look for in a Business Analyst

Three traits matter: Structured thinking (do they break a messy problem into clear components before diving in?). Requirements clarity (can they write requirements that engineering can actually build from, not vague wish lists?). Communication adaptability (can they present the same analysis to a developer and a VP, adjusting depth and language for each?).

For Indian IT services companies, also check for client-facing comfort (many BA roles are client-facing), documentation discipline (can they create process flows, user stories, and acceptance criteria that are actually usable?), and domain awareness (BFSI, healthcare, and retail all have domain-specific BA requirements).

How to structure the interview

A strong BA interview has three parts. First, a requirements elicitation exercise: give the candidate a vague business need ("we want to improve customer onboarding") and ask them what questions they would ask to turn it into a clear set of requirements. Score on question quality, not quantity. Second, a analysis walkthrough: ask them to describe a project where they analyzed data or a process and made a recommendation. Listen for how they structured the analysis and whether they can explain the "so what." Third, a stakeholder conflict scenario: present a situation where two stakeholders disagree on requirements and ask how they would resolve it.

Common mistakes when hiring Business Analysts

Hiring for documentation speed instead of analysis quality. A BA who produces documents quickly but does not understand the underlying business problem will create more confusion, not less.

Not testing for stakeholder management. BAs live in the gap between business and technology. If they cannot manage competing priorities from different stakeholders, they become a bottleneck instead of a bridge.

Assuming SQL skills. Many BA job descriptions list SQL as required, but many strong BAs have never written a query. Decide upfront whether you need a BA who can pull their own data or one who works with a data team.

What to test

Key skills for a Business Analyst

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

Sample questions

What a great interview looks like

Every question is from the GoodFit library. Customize the rubric for your context in the platform.

Suggested format

Recommended interview process