Got the offerMember of Technical Staff (MTS) at Salesforce
- Difficulty
- Process took
- 2-3 Weeks
- Rounds
- 4
- Format
- Remote
- Applied via
- Referral
How it went
- These interviews are not just about cracking problems, they are about showing that you can think like a builder.
- Can you solve problems under constraints?
- Can you explain your trade-offs clearly?
- Can you design systems that are reliable, not just functional?
What they would tell you
- These interviews are not just about cracking problems, they are about showing that you can think like a builder.
- Can you solve problems under constraints?
- Can you explain your trade-offs clearly?
- Can you design systems that are reliable, not just functional?
How to prepare
- In some rounds, the problems were known, but the constraints were tighter, which tested how well I could adapt existing patterns under pressure. So it is not enough to just solve, you need to be able to tweak your solutions quickly when conditions change.
- If you’re preparing for a role like MTS at Salesforce or similar product companies, do not just grind DSA problems blindly ,focus on depth and adaptability.
Round by round
- 1
Online Assessment90 min
The questions were familiar, but the tricky part was the constraints, they were stricter than usual.
- 2
DSA Round60 min
The first question was similar to one I’d seen before, but with a twist, the subset had to be sorted, and the input was a string. For the second one, I couldn’t crack the optimal solution, which was a bit disappointing, but I explained my approach clearly.
- 3
HM60 min
This round was a mix of behavioral and technical questions. It started with some behavioral questions How do you prioritize tasks when you are overloaded? and there were a couple more questions, but I just can’t recall them right now.
- 4
High-Level Design60 min
I initially expected this to be a standard LLD round, but to my surprise, it turned into more of an HLD discussion. The interviewer asked me to design a Notification System, and we went deep into how it should work end-to-end. We talked about sending different types of notifications like emails, SMS, and push, and then focused a lot on how to handle failures, add retries, and make sure the messages are always delivered. He also asked me about what kind of database I would use, and when to use things like queues or caching.
What came up
A candidate-reported account, lightly edited. Interview processes change by team and date.