Salesforce · Software engineer · Senior MTS / Lead MTS
System Design
Spoken whiteboard-style discussion for experienced/senior candidates
What they actually ask
The question shapes this round uses. Larpy does not read these out. It builds each one from your own resume, because the generic version is the one you have already rehearsed.
- “Design the core CRM data model: accounts, contacts and opportunities.”
- “Design a multi-tenant store where every row carries a tenant, isolated across customers.”
- “Design customer-defined objects and fields as metadata, so upgrades do not break them.”
- “Design per-tenant limits so one heavy customer cannot starve the others.”
- “Design workflow automation: a customer builds a rule, and it fires reliably on changes.”
- “Design a bulk API that ingests millions of records without hurting live traffic.”
What this round is judged on
- Requirements gathering · clarifying scope and constraints first
- Architecture · sensible components and data model
- Scalability · availability and performance tradeoffs
- API design · clean, well-reasoned interfaces
- Communication · structured, tradeoff-aware reasoning
Where this round sits
Salesforce’s published process. Lime marks the stage this round runs.
- 01Recruiter Phone Screen
- 02Technical Phone Screen (Coding)
- 03Virtual Onsite Loopthis round
- 04Debrief & Team Match
What happens in each stage›
- Recruiter Phone Screen
- ~30 min spoken call covering background, motivation, logistics, target level, and compensation, plus light role fit.
- Technical Phone Screen (Coding)
- ~45-60 min live coding in a shared editor with an engineer or hiring manager; 1-2 data-structures/algorithms problems. New-grad and university pipelines may instead use a timed HackerRank online assessment.
- Virtual Onsite Loop
- Commonly 4-5 back-to-back rounds: two coding rounds (DS&A, one may lean practical/OOP design), one system design round (senior; often OOD or omitted for new grads), one behavioral/values hiring-manager round, and sometimes a project or team-fit deep-dive.
- Debrief & Team Match
- Panel debrief, recruiter delivers the outcome, and a team match may follow.
Sources
Built from what Salesforce publishes about its own process and from real interview data. No leaked question lists. The questions you get are generated against your own resume, so they are not from anyone else's interview.
Confirms the level ladder (Associate MTS, MTS, Senior MTS, Lead MTS, Principal Architect, plus higher tiers) and compensation. No interview-process detail.
General software-engineer interview loop structure (coding, behavioral, system design) and recommended coding topics (Grind 75 / Blind 75). Not Salesforce-specific.
Intended primary source for Salesforce's official hiring process and interview stages.
The five core values (Trust, Customer Success, Innovation, Equality, Sustainability), each confirmed present on this page 2026-08-16. Deliberately does NOT back the Ohana framing: the old Ohana story URL 404s and this page does not use the word.
Sources last checked . Hiring loops change, so this date is the honest limit on everything above.
Other Salesforce rounds
- Recruiter Phone Screen
Conversational and warm; recruiter maps your background to a level, gauges motivation for Salesforce specifically, and confirms logistics and comp expectations
- Technical Phone Screen (Coding)
Collaborative and hint-friendly rather than adversarial
- Onsite Coding (DS&A)
Deeper algorithmic round in a shared editor
- Object-Oriented Design
Salesforce is notably fond of practical OOP/low-level design
- Behavioral & Values (Hiring Manager)
Conversational, usually with the hiring manager