Data & AI
Business Analyst Resume Examples & CV Template (Entry to Senior)
Business Analysts are the link between what the business needs and what the technical team builds. This guide explains what the job involves, which skills employers check for, how to write a CV that passes ATS screening, and how to prepare for the interview.
What the role does
A Business Analyst (BA) studies how a business works, finds problems or opportunities and defines clearly what a system, product or process change should do. In practice that means interviewing stakeholders, writing requirements and user stories, drawing process flows, analyzing data with SQL and Excel, and working with developers and testers so that what is built solves the right problem. Business Analysts also run workshops, prepare business cases, support user acceptance testing (UAT) and help teams adopt the change after release. They work closely with product owners, developers, QA, data teams and business units such as finance, operations and customer service. The role exists in banks, insurers, e-commerce, logistics, healthcare, consulting and software companies.
Main responsibilities
- Interview stakeholders and users to understand goals, pain points and constraints
- Write business requirements, user stories and acceptance criteria that developers and testers can use
- Map current and future processes with flowcharts (BPMN, UML) to find waste and gaps
- Analyze data with SQL and Excel to size a problem and measure the result of a change
- Create wireframes and prototypes to confirm the solution with users before development
- Work with developers and QA during delivery: answer questions, review work and manage changes in scope
- Plan and support UAT, and help train users and release the change
- Prepare business cases with costs, benefits and risks so leaders can decide what to fund
Career path
- 10-2 yrsIntern / Junior Business Analyst
Documents requirements and processes for defined features with guidance and learns the business and delivery process.
- 22-4 yrsBusiness Analyst
Owns requirements for a product area from discovery to release and works directly with stakeholders.
- 34-7 yrsSenior Business Analyst
Leads analysis for complex projects, shapes solutions and business cases and mentors other analysts.
- 47+ yrsLead BA / Product Owner / Product Manager
Owns the direction of a product or a group of analysts and decides what gets built and why.
- 58+ yrsHead of Business Analysis or Product Director
Leads the analysis or product function and sets practices and priorities across the company.
Skills employers ask for
Hard skills
- Requirements elicitation
- Interviews, workshops, observation and surveys to find real needs behind the first request.
- Documentation
- BRD, SRS or PRD, user stories with acceptance criteria and use cases that are clear and testable.
- Process modeling
- BPMN and UML diagrams (flowcharts, sequence and use case) to show how work flows and where it breaks.
- SQL and data analysis
- Querying data and using Excel or Power BI to size a problem and verify results.
- Agile and Scrum
- Backlog grooming, sprint planning, estimation with the team and working in short cycles.
- Wireframing and prototyping
- Figma or Balsamiq mockups to agree the screens and flow before development.
- Business case and cost-benefit analysis
- ROI, costs, benefits, risks and options so decision-makers can choose with confidence.
- UAT and testing
- Writing test scenarios, supporting user acceptance testing and tracking defects to closure.
- API and system basics
- Reading API docs, understanding integrations and testing them in Postman.
- Domain knowledge
- Understanding the business of your industry, such as payments, banking, retail or logistics.
Soft skills
Tools
Certifications
Open jobs right now
Latest Business Analyst jobs
CV examples
CV summary examples
Junior Business Analyst with a 6-month internship writing user stories and mapping processes for a payments company. Wrote 35 user stories with acceptance criteria, found 4 data mismatches with SQL and works well with developers and users.
Business Analyst with 4 years in fintech and e-commerce, defining requirements for payment and seller products. Cut seller onboarding from 5 days to 1 day and found support issues behind 40% of contacts using SQL.
Senior Business Analyst with 8 years in fintech, logistics and retail. Led analysis for a 35-person program, built a business case that secured $2.4M and grows analysts through mentoring and shared standards.
Experience bullet examples
Defined 45 user stories for seller onboarding; onboarding time fell from 5 days to 1 day and completion rose by 22%
Analyzed support tickets with SQL and found that 3 issues caused 40% of contacts; fixing them saved about $90k a year
Mapped 8 end-to-end processes in BPMN and removed 14 redundant steps, cutting handling time by 28%
Reduced requirement-related defects by 35% by adding acceptance criteria and a pre-sprint review
Built a business case that secured $2.4M of funding with projected savings of $1.9M a year
Redesigned the returns process, cutting cost per return by 26% and handling time from 7 days to 3 days
Defined API requirements for 6 partner integrations; partner go-live fell from 8 weeks to 3 weeks
Ran UAT for 5 releases across 3 business teams with no critical defects after go-live
Prioritized 10 of 40 manual processes for automation, saving 12,000 staff hours a year
Mentored 4 analysts; 2 were promoted within 18 months
How to write your CV
Put numbers in every bullet you can
Time saved, cost reduced, defects avoided, number of stakeholders, size of the budget or program. Numbers show the scale of the work and what changed because of you.
Write action, method and result
Start with a strong verb, say how you did it, end with the result: "Cut seller onboarding from 5 days to 1 day by redesigning the flow and writing 45 user stories with acceptance criteria."
Show business outcomes, not only documents
A requirements document is a means. Show what improved because of it: revenue, cost, speed, errors or customer satisfaction.
Show how you work with people
Mention workshops, number of stakeholders, conflicts you resolved and how developers and testers used your work. Stakeholder skills are a large part of the job.
Show data skills
SQL, Excel or Power BI used to size a problem or check a result separates a strong BA from one who only writes documents.
Match each job description
Use the same terms as the posting ("user stories", "BPMN", "UAT", "Agile") where they are true for you, and move the most relevant experience to the top. Keep it to one page under 5 years of experience.
Interview questions
TechnicalA stakeholder asks for a new report. How do you make sure you build the right thing?
How to answer: Ask what decision the report supports, who uses it, how often and what happens today. Confirm the real need before the solution, then validate with a prototype or sample.
TechnicalWhat is the difference between functional and non-functional requirements? Give examples.
How to answer: Functional: what the system does (a user can reset a password). Non-functional: how well it does it (speed, security, availability). Show that you capture both.
TechnicalHow do you write a good user story and acceptance criteria?
How to answer: As a [user], I want [goal], so that [value]. Acceptance criteria should be specific and testable, ideally in Given-When-Then form. Mention INVEST.
TechnicalHow do you prioritize requirements when everything is urgent?
How to answer: Use value versus effort, MoSCoW or weighted scoring, with stakeholders involved. Tie each item to a business goal and make trade-offs visible.
TechnicalHow would you map and improve an existing process, such as order refunds?
How to answer: Interview people who do the work, draw the current flow in BPMN, measure time and errors, find waste and bottlenecks, design the future process and define metrics.
TechnicalHow do you use SQL as a Business Analyst?
How to answer: Give examples: counting how often a problem happens, checking reports against the database, finding data issues before UAT. Mention joins and aggregations.
TechnicalHow do you manage a change in scope in the middle of a sprint?
How to answer: Assess impact on scope, time and risk, discuss with the product owner and team, decide what to swap or defer and update the backlog and documents.
BehavioralTell me about a time you had to handle conflicting requirements from stakeholders.
How to answer: Use situation, action, result: how you found the underlying goals, facilitated a discussion with data, reached a decision and kept the relationship strong.
BehavioralDescribe a time a project failed or went off track. What did you do?
How to answer: Be honest. Show how you spotted it, raised it early, proposed options and what you learned about requirements or communication.
BehavioralTell me about a project you are proud of.
How to answer: Pick one with a measurable result. Explain your part, the hardest problem and what you would do differently now.
SituationalDevelopers say your requirements are unclear and testers find gaps late. What do you do?
How to answer: Listen to specific examples, add examples and acceptance criteria, hold a short refinement session before each sprint and agree a definition of ready.
SituationalA senior executive asks you to add a feature that conflicts with the roadmap. What do you do?
How to answer: Understand the goal behind the request, assess the impact and cost, present options and trade-offs with the product owner and let the decision be made openly.
Frequently asked questions
What does a Business Analyst do?
A Business Analyst finds out what the business needs and defines clearly what a system, product or process should do. They gather requirements, write user stories, map processes, analyze data and work with developers and testers so the right solution is built.
Is a Business Analyst the same as a Data Analyst?
No. A Business Analyst focuses on requirements, processes and solutions with stakeholders. A Data Analyst focuses on data, SQL and dashboards. Many BAs use SQL and some Data Analysts work on business requirements, so the roles overlap.
Do I need an IT degree to become a Business Analyst?
No. Many BAs come from business, economics, finance, testing or customer-facing roles. Employers check clear writing, analytical thinking, domain knowledge and basic technical understanding such as databases and APIs.
Which skills should I learn first?
Writing requirements and user stories, process mapping (BPMN), SQL and Excel, and Agile basics. Add a tool like Jira and a wireframing tool like Figma.
What should a junior Business Analyst CV include?
Internships, 2 to 3 real or academic projects (requirements documents, process maps, prototypes), the tools and methods used and measurable results. Add your degree, relevant courses and certifications such as ECBA, and keep it to one page.
How long should a Business Analyst CV be?
One page for up to about 5 years of experience, two pages at most for senior roles. Put the most relevant, measurable work at the top.
What is the difference between a Business Analyst and a Product Owner?
A Product Owner owns the product vision and the backlog and decides priorities. A Business Analyst supports with research, requirements and analysis. In some teams one person does both.
Related roles
Build your Business Analyst CV in minutes
Start from an ATS-ready template, let AI improve your bullets, then score your CV and practise the interview out loud.