Salesforce Interview SMTS | MissionForce Team | Hyderabad location
- Location
- Hyderabad
- Experience
- 6 years
- Posted
- 26 Mar 2026
Summary
I cleared the interview for an MTS-3 role at Salesforce in Hyderabad and received an offer with a base salary of ₹30 LPA.
How it went
6 YOE | Interview process took ~1 week
If you’re interviewing here — go nail it. Happy to answer questions in comments
🔹 Interview Process (4 Rounds)
Round 1: Coding Test Standard coding round.
Round 2: DSA Question was around Floyd Warshall algorithm (graph-based problem). (Easy one only)
Round 3: LLD Designed Splitwise Focus areas:
Equal split Percentage split Extensibility of expense types Clean object modeling
Round 4: Hiring Manager (40 mins) Conducted virtually (even though I was in office)
Interviewer joined ~10 mins late and seemed rushed
Questions asked:
Introduction Current level in team Conflict with manager (interrupted midway) Approach to add two polynomials Design Login System No clear requirements given Didn’t entertain clarification questions I explained auth flow, storage, security, etc. AI tools I use
💼 Offer Role: MTS-3 Base: ₹30 LPA Stock: $52K Bonus: ₹3 LPA Relocation: ₹1.5 L
I have asked Recuriter to **** OFF
Questions asked (4)
- 01
Floyd‑Warshall Algorithm Problem
Data Structures & Algorithms · Easy
Implement an algorithm to compute all‑pairs shortest paths in a weighted graph using the Floyd‑Warshall technique. The problem was described as an easy‑level graph‑based question.
- 02
Add Two Polynomials
Data Structures & Algorithms
Describe how to add two polynomial expressions together, handling coefficients and exponents appropriately.
- 03
Design Login System
System Design
Design a login system, covering authentication flow, data storage, and security aspects, without concrete requirements and without allowing clarification questions.
- 04
Design Splitwise‑like Expense Sharing System
System Design
Create a design for an expense‑sharing application similar to Splitwise, focusing on equal split, percentage split, extensibility of expense types, and clean object modelling.