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.
I went through the SMTS onsite loop at Salesforce with four rounds. After a recruiter touchpoint, about a week later I showed up for the structured onsite process that felt pretty clearly organized, even though the technical parts were the ones that mattered most.
My first onsite stop included a single DSA prompt with a follow-up, and then there was a targeted HLD segment that focused on designing at a higher level. The next round shifted into a DSA problem paired with an LLD evaluation, where I had to break the solution down into components. After that came an HLD round focused on large-scale systems, with questions like designing something on the scale of YouTube or Instagram. The final round was managerial, built around a deep dive into my resume and whatever I said I’d been doing recently.
2 months ago
I interviewed for Salesforce in an MTS hiring flow that started with an online HackerRank assessment. I had to solve at HackerRank and finished on time, then I moved into a technical round.
The technical interview was centered on a classic stack-based problem: validating parentheses. The conversation was straightforward in the sense that the goal was clear, and I focused on explaining the stack approach and walking through how it handles different cases.
3 months ago
Average Positive San Francisco, CA
I ended up with roughly a three-week interview timeline at Salesforce, and it moved through a pretty standard sequence of stages. It started with a re…
3 months ago
Difficult Neutral San Francisco, CA
My interview process for Salesforce had three main steps, and the progression felt pretty intentional. First came a recruiter screening call, then I w…
4 months ago
Average Positive Seattle, WA
My interview was brief—about 30 minutes—and it focused on a single coding task. I was asked to write a function that validated whether a string was a …
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
Interview Structure & Timeline
The interview process typically starts with a recruiter screening, followed by an online assessment, and then moves into multiple technical rounds including coding and system design, culminating in a hiring manager interview. The overall timeline can vary, often taking around three weeks from initial contact to offer.
Candidates can expect to face multiple coding interviews focused on data structures and algorithms (DSA), often using LeetCode-style problems that require clear reasoning and problem-solving skills. The difficulty of these problems can range from easy to hard, with an emphasis on understanding edge cases and optimization techniques.
DSALeetCodeProblem-solving
High-Level & Low-Level Design
The interview process includes high-level design (HLD) and low-level design (LLD) rounds where candidates must demonstrate their ability to architect scalable systems and discuss trade-offs in design decisions. Questions may involve real-world scenarios and require a deep understanding of system constraints.
System designArchitectureScalability
Behavioral Interviews
Behavioral interviews focus on candidates' past experiences, teamwork, and project discussions, often using a conversational approach to assess cultural fit and alignment with company values. These rounds typically follow technical assessments and provide a lighter contrast to the technical pressure.
BehavioralCultural fitTeamwork
Overall Difficulty & Expectations
Candidates report that the interview process is challenging but fair, with a consistent expectation for clear communication and reasoning across all rounds. Success often hinges on demonstrating both technical proficiency and the ability to articulate thought processes effectively.
ChallengeClear communicationTechnical proficiency
Preparation Insights
Candidates suggest focusing on LeetCode-style problems and practicing system design concepts to prepare effectively. Familiarity with common algorithms and data structures, as well as understanding architectural principles, can significantly enhance performance during interviews.