The best ChatGPT prompts for a business analyst interview make you practice the job's core skill out loud: finding the real requirement behind what a stakeholder asks for. The 13 prompts below role-play elicitation sessions, check your user stories and acceptance criteria, drill process mapping, gap analysis and data questions, and rehearse the stakeholder conflicts BA panels like to ask about. They work in ChatGPT, Gemini, Claude and Microsoft Copilot.
Let the AI play the vague stakeholder and the picky developer; keep the projects and outcomes your own. For the wider method, see how to use AI for interview prep.
Before you start: match the prompts to the exercise
Formats vary by employer and by the type of BA role (IT, product, process, finance or data-leaning), as our business analyst interview questions explain. Ask the recruiter whether there is an exercise, then practice that one first.
| Exercise | What it usually looks like | Prompts below |
|---|---|---|
| Requirements from a brief | Write user stories or requirements from a short scenario | 2 to 4 |
| Process mapping | Describe a current-state process and its problems | 5 and 6 |
| Data task | Answer questions from a small dataset in Excel or SQL | 7 |
| Stakeholder case | Talk through a conflict or a late change | 8 to 10 |
Paste the job description and short, cleaned-up notes on two or three projects. Remove client names, internal system names you were told to keep confidential and any real data with personal information in it; ask the AI to invent sample data instead.
Elicitation and requirements
1. Elicitation with a hidden need
Play an [operations manager] who asks me for 'a new dashboard' but whose real problem is something different, which you decide in advance and don't reveal. I'll run a 15-minute elicitation interview. Answer only what I ask, in character, and reveal the underlying need only if my questions get there. Afterwards, tell me what the real need was, which questions uncovered it and which I should have asked.
BA panels want to see you dig past the requested solution to the problem. Deciding the hidden need in advance keeps the drill honest.
2. User stories with acceptance criteria
Give me a short feature brief for a [domain] system. I'll write three user stories in the 'As a…, I want…, so that…' format, each with acceptance criteria in Given/When/Then form. Review them: is each story small and testable, which criteria are vague, and which non-functional requirement did I miss?
The review mirrors what a product owner or tester would push back on. Our product owner interview questions show that side of the conversation.
3. Functional or non-functional?
Give me 12 requirement statements for a [type] system, mixed and unlabeled. I'll classify each as functional or non-functional and rewrite any that are too vague to test. Then tell me which I misclassified and why.
A quick classification drill makes the distinction automatic, and the rewrite step practices making requirements testable.
4. Defend a prioritization
Here are ten requirements for a project with a fixed deadline: [paste, or invent them]. I'll prioritize them with MoSCoW and explain my reasoning against the business objective. Then play the stakeholder whose 'must have' I made a 'could have' and challenge me. Tell me whether I held my position with reasons or simply gave in.
Prioritization answers are judged on the reasoning and on who makes the final call, not on the name of the method.
Process and data
5. Map a process out loud
Describe an invoice-approval process (or [a process from my domain]) in plain prose, with three handoffs, a rework loop and one step nobody owns. I'll describe how I'd map it as a swimlane diagram: actors, steps, decisions and handoffs. Then I'll name the pain points. Tell me what I missed.
Interviews rarely give you a diagramming tool, so describing a map clearly out loud is the skill worth practicing.
6. Gap analysis in five minutes
Here is a current state and a desired future state for [a process]: [paste, or invent both]. I'll list the gaps and give options to close each one, with a rough effort level. Then ask me one follow-up about how I'd choose between the options and one about who needs to sign off.
The follow-ups test whether your analysis leads to a decision someone can make, which is the point of a gap analysis.
7. The data question
Describe two small related tables for a [domain] business, with five sample rows each, as plain text. Ask me four questions a BA might get: a simple filter, a join, a grouped total and a data-quality question such as duplicates. I'll answer in SQL or describe the Excel steps. Check my logic against your sample rows.
Many BA roles expect basic SQL or Excel. If the posting leans heavily on data, read our data analyst interview questions as well.
Stakeholders and change
8. Two stakeholders, one requirement
Play a finance lead and a sales lead who want opposite things from the same requirement in a [system]: [describe, or invent it]. Speak as each in turn. I'll facilitate toward a decision. Afterwards, tell me whether I found each person's underlying need, kept the discussion on the business objective and identified who makes the final decision.
Conflict questions are the heart of many BA interviews. Facilitating to a recorded decision beats choosing a side.
9. A change after sign-off
Play a stakeholder who asks for a new requirement two weeks after sign-off, with development already under way. Be persuasive. I'll respond. Afterwards, tell me whether I assessed the impact on scope, schedule and related requirements, used a change process and offered options rather than a flat no.
Traceability and change control sound dry until you have to explain them to an annoyed stakeholder. This rehearses the human version.
10. The developer who says it's ambiguous
Play a developer who reads this requirement of mine: [paste] and says it is too ambiguous to estimate. Ask me three pointed questions about edge cases. I'll answer and then rewrite the requirement. Tell me whether the new version is testable.
Rewriting a requirement live, after real questions, shows the clarity panels are listening for.
Your stories, a scored round and the domain
11. Your best business analysis story
Here are notes on a project where I found that what stakeholders asked for wasn't what they needed: [paste]. Shape them into a two-minute answer: the request, how I discovered the real need, what I recommended, what changed for the business and how I confirmed it worked. Don't add outcomes I haven't given you; ask me instead.
This is the story most BA interviews are really asking for, whatever the wording of the question.
12. Score with a BA rubric
Rate my answer to '[question]' on five criteria, 1 to 5 each: elicitation, clarity of requirements, stakeholder handling, validation and business outcome. Back each rating with my own words and give me the follow-up question an interviewer would most likely ask next. Answer: [paste].
Answering the predicted follow-up straight away is the fastest way to strengthen a story.
13. Learn the domain's language
I'm interviewing for a business analyst role in [insurance / banking / healthcare / retail]. Give me 15 terms the business will use, each with a one-line definition and an example of how it would appear in a requirement. Quiz me on them afterwards, and mark any definition that could differ between companies as 'check'.
Domain vocabulary often separates a strong BA answer from a generic one. The 'check' flags stop you repeating a definition that doesn't fit their business.
What to double-check
Three things go wrong most often when BA candidates prepare with a chatbot.
- The stakeholder is too cooperative. Simulated stakeholders answer clearly and give in quickly. Real ones contradict themselves. Ask the AI to be vaguer and more stubborn, or practice with a colleague.
- Outcomes get invented. When you ask for a polished story, models add "reduced processing time by 30%". Remove any result you can't support.
- Technique details drift. If you cite a technique, notation or certification, check the details at the source rather than repeating the chatbot's summary.
Keep real data out of every prompt, and say your answers out loud before the interview. An AI mock interview that reads questions aloud and scores your spoken answer shows whether your requirements story is clear without slides.
Where CoPilot Interview fits
CoPilot Interview is an AI interview helper for rehearsing the spoken part of a BA interview. Its mock interview builds questions from your résumé and the job description, reads them aloud and scores each spoken answer out of 10. The free plan gives 15 minutes a day of live help in sessions of up to 15 minutes, with AI mock interviews included. Paid plans are Standard at $24.99 a month and Pro at $39.99 a month.
It runs as a desktop app for Windows 10 and 11 and macOS 12 or later, a free iPhone and iPad companion on the App Store (iOS 16 or later) and an Android companion in beta. In live interviews, the desktop app shows captions of the interviewer's question and a structured answer in about two seconds; if you use it, follow your employer's rules. Written exercises, take-homes and assessments that ban outside help are your own work.
Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly.
Frequently asked questions
What ChatGPT prompts help with a business analyst interview?
Prompts that make you do BA work: an elicitation role-play with a hidden need, user stories with acceptance criteria for review, a process to map out loud, a small data task and stakeholder conflicts to facilitate.
Can ChatGPT role-play a stakeholder for requirements practice?
Yes. Ask it to decide the stakeholder's real need in advance and reveal it only if your questions get there. Simulated stakeholders tend to be too cooperative, so ask for a vaguer, more stubborn character.
Do business analyst interviews include SQL?
Some do, especially data-leaning BA roles. Others focus on requirements and process. Read the job description, ask the recruiter about any exercise and practice basic joins, filters and grouped totals if data is mentioned.
How do I answer a question about conflicting stakeholders?
Show that you find each person's underlying need, bring the discussion back to the business objective and get a decision from the person who owns it, then record that decision. Avoid quietly picking a side.
Rehearse it out loud before the real one
The AI mock interview builds questions from your resume and the job description, reads them aloud and scores each spoken answer out of 10. Included on the free plan.
Start a mock interview