Business Analyst resume example

• Entry level

  Junior business analyst with an information systems degree and a six-month internship in process improvement for a regional insurer. Documented 12 workflows in Visio, wrote user stories for a claims intake form, and helped test the release. Eager to develop requirements and agile skills on a cross-functional product team.

• Mid level

  Business analyst with five years in financial services. Gathers requirements from operations and compliance, writes BRDs and user stories in Jira, and supports UAT for releases serving 800 users. Cut loan processing time by 20% through a redesigned workflow, and works closely with developers to keep scope clear.

• Senior

  Senior business analyst with eleven years in healthcare and banking. Leads discovery for programs up to $3M, mentors four analysts and sets documentation standards for the practice. CBAP certified, with experience in agile and waterfall delivery, vendor selection and benefits tracking that tie each project to measured savings.

• Systems analyst

  Systems business analyst specializing in Salesforce and ERP implementations for mid-sized manufacturers. Runs current-state workshops, writes functional specs for integrations and prepares UAT scripts with the people who will live in the system. Holds the ECBA and works across finance, sales operations and IT to keep each requirement traceable from request to release.

• Agile BA

  Agile business analyst embedded in two Scrum teams at an insurer, splitting time between backlog refinement and stakeholder discovery. Writes user stories with Given/When/Then acceptance criteria, models data flows for claims integrations and joins sprint reviews to confirm features meet the original need. Often stands in for the product owner when the business lead is away.

• Graduate

  Information systems graduate with SQL, Excel and BPMN coursework and an internship mapping a hospital's patient intake process in Lucidchart. Seeking a junior business analyst role where I can write requirements, support testing and learn from senior analysts.

• Operations supervisor

  Operations supervisor with five years in a logistics center, where I documented pick-and-pack procedures and helped test a new warehouse system. Now applying for business analyst roles with a recently earned ECBA and firsthand knowledge of how users work around poor software.

• QA to BA

  QA tester with three years writing test cases from requirements, and often the person who found the gaps in them. Applying for business analyst roles to work earlier in the cycle, with daily experience in Jira, Confluence and SQL validation queries.

• Calling everything 'stakeholder management'

  Fix: Name the stakeholders and the decision you helped them make: finance, operations, a product owner or a vendor. Then state the requirement you documented and what shipped because of it.

• Skipping the documents you produced

  Fix: Hiring managers screen for BRDs, user stories, process maps, use cases and acceptance criteria. List the artifacts by name and the tools you used to produce them, such as Visio, Lucidchart or Confluence.

• Giving no sense of project size

  Fix: Add budget, team size, system count or user population to each project. A requirements effort for 40 users and one for 4,000 are very different jobs, and the resume should say which one you did.

• Confusing analysis with reporting

  Fix: If you write SQL and dashboards, say so, but keep the focus on defining the problem and the solution. BA resumes that read like data analyst resumes miss the requirement-gathering signals recruiters look for.

Match these against the job posting you are applying to: the free resume checker shows which keywords your resume is missing.

Requirements gathering

Name the groups you elicited from, the technique you used and the document that came out of it.

Process improvement

Compare the as-is and to-be process in time, steps or error count.

User stories

Mention the backlog you wrote for, the team that built from it and how acceptance was checked.

UAT

Say how many business testers you coordinated and what the testing caught before go-live.

SQL

Describe a query you wrote to confirm a requirement or size a problem before work began.

Gap analysis

Point to a system or vendor gap you found and the decision it led to, such as a configuration change or a custom build.

Business case

Show the savings or revenue you estimated and whether leadership funded the project.

CBAP / CCBA / ECBA

List the IIBA credential with its year, choosing the level that matches your experience so it reads as earned.

Agile

Make clear whether you worked inside Scrum teams or ran discovery ahead of them, since BA roles differ on this.

Domain knowledge

Name the industry and its systems, such as claims, core banking or EHR, near the top of the page.

• Elicited requirements from 5 departments for a new claims platform, producing 140 user stories that were approved in two review cycles.
• Mapped 22 as-is processes in BPMN and found 7 redundant approval steps, which removed 3 days from average order fulfillment.
• Wrote acceptance criteria and led UAT for 6 releases, catching 45 defects before production.
• Built a business case for an invoice automation tool showing $210K in annual savings, which leadership approved in one meeting.
• Facilitated weekly workshops with 12 stakeholders to resolve conflicting requirements and cut scope creep by about 30%.
• Maintained a traceability matrix across 300 requirements so auditors could link each control to a test case.
• Analyzed 18 months of ticket data in SQL to prioritize 4 product fixes, reducing repeat support contacts by 15%.
• Served as the liaison between a vendor team of 8 developers and internal operations, keeping a $1.2M implementation on schedule.
• Defined KPIs and a reporting dashboard for a call center redesign that improved first-call resolution from 68% to 79%.
• Created a requirements template adopted by 3 project teams, shortening the documentation review period from two weeks to one.

• Decide which BA the posting describes

  Business analyst can mean requirements work on IT projects, process work in operations or reporting close to data analysis. Find the verbs the posting repeats, such as elicit, map or report, and move your matching projects and documents to the top. When the posting names an industry, put yours in the summary. Check the posting's requirements against your resume

• Show a requirement that mattered

  Begin the cover letter with a case where you found the real need behind a request, for example a report request that turned into a workflow fix. Name the stakeholders, the document you produced and the outcome. Then explain how that habit fits the system or process change the company is going through. Build a business analyst cover letter

• Practice a requirements case

  BA interviews often hand you a vague request and ask what you would ask next, or have you draw a process on a whiteboard. Rehearse a short elicitation plan, a simple BPMN sketch and a story about two stakeholders who wanted opposite things and how you reached a decision. Rehearse business analyst interview cases

• Bring a redacted work sample

  A cleaned-up process map, a page of user stories or a short requirements excerpt can carry an interview further than any adjective. Remove company names, customer data and anything confidential first, and share only what a former employer would be comfortable seeing outside the building.