Salesforce SMTS Interview Experience — Hyderabad, 2025 (Offer)

How the process went

1. Application & recruiter contact

   Applied directly through Salesforce's careers site; a recruiter also reached out separately on LinkedIn around the same time.

2. Online Assessment

   Sent within two days of the first conversation with the recruiter.

3. Hiring drive

   After clearing the OA, the candidate was slotted into the upcoming hiring drive, held the same week (the candidate noted these usually take place on Fridays). It consisted of a coding round, a low-level design round, and a manager round, each run as an elimination stage.

4. Decision

   The candidate was informed of the outcome — an offer — the following Monday.

Online Assessment

Two coding problems combining string processing with hash map and priority queue logic

• Given two strings s1 and s2, find the length of the longest string s3 such that s3 is a subsequence of s1 and a substring of s2.
• A second problem that needed a combination of a hash map and a priority queue to solve; the candidate did not recall the exact prompt.

Coding round

Graph traversal and string comparison, run as an elimination stage

• Given a list of directed edges [ui, vi] and a list of queries [ai, bi], return a list of integers where each element is the number of hops needed to get from ai to bi.
• Given two strings containing letters and '#' characters, where '#' represents a backspace, return true if the two strings are equal after applying all backspaces, false otherwise.

The candidate solved both problems and felt confident about advancing to the next round afterward.

Low-Level Design round

Designing a parking lot, including class structure, schema, and concurrency handling

• Design a parking lot.

The candidate walked through a class structure using factory, strategy, and singleton patterns, discussed the database schema for the entities involved, and addressed the interviewer's follow-up questions on concurrency control — both for multiple threads within a single application and for a distributed setup backed by a central database.

The candidate described talking through the available options at each step, explaining the reasoning for each choice, and pausing periodically for the interviewer's questions; by the end the interviewer had no open questions left.

Manager round

Conversational discussion covering career background, engineering tradeoffs, and incident-response scenarios, including a shadow interviewer

• What is the biggest difference you've noticed between working at Amazon and Microsoft?
• Which problem from your earlier rounds did you enjoy most? (The candidate picked the parking lot design, which the manager then used as the basis for a longer discussion.)
• Using the same framing you gave earlier (agility and customer obsession versus caution and robustness), how would you adapt the parking lot application along those two lines, and what tradeoffs would you make?
• What would matter most to you, to your customer, or to your customer's customer?
• How would you think about different failure-handling and detection mechanisms?
• Describe an instance in your career where you had to debug a high-severity incident in a system you knew little about, and what steps you took.
• (Shadow interviewer) Walk me through how you'd handle discovering, the day before a launch, that something is broken in a part of the system owned by another team — from error discovery to identifying the right owner to fixing it before the launch.
• (Shadow interviewer) If you had to co-develop an app with a partner team, what would you do to ensure faster delivery? (The interviewer wanted a technical answer rather than a process-focused one.)

The candidate described this as one of the best managerial rounds they'd had, mostly conversational rather than a straight Q&A.

The manager gave positive verbal feedback at the end and called it a strong interaction.

Source

The questions and process facts come from the candidate's public write-up, linked below. The retelling above is our own summary.