A business analyst resume needs to show you turned messy stakeholder needs into clear requirements — and that the delivered change moved a business metric.
Three things, in order of weight.
Requirements artifacts you produced: BRDs, user stories, process maps, acceptance criteria.
Hands-on data skills — SQL queries and dashboards you built yourself, not just reports you read.
Stakeholder range: which departments you worked between and how decisions got made.
Work them into your title, project descriptions and skills — don't pile them into a list.
Each cover is the template itself, rendered.
Clean section hierarchy mirrors the structured thinking a BA sells.
Neutral and corporate — fits banks, insurers, and consultancies where most BA roles sit.
One page. Unless you have 10+ years and a genuinely full second page, the second page only dilutes the first. Put requirements artifacts you produced: brds, user stories, process maps, acceptance criteria. above the fold.
Listing "gathered requirements" without saying what was built from them or what changed.. It is the single most common reason this role gets screened out, and fixing it matters far more than changing templates.
Use AI for the first draft, then verify every claim and number yourself and reorder keywords against the target job description. AI handles speed; the content is still your responsibility.