Business analyst is one of the most ambiguous titles in hiring — it means requirements work in one company and SQL analysis in another. Your resume has to resolve that ambiguity in the first three lines.
Keywords an ATS holds for business analyst roles
These are the terms that recur across business analyst postings and appear in the search filters recruiters run. They are not a checklist to paste in — use the ones that describe work you have genuinely done, phrased the way the market phrases it.
- business analysis
- requirements gathering
- requirements elicitation
- process improvement
- process mapping
- gap analysis
- stakeholder management
- user stories
- acceptance criteria
- business process
- as-is to-be
- data analysis
- sql
- uat
- user acceptance testing
- functional specification
- brd
- frd
- change management
- root cause analysis
- workflow design
Core skills to list explicitly
Skills sections are parsed into structured fields and searched directly, so a skill only mentioned inside a bullet is weaker than one listed here as well. Split them the way hiring managers think about them.
- Hard skills — Requirements elicitation and documentation, Process mapping (BPMN, swimlane), Gap and impact analysis, User story and acceptance criteria writing, UAT planning and execution, Data analysis and SQL, Business case development, Stakeholder workshops, As-is / to-be modelling, Root cause analysis
- Tools and platforms — Jira, Confluence, Visio, Lucidchart, Miro, SQL, Excel (advanced), Power BI, Tableau, ServiceNow, Azure DevOps, SAP
- Working skills — Facilitation, Stakeholder interviewing, Written clarity, Translating between business and technical teams, Negotiating scope, Conflict resolution
The numbers that move a business analyst hiring manager
Quantified bullets consistently outperform unquantified ones, but the useful numbers are role-specific. These are the ones that get read in this field. Use only figures you can defend in an interview — the builder will leave an [ADD METRIC] placeholder rather than invent one for you.
- Process time or cost reduced
- Number of stakeholders and business units engaged
- Volume of requirements delivered and defect rate against them
- Value of the project or system you supported
- Manual effort eliminated, in hours
- UAT defect detection and resolution rate
- Adoption rate of the process or system you specified
Example bullets (illustrative)
These are examples of shape and specificity, not text to copy. They belong to nobody, and the AI writers will never insert them into your resume — everything they produce comes from your own profile.
- Elicited and documented 140 functional requirements for a claims-handling system replacement across 5 departments, with a post-launch requirements defect rate under 4%.
- Mapped the as-is order-to-cash process across 3 systems and identified 6 handoffs that were removed, cutting average cycle time from 9 days to 5.
- Facilitated 14 stakeholder workshops to resolve conflicting requirements between operations and finance, producing a signed-off scope that held through delivery.
- Ran UAT for a £2M ERP module with 22 business testers, tracking 180 defects to closure before go-live.
- Automated a manual reconciliation process with the data team, eliminating roughly 60 analyst-hours per month.
Mistakes that recur on business analyst resumes
- Not resolving the title ambiguity — Say in your summary whether you are a requirements-and-process BA, a data BA, or a systems BA. Reviewers cannot tell from the title and will not guess in your favour.
- Documentation volume as achievement — 'Wrote 200 requirements documents' measures effort, not value. What changed in the business as a result?
- Omitting SQL when you have it — Many BA postings now filter on SQL. If you can write it, list it — it materially widens the roles you match.
- No domain specificity — Insurance claims, retail banking, healthcare and logistics BAs are hired for domain knowledge as much as method. Name your domain explicitly.
- Methodology without delivery — Listing BPMN, Agile and Waterfall is table stakes. What you delivered, and what improved, is not.
Section order and structure
Use your summary to state your BA type and domain in the first sentence. It is the single highest-value line on a business analyst resume, because it stops the reviewer guessing.
Recommended template: Chandler or Kestrel. BA hiring is portal-heavy in banking, insurance and government — stay single column.
- Contact
- Professional Summary
- Work Experience
- Core Competencies
- Tools & Techniques
- Certifications
- Education
Writing the summary
Type, domain, and one measured improvement. 'Business analyst, 6 years in general insurance; requirements and process specialist across claims and underwriting; mapped and re-designed an order-to-cash process, cutting cycle time from 9 days to 5.'
Certifications worth listing
Certifications are frequently used as hard filters, so list every relevant one you hold with the awarding body and year. Never list one you are 'planning to take' — in progress with an exam date is acceptable and honest.
- CBAP (Certified Business Analysis Professional)
- CCBA
- PMI-PBA
- BCS International Diploma in Business Analysis
- Certified ScrumMaster (CSM)
- Lean Six Sigma Green Belt
Frequently asked questions
- What is the difference between a business analyst and a data analyst?
- A business analyst elicits requirements and improves processes; a data analyst answers questions with data. Many roles blur the two, which is exactly why your resume must state which one you are in the summary.
- Do I need CBAP?
- It is valued in large enterprises, government and consultancies, and is a filter in some postings. Below senior level it is rarely required, and delivery evidence matters more.
- How much technical detail should a BA resume include?
- Name the systems you worked on and the technical skills you genuinely have — SQL, API concepts, data models. Depth should match the posting; systems-BA roles want more, process-BA roles want less.
- How do I show requirements quality rather than volume?
- Use downstream measures: post-launch defect rate against requirements, change requests raised after sign-off, UAT pass rate. Those demonstrate quality in a way document counts never will.
- Is domain experience essential?
- It is often the deciding factor in banking, insurance, healthcare and government, where regulation makes context expensive to learn. Name your domains explicitly and prominently.