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 the recruiter call, about a week later I went into an onsite loop for the SMTS track with four distinct rounds. The structure felt pretty clear to follow: I started with a short virtual screen, then progressed to onsite, then a high-level design stage, and finally a manager round that dug into my background.
Round one combined a quick introduction with a single DSA question and follow-up, and it also included a targeted HLD session. Onsite round two brought another DSA problem, followed by a low-level design evaluation. The third onsite round shifted harder toward high-level design for large-scale systems—think “design something like YouTube or Instagram” style questions. The last round was more managerial: a deep dive into my resume and a review of what I’d been working on day to day.
2 weeks ago
I ended up interviewing for an MTS role at Salesforce after a recruiter reached out to me directly. The first step was a HackerRank-style online assessment, and then I had a technical interview that focused on a single, very specific DSA problem.
For the online portion, I didn’t remember the exact prompts, but I stayed on track with the time limit and made sure I handled the edge cases. That mattered because the follow-up technical round was still very problem-solving oriented rather than vague discussion.
2 months ago
Average Positive San Francisco, CA
My Salesforce process for the MTS role moved in a pretty standard, step-by-step flow. It started with HackerRank using two LeetCode-medium style codin…
2 months ago
Average Neutral Paris
My Salesforce interview process for the role I was pursuing took around three weeks overall, and it played out in four steps. It began with a recruite…
2 months ago
Difficult Neutral San Francisco, CA
I went through a tighter Salesforce MTS-style sequence where the technical bar emphasized real problem-solving and then ended with system-level thinki…
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 follows a clear structure starting with a recruiter call, followed by an online assessment, technical interviews, and concluding with a managerial round. The overall timeline is generally around three weeks, with multiple rounds focusing on different aspects of technical and behavioral evaluation.
Recruiter callOnline assessmentManagerial round
Technical / Coding Screen
Candidates can expect a mix of DSA questions, often in the LeetCode style, with varying difficulty levels. The focus is on correctness, problem-solving, and the ability to articulate thought processes clearly during coding interviews.
DSALeetCodeProblem-solving
System Design Rounds
Interviews include both low-level and high-level design discussions, where candidates are expected to demonstrate their understanding of system architecture, scalability, and operational concerns. Candidates should prepare to discuss real-world scenarios and trade-offs in their design choices.
System designHigh-level designLow-level design
Behavioral & Values Assessment
Behavioral interviews focus on candidates' past experiences, alignment with company values, and the ability to communicate effectively about their work. Candidates should be prepared to connect their experiences to the role and demonstrate cultural fit.
BehavioralCultural fitExperience alignment
Difficulty & Outcome
The overall difficulty of the interview process is considered high, with an emphasis on both technical depth and clarity in communication. Candidates often reflect that consistent performance across rounds is crucial for success, with many noting that a coherent narrative about their skills and experiences can significantly impact outcomes.
High difficultyCommunicationConsistent performance
Preparation Insights
Candidates suggest focusing on practicing DSA problems and system design concepts, as well as preparing to discuss personal projects in detail. Understanding the Salesforce ecosystem and being able to articulate architectural decisions are also highlighted as beneficial.