Business Analyst
Technical BA
hard
You need to gather requirements for a new API integration. What do you ask?
Asked at
RazorpayStripePayUCashfree
Framework
purpose → payload → auth → reliability → volume → errors
Model answer
Six categories: purpose (what triggers the call), payload (request and response shape), auth (keys, OAuth, mTLS), reliability (retries, idempotency, timeouts), volume (RPS, burst), and error handling (error codes, fallback behaviour, alerting).
What great candidates actually do
- Idempotency keys are the #1 thing junior BAs forget.
- Ask for sample cURL commands — vendors love giving them.
- Document rate limits AND what the caller should do when hit.
Traps to avoid
- Naming the solution before the problem — always restate the goal in one sentence first.
- Answering without structure — pick a framework out loud, then execute it.
- Skipping the trade-off — every strong answer names what you would NOT do and why.
Related questions
Requirements
Walk me through the last BRD you wrote — how did you structure it?
Read answer →Requirements
What's the difference between a BRD, FRD and SRS — and when would you use each?
Read answer →Stakeholder
How would you elicit requirements from a senior stakeholder who won't give you time?
Read answer →
Practice with a human
Rehearse this out loud.
Book a 1:1 mock interview. Detailed feedback sheet + scoring on the exact rubric hiring managers use.
Book a mock interview