Salesforce Software Engineer Interview Experience

Salesforce interview reports show both a structured loop and some schedule changes. The two sources here cover an SMTS candidate in Hyderabad and a mid-level full-stack candidate in the US. Their questions are kept attached to the role and round where they were reported.

SMTS: coding and low-level design

The SMTS candidate reported an OA question asking for the longest string that is a subsequence of one input and a substring of another. The second OA problem was not remembered clearly, so it is omitted. In a later coding round, the prompts were to count hops between queried nodes in a directed graph and to compare two strings after applying # as a backspace. These are recorded in the Salesforce SMTS Hyderabad experience (2025).

The LLD round asked the candidate to design a parking lot, including class structure, database schema, and concurrency control for both threads in one application and a distributed system using a central database. The report describes the discussions but does not prescribe one design.

Mid-level full-stack: product design and coding

The US full-stack report included an Instagram or WhatsApp Stories design, then API design for an application like Ticketmaster. Its DSA rounds named Group Anagrams and Longest Common Prefix. The final round was changed to a trie-focused coding discussion, but the question was described only as similar to the prior round, so it is not reconstructed here. See the Salesforce full-stack report (2024).

How to prepare for the Salesforce interviews in these reports

For the SMTS graph prompt, state whether edges are directed and what to return when a destination is unreachable. For the parking-lot discussion, explain how you prevent two requests from claiming the same space. For the full-stack loop, prepare to connect API shape, storage, and failure handling. These are follow-up skills grounded in the reported tasks, not promises about Salesforce's current process.

For broader design practice, see system design interview questions and the interview experience hub.

More Salesforce candidate reports

These newer reports add campus, mid-level, backend, and frontend examples. The questions remain grouped by the report and role where they appeared.

AMTS campus interview

An India pool-campus account includes three questions about the candidate's technical choices and one implementation exercise:

1. Why did you choose a particular technology? (LeetCode Salesforce AMTS report)
2. Why did you make those implementation or design decisions? (same report)
3. Why did you choose that technology stack? (same report)
4. Implement an LRU Cache from scratch using OOP and production-ready code. (same report)

MTS and backend reports

A 2026 MTS account names an LRU Cache with O(1) get and put using a hash map and doubly linked list. It also describes a graph problem solved with DFS while tracking the maximum probability of reaching each node. (LeetCode Salesforce MTS report)

A backend SMTS report asks for rate limiting at different granularities: per user, per IP, per API key, and per tenant. (LeetCode Salesforce SMTS backend report)

A Bengaluru MTS account names a flash-sale system design prompt. (LeetCode Salesforce MTS report) Another SMTS account names cycle detection in a directed graph and asks why the candidate is leaving their current organization and where they see themselves in five years. (LeetCode Salesforce SMTS report)

AMTS Bangalore coding report

A January 2026 AMTS account names Number of Distinct Islands, described as a grid DFS problem. The post does not provide a fuller statement in the collected notes. (LeetCode Salesforce AMTS report)

SMTS frontend interview

A separate frontend report lists these prompts:

1. What CSS properties should be avoided for animation, and why are transform and opacity usually more performant? (LeetCode Salesforce SMTS frontend report)
2. What is semantic HTML, and why use semantic elements instead of only div elements? (same report)
3. What does forwardRef do, and what is useImperativeHandle? (same report)
4. How would you model the data for a chat application? (same report)
5. What is props drilling, and how can you address it? (same report)
6. What is client-side rendering, and when is it useful? (same report)
7. How would you improve Interaction to Next Paint (INP)? (same report)

The frontend list is a separate specialization from the backend and full-stack accounts above.

Other MTS questions

A separate MTS report asks the candidate to explain how quicksort works. (LeetCode Salesforce MTS report) Another selected MTS candidate reports being asked, “Why do you want to switch?” (LeetCode Salesforce MTS report)

Frequently asked questions

What was the exact trie question in the Salesforce full-stack report?

The candidate described a final trie-focused discussion as similar to an earlier round but did not give the question statement. This guide leaves it unnamed; the other reported prompts link to the original report.

Run it on Parlel

Choose a target role and team before you start contacting people. Parlel's company directory can help you map Salesforce hiring teams.