Business Analyst
Requirements
hard
Walk me through how you'd do a gap analysis for an ERP migration.
Asked at
SAPOracleInfosysDeloitte
Framework
AS-IS → TO-BE → categorised gap register
Model answer
Document the current state (AS-IS) at process, data, and integration layers. Document the target state (TO-BE) from the new ERP's out-of-box capability. The gap is what needs custom development, configuration, or process change — categorise each gap by cost and risk.
What great candidates actually do
- 80% of ERP gaps should be closed by changing YOUR process, not the ERP.
- Every gap needs an owner and a resolution path (build/buy/change/accept).
- Master data gaps kill ERP projects — audit them first, not last.
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