← All roles
Interview practice

Business Analyst

2–5 years · Mid — Requirements · SQL · Stakeholder management · Documentation · Excel · Process mapping

0–2 years 2–5 years 5–8 years 8+ years
scenario Documentation 1 of 6
You receive feedback that your documentation is not user-friendly. What steps do you take to improve it based on the feedback?
What a strong answer covers

Gathers specific examples of unclear sections from users; revises the layout for better readability; simplifies technical jargon into plain language; includes visual aids like flowcharts or diagrams; conducts a feedback session with users after revisions.

The follow-up you would get

How do you ensure ongoing clarity and usability of documentation in future projects?

Could you have answered that?
scenario Documentation 2 of 6
Tell me about a time you had to document complex processes. How did you ensure clarity and usability?
What a strong answer covers

Used clear language and visuals, iterated drafts with stakeholders, tested documentation with end-users, incorporated feedback, ensured easy access to documentation.

The follow-up you would get

How did you handle situations where users found the documentation unclear?

Could you have answered that?
scenario SQL 3 of 6
You discover that a critical report is generating incorrect results due to a flawed SQL query. What are your first steps to rectify this issue?
What a strong answer covers

Reviews the query logic against the expected output; checks for joins and aggregations that might cause discrepancies; runs the query with sample data to isolate the issue; consults with the data team to confirm data integrity; documents findings and prepares a fix plan.

The follow-up you would get

After fixing the query, how do you ensure that similar issues do not arise in the future?

Could you have answered that?
scenario Stakeholder Management 4 of 6
During a project, a key stakeholder changes their requirements last minute, impacting the timeline. How do you react in the first few minutes?
What a strong answer covers

Acknowledges the change and its potential impact on the project; assesses the feasibility of implementing the change within the current timeline; communicates with the project team to gauge the implications; prioritises requirements based on business value; schedules a meeting to discuss with the stakeholders.

The follow-up you would get

If the new requirements conflict with previously agreed-upon features, how do you handle that situation?

Could you have answered that?
technical Process Mapping 5 of 6
You are tasked with mapping a complex customer onboarding process that has numerous exceptions. What techniques do you use to capture all variations accurately?
What a strong answer covers

Utilises swimlane diagrams to delineate roles; identifies key decision points and exceptions; conducts workshops with involved teams to gather insights; iterates the map based on stakeholder feedback.

The follow-up you would get

If new exceptions arise after mapping, how do you integrate those into your existing process map?

Could you have answered that?
ownership Stakeholder Management 6 of 6
Share an experience where you owned a project from inception to delivery. What would you do differently if you had the chance?
What a strong answer covers

Engaged stakeholders from the start, tracked progress through regular updates, addressed feedback promptly, documented lessons learned, would improve communication channels.

The follow-up you would get

What specific feedback did you receive from stakeholders after the project was completed?

Could you have answered that?
That is this set.

Load six more — you will get questions you have not seen first.

Give me six more →

Say your answer out loud before revealing. Reading the answer first feels like learning and is not.