Business Analyst resume examples

Harish has 5 years of BA work, so his first bullet names the product, the team and the document he wrote: user stories and acceptance criteria for a 9-person Scrum team building carrier load tendering. A hiring manager sees the kind of software and the size of the backlog before reading anything else.

His strongest bullet pairs a BPMN process map with the number it moved, as truck wait fell from 52 to 31 minutes after the release. His earlier payments role uses SQL to confirm that migrated fee tables matched the source system, which is validation work, not reporting. The CCBA sits at the bottom with the issuer and year, and his hours clear its 3,750-hour rule.

Find the example closest to your level first, then the one closest to your platform or industry. The industry and platform examples name a system or business area in the headline. The entry-level and career change examples show analysis done under other job titles.

Use the ad's exact words for the platform, the business area, the documents you produce and the method, then put each where a reader checks for it. Ads for this job repeat a short list: elicitation, user stories, acceptance criteria, BPMN, UAT, SQL and Jira, plus a platform such as Salesforce CPQ or Workday.

Copy the ad's spelling. If it says 'acceptance criteria', don't shorten it to 'AC', and write out 'Business Process Model and Notation (BPMN)' once if the ad does. Put a platform keyword in a bullet with a number as well as in your skills list, because a skills list alone doesn't show how long or how deeply you used it.

Write each bullet so it names the system or process, the people who agreed to it, the document you produced and what changed after release. Every analyst gathers requirements, so that phrase alone tells a hiring manager nothing about your work.

For requirements, give the artifact and its size: 22 user stories, 85 business rules, a 140-field interface spec. Then say who signed off, such as credit, compliance or the product owner.

For process maps, say whether you mapped the current (AS-IS) or future (TO-BE) process, how many handoffs or units it covered, and which measure moved afterward: wait time, days to a loan decision, or orders re-keyed by hand.

For UAT, count the scripts or scenarios, the testers you coordinated and the defects you found before release. If you left before release or never saw the numbers, end the bullet with who used your work instead, as in 'replacing a spreadsheet queue used by 22 dispute agents.'

List a business analysis credential only after you've passed it, and check its experience rule against your work history first. Employers that mention CBAP, CCBA or PMI-PBA often list them as preferred, not required.

Write the full name with the acronym in parentheses, then the issuer and year: 'Certification of Capability in Business Analysis (CCBA), IIBA, 2024.' If an ad names one you hold, repeat the acronym in your summary, as the Salesforce example does with PMI-PBA.

The IIBA hours must be business analysis work, so a career changer with years in operations usually starts with the ECBA, which has no experience requirement.

Put 'Business Analyst' as your resume title, keep your real job titles in the experience section, and make your bullets show the BA work you've already done. Never rename a past job to Business Analyst. Keep the title your employer used.

Start with work that matches BA artifacts. An operations associate who wrote up process gaps, mapped an intake process or ran UAT scripts has done analysis. Say how many gaps, which process and how many scripts, as the entry-level example does with 6 gaps and 35-script UAT cycles.

Use your domain as the selling point. Years of school attendance coding, claims intake rules or deposit operations mean you know the people and exceptions a new system has to handle. Name that domain in your summary, then show one bullet where your knowledge became a requirement or a procedure.

If you've worked on a system project as a project analyst, super user or tester, list it as its own role with dates, or as a dated bullet if it ran alongside your main job. The career change example lists 10 months on a student information system migration as its own role above 8 years of data coordination.

Add the ECBA if you have no logged BA hours. List SQL, Visio or Jira in your skills only when a bullet above shows you using them.

Count any role where you elicited needs, wrote requirements or specs, mapped processes or tested system changes, whatever the title said. Systems analyst, business process analyst, IT business analyst and operations analyst all appear in ads for the same work.

In your summary, total the years across those titles, as in '9 years of business analysis as a systems analyst and IT business analyst.' Then make the first bullet under each title name the kind of analysis, so a reader doesn't have to guess from the title.