Sign in with Google

Business Analyst

"Business analyst" is one title covering two genuinely different jobs, which is why the salary ranges and job descriptions you find never agree. This page separates them, gives an honest read on pay and AI exposure, and shows where the role leads.

Typical Pay (US)*

$90kmedian*
$65k*
Entry
$90k*
Median
$125k*
Senior

* AI-estimated from general U.S. labor-market patterns — not measured data from the U.S. Bureau of Labor Statistics or any official source. Real pay varies widely by location, employer, experience, and timing.

Outlook

Stable demand*High AI exposure

Growth is modest — Mochivia's dataset estimates about 3.6% annually for the nearest occupation — and the artifact-production half of the job is squarely in the automation path. Drafting user stories from a transcript, converting notes into a process diagram, writing a first-pass requirements document, and building a standard variance report are all things a model now does in seconds and reasonably well. What resists automation is what O*NET itself points at: judgment and client-facing work. Getting three departments to agree on one definition, noticing the requirement nobody stated because everyone assumed it, and carrying political weight in a prioritization argument are not documentation tasks. The analysts who stay valuable move toward owning outcomes, which is why this role is a strong stepping stone into product or program management rather than a place to sit for fifteen years.

What does a Business Analyst do?

Before anything else: business analyst names two different jobs, and figuring out which one a posting means is the single most useful thing you can do. The first is the IT or systems business analyst. This person sits between a business team and a software team, works out what the business actually needs, and writes it down precisely enough to build — user stories with acceptance criteria, process diagrams in BPMN, data-flow mappings, and the specification for how an order should move through four systems that were never designed to talk to each other. They run requirements workshops, arbitrate between people who want incompatible things, and do user acceptance testing when the build lands. Tools are Jira, Confluence, Visio or Lucidchart, and increasingly SQL.

The second is the finance or operations business analyst. This person owns reporting and analysis for a business function — building the monthly operating review in Excel, maintaining a forecast model, investigating why a distribution center's cost per unit rose, sizing the savings from a process change. Tools are Excel first, then Power BI or Tableau, then an ERP system like SAP or NetSuite. The word "analyst" is doing very different work in the two jobs: one analyzes processes and requirements, the other analyzes numbers.

Both differ from the data cluster in a way worth being precise about. A data analyst answers questions from data in a warehouse using SQL. An analytics engineer builds the modeled tables that analyst queries. A data engineer builds the pipelines that land the data. A business analyst mostly works on process, requirements, and decisions — the data stack is something they consume occasionally, not something they own. When a company says "business systems analyst," they usually mean the first job with more technical depth.

O*NET 28.3 splits this across two occupations rather than one: 13-1111 Management Analysts, which lists "Business Analyst" as an alias and carries an estimated median near $99,000 with about 3.6% estimated annual growth, and 15-1211 Computer Systems Analysts, median near $103,000, which lists "Business Systems Analyst" as an alias. The federal assessment of the first is that judgment and client-facing work limit automation despite the analytic core — a fair description of where the durable value sits. The role suits people who are good with ambiguity and better with people than most technical staff, and it is one of the most reliable first rungs into product management, program management, or data work. It does not suit people who want to build things themselves; you will specify far more than you construct.

A day in the life

  • Run a 90-minute requirements workshop with operations and finance, and leave with a process map neither side had seen written down
  • Turn that map into eight user stories with acceptance criteria in Jira, then defend the edge cases in backlog refinement
  • Discover mid-sprint that two stakeholders defined "cancelled order" differently and get a written decision from whoever owns it
  • Rebuild a monthly operating report in Excel because a source system changed its export column order again
  • Write the current-state versus future-state comparison for a system migration, including the manual steps that quietly disappear
  • Run user acceptance testing on a release, log four defects, and negotiate which are launch blockers
  • Draft a one-page business case with cost, benefit, and assumptions for a process change that saves 20 hours a month

How to become a Business Analyst

  1. 1

    Decide which business analyst job you want

    ~2 weeks

    The IT and systems path leads toward product and technical program management; the finance and operations path leads toward FP&A and strategy. The skills only partly overlap, so choose before you invest.

  2. 2

    Learn requirements and process modeling

    ~2 months

    User stories with acceptance criteria, BPMN process diagrams, current-state versus future-state analysis, and elicitation techniques. The BABOK guide is the standard reference for the vocabulary employers use.

  3. 3

    Get seriously good at Excel, then add SQL

    ~3 months

    Pivot tables, lookups, and model structure carry the finance path entirely. SQL has become close to mandatory on the systems path because waiting on an analyst for every question makes you slow.

  4. 4

    Learn the delivery tooling and one BI tool

    ~1 month

    Jira and Confluence for how work actually moves, plus Power BI or Tableau for reporting. These appear in nearly every posting and are quick to become credible in.

  5. 5

    Enter sideways from a domain seat

    ~6 months

    Operations, customer support, finance, or implementation roles convert into business analysis extremely reliably, because domain knowledge is the part employers cannot train quickly. No degree is a hard gate.

  6. 6

    Add a certification only if your market rewards it

    ~4 months

    CBAP or PMI-PBA genuinely help in consulting, government, healthcare, and large enterprises where credentials gate interviews. At technology companies they carry almost no weight — skip them there.

Skills that matter

Requirements elicitation and stakeholder interviewingUser stories with testable acceptance criteriaProcess modeling in BPMN (Visio, Lucidchart, or Miro)Excel modeling: pivot tables, lookups, scenario structureSQL for self-service data pullsPower BI or Tableau reportingJira and Confluence workflow fluencyGap analysis and current-state versus future-state documentationUser acceptance testing and defect triageBusiness case writing with cost, benefit, and assumptionsFacilitation — running a workshop that produces a decisionDomain fluency in one function (finance, supply chain, healthcare, insurance)

Learn the actual skills

Tell Mochivia your goal and it builds your personal curriculum — 15 minutes a day.

Build My Path

Frequently asked questions

What does a business analyst do?
It depends which of two jobs the title means. An IT or systems business analyst sits between a business team and a software team: eliciting requirements, writing user stories with acceptance criteria, mapping processes, and running user acceptance testing. A finance or operations business analyst owns reporting and analysis for a function — operating reviews, forecast models, cost investigations, and business cases. Both roles center on turning an unclear business situation into a documented, decidable one.
How much do business analysts make?
In the United States, business analysts typically earn around $65,000 at entry level, about $90,000 at mid-level, and roughly $125,000 in senior positions. These are AI-estimated figures rather than measured Bureau of Labor Statistics data. For reference, O*NET carries an estimated median near $99,000 for 13-1111 Management Analysts and near $103,000 for 15-1211 Computer Systems Analysts, both of which list business analyst variants as aliases. Technical and systems-focused roles pay above operations-reporting ones.
Do you need a degree or a certification to be a business analyst?
A degree is not a hard gate, and this is one of the more accessible professional roles for career changers, especially from operations, support, finance, or implementation work where you already know a domain. Certifications are genuinely market-dependent: CBAP and PMI-PBA carry real weight in consulting, government, healthcare, and large enterprises where credentials filter applications, and almost none at technology companies. Check job postings in your target industry before paying for one.
Will AI replace business analysts?
It is taking a substantial bite out of the documentation half of the job. Producing user stories from a meeting transcript, converting notes into a process diagram, drafting a requirements document, and generating a standard variance report are all fast and reasonably good with current models. What does not automate is the part O*NET credits for limiting exposure: judgment and client-facing work. Getting three departments to agree on one definition, surfacing the requirement nobody stated, and holding weight in a prioritization argument remain human work.
Is business analyst a good career in 2026?
It is a good entry and transition role rather than a strong long-term destination. Projected growth is modest at roughly 3.6% annually, and the artifact-production side of the work is among the more automatable analytic jobs. Its real value is positional: it teaches you a business domain, gets you into rooms where decisions happen, and converts unusually well into product management, technical program management, or data roles. Treat it as a launchpad and plan the next move deliberately.
What is the difference between a business analyst and a data analyst?
A data analyst answers quantitative questions from data in a warehouse, working primarily in SQL and a BI tool, and is measured on the accuracy and usefulness of the answer. A business analyst works on processes, requirements, and decisions, and is measured on whether the resulting change worked. Data analysts own the data stack as their medium; business analysts consume it occasionally. Data analysis typically pays slightly less at entry and slightly more at senior levels, and is the more technical of the two.

Related careers

Data Analyst
Data analysts turn vague business questions into answers other people act on. This page covers what the job actually involves, what it pays, how it differs from analytics engineering and data science, and the honest picture of which parts of it AI already does well.
Product Manager
Product manager is one of the most searched and least clearly explained job titles in tech, partly because four different jobs share nearly the same name. This page separates them, explains what the work actually consists of, and is honest about how hard the role is to enter directly.
Financial Analyst
Financial analyst is a large, established profession where — unlike most tech-adjacent roles — the credential genuinely gates entry. This page explains what the work is, how the four main variants differ, what the CFA actually does for you, and which parts of the job automation is already absorbing.
Technical Program Manager
Technical program manager is one of the best-paid roles most engineers cannot describe. This page covers what a TPM actually owns, how the job differs from product and project management, what it pays, and the two realistic paths in.
Revenue Operations Manager
Revenue operations is one of the fastest-growing functions in go-to-market organisations and one of the worst-explained job titles anywhere. This page defines what RevOps actually owns, why it exists at all, what it pays, and the two routes people realistically take into it.

Sources