💻Technical Questions
Q1Write a SQL query to find customers who made purchases in January but not February.
💡Subquery or LEFT JOIN with NOT EXISTS. Show both approaches and explain the performance trade-offs.
Q2What is the difference between a use case and a user story?
💡Use case: actor → system interaction (formal, UML). User story: 'As a [user], I want [goal] so that [benefit]' (Agile, informal). Context for each in SDLC.
Q3How do you document requirements when stakeholders have conflicting needs?
💡Facilitation techniques (workshops, prioritization matrix), requirement categorization (functional vs non-functional), traceability matrix, sign-off process.
Q4What is a data flow diagram and when would you create one?
💡Shows how data moves through a system (processes, stores, flows, external entities). Level 0 (context), Level 1 (process breakdown). When to use vs swimlane diagrams.
🧠Behavioral Questions
B1Tell me about a time you discovered a business process that could be significantly improved.
💡Process mapping, gap analysis, root cause (not just symptoms), quantified the improvement opportunity, got stakeholder buy-in, implemented change.
B2Describe a time a project requirement changed mid-development. How did you handle it?
💡Impact assessment (scope, timeline, cost), stakeholder communication, change management process, trade-off negotiation.
B3How do you handle a stakeholder who keeps adding scope?
💡Scope creep recognition, structured change request process, impact visualization, executive alignment, maintaining project integrity while showing empathy.
🎯Situational Questions
S1A process that takes 5 days is being complained about by users. How would you analyze and improve it?
💡Process mapping (as-is), identify bottlenecks (value-added vs non-value-added steps), root cause analysis (5 Whys, fishbone), design to-be process, pilot, measure improvement.
S2You have 3 weeks to deliver a requirements document for a complex system. How do you approach it?
💡Stakeholder identification and interviews, existing system analysis, requirement elicitation workshops, iterative drafts with feedback loops, sign-off strategy.
Must-Know Topics
- ✓Requirements Elicitation & Documentation
- ✓Process Mapping (BPMN, swimlane diagrams)
- ✓SQL Basics
- ✓Business Process Improvement (Lean, Six Sigma basics)
- ✓Agile & Scrum Methodology
- ✓Stakeholder Management
- ✓Data Analysis (Excel/Google Sheets)
- ✓Use Cases & User Stories
Common Interview Mistakes to Avoid
- ✗Capturing solutions instead of requirements
- ✗Not involving the right stakeholders early
- ✗Missing non-functional requirements (performance, security)
- ✗Not tracing requirements to test cases
- ✗Ambiguous requirements that can be interpreted multiple ways
Frequently Asked Questions
Is SQL required for business analyst interviews?▼
Yes — most BA roles expect basic to intermediate SQL. You should be able to write SELECT queries with joins, GROUP BY, HAVING, and simple subqueries. Data extraction and analysis are core BA skills.
What's the difference between a business analyst and a product manager?▼
BAs focus on requirements, process, and bridging business and IT. PMs own the product vision, roadmap, and outcomes. In some companies, the roles overlap significantly. PMs typically require more ownership of metrics and business outcomes.
Do I need Six Sigma or CBAP certification for BA interviews?▼
Certifications help on your resume but aren't typically tested in depth during interviews. CBAP (Certified Business Analysis Professional) adds credibility for senior BA roles. Six Sigma basics (process improvement, DMAIC) are useful for operations-heavy BA roles.
What industries hire the most business analysts?▼
Banking/BFSI (regulatory requirements), IT services (Infosys, TCS, Wipro — large BA teams), e-commerce/product companies, consulting firms (McKinsey, BCG, Deloitte), and healthcare. Each has different domain knowledge requirements.
How do I move from IT services BA to product company BA?▼
Focus on: learning product metrics (DAU, conversion, LTV), SQL for self-service data analysis, Agile experience (not waterfall), and building case studies from your current work. Apply to mid-size product companies before top-tier — the BA→PM path is common.
Ready for your Business Analyst interview?
Make sure your resume gets you to the interview stage first. Get a free ATS score.
Score My Resume Free →