Interview questions

Salesforce Developer interview questions — and what they probe

I've sat the Salesforce Developer interview loop at six companies in eight years — including Salesforce itself — and the questions barely change from one loop to the next. What changes is who passes: the candidates who answer the interviewer's intent instead of just the words. These are the questions that recur everywhere from service-company first rounds to product-team panels, each with what the interviewer is actually listening for.

Walk me through a trigger you've written. How did you bulkify it?

ProbingWhether you design for 200 records by default — bulkification, collections over per-record SOQL/DML, and knowing WHY governor limits force this.

What are governor limits and how have they shaped your code?

ProbingWorking knowledge (SOQL/DML/CPU limits) plus real war stories — limits you actually hit and the redesign that fixed them.

When do you choose Flow vs Apex?

ProbingJudgment, not dogma: declarative-first reasoning, where Flow breaks down (complex logic, bulk performance), and maintainability for admins after you.

Explain the order of execution when a record is saved.

ProbingDepth check — before/after triggers, validation, workflow/flow re-fires. You don't need every step verbatim; you need to reason about why a field 'mysteriously' changed.

How do you call an external API from Salesforce?

ProbingCallouts (REST/SOAP), named credentials, async requirements (future/queueable), and the classic gotcha: no callouts after DML in the same transaction.

What's the difference between LWC and Aura, and why does LWC exist?

ProbingPlatform currency — modern web standards, performance, and whether your LWC experience is real (wire adapters, lifecycle, component communication).

How do you test Apex? What does good coverage mean to you?

ProbingWhether 75% is a floor or a goal for you — assertions over coverage-chasing, test data isolation (@TestSetup), and testing bulk + negative paths.

Describe a deployment that went wrong. What changed after?

ProbingDevOps maturity — sandboxes, change sets vs SFDX/CI-CD, and whether you learn systemically (process change) or anecdotally (blame).

How to prepare

Anchor every platform answer in a real org: 'in our 400-user Service Cloud org…' beats textbook definitions.
When you don't know a limit's exact number, say how you'd find and design around it — reasoning beats memorisation.
Bring one story each for: a governor-limit fight, an integration, and a production incident. Most behavioral probes map to one of these.

Don’t read these — rehearse them. Renonym’s AI coach asks Salesforce Developer questions with follow-ups and scores every answer. First interview free.

Practise these questions now →

Frequently asked

More question guides