Business Analyst CV in 2026: IT, Product or Process

Half my friends with 'Business Analyst' on LinkedIn are quietly retraining as Product Managers. The other half are pretending Analytics Engineer is the same job. Meanwhile recruiters open ten BA CVs and see ten different professions glued under one title. If your CV does not tell the reader in five seconds which kind of BA you are, the rest of it does not matter.

I get pinged at least once a week by a BA friend asking 'слухай, мені вже перевчатись на продакта чи ще можна виживати'. Short answer: ще можна. Long answer is this post.

BA is not one job in 2026, it is three

When a recruiter sees 'Business Analyst' they mentally try to fit you into one of three boxes: IT BA, Product BA, or Process BA. These are different careers with different daily work, different tools, different salary bands. If your CV reads like all three at once, it reads like none of them.

• IT BA: works between business and a dev team, owns BRDs, FRDs, user stories, lives in Jira and Confluence. The classic outsourcing BA role.
• Product BA: closer to a junior PM, owns discovery, runs interviews, writes specs, sometimes owns metrics for a feature. Often a stepping stone into PM.
• Process BA: lives in BPMN, AS-IS / TO-BE, owns the operational redesign of finance, logistics, support. The role consultancies hire for.

Pick one. Yes, you have done all three. Write the CV for the one you want next. Mention the other two in past roles, but the headline, the summary, and the first three bullets of your latest role all serve one box.

The BA-vs-PM-vs-Analytics-Engineer confusion

Here is the honest map of where each role eats BA territory in 2026. Product Managers took the 'owns the outcome' bullets. Analytics Engineers took the 'owns the data model' bullets. Designers running discovery took the 'runs user interviews' bullets. What is left for BA, and what is not, depends entirely on company size.

• Startups under 30 people: roles blur, one person wears all three hats, BA title is rare
• Scale-ups 30-300: BA + PM split is real, BA owns spec and handoff, PM owns roadmap
• Enterprise and outsourcing: IT BA role is alive, well paid and not going anywhere
• Consultancies (Big 4, boutique): Process BA dominates, BPMN and operating model work pays the most

If you are reading this thinking 'I should retrain as a PM', remember: good Senior BAs out-earn average mid PMs in 2026, especially in consultancies and regulated industries. The grass is not greener, it is just differently shaped.

The bullet shape that actually works

BA CVs die on one specific pattern: bullets that describe artefacts you produced, not decisions the business made because of you. 'Wrote BRD for the billing module' is invisible. 'Wrote BRD for the billing module that unblocked a 4-month-stuck integration with the payment provider and shipped on time' is the same work, but a recruiter can finally see why it mattered.

The shape is simple: what you produced + what changed in the business because of it + the number or the time saved. Three parts. The third one is where 80% of BA CVs fail.

• Bad: 'Gathered requirements from stakeholders for the new CRM'
• Better: 'Ran 40+ stakeholder interviews, consolidated requirements for CRM rebuild'
• Good: 'Ran 40+ stakeholder interviews and cut the CRM rebuild scope by 30%, which saved one quarter of dev time'
• Strong: 'Mapped AS-IS / TO-BE in BPMN for logistics, surfaced 7 inefficiencies and saved $18k a year in carrier costs'

SQL, Tableau, Power BI: be honest about your level

Every BA CV says 'SQL (intermediate), Tableau, Power BI'. Recruiters stopped believing that line in 2023. The fix is small and a little scary: add a concrete artefact next to each tool. 'SQL: wrote and maintained 40+ reports in Metabase' is verifiable. 'SQL (intermediate)' is not.

If your SQL is really 'I can edit a SELECT someone else wrote', say that differently: 'SQL: comfortable reading and modifying queries written by analysts'. Recruiters respect the honesty and the interviewer will not catch you out in round one. The fastest way to fail a BA interview in 2026 is to oversell SQL and then crash on a JOIN with two tables.

• Tableau / Power BI: name the actual dashboards you owned and who used them
• SQL: pair the level with a real artefact (number of reports, complexity of queries)
• Python: only put it if you actually used it for analysis, not because you finished a Coursera course
• LLM / AI tools: add the ones you use in daily work, with the use case (ChatGPT for spec drafting, Claude for SQL pair-work)

Killing the 'JIRA ceremony only' stereotype

There is a stereotype in tech, and it hurts BA hiring: 'BA just runs grooming sessions and writes tickets nobody reads'. Hiring managers carry that bias into your CV. The way to break it is to bury the ceremony work and lead with the strategic work. Even if 60% of your day is Jira hygiene, that is not what should open your bullets.

Lead with: gap analysis you ran, migration roadmaps you authored, integration scopes you negotiated, post-launch metrics you tracked. Bury, do not delete: 'maintained Confluence space', 'ran daily standups', 'kept Jira tickets up to date'. These are real work but they read as junior signals when they are at the top.

The requirements-gathering line that gets filtered

'Gathered and analyzed requirements from stakeholders' appears in roughly every second BA CV. It tells the recruiter nothing. Who were the stakeholders, how many, on what scope, what came out of it, what changed? Without those answers it is a placeholder bullet, and a recruiter doing a 6-second skim does not stop on placeholders.

Compare these two: 'Gathered requirements for new feature' vs 'Ran discovery with 12 stakeholders across sales, ops and finance for a quoting tool that replaced 4 spreadsheets and shaved 6 hours per week from the sales team'. Same work. One filters out, one books a screening call.

Positioning your summary in 3 sentences

Your summary line is the first thing a recruiter reads, and it has to do three jobs: which BA box you are in, what industry depth you bring, what kind of outcome you produce. Three sentences max. If you cannot do it in three, your positioning is not clear enough.

• IT BA: 'IT Business Analyst with 5 years building BRDs and FRDs for fintech web platforms. Handed off 12+ modules to dev teams without scope reopens. Last project cut delivery time by 25%.'
• Product BA: 'Product BA at a B2B SaaS, owning discovery and spec for the onboarding squad. Shipped 8 features last year, activation up from 34% to 51%.'
• Process BA: 'Process Analyst with consulting background, BPMN-fluent. Redesigned operating models for 3 logistics clients, average $40k annual cost savings per engagement.'

What to actually do this week

1. 1Pick one BA box (IT, Product or Process) and rewrite your headline and summary for it
2. 2Rewrite your top 3 bullets in the 'artefact + business change + number' shape
3. 3Add real artefacts next to SQL, Tableau and Power BI in your skills section
4. 4Move ceremony work (Jira hygiene, standups, Confluence upkeep) to the bottom of each role
5. 5Apply to 5 jobs in your chosen box, save them in Trackr, see what gets replies