Salesforce Software Engineer Onsite Coding Questions
95+ questions from real Salesforce Software Engineer Onsite Coding rounds, reported by candidates who interviewed there.
What does the Salesforce Onsite Coding round test?
The Salesforce onsite coding round is the core technical evaluation. Software Engineer candidates typically see 2-3 algorithm and data structure problems. Problems range from medium to hard difficulty, and interviewers evaluate both correctness and code quality.
Top Topics in This Round
Salesforce Software Engineer Onsite Coding Questions
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 Onsite Interview Experience and Coding Questions
**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
Technical Round 1 (60 mins) - Problem 1: Given a string and a number of rows, print the string in zigzag traversal. I provided the most optimized solution and executed it successfully. - Problem 2: Gi
**Mode of apply**: Direct apply on LinkedIn **Experience**: 5 years **OA Round (90 mins)** - 1. Don't remember the two questions. But mostly it was leetcode medium. **Technical Round 1 (DSA) (Virtual)
Older 2 IIT's(CSE) Total Exp: 8+ Years (Mostly startups). Was part of November hiring drive Round 1 - Algo DS Graph medium question. Did it in given time and ran all test cases. Interviewer had diffic
Salesforce USA Senior MTS Onsite Interview Experience and Offer
**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
Salesforce onsite question
In order to launch an application, we load smaller modules.These modules usually have dependencies on other modules. Print the order in which the application should load the modules given the...
#2571 Minimum Operations to Reduce an Integer to 0
LeetCode #2571: Minimum Operations to Reduce an Integer to 0. Difficulty: Medium. Topics: Dynamic Programming, Greedy, Bit Manipulation. Asked at Salesforce in the last 6 months.
#2380 Time Needed to Rearrange a Binary String
LeetCode #2380: Time Needed to Rearrange a Binary String. Difficulty: Medium. Topics: String, Dynamic Programming, Simulation. Asked at Salesforce in the last 6 months.
#443 String Compression
LeetCode #443: String Compression. Difficulty: Medium. Topics: Two Pointers, String. Asked at Salesforce in the last 6 months.
LeetCode #3035: Maximum Palindromes After Operations. Difficulty: Medium. Topics: Array, Hash Table, String, Greedy, Sorting, Counting. Asked at Salesforce in the last 6 months.
#3634 Minimum Removals to Balance Array
LeetCode #3634: Minimum Removals to Balance Array. Difficulty: Medium. Topics: Array, Binary Search, Sliding Window, Sorting. Asked at Salesforce in the last 6 months.
#146 LRU Cache
LeetCode #146: LRU Cache. Difficulty: Medium. Topics: Hash Table, Linked List, Design, Doubly-Linked List. Asked at Salesforce in the last 6 months.
#124 Binary Tree Maximum Path Sum
LeetCode #124: Binary Tree Maximum Path Sum. Difficulty: Hard. Topics: Dynamic Programming, Tree, Depth-First Search, Binary Tree. Asked at Salesforce in the last 6 months.
#740 Delete and Earn
LeetCode #740: Delete and Earn. Difficulty: Medium. Topics: Array, Hash Table, Dynamic Programming. Asked at Salesforce in the last 6 months.
#3 Longest Substring Without Repeating Characters
LeetCode #3: Longest Substring Without Repeating Characters. Difficulty: Medium. Topics: Hash Table, String, Sliding Window. Asked at Salesforce in the last 6 months.
#1219 Path with Maximum Gold
LeetCode #1219: Path with Maximum Gold. Difficulty: Medium. Topics: Array, Backtracking, Matrix. Asked at Salesforce in the last 6 months.
#1522 Diameter of N-Ary Tree
LeetCode #1522: Diameter of N-Ary Tree. Difficulty: Medium. Topics: Tree, Depth-First Search. Asked at Salesforce in the last 6 months.
LeetCode #2603: Collect Coins in a Tree. Difficulty: Hard. Topics: Array, Tree, Graph Theory, Topological Sort. Asked at Salesforce in the last 6 months.
#664 Strange Printer
LeetCode #664: Strange Printer. Difficulty: Hard. Topics: String, Dynamic Programming. Asked at Salesforce in the last 6 months.
What to Expect in the Salesforce Onsite Coding Round
The Salesforce Software Engineer Onsite Coding round has a specific calibration purpose distinct from other rounds in the loop. Across 95+ verified reports on LeakCode for this exact round type, the consistent expectations: clear scoping of the problem before diving into a solution, explicit reasoning about complexity, structured handling of edge cases, and the ability to discuss trade-offs between two reasonable approaches.
Reports tagged with the Onsite Coding round at Salesforce show recurring patterns in difficulty and topic distribution. The Onsite Coding round is typically 45-60 minutes; the interviewer is calibrated against a specific rubric. The discriminator between candidates who advance and candidates who do not is rarely the final correctness of the answer. It is the path: did you clarify, did you verbalize your approach, did you handle edge cases, and did you communicate throughout.
How To Prepare for This Specific Round
Filter the questions below to the most recent reports (past 6-12 months). Questions tagged for this exact round type from this exact company at this exact role level are the highest-signal data available. Older reports may reference questions that have since rotated out of the company's pool.
Practice 4-6 representative problems from this set under timed conditions. The goal is not memorization (companies rotate questions); the goal is to internalize the patterns the interviewer typically reaches for and the depth of follow-up to expect. Reports on LeakCode also tag the typical follow-up depth at this round type, which is the discriminating signal between hire and no-hire calibration.
Onsite Coding Round Timing and Format
The Onsite Coding round at Salesforce typically runs 45-60 minutes. Use the first 2-3 minutes to clarify requirements; you should never start coding or designing without verifying the input/output format, constraints, and edge cases out loud. Use the next 5-7 minutes to verbalize your approach before writing any code. The middle 20-30 minutes are implementation. Reserve the final 10 minutes for testing with concrete examples and discussing optimization or trade-offs.
Time budget discipline is one of the most reliable senior-vs-junior discriminators in this round. Strong candidates verbalize where they are in their budget out loud ("I've used about 20 minutes, I have 15 minutes left for testing and one optimization"). This signals engineering maturity to the interviewer and creates positive feedback they can capture in writing.
Common Failure Modes in This Round
Reports tagged "no hire" at Salesforce Software Engineer Onsite Coding commonly cite: coding silently without verbalizing approach, jumping to implementation before clarifying requirements, missing edge cases (empty input, single element, very large input), producing working code that the candidate cannot refactor when asked, and failing to test their solution with concrete examples before declaring done.
The single most predictive failure mode in 2025-2026 reports: not asking clarifying questions. Interviewers at all FAANG companies are explicitly trained to weight this dimension. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's notes.
See All 95 Questions from This Round
Full question text, answer context, and frequency data for subscribers.
Get Access