IT Business Analyst
Interview Questions.
15 practice questions across 11 skills — each with what the interviewer is really listening for. Prepare with intent, not guesswork.
Free · No signup · Grouped by skill
How to use this page
Don't memorise answers. For each question, read what the interviewer is looking for, then practise answering out loud in your own words with a real example. The notes describe strong answers and common red flags — they are for your prep, not a script.
Requirements Gathering
2 questionsA stakeholder asks for a feature but cannot say what problem it solves. How do you handle it?
IntermediateWhat the interviewer is looking for: Strong answers dig into the underlying business problem and outcome rather than just documenting the requested solution. Taking requests at face value is a red flag.
How do you elicit requirements when business and IT stakeholders disagree?
AdvancedWhat the interviewer is looking for: Look for surfacing conflicts, facilitating alignment, and driving to a documented, agreed scope. Documenting contradictions or letting the loudest voice win are red flags.
PRD
1 questionHow do you write requirements or a PRD that developers can build from without ambiguity?
IntermediateWhat the interviewer is looking for: Strong candidates frame the problem and outcome, give clear acceptance criteria, and leave implementation to the team. Vague requirements or dictating the how are red flags.
SQL
1 questionHow do you use SQL to validate a hypothesis about the business or a process?
IntermediateWhat the interviewer is looking for: Look for querying to check assumptions and quantify a problem, validating totals against a source. Not being able to write basic queries is a limitation for an IT BA.
Process Mapping
1 questionHow do you map a current process and identify where a system can help?
IntermediateWhat the interviewer is looking for: Strong answers document the as-is with stakeholders, find pain points and handoffs, and design an improved to-be. Redesigning without understanding the current process is a red flag.
Agile
1 questionHow do you turn a business need into user stories with clear acceptance criteria?
BasicWhat the interviewer is looking for: Look for well-formed, independently deliverable stories with testable criteria. Giant vague stories with no criteria are a red flag.
Business Acumen
1 questionHow do you prioritise a backlog when everything is 'high priority'?
AdvancedWhat the interviewer is looking for: Strong candidates use frameworks like MoSCoW or RICE tied to value and effort, and can justify trade-offs. Prioritising by who shouts loudest is a red flag.
Stakeholder Management
2 questionsHow do you keep business and technical stakeholders aligned through a project?
IntermediateWhat the interviewer is looking for: Look for translating between the two, managing expectations, and a single source of truth. Letting the two sides drift apart is a red flag.
How do you handle a stakeholder who keeps expanding scope mid-project?
IntermediateWhat the interviewer is looking for: Look for a change process, making trade-offs explicit, and renegotiating priorities. Silently absorbing scope or flatly refusing are red flags.
Data Analysis
1 questionHow do you validate that a delivered solution actually solved the business problem?
IntermediateWhat the interviewer is looking for: Strong answers define success metrics up front and measure against them post-delivery. Treating go-live as the finish line is a red flag.
Wireframing
1 questionHow do you use wireframes or UML to communicate a solution before it is built?
BasicWhat the interviewer is looking for: Strong candidates use lightweight visuals to align stakeholders and catch gaps early. Only using dense text specs when a picture would clarify is a limitation.
Technical Documentation
1 questionHow do you document requirements so they stay useful as the project evolves?
BasicWhat the interviewer is looking for: Look for a maintained single source of truth, versioning, and tying docs to decisions. Stale documents nobody trusts are a red flag.
Jira
1 questionHow do you use Jira and Confluence to keep requirements and delivery transparent?
BasicWhat the interviewer is looking for: Look for well-structured stories, traceability, and a living single source of truth the team actually uses. Requirements scattered across emails and chats are a red flag.
Behavioural & role-general
2 questionsTell me about a project where your analysis changed the solution or decision.
BasicWhat the interviewer is looking for: Strong answers show a concrete insight, influence on the outcome, and a measurable result. Vague involvement with no impact is a red flag.
How do you bridge the gap between what the business wants and what is technically feasible?
IntermediateWhat the interviewer is looking for: Look for translating both ways, finding pragmatic solutions, and managing expectations honestly. Overpromising to the business or dismissing their needs are red flags.