Business Analyst Job Description Template 2026

Last updated: July 10, 2026

A strong business analyst job description names which kind of BA you actually need, spells out the tools and methods, and posts a salary band, because one title quietly covers three different jobs that pay very differently. The template below comes from business analyst searches that filled, not the wishlist reqs that pull 250 applicants and hire none of them.

Ask a room of hiring managers to define a business analyst and watch the answers scatter. One wants the person who writes user stories and sits with the dev team. One wants the process person who maps how the claims department really works, then fixes it. One wants someone to build the reporting the CFO stares at every Monday. One is describing a product manager and hoping analyst money covers it. The last one just wants the requirements to stop changing halfway through the build. All real jobs.

One title. Several jobs. Every one of them gets written up as “Business Analyst,” and then the resumes come in looking like they answered five different ads.

I’m Mike Carter. I lead partnership success at KORE1, which in plain terms means I spend my days between the hiring managers who open these reqs and the recruiters on our desk who fill them. We staff business analysts through our business analyst staffing practice, part of our broader IT staffing services work, so yes, I have a stake in this. We earn a fee when you hire through us. I will still tell you the template and the numbers below work exactly the same whether you hand us the search or run it yourself with fifteen browser tabs open at midnight.

Scope it tight and the right analysts self-select in. Leave it vague and you read 250 resumes to find the four that fit. The posting is doing the first round of screening whether you meant it to or not. So write it on purpose.

Business Analyst vs Product Manager vs Project Manager vs Data Analyst

A business analyst defines what the business needs and translates it into requirements a team can build; a product manager decides what to build and why, a project manager runs the timeline and delivery, and a data analyst answers questions with SQL and dashboards. Four roles, four different hires.

This is the confusion that wrecks more BA searches than any skills gap ever does. It is not close. Get the boundary wrong on the posting and the shortlist comes back full of people who are good at a job you did not mean to advertise.

The business analyst owns the middle. They sit with stakeholders, pull out what the business is actually trying to accomplish, and turn that into requirements, process maps, and acceptance criteria the delivery team can act on. On an IT team that looks like user stories, systems requirements, and a lot of translating between the people who want the feature and the engineers who have to build it. On the operations side it looks like process discovery, gap analysis, and a redesign of how a workflow runs. Same instinct underneath. Different surface.

A product manager decides which problems are worth solving and in what order, and they own the outcome when the roadmap is wrong. They own the “why.” A BA can inform that call and often documents it beautifully, but the accountability for the “why” and the “what next” lives with product. Blur those two on a JD and it breaks one of two ways. You pay BA rates for a product hire who leaves in eight months. Or you set a real BA up to take the blame for prioritization calls they were never handed the authority to make. Neither ends well.

The project manager runs the plan. Scope, schedule, budget, the standup, the risk log, the uncomfortable status update. That is delivery, not analysis. A BA defines what good looks like; a PM makes sure it ships on time. Some smaller shops genuinely need one person wearing both hats, and that is fine, as long as the posting says so and the band reflects two jobs instead of one. Two jobs, two bands.

Then the data analyst, who lives in SQL and Tableau or Power BI and answers “what happened” with numbers. There is real overlap here, because plenty of business analysts read data all day. The overlap is real. The line is that a data analyst’s product is the analysis itself, while a business analyst’s product is a decision or a requirement that the analysis feeds. If your bullets are mostly queries and dashboards, you may be writing a data analyst job description instead.

Read the “core question” row before you write a word of the posting. Just that row. If the honest answer to your opening is “decide what we build next,” you want a product manager. If it is “keep the program on schedule,” that is a project manager. The business analyst is the person who makes sure that whatever gets built is the thing the business actually needed. Name that, and the right people raise their hands. That is the whole trick.

What a Business Analyst Actually Owns

The role is hard to pin down because it stretches across three flavors that share a spine but land in different orgs. A posting that says which flavor you need pulls a sharper pool than one that lists every BA skill ever printed and hopes the right person recognizes themselves. So pick the flavor.

The IT / systems business analyst. The bridge between the business and the build. They gather requirements, write user stories with acceptance criteria, sit in refinement, and keep the traceability between what was asked for and what shipped. Jira and Confluence are home. They speak enough SQL to validate data and enough system design to know when a request is a two-hour change or a two-quarter one. If your BA works next to engineers, this is the seat, and it is the closest cousin to the old computer systems analyst the BLS still tracks.

Then there is the analyst who never opens a ticket queue.

The business / process analyst. Different world entirely. This one maps how work really flows, not how the org chart says it does, then finds the gap that costs the company money or time. The gap is the job. Think BPMN diagrams in Visio or Lucidchart, stakeholder interviews, a current-state and future-state that survive contact with the people who do the job. Heavy in insurance, banking, healthcare, and manufacturing, where a process fix is worth more than any feature. This is the profile the government’s management analyst category lines up with.

The data-leaning business analyst. Requirements plus reporting. They own the metrics that a decision hangs on, build or spec the dashboards, and translate a fuzzy executive question into something a data team can answer. SQL is real here, and a BI tool, and enough business context to know which number is the one that matters. The line into data analyst work is thin, and the two titles poach each other constantly. It happens weekly.

One thing sits under all three. Judgment about what to leave out. A great business analyst is not the person who captures every requirement anyone mentions. It is the person who knows which requirements are load-bearing and which are somebody’s pet idea, and has the standing to say so before the team builds all of them. Load-bearing, or not. That instinct is what you are really paying for, and it is the hardest thing to screen for on paper. That is the whole game.

The Business Analyst Job Description Template

Here is the block. Copy it, swap the bracketed prompts for your real scope, and delete the italic notes before it goes live, because those are for whoever fills it in, not for the candidate. It assumes a mid-level business analyst on an established team. Turn the ownership language up for a senior or lead role, and down for a first BA hire who will be building the practice as they go. Start there.

Where Business Analyst JDs Go Wrong

I read a lot of these before a search opens, and the same handful of mistakes shows up over and over. Each one bleeds candidates in a way the hiring manager usually does not notice until the req has sat open for weeks. Five come up the most.

The everything analyst. One posting that wants a requirements writer, a process re-engineer, a dashboard builder, and a part-time project manager, all at a single mid-level band. No one person is strong at all four, and the generalists who apply are rarely great at the one you needed most. Pick the flavor. Write that posting.

Second, and it is the sneaky one. A product manager job wearing a BA title to save money. The bullets ask for roadmap ownership, prioritization calls, and market outcomes, but the title says Business Analyst and the band is set to match. The real product people skip it, and the analysts who apply get handed accountability they were never given authority for. If the job owns the “what next,” fund a product manager. If it owns the “what exactly,” a BA is right. Not the same person.

Requiring a specific degree. Some of the sharpest analysts our recruiters have placed came out of nursing, accounting, the military, or a support desk. They learned the business cold before they ever wrote a requirement. A hard degree filter would have cut every one of them. Pedigree is not the point. Make it preferred, or drop it, and let a structured case interview do the sorting instead.

Fourth, the tool checklist standing in for a scope. Jira, Confluence, SQL, Tableau, Power BI, Visio, SAP, Salesforce, and “Agile certification required,” all under must-have. It does not read as a high bar to a good analyst. It reads as a team that has not decided what the job is. So they close the tab. Name the three or four tools the person will touch on Tuesday. Stop there.

No salary band. In this market an unposted range is a self-inflicted wound. It costs you the applicants who will not spend a week interviewing for a mystery number. And it wastes the screens you do get, when the band finally surfaces and it was never going to work anyway. Four states already make you post it. The rest of your competition is posting it regardless. List the number.

Tools, Methods, and Certs Worth Naming

Naming the specific stack does two jobs at once. It filters for people who have actually used it, and it signals to a strong analyst that your practice is real instead of aspirational. Vagueness costs you on both counts. Specific beats thorough. So be specific about the few things that matter and quiet about the rest.

The requirements and workflow tools. Jira and Confluence are the default pairing on software teams, with Azure DevOps common in Microsoft shops. For process work, name Visio or Lucidchart and, if you use it, the notation, because a BA fluent in BPMN reads very differently from one who draws boxes and arrows freehand. Name the one or two your team actually runs. An analyst strong in Jira picks up Azure DevOps in a week, so treat the specific tool as transferable and the underlying habit as the real requirement.

The methods. Say how your teams work, honestly. Agile and Scrum if that is real, waterfall or a hybrid if that is the truth. An analyst who has only lived in one will feel every seam of the other for the first few months. The discipline behind the role has a formal body of knowledge too. It is the BABOK Guide, from the International Institute of Business Analysis. You would never make someone quote it. But its vocabulary is a decent shared language for what the role actually covers.

Certifications, in their place. The IIBA credentials, ECBA at entry, CCBA in the middle, and CBAP for the experienced, plus the PMI-PBA, are the ones that come up in our searches. They are a fair “preferred” signal that someone took the craft seriously. They make a poor “required” gate, because plenty of excellent analysts never bothered with the exam while they were busy doing the work it certifies. Weigh the track record first.

Business Analyst Salary Benchmarks for 2026

Most U.S. business analysts earn between $74,000 and $138,000 in 2026, with average base pay landing near $99,000 to $111,000 depending on the source, and senior analysts at tech and finance firms clearing $140,000 once bonus and equity come in.

The aggregators agree on the middle of the market and argue about the edges, and that argument is exactly where the useful information for setting a real band tends to hide once you know how to read it.

Now look at the senior line, where the aggregators come apart. Glassdoor’s self-reported senior business analysts average about $150,000 in total pay. ZipRecruiter’s senior sample sits near $107,000. PayScale lands closer to $96,000 on base. Same title, and roughly $54,000 between the high and low read. That gap is not three different jobs. It is one senior role measured three ways, one folding in bonus and equity, one scraped from cautious job ads, one reporting base alone. Read the label first. For a senior band, weight the self-reported total-pay figure and sanity-check it against your metro. For entry pay, the posted ads run closer to the truth.

A word on the government numbers, because the BLS has no “business analyst” code at all. The two closest tracked occupations are Management Analysts, at a $101,190 median with 9 percent projected growth through 2034 and roughly 98,100 openings a year, and Computer Systems Analysts, at a $103,790 median with the same 9 percent growth. Two proxies, one signal. Your real BA demand lives somewhere in the blend of those two, which is exactly why the title-specific aggregator numbers beat any single government code when you are setting an actual budget.

Here is the part only a recruiter sees from the inside. KORE1 fills business analyst and IT roles in 17 days on average across more than 30 U.S. metros, and 92 percent of those placements are still in the seat a year later. Location moves the band more than most hiring managers plan for. A senior BA in San Francisco, Seattle, or New York runs well above the same role in Austin, Denver, or most of the Midwest. The candidates who could take either offer already know it. They price it in before the first call. A contract analyst usually carries a 10 to 15 percent rate premium over the salaried equivalent, worth pricing in when you weigh contract or contract-to-hire against a direct hire. For the full picture on comp, our business analyst salary guide breaks it down by level and specialty.

Adapting the Template by Company Stage

The block above is a skeleton. Where your company sits decides which parts carry the weight.

Your first business analyst. If nobody has held this seat, the job is half analysis and half building the function from nothing. Say that out loud in the posting. This person writes the first requirements standard, earns trust with teams who have gotten by on hallway conversations, and has to show value before the new-hire goodwill runs out. That is a specific temperament. Someone comfortable with a blank page and patient with the politics. Lead with the mandate and name the leader backing it. A first BA with no executive air cover stalls fast, and the good ones smell that setup in the interview.

An established BA practice. If there is already a PMO, a requirements standard, and a few analysts, the role narrows to a specific gap, a platform migration, a compliance program, a team that keeps shipping the wrong thing. Pick the gap and name it. Name the tools already in place and the domain the analyst will step into. A strong candidate reads that specificity as proof the practice is real, and reads a generic BA post as proof it is not. Specificity sells.

What Hiring Managers Ask Us Before Posting a Business Analyst Role

Business analyst or product manager, which one do I actually need?

Ownership of the “why” is the dividing line. A product manager decides which problems to solve and answers for whether the product works in market; a business analyst makes sure whatever gets built matches what the business needs and documents it so the team can act. If the role owns roadmap and prioritization, that is product, and pricing it as a BA just loses you the real product people. If it owns requirements, process, and the translation between business and build, a business analyst is the right hire. Title follows work. Write the responsibilities first and it settles itself.

Does a business analyst need to know SQL?

For most IT and data-leaning BA roles, yes, enough to validate data and pull a straight answer, and it belongs in the required column. For a pure process or business analyst working in workflows and stakeholder maps, SQL is a genuine nice-to-have rather than a gate. Flavor first. So decide it before you write the requirement. Put “expert SQL” on a process analyst posting and you shrink your pool for a skill the job barely touches. Leave it off an IT BA posting and you invite resumes that cannot check their own work.

What certifications should I look for on a BA resume?

The ones that show up most are the IIBA family, ECBA for newcomers, CCBA in the middle, and CBAP for experienced analysts, along with the PMI-PBA. Treat them as a preferred signal, not a filter. A CBAP tells you someone studied the craft formally. That is worth something. But some of the best analysts we place never sat the exam. They were busy doing the work it certifies. Read the credential as a plus, and let a case-style interview show you how the person actually thinks through an ambiguous request.

How long should a business analyst job description be?

Shorter than most people make it. Three hundred to five hundred words of real content is plenty to scope the role, name the tools, and post a band. The reqs that sprawl past a thousand words are almost always padding the requirements list, which is the one section that actively repels strong applicants. Put the flavor and the scope up top, keep the responsibilities concrete and few, and push the legal boilerplate to the bottom where it belongs.

Is it worth posting the salary range?

Post it, every time. California, Colorado, New York, and Washington already require a range on the listing, and candidates everywhere else now read a missing band as either disorganized or evasive. A posted range filters out the mismatches before anyone burns a phone screen finding them. It also pulls in the strong analysts who will not gamble a week of interviews on a number you would not show. The only thing an unposted band protects is your option to underpay. The good BAs priced that in already.

Contract or direct hire for a business analyst?

It follows how bounded the work is. A specific program, a system migration, or a compliance push with an end date points to contract staffing, which usually carries a 10 to 15 percent rate premium over salary. If the analyst will own a standing part of how the business runs, hire direct. When you want to watch the work before you commit, contract-to-hire splits the difference. We place business analysts under all three models, and the right one tends to match the shape of the work rather than the preference on the req.

Next Steps

Take the template and make it yours. Yours, not ours. Pick the one flavor you are hiring, name the real tools and the domain, split must-have from nice-to-have without flinching, post the band, and cut every line that does not describe your actual hire. A short, specific business analyst JD beats a long generic one in every search we run.

Want a second read on a posting that has sat open too long, or help telling a BA role apart from the product or project job hiding inside it? That is our desk. Reach out to a recruiter on our team. KORE1 places business analysts and IT talent across 30+ U.S. metros through direct hire, contract, and contract-to-hire, with an average time-to-fill of 17 days and 92 percent of those hires still in seat a year later. When the shortlist is in front of you, our business analyst interview questions help separate the real analysts from the resume padders, and the full guide to hiring a business analyst walks the search end to end.