Business Analyst

You're the translator between the business and everyone building for it — turning "we need the system to be better" into requirements someone can actually build. Underrated, everywhere, and a proven bridge role into tech and product careers.

Median pay (US)

~$85k / yr

Typical range

$60k–$120k

Degree required?

Usually — but experience substitutes

What the job actually is

Business analysts figure out what an organization actually needs and specify it: interviewing stakeholders, mapping processes, writing requirements and user stories, analyzing data to size problems, and shepherding changes through delivery. You'll live in meetings, documents, spreadsheets, and increasingly SQL and BI tools. The craft is asking the question behind the request — the stated ask is almost never the real need.

Is it actually you?

You'll probably love it if

You ask "why" twice before accepting any request
You're organized enough to herd ambiguity into a document
You like being the person who understands both sides
Spreadsheets and process maps are oddly satisfying
You want a respectable path toward product management

Maybe not, if

Meetings-heavy weeks sound like punishment
You need to build the thing yourself to feel ownership
Documentation feels like busywork to you
Political navigation between departments drains you

The real day-to-day (no hype)

The title means five different jobs. Data-flavored BA, systems BA, process BA, agile BA, finance BA — read each description carefully. Salary and daily life vary widely under one name.
Influence without authority. You'll drive changes you can't mandate. Persuasion, documentation, and follow-up ARE the toolkit — if that sounds exhausting, believe it.
SQL is the separator. BAs who can pull and analyze their own data get the interesting problems and the higher band. It's the highest-ROI skill in the role.
It's a launchpad. BA → product manager, BA → data analyst, BA → program manager are all standard exits. Treat the role as both a career and a bridge.

How people break in — or switch in

Most BAs come from inside: the operations coordinator who kept fixing the process, the support lead who documented what engineering needed, the accountant who automated the reconciliation. The move is making your analysis visible — process maps, small data analyses, a requirements doc for a change you drove. An IIBA cert (ECBA/CCBA) can help with HR filters, but a portfolio of real problem-solving is the actual currency.

You've probably done BA work without the title — every process you fixed, every requirement you clarified. The switch is mostly re-labeling your evidence.

Your application, already half-written

Here's a question every Business Analyst application asks, answered the way pirch would — in a real voice, grounded in real experience:

“Describe a process you improved.”

Our returns team touched every request in three systems, and "make the software faster" was the executive ask. I shadowed the team for two days and timed the real work: 70% of handling time was re-typing order details between systems, not slowness in any of them. I wrote the requirement for a one-click order-import — two weeks of dev work instead of the six-month platform migration being discussed. Handling time dropped 40%. The lesson I carry: measure the actual workflow before believing anyone's diagnosis, including mine.

pirch's co-pilot writes answers like this for your background and the exact job — try it free →

pirch finds the analyst roles that are actually you

Tell pirch who you are — the processes you've fixed, the systems you know, the direction you're growing — and it hunts down real, still-open BA jobs that fit the whole you, with a tailored cover letter already written.

start your free hunt

first hunt free · we never auto-apply · you stay in control

Common questions

What does a business analyst actually do all day?

Meetings with stakeholders, documenting requirements and processes, analyzing data to size problems, and coordinating between business teams and builders. The mix varies by flavor — some BAs are nearly data analysts, others nearly project managers.

How much do business analysts make?

US median around $85k, ranging $60k–$120k. Technical/data-heavy BA roles and finance-sector BAs sit at the top of the band.

Business analyst vs data analyst — which should I pick?

Data analysts go deeper on SQL, statistics, and dashboards; BAs go broader on process, requirements, and stakeholders. If you love the numbers themselves, go data; if you love fixing how work works, go BA. The paths cross constantly.

Is business analyst a path to product manager?

One of the most common ones. BAs already do the requirements and stakeholder halves of PM work; adding user research, prioritization ownership, and outcome accountability completes the bridge.