Salesforce Business Analyst

Role overview A Salesforce-focused business analysis role responsible for owning scope on delivery engagements, turning business needs into buildable requirements, and holding the line when scope moves. Requirements discipline is treated as the single largest predictor of whether AI or automation work succeeds, so the role carries more weight than a typical ticket-writing seat.

Responsibilities - Run discovery with business users and map current-state processes before proposing a future state - Write user stories with acceptance criteria that can actually be tested, and trace each requirement back to a business outcome - Partner with architects and developers on feasibility before a requirement is committed to a sprint, and prototype candidate solutions in a sandbox using Flow and configuration - Distinguish reporting or data-quality problems from genuine functionality gaps - Groom and prioritize the backlog with the product owner, keeping dependencies visible and the list honest - Design and run UAT with test data that mirrors real edge cases, and support release communications, training material, and adoption tracking - Maintain one shared view of scope across competing stakeholder asks, and escalate conflicts rather than smoothing them into something no one actually wants

Requirements - Three or more years as a Business Analyst on Salesforce delivery, including full-lifecycle implementations - Working command of Salesforce Sales Cloud and Service Cloud data models and standard functionality - Practical skill with Flow, report and dashboard building, and enough configuration ability to prototype independently - Process mapping notation, user-story writing, and acceptance-criteria design - Jira, Azure DevOps, or an equivalent backlog tool - Salesforce Certified Administrator required; Business Analyst certification preferred - Experience running UAT and structured requirements workshops with senior business stakeholders - A documented example of pushing back on a requirement that should not have been built

Nice to have - Holds a point of view and states it, including to senior stakeholders and including after a decision when new evidence warrants reopening it - Asks why a process, data model, or delivery standard exists before extending it, instead of replicating the incumbent pattern - Surfaces risk, ambiguity, and weak requirements the moment they are noticed, rather than at sprint review or go-live - Argues from evidence and changes position on evidence; comfortable being corrected in public, uncomfortable staying silent

Benefits and work setup - Professional English, with the ability to run requirements and design conversations directly with North American stakeholders - Bachelor's degree in Information Systems, Business, Computer Science, or a related field, or equivalent practical experience - Visa sponsorship is not available for this role; candidates must already hold permanent work authorization in their country of residence