[Core] What does a business analyst actually do on a project?

Example Answer

I usually explain the role this way: a business analyst helps the team make the right change for the right reason. The job is not just taking notes in meetings or writing tickets after someone else already decided everything. It is understanding the business problem, clarifying what success looks like, surfacing constraints, and translating that into something the team can actually build, test, and roll out.

On a real project, that means I spend time with stakeholders, map current processes, identify pain points, document business rules, clarify decisions, and make sure the requirements are specific enough that engineering and QA are not forced to guess. I also stay involved through testing and rollout, because a requirement is not really done if users get to UAT and say, "That is not what we meant."

The way I think about it is that a good BA reduces ambiguity. If the business is asking for one thing, the delivery team is hearing something else, and leadership assumes everyone is aligned, my job is to close that gap before it turns into rework, delay, or mistrust.

Common Poor Answer to Avoid

"A business analyst mainly gathers requirements and writes documentation for the project team."

Why it's weak

• It reduces the role to note-taking and paperwork instead of judgment, clarification, and delivery support.

Why this works

• It explains the role in a way hiring managers recognize from real projects, not from generic job descriptions.