
Salesforce Software Engineer candidates report an online assessment, live coding, low-level and system design prompts, and hiring manager and behavioral conversations across three to five rounds, with format varying by team.
$169K
Avg. Base Comp
$200K
Avg. Total Comp
3-5 rounds
Typical Rounds
Not reported
Process Length
Candidates describe the Salesforce Software Engineer loop as an online assessment followed by coding, design and manager conversations, with the exact mix depending on the team. Reports give three to five rounds. One candidate said their process took about two weeks, but timelines likely vary by team, so plan around the sequence rather than a calendar.
The assessment is where accounts differ most. One candidate saw two medium LeetCode-style questions on HackerRank, another had two medium DSA problems in 75 minutes (3Sum and Burst Balloons), and a third faced a 90-minute test with three graph, greedy and dynamic programming problems. A 2026 candidate described a sliding-window request-counting problem plus an AI-assisted task to fix a banking app's search functionality, and a brute-force answer failed several tests on time limits.
Later rounds lean on fundamentals and design. Live coding reports include LRU Cache, minimum window substring, topological ordering with cycle detection and largest rectangle in a binary matrix. Design prompts include a job scheduler that handles concurrency and idempotency, a rate limiter, a notification system, a synchronized watch party and a Java workflow built around interfaces. One candidate said every round opened with about 15 minutes of situational questions, so keep STAR stories ready alongside technical prep.
Outcomes were mixed: several rejections, a few candidates still waiting, and offers in some accounts, including one after a process that included a Loom video interview, a small build task and a solution demo. Treat each account as one team's version of the loop.
Synthesized from 69 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Salesforce process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Salesforce
Write a query to display the top three users by downloads each day
| Question | |
|---|---|
| Weighted Keys | |
| Month Over Month | |
| Fast Food Database | |
| Shortest Path Algorithms | |
| Weighted Average Sales | |
| Subscription Retention | |
| Reverse List Starting at Index K | |
| Rolling Average Steps | |
| Hurdles In Data Projects | |
| Most Repetition | |
| Justify a Neural Network | |
| Success Measurement | |
| Reddit-like Notifications | |
| Three Indexes Adding Zero | |
| Client Solution Pushback | |
| Google Earth Storage | |
| The Pirate’s Hunt | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Merge Sorted Lists | |
| Empty Neighborhoods | |
| Subscription Overlap | |
| Random SQL Sample | |
| Raining in Seattle | |
| Size of Joins | |
| Upsell Transactions | |
| Find the Missing Number |
Synthesized from candidate reports. Individual experiences may vary.
Several candidates describe a recruiter screen and a hiring manager conversation early on, covering background, resume projects and the team they might join. One candidate had these two screens before the HackerRank assessment, which they counted as the third round. Another reported a hiring manager conversation again later in the loop.
Reports range from two medium LeetCode-style questions to a 90-minute test with three graph, greedy and dynamic programming problems. Others describe 3Sum and Burst Balloons in 75 minutes, or a sliding-window problem plus an AI-assisted bug-fixing task on a banking app. One candidate also got theoretical Java questions with the coding screen.
Candidates report problems such as LRU Cache moved from O(n) to O(1), minimum window substring, topological ordering with cycle detection and largest rectangle in a binary matrix using a monotonic stack. One candidate described two hard questions in a single coding round, and another a medium graph problem. Interviewers asked for step-by-step walkthroughs, edge cases and time complexity.
Reported prompts include a job scheduler with concurrency and idempotency, a rate limiter, a Java workflow built around interfaces, a notification system, a synchronized watch party and a platform integrating many third-party tools. One candidate expected requirement clarification, entity design and API specifications, so scope the problem aloud before designing.
Behavioral content appears both as its own round and at the start of technical rounds; one candidate said each round opened with roughly 15 minutes of it. Others describe a final manager round, a techno-managerial round built on scenario-based questions, or a question about a complex system they had built. One candidate described a Loom video interview and a solution demo.