Salesforce Software Engineer Interview Questions
224+ questions from real Salesforce Software Engineer interviews, reported by candidates.
Round Types
Top Topics
Questions
<h2>1. Collect Opportunity Data in a Tree</h2> <p>You are given an undirected <b>tree</b> with <code>n</code> nodes labeled from <code>0</code> to <code>n - 1</code>. The tree is defined by <code>n -
Salesforce Interview Experience Role: MTS Experience: 2.5 years at an MNC ## Interview Experience (5 Rounds | Virtual + Offline) All rounds were around 45 minutes with 10–15 minutes buffer. Round 1 –
Salesforce SMTS Interview Experience with DSA and LLD
The recruiter reached out to me directly for the SMTS role and shared a link to apply. She asked me to apply within an hour, after which I would receive the online assessment (OA) link. I was instruct
Absolutely bottled it. 1. Given an array of elements (n = 10^5), you can perform two operations on them: - Remove an element - Change it to any random integer Return the minimum no of removals such th
Salesforce MTS Interview Experience: LLD Workflow and Memory Task Scheduling
I was reached out to by a recruiter from Salesforce at the end of January 2026 for MTS role. The process started with an Online Assessment, followed by technical rounds. **Round 1: (LLD based)** Resum
Hey everyone I wanted to give back to this community because reading posts like this helped me a lot during my own process. Hopefully this helps someone who’s currently waiting or stressing. Timeline
Salesforce Low Level Design Interview Questions
In Salesforce LLD rounds, sometimes actual requirements may not be clear from problem statement and interviewer will expect you to figure it out by asking clarifying questions. For example, A message
Certifications are important because they help prove your skills and increase your knowledge in a specific area. Recently, I attempted the Salesforce Agentforce Specialist...
General SDE backend position The first round was a director interview (I specifically emphasized that this is not an hiring manager, but someone who came to help with the interview...), a deep dive in
**Context** The interview process was for a Salesforce MTS/SMTS Backend Engineer position, which ultimately turned out to be a role within Slack. The process bypassed standard Talent Acquisition scree
**Problem 1: Spam Classification System** **Problem Statement** Implement a function to evaluate a list of texts and determine if they are "spam" or "not_spam." A text is classified as spam if it cont
**HackerRank Assessment (Duration: 75 minutes)** **1. Longest Common Subsequence and Substring** **Problem Statement:** Given two strings, `x` and `y`, determine two specific values: 1. The length of
**Round 1 Interview Overview** The session began with a brief introduction and immediately transitioned to a Hackerrank assessment containing two coding questions. **1. Remove All Adjacent Duplicates
**Salesforce SMTS Backend Online Assessment Overview** * **Experience Level:** 6.5 Years * **Source:** Careers Portal * **Platform:** HackerRank * **Format:** 2 Questions, 75 Minutes **Problem 1: Mini
**Online Assessment** Completion of the preliminary coding rounds. **Round 1: Data Structures and Algorithms** * **Longest Non-Repeating Substring:** Identify the length of the longest substring withi
**Role:** Senior MTS **Hiring Manager Screen (45 mins)** * Focus: Work experience, role impact, and extensive behavioral questions. * Duration: The session ran over by 15 minutes (1 hour total). **Onl
**Role:** Senior Member of Technical Staff (Frontend) **Application Method:** Salesforce Career Site **Process:** 6 Rounds ### Round 1: Online Assessment (HackerRank) **Duration:** 60 minutes **Proble
The technical assessment required solving two algorithmic problems within a one-hour limit: 1. **Number of Islands:** The task involved identifying connected components within a grid. A complete solut
Salesforce Meeting Room Reservation System Design Interview
**Problem Statement** Design the low-level architecture for a Meeting Room Reservation Platform. The system must allow employees within an organization to book rooms, verify availability, and manage t
Salesforce SMTS LLD Interview: Cab Booking Service Design
I was asked to design a Cab Booking Service like Uber with the following requirements: - Allow passengers to request rides. - Allow drivers to accept and fulfill rides. - Allow passengers to cancel ri
What Salesforce Looks for in Software Engineer Interviews
Salesforce Software Engineer interviews are calibrated against the level and scope expected of the role. Across 224+ verified candidate reports on LeakCode, the consistent signals interviewers look for: clear problem decomposition before coding, explicit complexity reasoning, structured handling of edge cases, and the ability to articulate trade-offs between two reasonable approaches.
The discriminator between candidates who advance and candidates who do not is rarely the final correctness of the solution. It is the path to the solution: did you ask clarifying questions, did you state your approach before coding, did you handle edge cases without prompting, and did you communicate your reasoning throughout. Reports tagged "no hire" frequently cite a working solution with poor communication; reports tagged "strong hire" cite clear thinking even when the final solution was incomplete.
How To Use This Question Set
Real interview reports are a calibration tool, not a memorization target. Companies update their question pools every 2-4 months; memorizing exact problems risks misleading you when the interviewer uses a variant. The high-leverage use: identify the patterns that appear repeatedly in Salesforce Software Engineer reports, practice those patterns on similar (not identical) problems, and use the reports to understand the interviewer's typical follow-up depth.
Filter the questions below by round type, difficulty, and recency. Focus first on reports from the past 6-12 months; older reports may reference questions that have since rotated out of Salesforce's pool. Reports tagged with quantified difficulty (e.g., "medium-hard") are higher-signal than reports without difficulty tags.
Round-by-Round Expectations
Salesforce Software Engineer loops typically span 4-6 rounds across phone screens and on-site or virtual on-site interviews. The structure varies by company: some run 1 recruiter screen + 1 technical phone + 3-4 on-site rounds; others run 1 recruiter screen + 1 OA + 4-5 on-site rounds. The recruiter screen is logistics and culture-light; the technical phone screen is medium-difficulty coding; the on-site loop covers coding, system design (at L4+ levels), and behavioral rounds.
Each round is designed to surface a specific signal. Coding rounds: correctness, code quality, complexity reasoning, communication. System design rounds: requirements clarification, design judgment, operational thinking. Behavioral rounds: ownership scope, leadership, ambiguity tolerance, conflict navigation. Strong candidates explicitly hit each signal dimension out loud during the round; weak candidates focus only on solving the prompt.
Common Interview Mistakes At This Combination
Reports tagged "no hire" at Salesforce Software Engineer commonly cite: jumping into code without clarifying requirements, coding silently for 10+ minutes without verbalizing approach, missing edge cases (empty input, single element, very large input, overflow), and producing a working solution that the candidate cannot explain or refactor when probed. Strong candidates avoid these patterns by following a consistent template: clarify, verbalize approach, code with narration, test with examples.
Behavioral and design rounds have their own failure modes. Behavioral: stories that use "we" instead of "I" diluting individual signal, stories with no quantified outcome, defensiveness when probed about failure. Design: not asking clarifying questions, not stating requirements out loud, designing for a single server when the prompt clearly implies scale, ignoring operational concerns (deployment, monitoring, rollback). These show up in roughly half of Salesforce Software Engineer interview retrospectives on LeakCode.
See All 224 Salesforce Software Engineer Questions
Full question text, answer context, and frequency data for subscribers.
Get Access