A business analyst resume should explain the problem, the analysis you contributed and how the work was used. Requirements gathering and documentation are legitimate responsibilities. Make them specific: which process, which questions, which decisions and which stakeholders?

This guide uses a fictional resume and editorial skill prompts. It does not present a measured survey of job postings or promise callbacks. Use the vacancy to decide whether requirements work, process analysis, data tools or another part of your experience deserves the most space.

Choose sections that help a reader understand your relevant work. A summary and separate projects section are optional. The following order is a starting point, not a requirement for every BA role.

Choose length by relevant evidence and application instructions, not a seven-year threshold. Avoid padding; a second page can be useful when it adds distinct, relevant experience. See page-length guidance.

Use clear headings and selectable text. Inspect the exported reading order and the fields populated by the application system. Neither one column, two columns nor PDF guarantees correct parsing, and there is no universal seven-second screening rule.

Fictional example: Jamal Whitaker, Cedar Logistics, Juniper Financial, Alder Retail, Riverbend College, projects, training and recognition below are invented. Contacts are placeholders. The dates show analysis work since 2019. No actual recovered revenue, audited productivity gain or IIBA credential is claimed. Replace every entry and skill rating with your own evidence.

These are possible business-analysis terms, not universal requirements or a frequency ranking. Use the tools and methods that match both the vacancy and your actual work.

A relevant tool can appear in a skills list, with a work example where space allows. Do not invent a result for every term. A keyword comparison can highlight wording differences; it cannot reveal an employer’s private screening rules. See keyword guidance.

The example links tasks to concrete work: source-to-target checks, report definitions, workshop decisions and UAT tracking. It separates preparing evidence from approving a release. Grouping tools can help scanning, but no exact grouping or opening verb determines whether a resume succeeds.

A senior role may involve broader ambiguity, analysis standards, mentoring or decisions across several teams. Demonstrate the responsibilities you actually held. A senior BA does not universally own a budget, present to a VP or manage other analysts.

Consider these forms of evidence where they apply:

Use enough space to explain relevant scope without repeating similar duties. Older work can be compressed; it need not be forced onto a particular page. See experience-history guidance.

BA roles vary. A process-focused vacancy may emphasize workshops and operating models; another may require SQL and reporting. Technical and interpersonal capabilities can both be selection criteria. There is no evidence here for ranking SQL as the most demanded tool or treating communication as merely a tiebreaker.

The table gives ways to describe experience, not market-frequency findings.

Use both a readable skills list and concrete examples where useful. “Facilitated a review between operations and compliance to record conflicting requirements and unresolved decisions” explains the interaction without inventing a perfect resolution. See hard and soft skills guidance.

Use recognizable terminology where it accurately describes your work. User acceptance testing is more specific than “final-stage validation” when that is what you coordinated. ATS and recruiter workflows vary and may use more than literal word matches.

Consider the terms below only when supported; they are not a checklist that every candidate must satisfy.

Read the specific vacancy rather than assuming every bank or product team has the same needs. A wording gap may be a missing explanation or a real experience gap. Do not resolve the latter by adding a skill you lack. A concise skills list is acceptable; repeated keyword stuffing adds little. See ATS keyword guidance.

For each relevant tool, explain the actual task and your level of responsibility. You do not need a public artifact for every skill, and proprietary data or workbooks should not be shared to prove a claim.

Fictional SQL example: “Wrote read-only queries to compare source and target order totals and investigated exceptions with the migration team.” Explain joins, validation or reconciliation only if you used them. Do not imply unrestricted production access, database administration or ownership of a fix from running a query.

A discrepancy identified is not automatically revenue recovered. If you cite recovered money, distinguish a potential exposure, a corrected invoice and actual collected revenue, with permitted evidence and appropriate team attribution.

A useful dashboard example names its audience, definitions and use. Fictional example: “Built a Tableau view of fulfillment exceptions and reviewed metric definitions with operations before release.” Building a dashboard is valid work even without proving that it caused a vendor decision.

List Tableau and Power BI separately according to actual experience. Similar concepts do not make the tools interchangeable qualifications. A dashboard is not “live” unless its refresh behavior supports that description.

Describe the Excel work you actually did: Power Query transformations, a reconciliation workbook, pivot analysis or a forecasting model. “Advanced” is ambiguous, but a simple skills entry is not worthless. Use a specific example when it strengthens the application, and do not claim ownership of the entire financial model if you maintained one input.

If reporting effort fell from six hours to one, that is about an 83% reduction, not 90%. Label estimates, include the measurement period and account for recurring maintenance where relevant.

An optional summary can state your domain and the kind of analysis you perform. Fictional example: “Business analyst working on order-management and reporting processes. Translates workshop decisions into requirements and acceptance criteria, and uses SQL reconciliation to investigate migration exceptions.”

Add a measured result only if supported. A summary need not fit a rigid three-line formula or claim a financial outcome. A short target statement can help a career transition when it adds context. See summary guidance.

A project example can show context, contribution and how the work was used. Ongoing operational analysis is also legitimate BA experience; not every role needs to read as a series of projects.

Fictional example: “Documented returns-workflow requirements, recorded open questions from store users and coordinated UAT findings for the product team’s release decision.” UAT coordination is distinct from formal acceptance or release approval. A lack of detected critical defects is not proof of defect-free software.

Use a separate Projects section for relevant coursework or independent work and label it accurately. A public portfolio is optional; use synthetic data and approved material. Choose bullet count by the evidence rather than forcing three to five. See bullet-selection guidance.

Before accepting an AI rewrite, supply the facts it needs: process, stakeholders, deliverable, decision authority and any supported result. For “supported a migration,” explain whether you wrote reconciliation queries, maintained requirements or coordinated test findings.

Check the proposed text for invented money, scale, authority or tools. AI suggestions and match assessments do not verify your work history or predict an employer’s decision. Use Roleframe to organize the resume, then review the wording yourself.

Put the most relevant evidence early. Career stage can influence section order, but there is no automatic switch after two years or after a first project ships.

List an earned credential with its exact name, issuer and current status. Training or exam preparation belongs under professional development until the qualification is earned. IIBA’s current certification handbooks explain the different requirements for ECBA, CCBA and CBAP; they are not interchangeable and a certificate does not replace work history.

Place a required credential prominently if you hold it. A credential is not required for every BA vacancy. See section-order guidance.

Start with an accurate base record, select the most relevant examples and compare them with each vacancy. Tailoring means emphasis and clearer explanation, not invented domain experience. See tailoring guidance.

Follow the employer’s accepted formats. Check the export, links, reading order and populated application fields. PDF does not render or parse perfectly in every environment, and a keyword score cannot guarantee a callback.