CV gaps
CV gaps for Business Analyst
Business analyst CVs often list techniques and tools but not the problems analysed, the stakeholders involved or what was delivered. Readers look for evidence that your requirements led to something built or changed.
The 4 gaps to check
Techniques without a problem
Why it matters: Listing process mapping or user stories does not show you used them.
How to close it honestly: Pair each with a short example of the problem and the result.
Stakeholders unclear
Why it matters: Analysts bridge business and technical teams.
How to close it honestly: Say who you gathered requirements from and who built from them.
Delivery not shown
Why it matters: Requirements that never shipped matter less.
How to close it honestly: State what was delivered and any benefit that was measured, if true.
Domain and tools thin
Why it matters: Context helps readers judge fit.
How to close it honestly: Name the industry or function and the tools you used, such as Jira or Visio, only where true.
Questions that find your real evidence
- What problem did you analyse that changed how people work?
- Who did you gather requirements from?
- What was delivered from your documentation?
Only add what is true. If you cannot back a line up with a real example, leave it out.