Senior Salesforce Business Analyst

Senior Salesforce Business Analyst

When a client asks for a new field, do you want to know why they need it before you add it? Can you sit across from a VP of Sales, tell them their process has a gap, and leave them glad you did? Do you know when standard Salesforce is enough and when it isn’t?

Then our Senior Salesforce Business Analyst role here at CUBE84 may interest you.

In this gig,

1. You ask “why” before you write “what”
   You run the discovery sessions, stakeholder interviews and requirements workshops. You learn how the client’s business works: their operating model, what’s slowing them down and what they’re trying to achieve. You leave with a clear view of the real problem, not just a list of feature requests.

2. You’re allowed to say “there’s a better way”
   You look at existing processes, find the gaps, waste and workarounds, and suggest better ones. Sometimes the answer is Salesforce. Sometimes it’s a simpler workflow. You can tell the difference, and you can explain your reasoning to people who’ve done it the same way for ten years.

3. Standard first, custom second
   You know the Salesforce ecosystem well enough to advise clients on what the platform can do, where it falls short, and how to get there. You push for out-of-the-box features before custom builds. You also work with our Architects to make sure what you recommend will scale and stay maintainable.

4. You turn conversations into buildable requirements
   BRDs, FRDs, user stories, process flows, acceptance criteria, traceability matrices: you write them so a developer can build from them and a QA engineer can test against them without chasing you for answers. When scope shifts mid-project, you track it, flag the impact and keep everything lined up.

5. You’re the bridge, not the bottleneck
   You’re the main functional link between the client and our Architects, Developers, QA and PMs. You make sure what the business expects, what we designed and what gets built all match. You spot risks and missing requirements early, before they become surprises at go-live.

6. Done means adopted, not just deployed
   You define test scenarios, check the build against the agreed requirements, and run UAT. Then you help with training, demos and change management, because a solution nobody uses hasn’t solved anything.

It’ll be awesome if you...

• Have 5–8 years of experience as a Business Analyst or Functional Consultant

• Have at least 4 years of hands-on Salesforce consulting or implementation experience (this one’s non-negotiable)

• Know Sales Cloud, Service Cloud and Experience Cloud well at the functional level

• Have led client discovery sessions, workshops and stakeholder discussions yourself, not just taken notes in them

• Are strong in business process analysis, gap assessment, and process optimization

• Have process modelling and workflow/automation analysis experience

• Write strong BRDs, FRDs, user stories, functional specs and acceptance criteria

• Communicate, present and manage stakeholders well, including with global, cross-functional teams

More awesome, if you have

• Experience on enterprise-scale or complex Salesforce implementations

• Exposure to CPQ, Marketing Cloud, Account Engagement (Pardot), Nonprofit Cloud or MuleSoft integrations

• Business transformation, digital transformation or process re-engineering experience

• Pre-sales exposure: RFP responses, solution proposals, client presentations

• Familiarity with Agile, Salesforce DevOps and enterprise governance frameworks

• Salesforce certifications such as Business Analyst, Administrator, Sales Cloud Consultant or Service Cloud Consultant