At 10 a.m. Monday, a product owner asks you to 'fix the employee portal' used by 120 people before Friday; what do you do within your junior BA role?

I would clarify the business outcome, gather evidence, and draft requirements without deciding business rules or policies myself. - I would ask which observable problem matters by Friday, such as 30 failed logins a day or a 12-minute task taking too long. - I would document the current behavior, affected users, desired outcome, scope, and open questions in a short discovery note. - I would ask the product owner to confirm delivery priority, the accountable policy or process owner to decide rules and policies, and engineering to assess feasibility before I create backlog items.

Sales asks for a new order dashboard in 5 days because 18 of 200 weekly orders ship late; how do you separate the business problem from the requested solution?

I would treat late shipment as the problem and the dashboard as one proposed solution until evidence supports it. - I would define the problem with a baseline: 18 of 200 orders are late, which users are affected, and where the delay begins. - I would ask sales and fulfillment what decision a dashboard would enable and inspect whether missing data or a warehouse handoff causes the delay. - I would document the requested dashboard separately from the problem statement and take the evidence to the product owner for the solution decision.

You must draft functional requirements by Thursday for an onboarding portal that processes 300 hires a month; how would you make the account-creation behavior clear?

I would describe the exact system behavior, trigger, inputs, result, and failure response. - I would draft a statement such as: after HR approves a hire, the portal creates one account using the approved work email. - I would specify required inputs, duplicate-email handling, the success confirmation, and who receives the activation link. - I would review the draft with HR and engineering, record unresolved policy choices, and ask the accountable owner to approve them.

An order portal must support 500 users at the Monday launch in 7 days, but the request only says it should be 'fast and secure'; how do you draft nonfunctional requirements?

I would replace the adjectives with measurable targets and identify who can approve each target. - I would ask for expected concurrent users, critical pages, current response times, and an acceptable threshold such as 95% of order searches under 2 seconds. - I would capture concrete security needs such as company SSO, role-based order access, and a 15-minute idle timeout instead of writing only 'secure.' - I would mark unconfirmed numbers as open decisions and have the product owner, security contact, and engineering validate them before Friday.

A team assumes every one of 250 monthly portal applicants has a mobile phone, and requirements are due in 4 days; how do you handle that assumption?

I would record the phone assumption explicitly and test it before using it as a requirement. - I would note why it matters, for example because the proposed login sends a one-time code by SMS. - I would ask support for recent contact data or sample 20 applicant records to estimate how many lack a valid mobile number. - I would document the evidence and fallback options, then ask the product owner and security owner to decide whether SMS-only access is acceptable.

You have 2 weeks and no new software budget to add supplier access to a portal that must keep the existing SSO; how do you capture the constraints?

I would document time, budget, and technology limits separately from desired behavior. - I would record the fixed 10-business-day deadline, zero license budget, and mandatory reuse of the current SSO as named constraints with their sources. - I would ask engineering whether external suppliers can use that SSO and log the answer as evidence, not as my own architecture decision. - I would show any requirement blocked by a constraint and escalate the conflict to the product owner for a scope or deadline decision.

Orders over $500 need manager review before a Friday release, but operations has not defined whether exactly $500 qualifies; how do you document the business rule?

I would draft the rule with explicit boundaries and obtain a policy decision for the unresolved threshold. - I would write two examples, $499.99 without review and $500.01 with review, then flag exactly $500 as an open case. - I would identify the policy owner, rule source, effective date, and any exceptions such as approved supplier accounts. - I would ask operations to approve the boundary by Wednesday and link the confirmed rule to the related requirement and acceptance criteria.

Support asks you by noon to change the automatic refund limit from $30 to $45 for 600 weekly orders; what is inside and outside your authority?

I can gather the impact and draft the change, but I cannot approve a new refund policy. - I would confirm the current $30 rule, its policy owner, and how many recent refunds fall between $30.01 and $45. - I would document support's reason, affected scenarios, and system changes without telling developers to implement an unapproved limit. - I would send the evidence and decision deadline to the finance or operations owner, then update the requirement only after their recorded approval.

You have 2 days to interview 4 stakeholders for a returns portal, with only 30 minutes per person; how would you prepare and run the interviews?

I would use one focused interview guide while tailoring a few questions to each stakeholder's role. - I would review existing return forms and define the gaps I need to fill, such as triggers, decisions, exceptions, volumes, and pain points. - I would reserve 5 minutes for context, 20 minutes for open and follow-up questions, and 5 minutes to summarize what I heard. - I would capture facts, assumptions, and open decisions separately, then send each person a confirmation note within 24 hours.

Twelve warehouse clerks enter orders in an average of 8 minutes, and you must explain the delay by Wednesday; how would you use observation?

I would observe a representative sample of real orders and record the process without interrupting normal work. - I would watch at least 3 clerks process simple and exception orders, timestamping steps, waits, rework, and tool switches. - I would ask short clarification questions after each case so my presence does not change how the clerk performs the task. - I would compare observations with the written procedure and validate the draft findings with a clerk and supervisor before reporting them.

You receive a 40-page refund procedure and 18 form screenshots at 9 a.m., with a requirements summary due the next day; how do you analyze the documents?

I would extract relevant rules and flows systematically, then verify anything outdated or inconsistent. - I would scan headings and version dates first, then build a table of actors, triggers, inputs, rules, exceptions, and outputs. - I would compare the 18 screenshots with the written procedure and flag mismatched field names, limits, or approval steps. - I would cite page and screen sources in the summary and send unresolved contradictions to the process owner instead of choosing one version myself.

Five stakeholders can attend one 60-minute workshop in 3 days to define a supplier onboarding flow; how would you structure the session?

I would set one concrete outcome, timebox the discussion, and preserve decisions and open points visibly. - I would send the current draft, scope, and three key questions a day ahead so the hour is not spent reading background. - I would use 10 minutes for scope, 30 minutes to map the flow, 15 minutes for exceptions and rules, and 5 minutes to recap. - I would maintain a parking lot and decision log, assigning each unresolved policy question to its accountable owner with a date.

A portal has 200 abandoned applications a week, and you get one 20-minute interview with a service agent tomorrow; which open questions would you ask first?

I would start with questions that reveal the agent's actual experience before testing a proposed cause. - I would ask, 'Walk me through the last application that a customer could not finish,' to obtain a concrete sequence. - I would ask, 'Where do customers hesitate or contact you, and what information is missing at that point?' to locate pain points. - I would ask, 'What varies between successful and abandoned cases?' and use closed questions only afterward to confirm frequencies or boundaries.

Three stakeholders gave broad answers about a 15-minute session timeout, and you must confirm the rule by noon; how would you use closed questions?

I would use closed questions to verify specific facts after the broad discussion, not to replace discovery. - I would ask whether the 15 minutes starts after the last user action and whether viewing a page counts as inactivity. - I would ask each stakeholder to choose yes, no, or unknown for warning at 13 minutes and automatic logout at 15 minutes. - I would record disagreements and ask the security policy owner for the final decision rather than treating the majority as approval.

An order-tracking portal launches in 10 days and the request names only sales, although 6 groups touch an order; how do you build the stakeholder list?

I would map everyone who supplies information, performs work, receives an outcome, or can approve a rule. - I would trace one order from creation to delivery to identify sales, fulfillment, finance, support, IT, and the product owner. - I would record each group's interest, contribution, decision authority, contact, and required involvement in a simple table. - I would review the list with the sponsor and ask who is missing, especially downstream users affected after launch.

Sales says orders must ship within 24 hours, operations says 48 hours, and the requirement is due in 2 days; how do you handle the contradiction?

I would document both statements with their sources and bring the conflict to the accountable shipping process owner. - I would check the current policy, customer promise, and recent shipment data to see whether the teams mean different customer groups, order types, or process stages. - I would show exactly which customer groups and stages from order acceptance through dispatch each 24-hour or 48-hour option affects, without selecting the target myself. - I would arrange a short decision meeting or written approval, then circulate the chosen rule and update the requirement trace.

After a 45-minute workshop with 6 stakeholders, you must send confirmation notes within 24 hours; what would the note contain?

I would send a concise record that separates confirmed facts, decisions, actions, and unanswered questions. - I would summarize the agreed process and scope in plain language, linking the draft diagram rather than pasting a transcript. - I would list each decision with its owner, plus every action with one named person and a due date. - I would ask recipients to correct factual errors by a specific time and state that silence does not approve unresolved policy points.

80 support agents need order history in the portal next sprint, and your story draft is due tomorrow; how would you write the role-value statement?

I would name the real user, the needed capability, and the business value without embedding a technical solution. - I would draft: 'As a support agent, I want to view a customer's last 10 orders so that I can answer delivery questions during one call.' - I would verify that support agents, not managers or customers, perform this task and that 10 orders covers the common case. - I would keep database and screen-layout choices out of the story, then record them only if the team needs separate constraints or design notes.

A 10% discount applies to orders of at least $100, and acceptance criteria are due Friday; how would you cover examples and the boundary?

I would write testable criteria that show behavior below, at, and above the threshold. - I would specify $99.99 produces no discount, $100.00 produces a $10.00 discount, and $100.01 follows the agreed rounding rule. - I would include preconditions such as eligible customer type and clarify whether tax and shipping count toward the $100. - I would flag any missing rounding or eligibility policy for the commerce owner and update the criteria after approval.

A portal should lock an account after 5 failed logins within 15 minutes, and developers need criteria in 2 days; how would you express the key examples?

I would define a failed login and an inclusive rolling 15-minute window, then use exact timestamps at both boundaries. - A failed login is a rejected authentication result, and at each failure the window includes that event and earlier failures timestamped from exactly 15 minutes before it through its own timestamp. - Failures at 10:00:00, 10:03:00, 10:07:00, and 10:10:00 leave the account unlocked because the window contains four failures. - A fifth failure at 10:15:00 locks the account because the 10:00:00 event is included, while a fifth at 10:15:01 does not because that event has left the rolling window. - I would leave reset after a successful login, lock duration, and unlock behavior open for the accountable security policy owner.

Business Analyst interview questions

100 real questions with model answers and explanations for Junior Business Analyst candidates.

See a Business Analyst resume example →

Practice with flashcards

Spaced repetition · Hunter Pass

Questions

I would clarify the business outcome, gather evidence, and draft requirements without deciding business rules or policies myself.

I would ask which observable problem matters by Friday, such as 30 failed logins a day or a 12-minute task taking too long.
I would document the current behavior, affected users, desired outcome, scope, and open questions in a short discovery note.
I would ask the product owner to confirm delivery priority, the accountable policy or process owner to decide rules and policies, and engineering to assess feasibility before I create backlog items.

Why interviewers ask this: The interviewer is checking whether you understand a junior BA's evidence-gathering and documentation boundaries.

I would treat late shipment as the problem and the dashboard as one proposed solution until evidence supports it.

I would define the problem with a baseline: 18 of 200 orders are late, which users are affected, and where the delay begins.
I would ask sales and fulfillment what decision a dashboard would enable and inspect whether missing data or a warehouse handoff causes the delay.
I would document the requested dashboard separately from the problem statement and take the evidence to the product owner for the solution decision.

Why interviewers ask this: A strong answer distinguishes an observed business outcome from a stakeholder's preferred feature.

requirementsonboardingconcurrency

I would describe the exact system behavior, trigger, inputs, result, and failure response.

I would draft a statement such as: after HR approves a hire, the portal creates one account using the approved work email.
I would specify required inputs, duplicate-email handling, the success confirmation, and who receives the activation link.
I would review the draft with HR and engineering, record unresolved policy choices, and ask the accountable owner to approve them.

Why interviewers ask this: The interviewer wants to see functional requirements expressed as testable behavior rather than vague feature labels.

requirementsnonfunctional-requirements

I would replace the adjectives with measurable targets and identify who can approve each target.

I would ask for expected concurrent users, critical pages, current response times, and an acceptable threshold such as 95% of order searches under 2 seconds.
I would capture concrete security needs such as company SSO, role-based order access, and a 15-minute idle timeout instead of writing only 'secure.'
I would mark unconfirmed numbers as open decisions and have the product owner, security contact, and engineering validate them before Friday.

Why interviewers ask this: This tests whether you can turn broad quality expectations into measurable requirements without inventing targets.

requirementssoft-skills

I would record the phone assumption explicitly and test it before using it as a requirement.

I would note why it matters, for example because the proposed login sends a one-time code by SMS.
I would ask support for recent contact data or sample 20 applicant records to estimate how many lack a valid mobile number.
I would document the evidence and fallback options, then ask the product owner and security owner to decide whether SMS-only access is acceptable.

Why interviewers ask this: The interviewer is evaluating whether you expose and validate assumptions instead of silently designing around them.

I would document time, budget, and technology limits separately from desired behavior.

I would record the fixed 10-business-day deadline, zero license budget, and mandatory reuse of the current SSO as named constraints with their sources.
I would ask engineering whether external suppliers can use that SSO and log the answer as evidence, not as my own architecture decision.
I would show any requirement blocked by a constraint and escalate the conflict to the product owner for a scope or deadline decision.

Why interviewers ask this: A good answer identifies hard constraints, verifies them, and routes conflicts to the accountable owner.

business-rules

I would draft the rule with explicit boundaries and obtain a policy decision for the unresolved threshold.

I would write two examples, $499.99 without review and $500.01 with review, then flag exactly $500 as an open case.
I would identify the policy owner, rule source, effective date, and any exceptions such as approved supplier accounts.
I would ask operations to approve the boundary by Wednesday and link the confirmed rule to the related requirement and acceptance criteria.

Why interviewers ask this: The interviewer checks whether you make business rules precise while leaving policy authority with the owner.

I can gather the impact and draft the change, but I cannot approve a new refund policy.

I would confirm the current $30 rule, its policy owner, and how many recent refunds fall between $30.01 and $45.
I would document support's reason, affected scenarios, and system changes without telling developers to implement an unapproved limit.
I would send the evidence and decision deadline to the finance or operations owner, then update the requirement only after their recorded approval.

Why interviewers ask this: This assesses whether a junior analyst supports decisions with evidence rather than changing policy unilaterally.

stakeholder-managementstakeholder-interviewscommunication

I would use one focused interview guide while tailoring a few questions to each stakeholder's role.

I would review existing return forms and define the gaps I need to fill, such as triggers, decisions, exceptions, volumes, and pain points.
I would reserve 5 minutes for context, 20 minutes for open and follow-up questions, and 5 minutes to summarize what I heard.
I would capture facts, assumptions, and open decisions separately, then send each person a confirmation note within 24 hours.

Why interviewers ask this: The interviewer is looking for disciplined preparation, active listening, and prompt confirmation under a tight schedule.

process-observationwarehouse

I would observe a representative sample of real orders and record the process without interrupting normal work.

I would watch at least 3 clerks process simple and exception orders, timestamping steps, waits, rework, and tool switches.
I would ask short clarification questions after each case so my presence does not change how the clerk performs the task.
I would compare observations with the written procedure and validate the draft findings with a clerk and supervisor before reporting them.

Why interviewers ask this: A strong answer uses observation to capture actual work while controlling bias and confirming interpretations.

requirementsforms

I would extract relevant rules and flows systematically, then verify anything outdated or inconsistent.

I would scan headings and version dates first, then build a table of actors, triggers, inputs, rules, exceptions, and outputs.
I would compare the 18 screenshots with the written procedure and flag mismatched field names, limits, or approval steps.
I would cite page and screen sources in the summary and send unresolved contradictions to the process owner instead of choosing one version myself.

Why interviewers ask this: The interviewer wants evidence that document analysis is traceable and does not treat old material as automatically correct.

stakeholder-managementfacilitationonboarding

I would set one concrete outcome, timebox the discussion, and preserve decisions and open points visibly.

I would send the current draft, scope, and three key questions a day ahead so the hour is not spent reading background.
I would use 10 minutes for scope, 30 minutes to map the flow, 15 minutes for exceptions and rules, and 5 minutes to recap.
I would maintain a parking lot and decision log, assigning each unresolved policy question to its accountable owner with a date.

Why interviewers ask this: This checks whether you can support a small workshop with preparation, time control, and clear follow-up.

stakeholder-interviews

I would start with questions that reveal the agent's actual experience before testing a proposed cause.

I would ask, 'Walk me through the last application that a customer could not finish,' to obtain a concrete sequence.
I would ask, 'Where do customers hesitate or contact you, and what information is missing at that point?' to locate pain points.
I would ask, 'What varies between successful and abandoned cases?' and use closed questions only afterward to confirm frequencies or boundaries.

Why interviewers ask this: The interviewer is assessing whether your open questions elicit evidence rather than lead the participant.

stakeholder-managementcommunicationsessions

I would use closed questions to verify specific facts after the broad discussion, not to replace discovery.

I would ask whether the 15 minutes starts after the last user action and whether viewing a page counts as inactivity.
I would ask each stakeholder to choose yes, no, or unknown for warning at 13 minutes and automatic logout at 15 minutes.
I would record disagreements and ask the security policy owner for the final decision rather than treating the majority as approval.

Why interviewers ask this: A strong answer uses closed questions for precise confirmation and still handles authority correctly.

stakeholder-managementcommunication

I would map everyone who supplies information, performs work, receives an outcome, or can approve a rule.

I would trace one order from creation to delivery to identify sales, fulfillment, finance, support, IT, and the product owner.
I would record each group's interest, contribution, decision authority, contact, and required involvement in a simple table.
I would review the list with the sponsor and ask who is missing, especially downstream users affected after launch.

Why interviewers ask this: The interviewer checks whether you find stakeholders through the process rather than relying on the first name supplied.

soft-skills

I would document both statements with their sources and bring the conflict to the accountable shipping process owner.

I would check the current policy, customer promise, and recent shipment data to see whether the teams mean different customer groups, order types, or process stages.
I would show exactly which customer groups and stages from order acceptance through dispatch each 24-hour or 48-hour option affects, without selecting the target myself.
I would arrange a short decision meeting or written approval, then circulate the chosen rule and update the requirement trace.

Why interviewers ask this: This evaluates whether you investigate apparent conflicts and facilitate an owned decision instead of choosing a side.

stakeholder-managementfacilitationcommunication

I would send a concise record that separates confirmed facts, decisions, actions, and unanswered questions.

I would summarize the agreed process and scope in plain language, linking the draft diagram rather than pasting a transcript.
I would list each decision with its owner, plus every action with one named person and a due date.
I would ask recipients to correct factual errors by a specific time and state that silence does not approve unresolved policy points.

Why interviewers ask this: The interviewer is looking for usable confirmation notes that prevent ambiguity without manufacturing consent.

agile

I would name the real user, the needed capability, and the business value without embedding a technical solution.

I would draft: 'As a support agent, I want to view a customer's last 10 orders so that I can answer delivery questions during one call.'
I would verify that support agents, not managers or customers, perform this task and that 10 orders covers the common case.
I would keep database and screen-layout choices out of the story, then record them only if the team needs separate constraints or design notes.

Why interviewers ask this: A strong answer produces a specific role-capability-value story rather than a disguised implementation task.

specsacceptance-criteria

I would write testable criteria that show behavior below, at, and above the threshold.

I would specify $99.99 produces no discount, $100.00 produces a $10.00 discount, and $100.01 follows the agreed rounding rule.
I would include preconditions such as eligible customer type and clarify whether tax and shipping count toward the $100.
I would flag any missing rounding or eligibility policy for the commerce owner and update the criteria after approval.

Why interviewers ask this: The interviewer checks whether you make acceptance criteria executable with boundary examples and explicit preconditions.

I would define a failed login and an inclusive rolling 15-minute window, then use exact timestamps at both boundaries.

A failed login is a rejected authentication result, and at each failure the window includes that event and earlier failures timestamped from exactly 15 minutes before it through its own timestamp.
Failures at 10:00:00, 10:03:00, 10:07:00, and 10:10:00 leave the account unlocked because the window contains four failures.
A fifth failure at 10:15:00 locks the account because the 10:00:00 event is included, while a fifth at 10:15:01 does not because that event has left the rolling window.
I would leave reset after a successful login, lock duration, and unlock behavior open for the accountable security policy owner.

Why interviewers ask this: This tests whether you identify time and count boundaries plus unresolved security rules.

Locked questions

21
Customers may cancel an order within 30 minutes, and you have 2 days to draft a use case; what structure would you produce?
22
In a 7-step employee onboarding use case due tomorrow, 20% of hires cannot complete automatic ID verification; how do you document the alternate flow?
onboarding
23
A payment service times out after 30 seconds on about 2% of 1,000 daily orders, and the error flow is due Friday; what do you capture?
24
One story contains 8 capabilities for supplier registration but the team has a 2-week sprint; how would you split it without losing user value?
agile
25
A refund story is scheduled for refinement tomorrow but lacks 2 business rules and a screen example; how do you assess it against Definition of Ready?
business-rulesdefinition-of-ready
26
A delivery-estimate story depends on 3 teams and must be ready in 7 days; how would you make the dependencies visible?
estimationdependencies
27
You have 12 portal requirements across Jira and Confluence and must show traceability by Friday; what simple setup would you use?
requirementsrequirements-traceability
28
You must map a 9-step invoice process by tomorrow, but staff disagree on when it starts and finishes; how do you use BPMN start and end events?
process-modelingconflictconcurrency
29
A refund process has 11 boxes labeled with department names and must be corrected in 2 days; how would you model the BPMN tasks?
process-modelingconcurrency
30
An onboarding process routes 70% of hires to standard review and 30% to enhanced review, and the diagram is due Friday; how do you model the decision?
onboardingconcurrency
31
After invoice capture, tax validation takes 2 minutes and supplier validation takes 3 minutes and can run simultaneously; how would you show this by tomorrow?
validation
32
A 6-step refund spans the customer, support, and finance, and you have 1 day to clarify responsibility; how would you use pools and lanes?
33
An onboarding portal sends data to an external screening vendor twice in a 12-step process due Monday; when do you use message flow versus sequence flow?
procurementonboardingconcurrency
34
Ninety percent of 400 monthly invoices follow one route, and a readable BPMN draft is due tomorrow; how do you capture the happy path?
process-modeling
35
About 15 of 300 weekly refunds lack a receipt, and the BPMN exception path is due in 2 days; how would you add it?
process-modelingerror-handling
36
New-hire setup crosses from HR to IT 3 times and averages 6 days, with a handoff review due Friday; what would you mark in BPMN?
process-modeling
37
Invoice approval currently takes 14 days and the sponsor wants a 5-day target in 3 weeks; how do you produce simple as-is and to-be maps?
sponsor
38
Refund completion must fall from 4 days to 2 days within 1 month, and you have 2 days for a basic gap analysis; what do you compare?
gap-analysis
39
You receive 2,400 order rows in Excel with inconsistent dates, 37 blank customer IDs, and possible duplicates, and a clean file is due in 3 hours; what do you do?
excel
40
A manager needs tomorrow's review of 12,000 support tickets by week and channel; how would you build and verify an Excel pivot table?
excel
41
You must add product category to 3,500 order rows from a 120-row SKU list by 4 p.m.; how would you use a lookup safely?
42
From 50,000 orders, finance needs all paid orders created from July 1 through July 7 by noon; what basic SQL would you write and verify?
sql
43
You have 90,000 refund rows and 2 hours to show refund count and total amount per month; how would you use GROUP BY?
aggregation
44
A report due Friday needs 20,000 orders with customer segment from a 5,000-row customer table, including orders whose customer record is missing; which JOIN do you use?
joins
45
In 15,000 onboarding records, the team wants all applications not yet approved by 3 p.m.; how do you handle NULL in SQL?
soft-skillsonboardingsql
46
An 80,000-row login log must show the number of unique users active in the last 30 days by tomorrow; how would you count them?
47
Operations claims a new portal made order handling 25% faster over 2 quarters, and you have 1 day to validate the claim; what evidence do you gather?
validation
48
A dashboard due in 2 days needs the monthly application approval rate from 6,200 records; how do you define the KPI numerator and denominator?
kpi-definition
49
Three teams use different meanings for 18 portal fields, and you have 2 days to draft a data dictionary; what would each entry contain?
data-dictionary
50
At 1 p.m., Excel shows 9,850 July orders while a SQL extract shows 9,920, and finance needs one number by 3 p.m.; how do you reconcile them?
data-reconciliationsqlexcel
51
At 9 a.m. you receive 35 recent return tickets, 3 policy documents, and 2 conflicting form versions to analyze in one day before you can access stakeholders; how would you use document and content analysis?
stakeholder-managementcommunicationforms
52
The warehouse manager is unavailable until Monday, but 5 shipping stories must be ready for review by Friday afternoon; what would you do?
warehouse
53
Search over 8,000 products is described only as returning 'relevant results,' and refinement is in 3 days; how would you make the behavior testable?
54
A stakeholder asks for an easy invoice-upload screen for a 2-week sprint starting tomorrow; what would you clarify before writing acceptance criteria?
stakeholder-managementcommunicationspecs
55
Two branches mark a return Complete at different points: one when the parcel is received and one when the refund is issued; how would you establish a canonical definition for reporting?
56
You need a neutral 10-question survey for 200 service agents about their case-handling process; how would you design and run it?
designconcurrency
57
A 40-minute meeting ends with three decisions, two open questions, and one reversed assumption; what would you put in the decision log by 4 p.m.?
decision-log
58
Marketing treats an active customer as someone who bought within 30 days, Finance uses 90 days, and a dashboard story is due Friday; how would you resolve the glossary issue?
59
You join an insurance project on Wednesday and have 2 days to prepare questions for a claims specialist about a domain you do not know; how would you prepare?
joins
60
An unverified assumption says a discount is applied before tax, and build starts in 3 days; how would you handle it?
61
A saved-address feature must cover guest, member, and administrator access, but permissions and unauthorized paths are not documented; how would you write the use case?
62
A pickup-order story enters refinement tomorrow: SKU-42 has 1 unit and 2 customers can submit orders within seconds; how would you write a Given/When/Then criterion that prevents overselling?
63
A transfer form accepting amounts from $1.00 to $10,000.00 must be specified by Friday; which validation rules would you document?
formsvalidation
64
An expense app receives the same $75 receipt twice within 30 seconds and creates 2 reimbursement claims; what error rules would you add for a fix due in 7 days?
65
Security review is Friday and you need a permissions matrix for 4 roles across 6 invoice actions; how would you prepare it?
66
You have 2 days to produce low-fidelity wireframes for 3 appointment-booking screens; what would you include?
wireframesdesign-collab
67
5 users test a prototype today, 3 miss the Save action and 2 ask for a new export feature; how would you report feedback by tomorrow morning?
prototypingprototypesfeedback
68
An upload story must be ready for accessibility review in 3 days; which basic states and interactions would you add to its wireframe and criteria?
design-collaba11y
69
A story says paid orders placed before 2 p.m. in delivery zones A or B qualify for same-day delivery, and UAT starts in 3 days; what acceptance evidence would you prepare?
uat
70
Developers need a password-reset use case tomorrow with a link that expires after 15 minutes and allows three attempts; which paths would you document?
passwords
71
You must map the current claims process across 7 steps and 3 departments by Friday; how would you produce a reliable as-is map?
concurrency
72
Operations asks you to map an eight-step order-entry flow after observing 20 orders, and the draft is due Wednesday; how would you use the observations?
process-observation
73
A refund flow is scheduled for release in 6 days, but the map has no path for a partial refund to an expired card; what would you do?
74
For 12 onboarding cases, average work time is 35 minutes and average queue time is 4 hours 25 minutes; by 3 p.m. how would you report cycle and wait time?
onboardingdata-structures
75
Eighteen of 50 invoices missed a two-day target because approval was late; how would you support a five-whys review within 48 hours?
76
In 40 loan applications, the Sales-to-Risk handoff waits 19 hours out of a 26-hour average cycle; what would you present to the lead analyst by Friday?
77
The current loan process sends rejected applications back to Sales for rework up to 3 times, but the BPMN model omits the loop; how would you correct and validate it?
process-modelingvalidationconcurrency
78
Agents re-enter cancellation reasons in two systems, and 14 of 100 orders have mismatched codes; what small improvement would you propose by Thursday?
system-designresilience
79
In a sample of 60 claims, 22 required follow-up for missing documents; what evidence-backed improvement would you draft for review tomorrow?
80
A refund-email template will be piloted for two weeks across 100 cases, but the 28% baseline uses an undefined 'clarification call'; how would you make the assessment valid before the pilot?
fundamentals
81
UAT starts tomorrow and a feature has six acceptance criteria; how would you prepare 10 executable test cases by 4 p.m.?
test-casesuatacceptance-criteria
82
You need test data for 12 payment UAT cases across three roles by Thursday, but production records contain personal data; what would you prepare?
test-datauatdiscovery
83
You must recruit four business users from two branches for a 90-minute UAT session next Tuesday; how would you coordinate it?
sessionsuat
84
During UAT, 2 of 4 users ask for PDF export, but the approved criterion requires CSV export and CSV works; how would you classify and log this by end of day?
uat
85
A UAT case shows a 5% discount instead of the approved 10% on 300 daily member orders, and release is tomorrow; how would you handle severity and priority?
severity-priorityuatprioritization
86
Three of 20 UAT cases fail because tax totals differ by $0.01, but no requirement defines rounding; what would you do within four hours?
uat
87
Developers fix a login defect at noon and ask for retest evidence across two browsers and three roles by 3 p.m.; how would you retest it?
defects
88
UAT has 24 cases, 22 passed, and two known low-impact defects were accepted for later; what sign-off evidence would you assemble for the owner by noon?
defectsuat
89
A release with 3 user-visible changes and 1 known limitation goes live Friday; how would you draft release notes by end of day Thursday?
90
1 day before go-live, 6 of 8 service agents cannot find a new refund field although the feature passed UAT; how would you handle the training gap?
uat
91
A 45-minute backlog refinement tomorrow covers eight stories, and three lack examples; how would you prepare the session?
backlogsessionsbacklog-management
92
Sprint planning starts in two hours, but a story uses customer tier while CRM and billing disagree for 8% of accounts; what would you raise and recommend?
agileconflict
93
On day 7 of a 10-day sprint, Finance requests a mandatory VAT field for the checkout story already in testing; what would you do that day?
agiletesting
94
By Friday you must clean 25 Jira tickets, of which seven lack acceptance criteria and four have stale statuses; how would you improve hygiene?
specsacceptance-criteria
95
A table has 25,000 refund rows and may contain duplicate refund references and amounts within one day; how would you find and validate the candidates with SQL?
sqlvalidation
96
Excel reports an average branch refund rate of 14%, but monthly branch volumes vary 10x and leadership needs the overall rate; how would you calculate and present it?
capacityexcel
97
Support wants to reduce first response from 6 hours to 3 hours, while the current ticket reopen rate is 12%; how would you define the KPI and quality guardrail?
guardrailskpi-definition
98
A dashboard due Friday labels a tile Conversion, but teams use 3 different funnels; how would you make the label and definition usable?
funnelfunnel-analysis
99
A release has slipped three days because of two blockers, and six stakeholders need an update within 30 minutes; what would you send?
stakeholder-managementcommunication
100
In a 2-week sprint, 4 of 9 completed stories were reopened because error criteria were missing; what retrospective action would you propose before the next sprint?
agile

Questions

1At 10 a.m. Monday, a product owner asks you to 'fix the employee portal' used by 120 people before Friday; what do you do within your junior BA role?

2Sales asks for a new order dashboard in 5 days because 18 of 200 weekly orders ship late; how do you separate the business problem from the requested solution?

3You must draft functional requirements by Thursday for an onboarding portal that processes 300 hires a month; how would you make the account-creation behavior clear?

4An order portal must support 500 users at the Monday launch in 7 days, but the request only says it should be 'fast and secure'; how do you draft nonfunctional requirements?

5A team assumes every one of 250 monthly portal applicants has a mobile phone, and requirements are due in 4 days; how do you handle that assumption?

6You have 2 weeks and no new software budget to add supplier access to a portal that must keep the existing SSO; how do you capture the constraints?

7Orders over $500 need manager review before a Friday release, but operations has not defined whether exactly $500 qualifies; how do you document the business rule?

8Support asks you by noon to change the automatic refund limit from $30 to $45 for 600 weekly orders; what is inside and outside your authority?

9You have 2 days to interview 4 stakeholders for a returns portal, with only 30 minutes per person; how would you prepare and run the interviews?

10Twelve warehouse clerks enter orders in an average of 8 minutes, and you must explain the delay by Wednesday; how would you use observation?

11You receive a 40-page refund procedure and 18 form screenshots at 9 a.m., with a requirements summary due the next day; how do you analyze the documents?

12Five stakeholders can attend one 60-minute workshop in 3 days to define a supplier onboarding flow; how would you structure the session?

13A portal has 200 abandoned applications a week, and you get one 20-minute interview with a service agent tomorrow; which open questions would you ask first?

14Three stakeholders gave broad answers about a 15-minute session timeout, and you must confirm the rule by noon; how would you use closed questions?

15An order-tracking portal launches in 10 days and the request names only sales, although 6 groups touch an order; how do you build the stakeholder list?

16Sales says orders must ship within 24 hours, operations says 48 hours, and the requirement is due in 2 days; how do you handle the contradiction?

17After a 45-minute workshop with 6 stakeholders, you must send confirmation notes within 24 hours; what would the note contain?

1880 support agents need order history in the portal next sprint, and your story draft is due tomorrow; how would you write the role-value statement?

19A 10% discount applies to orders of at least $100, and acceptance criteria are due Friday; how would you cover examples and the boundary?

20A portal should lock an account after 5 failed logins within 15 minutes, and developers need criteria in 2 days; how would you express the key examples?

Locked questions