Salesforce Software Engineer candidates report a HackerRank assessment, live coding on classic DSA problems, low-level and high-level design rounds, and behavioral questions. Formats vary by team, and outcomes are mixed.
$170K
Avg. Base Comp
$211K
Avg. Total Comp
3-5 rounds
Typical Rounds
Not reported
Process Length
Candidates describe the Salesforce Software Engineer interview as a coding-first process with design and behavioral rounds layered on top. Most reports open with a recruiter or hiring manager conversation and a HackerRank-style online assessment. The assessment is where several people say the process got filtered, and difficulty ranged widely: some saw two medium questions, while two 2026 reports describe dynamic programming, graph and greedy problems that felt medium to very hard.
Live rounds lean on well-known patterns. Reported questions include 3Sum, cycle detection and merge points in linked lists, an LRU Cache optimized from O(n) to O(1), topological ordering, and a largest-rectangle problem solved with a histogram and monotonic stack. A few candidates were also asked Java fundamentals, and one was asked to explain time complexity on a simple string-reversal task.
Recent reports also describe low-level and high-level design. Prompts include a job scheduler that handles concurrency and idempotency, a rate limiter, a Java workflow built around an interface, a notification system, and a synchronized watch party. One candidate describes a broader platform that integrates third-party tools.
Behavioral questions matter more than the coding focus suggests. One candidate says each round started with about 15 minutes of situational questions. Others mention STAR-format answers and a question about fostering inclusivity. Outcomes are mixed, with both offers and rejections reported, and one offer came through a referral path with a recorded video and a small build-and-demo task. Prepare for timed coding, and be ready to explain your design trade-offs out loud.
Synthesized from 64 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.
I applied to Salesforce in July and didn't hear back until September, so the whole process was drawn out from the start. Once they got back to me, things moved quickly. I had an initial screening call with the recruiter, then they sent me an FDE assessment on HackerRank—I actually had to complete it twice, but I cleared both attempts and got positive feedback. After that came a technical interview where they asked me questions on DBMS, OOP concepts, and programming problems based on my resume and projects. The interviewers were genuinely interested in my background and even asked about extracurricular activities, which made it feel less like a checkbox exercise. I also had a hiring manager round that went really well; we had a great discussion and the conversation felt collaborative rather than adversarial. They were impressed enough to invite me to visit the Dublin office to meet a colleague and get a feel for the team. I thought it was heading in the right direction, but at the end they told me they had decided to go with someone else for the role. It was disappointing given how far I'd gotten and how positive the conversations felt, but at least the process itself was thorough and the feedback was honest.
Prep tip from this candidate
The FDE assessment appears twice in this process, so make sure you're solid on that specific format. Prepare concrete project examples and be ready to discuss them in depth—they'll dig into your resume, not just ask generic questions. Also, the office visit round suggests they were seriously considering you, so practice articulating why you want to work there and what you'd contribute to the team.
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
Return keys with weighted probabilities
| Question | |
|---|---|
| Top 3 Users | |
| Month Over Month | |
| Rolling Average Steps | |
| Most Repetition | |
| Hurdles In Data Projects | |
| Success Measurement | |
| Subscription Retention | |
| The Pirate’s Hunt | |
| Three Indexes Adding Zero | |
| Shortest Path Algorithms | |
| Client Solution Pushback | |
| Justify a Neural Network | |
| Your Strengths and Weaknesses | |
| Weighted Average Sales | |
| Fast Food Database | |
| Google Earth Storage | |
| Reverse List Starting at Index K | |
| Reddit-like Notifications | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Rolling Bank Transactions | |
| Monthly Customer Report | |
| Prime to N | |
| Random SQL Sample | |
| String Shift |
Synthesized from candidate reports. Individual experiences may vary.
Candidates typically report starting with a recruiter call, a hiring manager conversation, or both. These conversations cover your background, resume projects and motivation for the role. Some candidates also mention behavioral questions at this stage. The exact order varies by team, so be ready to explain your projects clearly.
Many candidates report a HackerRank assessment early in the process. Formats reported include two medium questions in 75 minutes and a 90-minute test with three questions. Two 2026 reports describe dynamic programming, graph and greedy problems that felt hard. One candidate saw an AI-assisted task to fix a banking application's search feature. Difficulty may vary by team and timing.
Candidates describe live coding on standard problems: 3Sum, linked list cycle and merge point, LRU Cache, topological ordering, and a histogram-based largest rectangle. Interviewers reportedly ask for time and space complexity and probe edge cases. Some candidates also mention Java theory or basic computer science questions. These rounds may include follow-up optimization prompts.
Several recent candidates report design rounds. Prompts include a job scheduler that handles concurrency and idempotency, a rate limiter, a Java workflow built on an interface, a notification system and a synchronized watch party. Candidates say interviewers expect requirement clarification, class or API structure, and trade-off discussion. Not every candidate reports a design round.
Candidates report behavioral questions throughout, and one says each round began with about 15 minutes of situational questions. Topics include STAR-style stories, inclusivity, project setbacks and motivation. Accounts of the final rounds differ, from smooth conversations to one described as hostile. Outcomes are mixed: some candidates report offers, others rejections, silence or waiting.
