Prova

Interview questions

Business analyst interview questions

A business analyst sits between people who know the problem and people who build the solution. Interviewers test whether you can get clear requirements out of vague requests and keep both sides aligned when scope moves.

Rehearse this interview by voice2 minutes without an account, 3 more after sign-up. No card.

Questions by stage and what a strong answer includes

  1. 01

    What kind of projects have you worked on as a BA?

    Strong answer: Domain (finance, retail, healthcare), type (system implementation, process change, new product) and your deliverables: BRDs, user stories, process maps, UAT plans.

  2. 02

    Which methods and tools do you use?

    Strong answer: Agile or waterfall context, Jira and Confluence, BPMN or Visio for process maps, SQL or Excel for data checks. Mention certification such as CBAP or IIBA only if you have it.

  1. 03

    Tell me about a time stakeholders gave you conflicting requirements.

    Strong answer: How you surfaced the conflict, mapped each requirement to a business goal, and got the right owner to decide. Document the decision so it does not reopen.

  2. 04

    Describe a requirement you missed and what it cost.

    Strong answer: The gap, when it surfaced (testing, go-live), the impact and the change you made to your elicitation process afterwards.

  1. 05

    How do you run a requirements workshop?

    Strong answer: Clear objective, the right people in the room, a current-state walkthrough, structured techniques (process mapping, story mapping), and a summary sent the same day for confirmation.

  2. 06

    Write a user story with acceptance criteria for a password reset feature.

    Strong answer: As a / I want / so that, plus testable criteria in Given-When-Then, including edge cases: expired links, unknown email, rate limiting.

  3. 07

    How do you tell a real requirement from a solution someone has already decided on?

    Strong answer: Ask why until you reach the business need, then check whether the proposed solution is the best way to meet it. Five whys or a problem statement exercise works.

  4. 08

    Map the current process for approving supplier invoices. Where would you look for waste?

    Strong answer: Swimlanes by role, hand-offs, wait times and rework loops. Point to manual re-keying, duplicate approvals and unclear exception handling as typical waste.

  1. 09

    Case: a client wants a new CRM in six months. What are your first three weeks?

    Strong answer: Stakeholder map, current-state discovery, pain points ranked by impact, high-level requirements and a scope proposal with assumptions. Raise data migration early.

  2. 10

    How do you know a project you worked on delivered value?

    Strong answer: Benefits defined upfront with a baseline, measured after go-live: hours saved, error rate, cycle time. If nobody measured, say so and what you would do differently.

  1. 11

    Are you interested in moving toward product or project management?

    Strong answer: An honest direction. Either way, show you see the BA role as valuable in itself, not as a waiting room.

One answer, before and after

Tell me about a time stakeholders gave you conflicting requirements.

Weak answer

This happens on every project. I usually set up meetings with everyone and we discuss until we agree on what is best for the business. Communication is very important.

Strong answer in STAR

Situation
On a claims system upgrade at an insurer, the claims team wanted a mandatory 12-field intake form to reduce follow-up calls, while the call center wanted fewer fields to keep calls short.
Task
I had to give the development team a single requirement within two sprints, without letting either group feel overruled.
Action
I pulled three months of claims data and found that only four fields caused 80% of follow-ups. I proposed four mandatory fields at intake and the remaining eight as optional, with a reminder sent to the customer by email. I presented it to both team leads together and took the final decision to the product owner, documenting it in Confluence.
Result
Average call length grew by 40 seconds instead of the three minutes the full form would have added, and follow-up calls on new claims dropped by about a third in the first two months.

Why it works

The weak answer describes meetings, not analysis. The strong one uses data to find a compromise, involves the decision owner and records the outcome. The numbers in this example are illustrative: use your own.

How a practice session works

  1. 01

    Pick a stage, paste the job posting

    Recruiter screen, HR interview, hiring manager, final round or offer talk. Add the posting and your resume so the questions are about your role, not generic.

  2. 02

    Talk it through by voice

    The interviewer speaks the language you chose, interrupts, follows up and digs into details like on a real call. If the connection drops, you pick up where you stopped.

  3. 03

    Get the review and drills

    A score, 7 skills, what you said next to a stronger way to say it, plus pace, filler words and talk share. Weak spots turn into short drills.

Rehearse this interview by voice

Related roles