Salesforce MTS Interview Experience for Experienced Candidate
Interview Experience
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 –
Full Details
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 Technical (Virtual) Special Subarrays Count subarrays whose element product has an odd number of divisors. Subsequence + Substring Find the maximum length string that is a subsequence of x and also a substring of y. - Live coding with continuous explanation. - Got hints on an edge case and fixed it. - All test cases
passed.
Round 2 Technical (Virtual) Remove K Duplicates Repeatedly remove k consecutive identical characters from a string until stable. IPO Share Allocation Allocate shares based on highest price, then earliest timestamp, with round-robin distribution for equal prices;
return users who get no shares. - Optimized solutions quickly. - Discussion on time & space complexity. - All test cases
passed. - Couple of behavioural questions and discussion on current project.
Round 3 Hiring Manager (Virtual) Deep dive into recent project Multiple behavioral and situational questions Grilling around: - Reason for job change & reliability - Mentoring juniors - Design decisions & ownership in current project - Understanding of SDLC & testing methods - Fit for SD2-level role
Round 4 Technical (Offline) Resume discussion + design of an agent workflow to process bank documents LRU Cache implementation (interviewer expected a specific approach) String transformation problem: After each pass, A → AB, B → A; determine result after N passes Mix of coding, design, and behavioral discussion
Round 5 Hiring Manager (Offline) More technically deep than earlier HM round Design discussions around microservices, kafka, APIs Situational and decision-making scenarios Got the offer around 3-4 days later. Overall, the interview process was structured and smooth.
About This Question
This is a candidate experience report from a salesforce interview for a swe role during the coding round reported in 2026.
It covers the following topics: Arrays, Strings, Probability Stats, System Design, Behavioral .
More Salesforce Interview Questions
About Salesforce Interview Reports
This question was reported by a candidate who interviewed at Salesforce. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Salesforce are the higher-signal extractions to take from this report.
For broader preparation context, the Salesforce interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Salesforce reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Salesforce Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Salesforce reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. 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 written notes.