IT Business Analyst interview questions and how to answer them
IT business analyst interviews test whether you can sit between a business team and a technical team without either side losing trust in you. Expect questions about requirements and testing, but also about systems, data and the messy moments when a release goes wrong. Bring real examples from projects you've worked on, and be ready to write or sketch something on the spot.
What happens in each round
- 1
Recruiter screen
What happens
Whether your background matches the systems in the posting, such as an ERP, a CRM or ServiceNow, and whether you've worked inside an IT department or a vendor's delivery team.
- 2
Hiring manager interview
What happens
How you run requirements work from intake to sign-off, how you handle scope changes, and whether you can explain a technical problem to a business audience in plain words.
- 3
Stakeholder or team panel
What happens
Developers and business users both interview you. Developers check that your stories are buildable; business users check that you'll listen and won't bury them in jargon.
- 4
Practical exercise
What happens
A short case where you write user stories with acceptance criteria, map a process, or query a small table with SQL. They're watching the questions you ask as much as the output.
Questions you're likely to get
1.Walk me through how you take a request from the business and turn it into something the IT team can build.
Why they ask
It's the core of the job, and it shows whether you have a repeatable method or just react to whoever shouts loudest.
How to answer
- Start at intake: how the request arrived, usually through ServiceNow or a demand process, and how you judged its size
- Describe the elicitation step: workshops, shadowing users, reviewing existing screens and reports
- Explain the artifacts you produced, such as a current and future process map and user stories with acceptance criteria in Jira
- Cover how you got sign-off and handed off to developers or admins in refinement
- Close with how you confirmed it worked, through UAT and a check after go-live
2.Here's a request: finance wants a new approval step for purchase orders over a certain amount. Write a user story and acceptance criteria.
Why they ask
It tests whether you can write something a developer can build and a tester can check, under a bit of pressure.
How to answer
- Ask clarifying questions first: who approves, what happens on rejection, whether delegation applies when an approver is out
- Write the story in the usual form: as a finance manager, I want, so that
- Give testable acceptance criteria in given, when, then format, including the rejection and missing-approver cases
- Flag what you'd confirm with the system owner, such as whether the ERP supports the rule through configuration
3.Tell me about a time a vendor's system couldn't do what the business asked for.
Why they ask
Most IT business analysts work on bought software, so hitting a product limit is a weekly event, not a rare one.
How to answer
- Name the system and the gap in specific terms
- Explain how you confirmed the limit with vendor documentation, support or a sandbox test rather than guessing
- Lay out the options you brought back: change the process, configure a workaround, customise, or wait for the vendor
- Say which option the business chose and what it cost them in effort or future upgrade pain
4.How do you run user acceptance testing when the business users are busy?
Why they ask
UAT is where IT projects slip, and hiring managers want someone who plans for real people's calendars.
How to answer
- Plan early and book users' time before build finishes, avoiding month-end or peak seasons
- Write test scripts tied to the acceptance criteria and use realistic test data from production-like records
- Keep sessions short and focused, and track results and defects in Jira or a test tool
- Be clear about exit criteria and who signs off
5.A release went out last weekend and now orders are routing to the wrong approvers. What do you do?
Why they ask
They want to see whether you stay calm, help diagnose, and communicate, rather than hiding behind the developers.
How to answer
- Confirm the scope: which records are affected and since when, using a report or a SQL query
- Compare the release's changes against the requirements to find the likely cause
- Work with the support team through the incident process instead of fixing things quietly
- Send a plain update to the business owner with impact, workaround and expected fix
- Afterwards, add the missed case to your test scripts so it can't slip again
6.How comfortable are you with SQL? Show me.
Why they ask
Many IT business analyst roles expect you to check data yourself during analysis, data migration and defect triage.
How to answer
- Be honest about your level, then prove it with a query using joins, filters and a group by
- Explain a real case where a query answered a question faster than waiting on a report
- Mention how you'd sanity-check results, like comparing counts to what users see on screen
7.Explain how you'd document an integration between two systems.
Why they ask
Integrations are where requirements fall through the gaps between teams, and this is specific to IT-side analysis.
How to answer
- Start with a system context diagram showing what data moves, which direction, and how often
- Build a field mapping document: source field, target field, format, transformations and defaults
- Cover error handling: what happens when a record fails and who gets told
- Reference the API documentation and confirm payload examples with the developers
8.How do you handle a stakeholder who keeps adding requirements after sign-off?
Why they ask
Scope creep is constant, and they want someone who protects the delivery without starting a war.
How to answer
- Acknowledge the request and capture it rather than refusing on the spot
- Assess its impact on the timeline and effort with the delivery team
- Route it through change control or the backlog so the product owner or sponsor decides
- Give a real example where this kept a release on track
9.What's the difference between a business requirement, a functional requirement and a non-functional requirement?
Why they ask
It's a quick check that you know the vocabulary used in IT delivery and can apply it.
How to answer
- Business requirement: the outcome the business needs, like faster invoice processing
- Functional requirement: what the system must do, like auto-match invoices to POs
- Non-functional requirement: how well it must do it, like response time, security or audit logging
- Tie each one to an example from a system you've worked on
10.How do you work with IT change management?
Why they ask
In an IT department, nothing reaches production without a change request, and analysts who ignore that cause outages.
How to answer
- Explain your part in change requests: describing the business impact and the test evidence
- Mention change advisory board reviews and freeze periods if you've dealt with them
- Describe how you plan communication and training for users around a change
11.Tell me about a time you disagreed with a developer about how to build something.
Why they ask
They want to know you can hold your ground on business needs while respecting technical judgement.
How to answer
- Set up the disagreement fairly, including the developer's reasons
- Show how you separated the need from the proposed solution
- Describe how you reached a decision, with data, a quick prototype, or escalation to the product owner
- Share what you'd do the same or differently
Mistakes that sink good candidates
Talking only about documents you produced and never about what happened to the system after go-live
Using heavy jargon with the business panel, or vague business language with the developers
Skipping clarifying questions in the practical exercise to look fast
Blaming users or developers for every project problem you describe
Need more IT Business Analyst interviews to prep for?
HeroApply applies to IT Business Analyst jobs that match you, every day. 143 jobs are open today.