Pre-Interview Cheatsheet
Business Analyst — Confidence Cheatsheet
A printable, focused refresher tuned for Business Analyst. Open the sections that matter to you and walk in confident.
Tuned for Business Analyst · Business, Finance & Analytics > Analytics, Strategy & OperationsRefresh Right Now The 60-second mental warm-up before you start.
- Know requirement elicitation, stakeholder mapping, current-state/future-state process mapping, gap analysis and acceptance criteria.
- Understand business cases, KPIs, cost-benefit logic, process bottlenecks and change impact.
- Be ready to discuss user stories, use cases, workflows, data requirements and prioritization.
- Strong BA work translates messy business needs into clear, testable requirements.
- Know the difference between solution requirements, business requirements and technical specifications.
Core Vocabulary Terms interviewers expect you to use precisely.
- Requirement: documented need or condition that a solution must satisfy.
- Acceptance criteria: conditions that prove a requirement is met.
- As-is / to-be: current process vs target process.
- Stakeholder: person or group affected by or influencing the change.
- Scope creep: uncontrolled expansion of work beyond agreed boundaries.
Formulas & Frameworks The mental models that organise your answers.
- Requirement method: identify stakeholders -> elicit needs -> analyze conflicts -> document -> validate -> manage changes.
- MoSCoW: Must, Should, Could, Won’t for prioritization.
- RACI: Responsible, Accountable, Consulted, Informed.
- Process analysis: input, activity, output, control, owner, metric.
Likely Interview Prompts Questions you should be ready for.
- How do you gather requirements?
- How do you handle conflicting stakeholder needs?
- What makes a good user story?
- How do you define success for a process improvement?
- Tell me about a time requirements changed late.
Red Flags To Avoid Common answers that lose interviews.
- Writing requirements that are vague or not testable.
- Acting as a note-taker instead of an analyst.
- Skipping stakeholder validation.
- Confusing desired solution with underlying business problem.
- Not managing scope.
What Sets You Apart Signals that move you from competent to memorable.
- Asks 'what problem are we solving?' before solutioning.
- Can use data to validate process pain points.
- Can communicate equally well with business and technical teams.
- Documents decisions and assumptions clearly.
30-Second Confidence Reset Anchor sentence to read just before you walk in.
A strong BA reduces ambiguity: clarify the problem, align stakeholders, convert needs into testable requirements, and keep scope controlled.