Business Analyst Job Description Template (2026)

A ready-to-edit template, what business analysts actually produce, U.S. pay data and first-round questions that test real analysis.

This business analyst job description template is yours to copy and change for free. It spells out real deliverables (requirements, process maps, user stories, test plans) instead of vague "liaison" language. Below the template you'll also find how the role works in practice, U.S. pay data from O*NET, sample interview questions and tips for writing the post.

Business analyst job description template

Job title: Business Analyst [or Business Systems Analyst / IT Business Analyst]

Location: [City, State / Remote / Hybrid, X days a week in office]

Reports to: [Business Analysis Manager / Director of IT / Head of Product or Operations]

About [Company]

[One or two sentences about your company and mission.]

About the role

We need a business analyst to turn business problems into clear, buildable requirements. You'll work with [finance / operations / customer service] teams and our [engineering / IT / vendor] partners on projects like [replacing our billing system / automating order intake / rolling out a new CRM]. In your first 90 days, you'll map one core process end to end, write the requirements for its first improvement, and help test it before launch.

What you'll do

  • Interview users and watch the work being done to understand current processes, pain points and workarounds.
  • Map current and future processes in [Visio / Lucidchart / Miro], using BPMN or swimlane diagrams.
  • Write requirements as user stories with acceptance criteria in [Jira / Azure DevOps], ready for engineering to estimate.
  • Keep a requirements log that traces each requirement to a business goal and a test case.
  • Run working sessions where stakeholders agree on priorities and trade-offs, and record the decisions.
  • Pull and check data with [SQL / Excel] to size a problem and measure whether a change worked.
  • Plan and run user acceptance testing (UAT), track defects, and confirm fixes with users.
  • Write training notes and process documents so the change holds after launch.

What you'll bring

  • [2+] years as a business analyst, business systems analyst or in a similar requirements role.
  • Experience writing user stories and acceptance criteria that engineers could build from without guessing.
  • Process mapping skills, with examples you can walk us through.
  • Strong Excel or Google Sheets skills, and enough SQL to run basic queries with joins and filters.
  • Experience running or supporting UAT on at least one system launch.
  • Clear writing and the habit of asking "why" until you reach the real need.

Nice to have

  • IIBA certification (ECBA, CCBA or CBAP) or a similar credential.
  • Experience with [Salesforce, NetSuite, SAP, Workday or the systems we use].
  • Knowledge of [our industry, e.g. insurance, healthcare, banking, logistics] processes and rules.
  • Experience in Agile teams, including backlog refinement and sprint reviews.

Pay and benefits

[Salary range, e.g. $X to $Y per year, based on experience and location]. [Bonus, if any.] [Health, dental and vision coverage, retirement plan with match, paid time off, training budget.]

How we hire

Our hiring process is the same for every candidate. It starts with a [30]-minute structured interview on requirements, process analysis and stakeholder work. Next is a short exercise: we share a one-page process description and ask you to list the questions you'd ask and draft three user stories, live in [45] minutes or as a take-home capped at [90] minutes. Last, you meet [the hiring manager and an engineering partner]. Expect a decision within [10] business days.

What a business analyst does

A business analyst figures out what a team really needs before money gets spent building it. That means a lot of listening, then a lot of writing. A typical week includes interviews with users, a process map that shows where work gets stuck, a batch of user stories for the next sprint, and a meeting where two departments argue about priorities and the analyst writes down what they agreed. O*NET's tasks for the related occupation follow the same arc: gather information on problems and procedures, interview staff and observe the work, analyze what's found, and document recommendations.

Business analysts sit between the people who run the business and the people who build or buy systems. They work closely with product managers, project managers, engineers and testers. A good one saves engineering weeks by catching a missing requirement on paper rather than in production.

At a startup, the role may blend into product or operations, with one person writing requirements, testing and training users. At a large company, especially in banking, insurance or government, business analysts usually belong to a formal practice with templates, traceability rules and sign-off steps, and they may focus on one system for years.

Skills and qualifications

SkillMust-have or nice-to-haveWhy it matters
Requirements elicitationMust-haveUsers rarely ask for what they need on the first try.
User stories and acceptance criteriaMust-haveThis is what engineering builds and tests against.
Process mappingMust-haveA clear map shows where time and errors pile up.
Excel or Google SheetsMust-haveSizing problems and checking data starts here.
Basic SQLMust-have for systems roles, nice-to-have otherwiseLets the analyst answer data questions without waiting in a queue.
FacilitationMust-haveGetting stakeholders to agree is half the job.
UAT planningMust-haveTesting with real users is where gaps finally show up.
Domain knowledgeNice-to-haveSpeeds up ramp-up in regulated or complex industries.
IIBA certificationNice-to-haveSignals shared methods, but real work samples tell you more.

Most business analysts hold a bachelor's degree. In O*NET's survey for Management Analysts, the group that includes business analysts, 57% of respondents said a bachelor's degree is required for new hires, 24% said a master's and 10% said some college. Degrees come from many fields, and no license is required.

Salary

O*NET doesn't have a separate business analyst occupation. It lists "Business Analyst" as a reported title under Management Analysts (13-1111.00), a group that also includes management consultants and organizational development consultants. Based on 2025 Bureau of Labor Statistics wage data, the U.S. median for that group is $101,860 a year ($48.97 an hour). The 10th percentile is $60,640 and the 90th percentile is $171,640.

Because consultants are in the same group, use these figures as a broad benchmark. Pay for systems-focused analysts in your market may differ, so check your state on O*NET's local wage page. Publish the range you land on: a growing number of states and cities require pay ranges in job posts, and candidates expect one.

Interview questions for business analyst candidates

  • "A manager asks for a new report with 40 columns. What do you do before building anything?" Strong candidates ask what decision the report supports, who uses it and how often, and often find a smaller answer that solves the real problem.
  • "Write an acceptance criterion for 'users can reset their password.'" Good answers are testable and cover the edges: expired links, wrong email, repeated attempts.
  • "Two departments want opposite changes to the same process. How do you handle it?" Listen for bringing both sides together, tying each request to a business goal, and getting a decision from the right owner, written down.
  • "Tell me about a requirement you missed. What happened?" The best answers own the miss, explain how it was caught and what they changed in their process afterward.
  • "How would you check if a new process actually worked?" Look for a baseline measured before launch, a clear metric and a follow-up date.

See all our business analyst interview questions for 20+ questions, model answers, red flags and a rubric.

Writing tips for this role

  • Say which kind of BA you mean. "Business analyst" covers requirements analysts, systems analysts, process analysts and some reporting jobs. Name the main output in the first lines.
  • Don't list SQL, Python and Tableau if the role writes requirements. If the job is really reporting, our data analyst template is a better fit.
  • Name the systems involved. "Owns requirements for our Salesforce rollout" attracts analysts with the right background and lets others rule themselves out.
  • Keep certifications optional. Many strong analysts learned on the job. Treat CBAP and similar credentials as a plus.
  • Include common title variants. Candidates search for "business analyst," "business systems analyst" and "IT business analyst." Use the most common one as the title and mention the others.

Screening business analyst candidates with AI

Business analysis is mostly about asking good follow-up questions, so a first round with fixed prompts misses a lot. NTRVSTA runs a live AI interview, by video avatar or audio only, that adapts its next question to each answer and raises or lowers difficulty as it goes. Its hint system shows how a candidate takes guidance, which is a daily part of a BA's work. You can customize questions per role and add your own requirements scenarios.

Before the interview, AI resume scoring ranks every applicant against your job description. Afterward, the hiring manager gets a shareable report with scores, highlights and video snippets. Read how AI interviews are scored to judge any automated score critically.

Questions

What's the difference between a business analyst and a data analyst?

A business analyst defines what a process or system should do and writes requirements for it. A data analyst answers questions with data, mostly through queries, reports and dashboards. The roles overlap when a BA sizes a problem with data, but the main output is different: requirements versus analysis.

Is a business analyst the same as a product owner?

Not quite. A product owner decides what goes into the backlog and in what order. A business analyst helps define each item in detail and checks it with users. On some Agile teams one person does both, so say in the post who makes the final priority calls.

Does a business analyst need to know SQL?

For systems and data-heavy roles, basic SQL is very useful because it lets the analyst check data without waiting for someone else. For process-focused roles it's a nice-to-have. Test only what the job uses in its first few months.

See what an adaptive AI interview looks like for an analyst role: book a 20-minute demo, or take a sample interview yourself. For more ready-to-use posts, visit our job descriptions library or the product manager template.

Sources

NTRVSTA
‍