How to write a business analyst resume

Layout: put a requirement and a go-live in the first scan

One page. BA postings at banks and IT services firms draw high volumes, and the first pass stops at the top half. Use the standard headings: Summary, Experience, Skills, Certifications, Education. Parsers cut the document into sections on those words, and anything under an invented heading lands in an unlabelled bucket.

Write each role by project or system, not by duty. Three systems under one title means three groups of bullets, each stating which stretch was yours: requirements, process, testing, or the change management after launch.

1. 1
   Summary

   Three lines: years and domain (core banking, payments, claims), one requirement-level or process-level result, and where you are heading. The reader decides here whether to continue.

2. 2
   Experience

   Reverse chronological. Each bullet names one deliverable and what became of it: the share of requirements that passed UAT, the steps a process lost, the change requests raised after launch. Describe systems by function, never by internal code name.

3. 3
   Skills

   Four groups: requirements and process methods, testing and delivery, tools, domain. List only items you can answer “what did you do with it” about.

4. 4
   Certifications

   CBAP, PSM, ECBA on one line each. A certification is a keyword match, not evidence. The evidence sits in the bullets above it.

5. 5
   Education

   Degree and major on one line. Within three years of graduating, keep one project bullet if it involved a process or a system; drop it after that.

Summary examples by level

A summary says three things: which kind of system you write requirements for, the largest thing you delivered that stayed delivered, and where you want to go next. Three lines.

Bullet examples by competency

Interviewers at banks and IT services firms look for five kinds of evidence on a BA resume. Each example is a complete line: verb first, a named deliverable, what became of it, and [N] where a figure belongs.

Weak lines, rewritten

Each pair names the defect first. The pattern behind all five: weak lines prove you were present, strong lines name a deliverable and what became of it.

Skills: what stays, what goes

Every item must answer “what did you do with it”. A BA’s skills section is a question bank for the interviewer, not a column of adjectives.

ATS keywords, spelled the way the posting spells them

BA postings at banks and IT services firms use a fixed vocabulary, listed below by category. Use the terms inside bullets, match the posting’s spelling, and give the full name the first time an acronym appears.

Only use terms your experience can carry. Every keyword is a door the interviewer can walk through: write “traceability matrix” and you must be able to say how many requirements it linked and which missed test it caught. A term you cannot answer for is safer deleted than kept.

The proof that is not on the resume

Nearly everything you produce stays behind a client login. The little you can hand a reader has to be exactly right, and the rest has to be pointed at rather than sent.

• There is no repository to open

  An engineer’s resume gets read with a second tab open on GitHub. Yours has no equivalent: the BRD sits on the client’s Confluence, the process model in a bank’s file store, the UAT results behind a VPN. Three things actually get opened — your LinkedIn profile, the register of whichever body certified you, and, much later, the referee you name. Write for those three doors instead of padding the header with a fourth link.

• Spell the certification the way the issuing body spells it, and date it

  One per line: “CBAP, IIBA — certified [Month Year]”, “PSM I, Scrum.org — [Month Year]”. That spelling is what the register returns and what a recruiter searches for. Renewal differs by body: PSM does not expire, while PMI credentials and CBAP run on recertification cycles. An undated credential reads as current whether it is or not, and this is a field that gets checked before an offer.

• Write the stage you have actually reached

  Booking an exam is not holding a credential. “ECBA, IIBA — exam scheduled [Month Year]” is honest. “CBAP (in progress)” after a two-day course is not: the CBAP application itself requires documented practice hours, so the phrase invites the question of how many you have logged and whether they were accepted. If the application has been accepted, write that. If all you have is the course, it is training — it belongs under Education, not Certifications.

• The register entry is the only claim a stranger can settle alone

  IIBA, PMI and Scrum.org each publish a way to confirm that someone holds what they say they hold. Everything else — [N] requirements, [N]% churn, the day a release went live — rests on documents you cannot send. So the entry has to match: the name it was issued under, the credential as written, the date. When a profile says CBAP and the register says CCBA, the reader stops believing the numbers, and the numbers were the resume.

• Rebuild the work sample from a process anyone can watch

  Asked to see a BRD, you cannot send the bank’s. Write a fresh one. Pick a process the public can observe — the account-opening steps a bank publishes, a parcel-tracking flow, a government online application — and produce the as-is model, [N] business rules, and acceptance criteria for a single story. Two pages, your own words, nothing confidential inside them. Then one header line: “Writing sample: as-is model and acceptance criteria for a public [service] — [link]”.

• Redacting a client document does not make it yours to send

  A BRD with the client name blacked out is still the client’s BRD, and sending it settles their confidentiality on their behalf. What you can take with you is a person. The product owner who signed your UAT plan and the delivery manager who chaired the board with you both watched the work and can describe it. Ask them first, then write “References: product owner and delivery lead from the [core-banking] programme, available on request”. Someone willing to confirm a go-live beats a file you were never allowed to attach.

• Leave the link off when there is nothing behind it

  A GitHub URL in a BA header holding two SQL snippets and a forked tutorial is worse than a blank field: it answers a question the posting did not ask and invites a side-by-side with data analysts. A personal site whose portfolio page says “coming soon” does the same. Email, location, a LinkedIn URL that resolves. Add the fourth line once the thing behind it is finished.

Common business analyst resume mistakes

1. 1
   Counting documents as results

   “Wrote [N] BRDs” proves you can type. The reader wants to know what happened to those requirements: how many passed UAT, how many came back, how many change requests followed go-live.

2. 2
   Describing a whole programme with “participated”

   A core-system replacement runs to hundreds of people. “Participated in the implementation” leaves the reader unable to tell whether you wrote the requirements or sat nearby. Write your workstream first, then the programme as context.

3. 3
   Requirements with no ending

   Every requirement has a fate: passed, changed, cut, or patched after launch. A resume that stops at “documented requirements” tells half the story. The ending is the evidence of quality.

4. 4
   Process improvements with no size

   “Improved the onboarding process” has neither direction nor magnitude. How many steps, hand-offs or days did it lose? If you have no record, go back to the process map. Do not paper over the gap with an adjective.

5. 5
   Calling systems by their internal code names

   Project Phoenix or CBS Next mean nothing outside the building. Describe the system by function: the account-opening system, a policy-administration platform. The reader gets the scale and the domain at once.

6. 6
   Listing methodology names as capabilities

   Agile, Scrum and BPMN in Skills with no bullet that uses them read like a course certificate. Each method should connect to at least one bullet about what you delivered with it.

7. 7
   Sending a data analyst resume to a BA posting

   Dashboards, SQL queries and automated reports are data analyst evidence. A BA posting wants requirements, process and UAT. One person can have done both, but the main course has to match the posting, and the other set goes on one line in Skills.

The follow-ups your resume will trigger

An interviewer reads a BA resume by picking one deliverable and asking what became of it. Every line you write should be ready for the exchange below.

FAQ

Keep reading

More Consulting resume examples

• Management Consultant