Real, anonymous reports from people who interviewed for Software Engineer at Salesforce, newest first and distilled into what to expect across the loop.
Get your personalized Salesforce Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
After I applied, I got an invite to a coding challenge hosted through HackerRank. It was the Salesforce Futureforce Coding Challenge with a hard 60-minute limit, and the whole thing ran under AI Proctor Mode, so it actively monitored for anything like switching away from the screen, changing tabs, or doing copy-paste.
It felt less like a casual timed quiz and more like a controlled exam. The strict time window and the proctoring rules made me hyper-aware of my workflow the entire time. I didn’t end up getting an offer from the process, but at least I knew exactly how the test was going to run before I started.
2 months ago
Average Positive United States
My process started after the early screen, and then I went into a behavioral round and a technical round. The behavioral interview was about 30 minutes and stayed pretty standard—things like telling me about myself.
The technical interview ran around 45 minutes and was focused on LeetCode-style coding. I was asked two problems in that style, and overall the pacing felt straightforward enough that I could keep thinking clearly.
2 months ago
Difficult Positive Bengaluru
Right after applying, I went through a HackerRank-based technical stage that felt genuinely competitive. The first round was a DSA coding test on Hack…
2 months ago
Average Neutral United States
For my technical round, I was asked to solve a merging intervals problem where overlapping ranges had to be handled carefully. The question pushed me …
2 months ago
Difficult Positive San Francisco, CA
My interview path started with an online coding assessment. I worked through a take-home style technical round where I had to solve a coding question,…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Online Assessment
The interview process begins with a timed online assessment via HackerRank, typically consisting of two coding questions, one easy and one medium, with strict proctoring rules in place. Candidates should prepare for a competitive environment where scoring is based on passing test cases.
HackerRanktimed assessmentcoding challenge
Technical Interviews
Following the online assessment, candidates participate in one or more technical interviews focused on LeetCode-style problems and data structures. Expect to solve medium-level coding problems and discuss time and space complexity.
LeetCodedata structurestechnical interview
Behavioral Interviews
Candidates will face behavioral interviews that assess communication skills, teamwork, and project experiences. These discussions often involve situational questions and reflections on past work to gauge cultural fit.
behavioralcommunicationcultural fit
System Design Round
Some candidates will encounter a system design interview that tests their ability to architect solutions and reason through complex problems. This round can be more demanding and requires a solid understanding of system architecture.
system designarchitectureproblem-solving
Interview Atmosphere and Tone
The interview environment can vary significantly, with some candidates experiencing a relaxed atmosphere while others find it intense and high-pressure, especially during technical rounds. Being prepared for different interviewer styles is crucial.
interview atmospherepressureinterviewer styles
Overall Process Structure
The overall interview process is generally well-structured, often comprising multiple rounds that assess both technical and soft skills. Candidates should expect a mix of interviews that evaluate their problem-solving abilities and interpersonal skills.