Examples & writing guide
Salesforce Business Analyst CV example and writing guide
Updated 31 July 2026
A strong Salesforce Business Analyst CV connects a genuine business problem with the analysis you performed, the Salesforce change you supported and the result. This guide shows how to carry that thread through your personal statement, experience and qualifications, using evidence you can defend. If your work focuses on advising clients across business problems rather than supporting Salesforce delivery, the consulting CV guide may be a better fit.
Examples by experience level
Junior Salesforce Business Analyst
TemplateNavy Atlas4 / 5
Why this works
This example turns early-career experience into credible evidence through clear project scope, traceable requirements and defensible outcome measures.
Continue writing your CVSalesforce Business Analyst
TemplateBlue Horizon3 / 5
Why this works
This example connects discovery, requirements, testing and adoption work to credible business outcomes, while keeping the candidate's Salesforce experience clear.
Continue writing your CVSenior Salesforce Business Analyst
TemplateTeal Signal2 / 5
Why this works
Shows leadership, delivery scale and measurable outcomes while connecting stakeholder needs, Salesforce changes, testing and adoption.
Continue writing your CVJunior vs senior: what changes
| Aspect | Junior | Senior |
|---|---|---|
| Personal statement | Lead with transferable analysis experience, Salesforce exposure and the types of project or process work completed. Keep the scope precise and avoid presenting training as delivery experience. | State the length of experience, programme or portfolio scale, leadership remit and business outcomes. Check that any stated number of years agrees with the dates in the employment history. |
| Discovery and requirements | Show structured note-taking, stakeholder interviews, workshop support and clearly written requirements for a defined process area. | Show ownership of discovery across several stakeholder groups, resolution of competing needs and prioritisation of requirements with assumptions and dependencies. |
| Process and solution work | Use a focused example of documenting a current process and contributing to a practical future-state map. | Demonstrate oversight of complex process redesign and the ability to connect business needs with suitable Salesforce capabilities across teams. |
| Delivery and UAT | Evidence writing acceptance criteria, preparing test scenarios, recording results and following defects through to resolution. | Evidence UAT planning, business readiness, risk discussions, defect triage and a well-supported go/no-go recommendation. |
| Adoption and measurement | Include training support, user feedback and straightforward usage or report measures collected after release. | Show how adoption dashboards, usage trends and business measures shaped training, release decisions and the prioritised backlog. |
| Scale and influence | Use honest measures such as workshop numbers, user-story counts, test cases, users supported or processes documented. | Use defensible measures covering multiple teams, larger user groups, delivery portfolios, efficiency gains or customer response improvements. |
How to write a salesforce business analyst CV
Use a clean, reverse-chronological format so the reader can find your recent work, dates and results without hunting for them. Two pages is a sensible target for most candidates, although one page may suit someone with limited experience. Start with your name and contact details, followed by a personal statement, selected skills, employment history, education and any relevant additional information.
| Section | What earns its place |
|---|---|
| Personal statement | Your experience level, project setting, strongest Salesforce and analysis evidence, and one credible result |
| Skills | A focused selection of platform features, tools and methods you have used |
| Experience | Recent roles first, with concise bullets that connect your work to an outcome |
| Education | Awarded qualifications, providers and completion dates |
| Extras | Relevant learning, projects, volunteering or languages that add evidence |
Keep the personal statement to two or three sentences. State the kind of Salesforce Business Analyst work you have done, the processes or teams involved and the outcome you helped achieve. If you are new to the role, draw on a placement, apprenticeship, course project or transferable work. With more experience, lead with delivery scope, judgement and results.
In each role, connect the business need to your contribution. Relevant evidence may include discovery interviews, current-state and future-state process maps, prioritised requirements, user stories with acceptance criteria, UAT coordination or adoption analysis. Include these only when they reflect your own work, and make your precise contribution clear.
Treat the skills section as an index to evidence elsewhere in the CV. Salesforce CRM, Salesforce Service Cloud and backlog management are terms found in UK Salesforce Business Analyst roles. Requirements workshops, stakeholder management and translating business requirements also appear in roles outside London. Visualforce and Lightning Web Components belong on the CV only when you have used them and can discuss the context.
Tailor the wording to the vacancy. If the advert stresses analysis and reporting, bring forward your experience of reports and dashboards used in business decisions. If it focuses on service operations, give more space to the relevant process, testing and outcome. Do not copy every phrase from the advert.
List education and professional development plainly. Give exact titles and dates, and keep additional sections short enough that they do not push stronger project evidence off the page.
Personal statement examples
Salesforce Business Analyst with four years of experience translating sales and service problems into prioritised requirements, process maps and testable user stories. Coordinated UAT for a service workflow used by 85 colleagues, closing 31 defects before release and helping reduce average response time by 18%. Comfortable working with sales managers, operations teams and delivery colleagues across discovery, testing and adoption review.
Hard-working Salesforce Business Analyst seeking a challenging position with a successful company. I am a good communicator, work well alone or in a team and have excellent IT skills. I can undertake any task and always give 100%.
Writing your experience
Treat every experience bullet as a small, testable piece of evidence. Start with a precise action, establish the scope, explain your contribution and finish with the result. Useful measures include time saved, transaction or case volume, number of users, defects resolved, adoption, accuracy and service performance. A modest figure that you can explain is more convincing than a dramatic number with no clear basis.
A dependable structure is: action + scope + contribution + outcome. For example: "Mapped the web-to-closure Case process across four service teams, identified seven duplicated hand-offs and helped reduce average resolution time by 12%." This tells the reader what you analysed, how broad the work was and what changed.
| Weak bullet | Stronger version |
|---|---|
| Helped gather requirements | Interviewed 14 sales and operations users, converted 46 findings into prioritised requirements and secured agreement through two workshops |
| Assisted with UAT | Prepared 38 scenario-based UAT scripts, tracked 27 defects and supplied test evidence for the release decision |
| Improved Salesforce adoption | Compared login, report and feature usage across 120 users, produced targeted training notes and raised weekly dashboard use from 54% to 73% |
These figures are illustrative. Use only measurements supported by reports, project records or a calculation you can describe. When commercial data is confidential, use an authorised percentage, range or operational measure. If the outcome was not measured, quantify the scope instead: users interviewed, processes mapped, stories written, workshops facilitated or defects triaged.
Choose verbs that describe what you actually did: elicited, interviewed, mapped, analysed, prioritised, documented, translated, facilitated, wrote, validated, coordinated, tested, tracked and recommended. Be careful with broad verbs such as "delivered" or "implemented" when administrators, developers or release colleagues owned substantial parts of the change.
Discovery evidence can show how you interviewed sales managers about issues such as skipped Opportunity stages, then produced a problem statement, stakeholder list and current-state notes. Process work can trace a Case from web submission to closure and distinguish the current state from the proposed future state. Requirements analysis can show how you separated necessary approval controls from optional changes and recorded priorities, assumptions and dependencies.
For user stories, name the user group where useful and state that your acceptance criteria were testable. Testing bullets can explain whether you prepared scripts for business scenarios, gathered test evidence, maintained a defect log or contributed to a go/no-go recommendation. After release, show whether you compared login, report or feature usage before and after go-live, then turned the findings into training notes, an adoption dashboard or backlog items.
Avoid diary-style bullets such as "attended stakeholder workshops" or "responsible for Salesforce requirements". They record presence or ownership without revealing the output. State whether you resolved conflicting needs, obtained agreement, improved traceability or gave the delivery team requirements they could test. That gives the recruiter something concrete to examine.
Key skills & ATS keywords
Hard skills
Soft skills
ATS keywords
Education & certifications
Keep this section factual and compact. Record the exact awarded qualification or completed course, the provider and the completion date. For recent study, add one or two relevant modules or projects when they support the vacancy. Label ongoing study clearly and give the expected completion date instead of presenting it as finished.
For entrants to the broader Business Analyst occupation in the UK, the Business Analyst Level 4 Higher Apprenticeship is an optional route for gaining some relevant skills and knowledge. The Project Manager Level 6 Degree Apprenticeship is another optional route for Business Analyst role entrants. Neither route is presented here as a universal entry requirement for Salesforce Business Analyst jobs. If you completed one, use its exact title and add a short project note where it supplies useful evidence.
Your CV should demonstrate needs analysis, requirements elicitation, business case definition, requirements writing and review, flow and process diagramming, wireframing, business data analytics and problem solving. It should also show at least a basic understanding of AgentExchange, automation, collaboration, data management, reports and dashboards, CRM, platform, and sales and marketing. Prove these areas through employment or project bullets where possible; a bare list in the education section carries less weight.
If you hold Certified Administrator, Advanced Administrator or Certified Platform Developer, include the exact credential when it is relevant to the vacancy. A credential should not imply project experience you have not gained. Since 2 May 2023, the Salesforce Certified Platform Administrator certification has not been required before earning the Salesforce Certified Business Analyst certification, so do not present that former sequence as a current prerequisite.
If you do not hold a named credential, record relevant completed learning briefly and let practical project evidence carry the application. Put recent, relevant development above older study. Senior candidates can trim early academic detail once their delivery record gives stronger proof of capability.
Common mistakes to avoid
AvoidListing Salesforce features without explaining the business problem they addressed.
InsteadConnect each relevant tool or feature to a specific process issue and outcome, such as reduced response time, stronger adoption or improved sales efficiency. Use only figures you can defend.
AvoidWriting vague duties such as "gathered requirements" without showing the method, decisions or outputs involved.
InsteadName the work performed and the resulting artefact. For example, refer to stakeholder interviews, requirements workshops, prioritised requirements, process maps, user stories or testable acceptance criteria.
AvoidTreating UAT as a single line rather than a controlled piece of analysis.
InsteadShow your contribution to business scenarios, UAT scripts, test evidence, defect tracking and the go/no-go recommendation. Keep the wording accurate if another person owned the final decision.
AvoidUsing one generic CV for every Salesforce Business Analyst vacancy.
InsteadMatch the vacancy's language where it reflects your real experience. If reporting is prominent, give more space to reports, dashboards and the decisions they informed.
AvoidGiving technical terminology more space than stakeholder and process evidence.
InsteadBalance Salesforce knowledge with examples of discovery, process analysis, requirements translation and collaboration between business and delivery teams.
AvoidClaiming improvements without a credible baseline, period or measure.
InsteadState what changed, how it was measured and over what period. If you cannot support a percentage, use a defensible count, scope or delivery measure instead.
Frequently asked questions
Two pages is a practical target for many experienced candidates, while a recent entrant may need only one. Use reverse-chronological order and give the most space to recent Salesforce, requirements, process and delivery evidence rather than older, unrelated duties.
Use projects, placements, apprenticeships or adjacent roles to demonstrate discovery, process mapping, requirements writing, data analysis and stakeholder communication. Describe your scope honestly, distinguish hands-on delivery from training or observation, and use measures such as users interviewed, processes mapped or test cases completed.
No. A British-style CV normally omits a photo and date of birth. Use the space for contact details, a focused personal statement and evidence relevant to the vacancy.
List only tools and capabilities you have used and can discuss confidently. Depending on your experience and the vacancy, relevant terms may include Salesforce CRM, Salesforce Service Cloud, reports and dashboards, data management, Visualforce or Lightning Web Components; do not add keywords that you cannot support with evidence.
Translate previous work into Salesforce Business Analyst evidence: interviewing users, clarifying problems, mapping processes, analysing data, writing requirements, supporting tests or training colleagues. Keep the original job title accurate, explain the business context and make clear where Salesforce experience came from projects or learning rather than employment.
Yes, where the wording reflects experience you genuinely have. For a role centred on data analysis, bring forward Salesforce reporting and dashboard examples and explain which business decisions they supported; for a discovery-heavy role, prioritise interviews, workshops and requirements evidence.
From example to application
Turn this salesforce business analyst example into a CV that sounds like you.
Keep the structure that works. Tailor the details around your experience, strengths, and the role you want.