Business Analyst Job Description: Duties, Skills, Pay and a Free Template
A business analyst finds out what an organization needs, then helps it get there. The job sits between the people who have a problem and the people who build or run the fix. This guide covers what business analysts do, a typical day, skills, titles, pay and outlook, certifications, and a copy-paste job description template for employers.
What a business analyst does
The International Institute of Business Analysis (IIBA) defines business analysis as “the practice of enabling change in an organizational context, by defining needs and recommending solutions that deliver value to stakeholders.” It calls the business analyst an agent of change.
In plain English, a business analyst:
- listens to the people affected by a problem,
- works out what is really needed,
- writes it down clearly enough for others to act on,
- and checks that the result delivers what was promised.
Business analysts work in companies, governments and non-profits. The work can be about software, but it does not have to be. A new approval process, a policy change or a reorganized team can all need an analyst.
Core duties
| Duty | What it involves | Typical output |
|---|---|---|
| Understand the problem | Interview stakeholders, observe the work, review data and documents. | Problem statement, interview notes. |
| Define needs and requirements | Turn wishes into clear, testable statements, and agree on priorities. | Requirements list, user stories. |
| Model the current and future state | Map how work flows today and how it should flow. See what a business process is. | Process maps, data diagrams. |
| Analyze options | Compare solutions by value, cost, risk and effort. | Options and business case. |
| Communicate and facilitate | Run workshops, resolve conflicting views, keep everyone informed. | Agendas, decision records. |
| Support delivery | Answer questions from builders, review designs, help plan testing. | Acceptance criteria, test scenarios. |
| Check the result | Confirm the change works and delivers the expected value. | Benefit review, lessons learned. |
IIBA also describes business analysts working at every level of an organization, from strategy to the goals and requirements of programs and projects. Its tasks and techniques are set out in the BABOK® Guide.
A typical week
No two weeks are alike. This made-up example shows the mix of work on a project to replace a manual leave-approval process.
| Day | Main activity |
|---|---|
| Monday | Interview two HR coordinators about how leave requests are handled. Take notes on delays. |
| Tuesday | Draw the current process. Find three hand-offs where requests wait. |
| Wednesday | Run a workshop with managers and HR. Agree what must change first. |
| Thursday | Write requirements and acceptance criteria. Review them with the developer. |
| Friday | Update the project lead. Prepare test scenarios for next week. |
The week is our illustration. The mix of interviews, modeling, writing and meetings is typical.
Skills employers look for
| Skill group | Examples | Why it matters |
|---|---|---|
| Analysis | Problem solving, spotting root causes, working with numbers. | Finds the real issue, not just the symptom. |
| Communication | Asking good questions, listening, clear writing, presenting. | Requirements fail when people read them differently. |
| Facilitation | Running workshops, handling disagreement, negotiating. | Stakeholders often want different things. |
| Modeling | Process maps, use cases, data and decision tables. | Makes complex work easy to discuss. |
| Business knowledge | Understanding the industry, finance basics, how the company earns money. | Solutions must fit how the business works. |
| Technical awareness | Spreadsheets, basic data queries, how systems connect. | Helps you talk to developers and check data. |
| Planning and delivery | Prioritizing, agile and traditional project methods. | Links requirements to delivery. See what project management is. |
For a fuller breakdown, read business analyst skills.
Job titles you will see
The title varies by company. IIBA lists titles including business analyst, business systems analyst, systems analyst, requirements engineer, process analyst, product manager, product owner, enterprise analyst, business architect, management consultant and business intelligence analyst. It also notes that many roles in management, project management, product management, software development and quality assurance rely heavily on business analysis skills.
When you read a job posting, look past the title at the duties. A “systems analyst” role may be a business analyst role, or a more technical one. For the difference, see business analyst vs. system analyst.
Education and certifications
There is no single required path. BLS says a bachelor’s degree is typical for the related occupations (see pay and outlook below). Some analysts move over from operations, finance, customer service or IT.
IIBA offers three core certifications, by experience level:
| Certification | Full name | Who it is for (per IIBA) |
|---|---|---|
| ECBA | Entry Certificate in Business Analysis | People ready to develop their business analysis skills; no experience years are stated. |
| CCBA | Certification of Capability in Business Analysis | Two to three years of practical business analysis work experience. |
| CBAP | Certified Business Analysis Professional | Over five years of practical business analysis work experience. |
IIBA also lists specialized certifications, including agile analysis, business data analytics, cybersecurity analysis and product ownership analysis. Requirements can change, so check the IIBA site before you apply. Certification is optional, but it can help show your knowledge when you are starting out.
To compare study options, see our business analysis certificate guide. Online providers such as Coursera and Udemy offer introductory courses. We may earn a commission if you sign up, at no cost to you. We are not affiliated with any university.
Pay and outlook
The U.S. Bureau of Labor Statistics (BLS) does not publish a page titled “business analyst” in its Occupational Outlook Handbook. The closest matches are management analysts and computer systems analysts. Use these as a guide, not an exact measure.
| BLS occupation | Median pay (May 2025) | Jobs, 2025 | Projected growth, 2025–2035 | Typical entry education |
|---|---|---|---|---|
| Management analysts | $101,860 per year | 1,077,100 | 10% | Bachelor’s degree; some employers prefer an MBA. |
| Computer systems analysts | $105,850 per year | 544,400 | 8% | Bachelor’s degree, usually in computer and information technology or a related field. |
BLS describes both growth rates as much faster than the average for all occupations. For management analysts, it reports that the lowest-paid 10 percent earned less than $60,640 and the highest-paid 10 percent more than $171,640. Pay for business analysts in your area and industry may differ, so check current job listings.
These figures describe the occupations, not any course or certificate. Read more in business analyst career.
Job description template
Employers can copy this template and edit the brackets. It is our own sample, not a legal or HR standard. Keep requirements honest: asking for ten years of experience for an entry role drives good people away.
Business Analyst — [Company name]
Location: [On-site / hybrid / remote] · Team: [Team] · Reports to: [Title]
About the role: You will work with [teams or customers] to understand their needs, define clear requirements and help us deliver [type of change, e.g., better onboarding, a new reporting system].
What you will do:
- Interview stakeholders and map how work is done today.
- Write clear requirements and acceptance criteria.
- Compare options and recommend a solution with costs and risks.
- Run workshops and keep stakeholders informed.
- Work with developers and testers to deliver the change.
- Check that the result delivers the expected benefits.
What we are looking for:
- [X] years of experience in [business analysis or related work] (or equivalent).
- Strong written and spoken communication.
- Comfort with [spreadsheets / basic data queries / process modeling].
- Experience with [agile / traditional] delivery.
Nice to have: [Certification, industry knowledge, specific tools].
Pay and benefits: [Salary range] · [Benefits] · [Application deadline and process]
Some places require a pay range in job postings, so check the rules where you hire.
How to become a business analyst
- Learn the basics. Read an introduction to business analysis and learn to map a process.
- Practice on real problems. Pick a process at your current job and document how to improve it.
- Build a small portfolio. A process map, a requirements document and a short business case, with sensitive details removed.
- Start from where you are. Some analysts move over from operations, finance, support or IT.
- Add credentials when useful. A certificate or the ECBA can help when you have little experience.
- Apply for entry roles and related titles. Junior analyst, associate analyst, operations analyst and similar titles are worth searching for.
See business analysis best practices and all business analysis guides for more.
Common mistakes
- Writing requirements without talking to users. Interview the people who do the work.
- Jumping to a solution. Define the problem first.
- Vague requirements. “Fast” and “user-friendly” cannot be tested. Add numbers.
- Ignoring stakeholders who disagree. Conflicts do not go away when left unspoken.
- Treating the role as paperwork. The value is in understanding and judgment, not documents.
- Overloaded job ads. Asking for a developer, a project manager and a data scientist in one role makes the job unclear for everyone.
Frequently asked questions
What does a business analyst do?
A business analyst finds out what an organization needs, defines it clearly, compares solutions and helps deliver and check the change.
What are the main responsibilities of a business analyst?
Gathering and analyzing requirements, modeling processes, recommending solutions, facilitating workshops, supporting delivery and checking results.
What skills does a business analyst need?
Analysis, communication, facilitation, modeling, business knowledge and basic technical awareness are the main groups.
Do business analysts need to code?
Not usually. Basic data skills, such as spreadsheets and simple queries, help. Understanding how systems fit together matters more than writing code.
How much do business analysts earn?
BLS does not publish a business analyst category. For related occupations in May 2025, it reports a median of $101,860 for management analysts and $105,850 for computer systems analysts.
Do I need a certification to be a business analyst?
No. Certification is optional. IIBA offers the ECBA, CCBA and CBAP for different experience levels.
What is the difference between a business analyst and a project manager?
A business analyst defines what needs to change and why. A project manager plans and runs the work to deliver it. Small organizations sometimes combine the roles.
Browse certificate, course and degree programs side by side.