Salesforce SMTS Interview: A Level Bump to LMTS That Ended in Rejection
Updated July 17, 2026
A candidate with roughly eight years of experience interviewed for a Senior Member of Technical Staff (SMTS) role at Salesforce, going through an onsite loop in mid-October. The candidate describes the overall process, from first contact to final decision, as spanning about a month and a half.
The candidate performed well across a coding round, a high-level design round, and a hiring-manager round, and a recruiter later confirmed the SMTS bar had been cleared. Because the candidate's compensation expectations were above the SMTS band, the recruiter proposed evaluating the candidate for the higher Lead Member of Technical Staff (LMTS) level instead, which added one more interview. That final round did not go as well as the earlier ones; the recruiter then delivered a no-go decision for LMTS. The recruiter mentioned a possible future LMTS opening, but the candidate chose to treat the outcome as a rejection and move on.
How the process went
Application and scheduling
Candidate went through application and scheduling ahead of an onsite interview held on October 14; the candidate reports the overall process took about a month and a half.
Onsite loop
The onsite consisted of a coding round, a high-level system design round, and a hiring-manager round.
Recruiter check-in
After the onsite, a recruiter called to say the candidate had cleared the bar for the SMTS level.
Compensation mismatch and level review
Because the candidate's target compensation exceeded the SMTS band, the recruiter proposed processing the candidate for the higher LMTS level instead, which required one additional interview.
Final decision
The extra round covered low-level design. Afterward, the recruiter delivered a no-go decision for the LMTS level, while mentioning that another LMTS opening might come up later; the candidate treated the outcome as a rejection.
Round 1 - Coding
Algorithmic problem solving
- Print all paths from the top-left corner to the bottom-right corner of a grid.
- Implement a basic calculator that evaluates a string expression, in the style of the Calculator III problem.
Candidate reported this round went well overall.
Round 2 - High-Level Design
System design for a business rules engine
- Design a rule engine for a banking system that applies conditional logic, such as granting a discount percentage based on a customer's salary and how long their account has been open.
Candidate considered this the strongest round of the loop.
Round 3 - Hiring Manager Round
Past project deep dive plus applied system design
- Discuss a past project in depth, including a request to adjust part of the design on the spot.
- Design a system for displaying live match scores, similar to a sports-streaming app.
- Additional standard interview questions not detailed in the original account.
Final Round - Low-Level Design (LMTS)
Schema design and search internals
- Design Stack Overflow, including the underlying data schema.
- Write code implementing part of the design.
- Explain how the search functionality for the system would work.
- Describe the data structures behind how a search engine such as Elasticsearch indexes and searches data, including structures like LSM trees.
Candidate said the question on search internals and data structures was the weak point of this round.
Key takeaways
- A strong performance across every round does not guarantee a specific level or offer outcome; a compensation mismatch can trigger an additional round tied to a different level partway through the process.
- For rule-engine or policy-style design prompts, practice translating business conditions such as tenure and salary tiers into a structured decision model rather than a simple description of rules.
- When asked about search internals, be ready to go beyond the high-level design and explain the data structures an indexing system relies on, such as LSM trees.
- If interviewers ask for a schema-heavy design like a Q&A platform, practice writing both the schema and supporting code, since both were requested in this loop.
- If a recruiter proposes an additional round tied to a higher level after an initial pass, treat it as a distinct evaluation rather than a formality, since the outcome can differ from the earlier rounds.
Practice a Salesforce interview
Rehearse out loud against the kinds of questions in this story — with an AI interviewer that asks follow-ups.
Practice this interviewSource
The questions and process facts come from the candidate's public write-up, linked below. The retelling above is our own summary.
Candidate's public write-up on LeetCode Discuss