Salesforce software engineering interview questions

The Process

Five rounds, and the assessment cuts more people than the loop

01

15 to 30 minPhone call

Recruiter screen

Short, and mostly about levelling. The band written down on this call decides whether you get the SMTS loop or the MTS one, and it is hard to move later.

Settle the cloud before the level.
Sales Cloud, Service Cloud, Marketing Cloud, MuleSoft, Tableau and Slack hire separately and weight the rounds differently.
Ask whether your track has an assessment.
Some orgs send the HackerRank first, others go straight to a live screen. It changes what you should be practising this week.
Give one number for total compensation.
Base moves in narrow bands per level, so anchoring on salary alone caps you. The stock and the bonus are where the room is.

02

30 to 60 minVideo call

Hiring manager call

Genuinely evaluative, not a courtesy call, and it sits before the assessment rather than after it. Expect your last two years of work in detail, plus the first values questions of the process.

Bring the customer, not just the code.
Interviewers score whether you can say who used the thing you built and what changed for them. Most candidates only describe the system.
Know the product you would sit next to.
A working idea of what Sales Cloud or MuleSoft actually does separates you from candidates who applied to every SaaS company at once.
Have a reason for Salesforce specifically.
It gets asked here and again at the end. Wanting a large stable company is a true answer and a weak one.

03

60 to 90 minHackerRankNo AI tools

Online assessment

Two to three problems in 60 to 90 minutes, proctored with the camera on: dynamic programming, graphs, greedy, sliding window and arrays. The reported bar is about 80 percent, and this is the gate that eliminates most candidates.

Hidden tests decide the score.
Partial credit is real. Ship a correct brute force first, then optimise, because an elegant half finished answer scores nothing.
Budget the time before you read anything.
Ninety minutes across four problems is under twenty five each. Skipping the hardest one on purpose is usually the right call.
Practise in the language you will use.
The editor has no autocomplete worth having and no debugger. Fluency in the syntax beats another week of theory.

04

4 to 6 rounds3 to 5 hoursVirtual

The onsite loop

One or two coding rounds, multi tenant system design, a values round against the five values, and a hiring manager deep dive. Full stack roles get a browser build instead of one coding round.

System design here means multi tenancy.
Tenant isolation, request routing, per org quotas and governor limits. Generic design a social feed prep does not transfer.
Front end candidates get front end problems.
A progress bar, a typeahead, a virtualised list, in plain JavaScript with no framework. The rounds are language specific by design.
Every interviewer scores values too.
The behavioural round is not the only place they are marked. Trust and Customer Success get scored inside the coding rounds.

05

30 to 45 minThen 1 to 2 weeks

Executive round and offer

A director or VP conversation, but only for LMTS and above. Below that band this stage is purely offer approval, and that approval is where most of the waiting in the process actually sits.

Only lead and above get a real round.
At LMTS and PMTS a director or VP will probe scope and stakeholder judgement. At AMTS, MTS and SMTS the slot is never booked, so the stage is paperwork.
Most of the wait lives in this stage.
The interviews move quickly. Offer approval and panel scheduling are what turn four weeks into eight, so ask for the approval date rather than a feeling.
The manager owns the offer.
There is no separate hiring committee. Feedback lands back with the hiring manager, which is why round two rapport matters.

Levels and Pay

Base moves in small steps. The stock does the work

Pick a level to see how the package splits, what changes by city, and what the loop actually asks of you at that band. The ladder does continue past PMTS, but what sits above it is a parallel Architect and Distinguished track rather than the next rung.

San Francisco

Seattle

Indianapolis

Atlanta

Level	Experience	Total comp
Software EngineerAMTSEntry	0 to 2 yrs	~$176K
Software EngineerMTSMid	2 to 5 yrs	~$227K
Senior EngineerSMTSSenior	5 to 9 yrs	~$317K
Lead EngineerLMTSLead	9 to 12 yrs	~$412K
Principal EngineerPMTSPrincipal	12+ yrs	~$552K

Live Question Feed

What Salesforce is asking right now

40 questions · new ones added every 7 days

40 Verified

SYSTEM DESIGN

Design per tenant rate limiting for a shared API: quota accounting, burst allowance, and what happens when one org floods the cluster.

The onsite loop

60 min

Shared editor

Reported 8 times

Open

SYSTEM DESIGN

Design webhook delivery for an integration platform: retries, idempotency, dead letter queues, per org isolation.

Locked

VALUES

Tell me about a time you put a customer outcome ahead of your team's preferred design.

Locked

CODING

Given a weighted directed graph, find the cheapest route with at most K stops and bound the memory.

Locked

FRONT END

Build a progress bar in plain JavaScript with smooth animation, a percentage readout and screen reader support.

Locked

SYSTEM DESIGN

Design tenant isolation for a shared database: noisy neighbours, per org quotas, and what breaks first.

Locked

BEHAVIORAL

Describe a disagreement about technical direction that you lost, and what you did afterwards.

Locked

CODING

Count the ways to make a target from a set of values, then extend it to report one valid combination.

Locked

VALUES

Which of the five values is hardest for you to demonstrate at work, and why?

Locked

39 more questions available

The exact questions Salesforce is asking this week, tagged by round and difficulty.

Unlock All 40 Questions

Each question stays in the bank for 14 days, so everything here was asked in the last 14 days. Candidates who see them first pass at 3.2 times the normal rate.

Get Full Access

The Unfair Advantage

Why this actually works

01

Real questions, not guesses

Collected from engineers who sat the loop, then cross validated against other intel sources.

02

Fresh every week

The database updates every 7 days, so you never study stale problems.

03

Covers every round

Coding, multi tenant system design, front end builds, the values round and the HackerRank assessment.

04

120+ companies tracked

Also interviewing at Oracle, Workday or Adobe? We have their questions too.

05

Difficulty and pattern data

Tagged by difficulty, round and category, so you know where prep time goes.

06

Candidate verified only

Reported by a candidate, then cross verified against multiple data points.

3.2×

Higher pass rate

120+

Companies tracked

3.2K+

Engineers using this

FAQ

Common questions

How are the questions sourced?

Directly from engineers who interviewed at Salesforce, then cross validated against other intel sources into a stack ranked list.

How often are questions updated?

We add new questions every 7 days and retire each one after 14 days, so the bank turns over twice in the window it covers. Each Salesforce cloud calibrates its own coding and design rotation, so Marketing Cloud and MuleSoft drift apart while the values questions stay shared.

Does Salesforce ask LeetCode questions?

Yes. The assessment leans on dynamic programming and graphs, the onsite sits at medium. The rounds are language specific though, so full stack candidates get browser problems.

Can I use AI tools in the interview?

No. The assessment is proctored and the live rounds are watched. Salesforce states it in the candidate instructions and does act on it.

What is the Salesforce values round?

A scored conversation about Trust, Customer Success, Innovation, Equality and Sustainability, sat inside the onsite panel rather than after it. Prepare it like a technical round. Clean code does not rescue a weak showing.

What does Salesforce pay an MTS?

Around $227K in San Francisco, about $150K in Indianapolis. Roughly a sixth is RSUs on a four year vest, and the bonus is a target rather than a promise.

How long does the process take?

Four to eight weeks. The assessment turns around quickly, but scheduling a four to six person panel is what stretches it, not the interviews themselves.

Is this just for Salesforce?

No. GothamLoop covers 120+ companies including Google, Amazon, Oracle, Adobe and Stripe.

The Salesforce interview cheat code nobody talks about

Five rounds, and the assessment cuts more people than the loop

Recruiter screen

Hiring manager call

Online assessment

The onsite loop

Executive round and offer

Base moves in small steps. The stock does the work

What Salesforce is asking right now

Why this actually works

Real questions, not guesses

Fresh every week

Covers every round

120+ companies tracked

Difficulty and pattern data

Candidate verified only

Common questions

Pricing plan

Company Interview Guides