Business analysts sit between the business and the technical team, so hiring managers look for two sides in your resume: can you understand what the business needs, and can you turn that into clear requirements that a team can build? Show both with examples and the outcome of the projects you worked on.
Summary
Business analyst with six years of experience in insurance and financial services. Gathers and writes requirements, maps processes and works closely with product owners and developers from discovery to release. Uses SQL and Excel to back up recommendations with data. Clear communicator with stakeholders at every level. Looking for a senior business analyst role on a digital transformation program.
Work experience
Business Analyst, Insurance company in Hartford, CT (2021 - Present)
Lead requirements for a new online claims process, used by about 30,000 policyholders a year.
Mapped the old claims process with 6 departments and found steps that could be removed, cutting average handling time.
Write user stories and acceptance criteria for a Scrum team of 7 developers and testers.
Plan and run user acceptance testing with business users before each release.
Junior Business Analyst, Regional bank in New Haven, CT (2018 - 2021)
Documented requirements for updates to the loan application system.
Pulled data with SQL to support business cases and reporting.
Supported testing and training for a new customer relationship system.
Education
B.S. in Information Systems, State university in Connecticut (2014 - 2018)
IIBA Certification of Capability in Business Analysis (CCBA), International Institute of Business Analysis (2022)
Skills
Requirements gathering and documentation
User stories and acceptance criteria
Process mapping (BPMN)
Stakeholder interviews and workshops
Gap analysis
SQL and Excel
Jira and Confluence
User acceptance testing
Agile and Scrum
Visio and Lucidchart
Keywords the software looks for
Many employers have your resume read first by software that filters on these words. Use them where they match your experience: in your summary and in your work experience.
business analyst
requirements gathering
user stories
process mapping
stakeholder management
gap analysis
UAT
SQL
Jira
Confluence
Agile
BPMN
How to make your resume stronger
Show the outcome of your projects
Faster processes, fewer errors, a system that launched. Requirements are the means, the result is what hiring managers want to see.
Name your methods and software
User stories, BPMN, UAT, Jira, Confluence, SQL. Postings filter on them, and they show how you work.
Describe your stakeholders
Which departments, how many, at what level. Working across many teams is a big part of the job.
Mention domain knowledge
Insurance, banking, healthcare, retail. Domain knowledge shortens your ramp-up and is often a hard requirement.
Keep technical skills honest
Say how you use SQL or other data software. A business analyst is not a data engineer, and interviews will test your level.
Common mistakes
Only listing documents you wrote, without the result of the project.
Leaving out the domain or industry you worked in.
Vague phrases like 'liaison between business and IT' without examples.
Too much technical jargon for a business audience.
Frequently asked questions
What should a business analyst resume include?
Your methods, software, domain knowledge, the stakeholders you work with and the outcomes of your projects.
Do business analysts need SQL?
It is not always required, but it helps. Many postings ask for basic SQL to check data and support recommendations.
Is a CBAP or CCBA certification worth it?
It can help, especially in larger organizations. Experience and results still carry more weight.
How long should a business analyst resume be?
One to two pages. Focus on your most relevant projects and their results.
Resumate is an AI resume builder for job seekers, at getresumate.com and getresumate.nl. We help candidates get past the filter with a resume, a cover letter and a match per job posting. Resumate is not a recruiter ATS and not a job board.