Business analyst job description template: the kind of analysis, who decides, IIBA lines and screening
On this page
A business analyst posting that lists "gather requirements, document processes, work with stakeholders, support testing" could describe a junior analyst writing user stories for one team or a senior analyst redesigning order to cash across five departments. Candidates cannot tell which, and neither can the recruiter screening them. The details that separate one business analyst job from another are the kind of analysis, the size of the change, who makes the final call and what the analyst hands over at the end. Below is a copy-ready business analyst job description template, the IIBA and classification lines with sources, screening questions and scorecard rows, and the mistakes that make business analyst postings interchangeable. The general method is in how to write a job description that screens.
Decide what kind of business analyst you need
| Kind | Typical deliverable | Must-have that separates it |
|---|---|---|
| IT or systems analyst | Functional requirements, user stories with acceptance criteria, interface specifications | Has written requirements that developers built from, and handled the questions that followed |
| Process improvement analyst | Current and future process maps, a case for change, rollout plan | Has mapped a process across several teams and seen a change adopted |
| Data or reporting analyst | Report definitions, data mappings, metric definitions agreed with the business | Has resolved conflicting definitions of the same number |
| Enterprise application analyst (ERP, CRM) | Configuration decisions, fit-gap analysis, test scripts | Has configured or specified changes to a named business system |
| Agile team analyst | Refined backlog items, acceptance criteria, demos | Has worked inside a delivery team, sprint to sprint |
Then pin down who decides. If a product owner prioritizes and signs off, the analyst elicits and documents. If no one else does, the analyst is effectively making product decisions and should be leveled and paid accordingly. Also note the methodology, the system or process in scope, and how many stakeholder groups the analyst will work with.
The business analyst job description template
[Senior] Business Analyst, [Systems / Process / Data / ERP]
[Company], [city] — [On-site / Hybrid: days / Remote within: states]
Pay: $[min]–$[max] per year. [Benefits summary, if required.]
[Exempt, after review.]
SUMMARY
You will work out what [system / process] needs to do for [teams],
and turn that into [requirements / process designs / report
definitions] that [developers / vendors / operations] can deliver.
Current work: [project, e.g. replacing our order management system
for N users across N sites]. You will work with [product owner /
project manager] and report to [title].
WHAT YOU WILL DO
- Run workshops and interviews with [stakeholder groups] to find out
what they need and why.
- Write [user stories with acceptance criteria / functional
specifications / process maps] in [tool].
- Analyze current processes and data to find gaps and causes.
- Answer developers' and testers' questions during delivery, and
confirm the result does what was agreed.
- Help [teams] adopt the change: [training, procedures, cutover].
YOU MUST HAVE
- Written requirements or designs that were built or implemented,
and dealt with the gaps found afterward.
- Run sessions with stakeholders who disagreed, and reached a
decision someone could own.
- Mapped a process end to end, including exceptions.
- [Data seats: SQL used to answer your own questions.]
- [ERP or CRM seats: configured or specified changes to [system].]
NICE TO HAVE
- [CBAP / CCBA / ECBA] or similar.
- Experience in [industry or domain].
- [Modeling notation or tool used by the team.]
If you meet the must-haves and none of these, please apply.
HOW WE HIRE
[Recruiter screen; conversation with [title]; a 45-minute exercise
turning a short scenario into requirements; meeting the delivery
team.]
[EEO STATEMENT]
For an adjustment in the application or interviews, email [address].IIBA certifications, classification and pay
Not legal advice. Classification points were checked against federal regulations and Department of Labor fact sheets as of October 2026. States can set higher salary levels; confirm with counsel.
Certifications. IIBA offers three core levels: ECBA (entry), CCBA and CBAP. CBAP requires five or more years of business analysis work in the last ten years (7,500 hours), 35 hours of professional development in the last four years and two references (IIBA CBAP). CCBA requires two to three years of experience in the last seven years (3,750 hours) and 21 hours of professional development (IIBA CCBA). Match the line to the level: "CBAP preferred" for a senior seat, "CCBA or ECBA a plus" for a junior one, and never as a substitute for asking about delivered work.
Exempt or nonexempt. The administrative exemption requires at least $684 a week, office work directly related to the management or general business operations of the employer, and discretion and independent judgment on matters of significance (DOL Fact Sheet 17C). For technical seats, the regulation says systems analysts whose primary duty includes planning, scheduling and coordinating activities to develop systems that solve complex business problems generally meet the administrative duties test (29 CFR 541.402). A "business analyst" who mostly compiles reports to a fixed template is closer to the routine work the regulation excludes from discretion (29 CFR 541.202(e)).
Pay. Post the approved range; see pay transparency laws by state. BLS has no business analyst profile. The closest Occupational Outlook Handbook entries are management analysts for process seats and computer systems analysts for IT seats (management analysts last modified August 27, 2026). Neither matches exactly, so this page does not quote figures. Close with your EEO statement and an accommodation contact.
From must-haves to screening questions and scorecard rows
| Must-have | Screening question | Scorecard competency | Evidence of a strong answer |
|---|---|---|---|
| Requirements that were built | "Pick one requirement you wrote that turned out to be wrong or incomplete. How did you find out?" | Requirements quality | Specific gap, how it surfaced in build or test, and what they now do differently |
| Stakeholder disagreement | "Two departments wanted opposite things from the same system. What did you do?" | Facilitation | Made the trade-off visible, found the decision owner, recorded the decision |
| Process mapping | "Describe a process you mapped. What was the exception that caused the most trouble?" | Analysis depth | Knows volumes and handoffs; found the exception by asking people who do the work |
| Delivery support | "What happened between handing over requirements and go-live on your last project?" | Follow-through | Answered developer questions, helped test, checked the result against the need |
| SQL (data seats) | "What was the last question you answered with your own query, and how did you check the result?" | Data self-sufficiency | Explains joins or filters in plain words and cross-checked against a known total |
The full first call is in business analyst phone screen questions, and first-quarter goals for the hire are in the 30-60-90 day plan for business analysts. If the person will decide what gets built, compare the product manager job description template; if the work is mostly dashboards and analysis, the data analyst job description template fits better.
Common mistakes in business analyst job descriptions
Three jobs in one posting
Business analyst, project manager and scrum master in a single role usually means none of them gets done well. If the role truly combines them, say how the week splits.
Tool lists instead of deliverables
Naming every diagramming, ticketing and documentation tool says little. Name what the analyst produces and who uses it; tools are learned in a week.
Unclear decision rights
"Own requirements" means different things when there is a product owner and when there is not. Say who prioritizes and who signs off.
"Excellent communication skills"
Every candidate claims it. Replace it with the situation: "run workshops with warehouse supervisors and finance leaders, who often disagree."
Domain experience as a hard filter
Requiring years in your exact industry rules out analysts who learn domains quickly. Make domain knowledge a nice-to-have unless regulation or complexity truly demands it.
Before you publish
- The kind of analysis, the system or process in scope and the current project are named.
- Decision rights and the analyst's partners are clear.
- Deliverables are listed; tools are in the nice-to-haves.
- IIBA certifications match the level and are preferred, not required.
- Classification is reviewed, and an approved pay range, the EEO statement and an accommodation contact close the posting.
Questions people ask
Should a business analyst job description require the CBAP?
Usually not. IIBA's CBAP requires five or more years of business analysis work in the last ten years (7,500 hours) plus 35 hours of professional development, so it marks experienced analysts but does not cover everyone who can do the work. List CBAP or CCBA as preferred and screen for the requirements and process work itself.
What is the difference between a business analyst and a product manager posting?
A business analyst works out what a process or system needs to do and documents it so it can be built or changed correctly. A product manager decides what to build and why, and owns the outcome. In agile teams the lines blur, so say who prioritizes the backlog and who signs off on requirements.
Does a business analyst need to know SQL?
Only if the seat needs it. Data-focused business analysts query databases daily, while process and systems analysts may never write a query. Require SQL when the person will pull their own data; otherwise list it as a nice-to-have so you do not lose strong requirements analysts.
Is a business analyst exempt from overtime?
Often, but the title does not decide it. Business analysts are usually reviewed under the administrative exemption, which requires at least $684 a week and discretion and independent judgment on matters of significance. The computer-employee rules note that systems analysts who plan and coordinate system development generally meet the administrative duties test. Review the actual duties.