Interview questions
Salesforce Developer Interview Questions
18 Salesforce developer interview questions on Apex, governor limits, triggers, LWC, integrations and deployment, with what to look for. For both sides.

What's here
18 Salesforce Developer interview questions, grouped into 4 areas: apex and governor limits, declarative versus code, and the ui, integration, testing and deployment and situational questions. Each one comes with why it is worth asking and what a strong answer contains, so the same question can be scored the same way by different interviewers.
- Ask candidates to fix a non-bulkified trigger on screen; it reveals real experience quickly.
- Probe the Flow versus Apex decision to see whether they think about long-term maintenance.
- Check security knowledge: sharing, field permissions and injection risks are often overlooked.
Cohesyve finds, contacts and tests Salesforce Developer candidates on the real work, then ranks them for these interviews. 14-day free trial for 10 candidates, not charged until it ends.
Preparing for this interview yourself? Practise it free →A Salesforce developer builds custom functionality on the Salesforce platform: Apex classes and triggers, Lightning Web Components, integrations with other systems, and automation that goes beyond what admins can configure. Because Salesforce is a shared, multitenant platform, good developers write code that respects governor limits and works on records in bulk. These questions test platform knowledge, coding habits and judgement about when to write code at all. Interviewers can use the 'what to look for' notes as a scoring guide; candidates can use them to prepare.
Apex and Governor Limits
Core coding on the platform and the constraints it imposes.
- 1
What are governor limits, and why does Salesforce enforce them?
Why ask it
Every Salesforce developer must design around them.What to look for
Limits on resources per transaction (such as SOQL queries, DML statements, CPU time and heap size) that stop runaway code monopolising shared resources on the multitenant platform. Strong candidates describe how they design to stay well within them. - 2
What does it mean to bulkify a trigger? Show how you would fix a trigger that queries inside a loop.
Why ask it
Non-bulkified code is the most common Salesforce bug.What to look for
Assuming triggers receive many records, collecting IDs into a set, one SOQL query outside the loop with an IN clause, building maps, and one DML statement on a list after the loop. - 3
What is your approach to structuring triggers?
Why ask it
Trigger sprawl makes orgs hard to maintain.What to look for
One trigger per object, logic moved into handler classes, clear order of operations, recursion control, and the ability to switch logic off for data loads. - 4
When would you use Queueable, Batch or Scheduled Apex, or a future method?
Why ask it
Asynchronous options handle work that would exceed synchronous limits.What to look for
Batch for very large data sets, Queueable for chained jobs and complex types, Scheduled for timed jobs, future methods for simple callouts or legacy cases. Awareness of monitoring and error handling for async jobs. - 5
How do you enforce security in Apex code?
Why ask it
Apex can bypass user permissions if written carelessly.What to look for
Using with sharing by default, respecting object and field permissions (for example user-mode queries or permission checks), avoiding SOQL injection with bind variables, and not exposing data through public methods.
Before the Salesforce Developer interviews, see who can do the work
Cohesyve finds and contacts Salesforce Developer candidates from your job description and tests each one on an AI job simulation of the role, so these questions go to a ranked shortlist. 14-day free trial for 10 candidates, not charged until it ends.
Declarative versus Code, and the UI
Knowing when to write code and how to build modern interfaces.
- 6
A business user asks for an automation. How do you decide between Flow and Apex?
Why ask it
Over-coding increases maintenance costs.What to look for
Preferring declarative tools when they can do the job maintainably, choosing Apex for complex logic, heavy data volumes or integrations, and considering who will maintain it. Awareness that Flows also consume limits. - 7
What are Lightning Web Components, and how do they differ from Aura components?
Why ask it
LWC is the current component model.What to look for
Built on web standards (modern JavaScript, custom elements) rather than Aura's own framework, and able to coexist with Aura components. Practical experience building one. - 8
How do you get data into a Lightning Web Component?
Why ask it
Tests practical LWC skills.What to look for
Lightning Data Service and wire adapters for standard record access, wired or imperative Apex calls for custom logic, caching considerations, and error handling in the UI. - 9
How do you handle the order of execution when a record is saved?
Why ask it
Unexpected interactions between automations cause bugs.What to look for
Understanding that validation rules, before and after triggers, flows and other automations run in a defined sequence, and designing so automations do not conflict or cause recursion.
Integration, Testing and Deployment
Connecting Salesforce to other systems and shipping changes safely.
- 10
How would you integrate Salesforce with an external system?
Why ask it
Most orgs connect to ERP, marketing or data platforms.What to look for
Choosing between REST or SOAP APIs, outbound callouts, platform events or middleware based on volume and timing, using Named Credentials for authentication, and handling errors and retries. - 11
How do you write good Apex tests?
Why ask it
Tests are required for deployment, but coverage alone is not quality.What to look for
Creating test data in the test (or with test factories), testing bulk cases, positive and negative paths, using assertions that check behaviour, and mocking callouts. Not writing tests just for coverage. - 12
How do you deploy changes between sandboxes and production?
Why ask it
Release discipline prevents outages.What to look for
Source control, Salesforce DX or a deployment tool, a pipeline through development, testing and staging sandboxes, running tests, and a rollback plan. Change sets are acceptable for smaller teams. - 13
Tell me about a performance problem you fixed in a Salesforce org.
Why ask it
Real examples show depth.What to look for
Diagnosing with debug logs or monitoring, finding the cause (inefficient queries, too many automations, large data volumes), and the fix, with honest reflection.
Situational Questions
How the candidate works with admins, users and messy orgs.
- 14
You inherit an org with many old triggers, Process Builders and Flows on the same object. What do you do?
Why ask it
Many orgs carry years of technical debt.What to look for
Inventorying automations, documenting what each does, consolidating carefully with tests, moving older automation to the tools the team now standardises on, and agreeing priorities with the admin team. - 15
A deployment fails in production because of failing tests you did not write. What do you do?
Why ask it
Tests realistic pressure.What to look for
Investigating the failures, fixing or working with the owner, not disabling tests to push through, and improving test reliability. - 16
A sales leader wants a feature by Friday that you think needs more design. How do you respond?
Why ask it
Developers must balance speed with maintainability.What to look for
Understanding the real need, offering a smaller version by Friday, explaining risks plainly, and agreeing a plan for the rest. - 17
How do you keep up with Salesforce releases?
Why ask it
The platform releases updates regularly.What to look for
Reading release notes, Trailhead modules, testing in preview sandboxes and following community resources. Certification, such as the Salesforce Platform Developer credential, is a plus but not a substitute for experience. - 18
How do you work with Salesforce admins on a project?
Why ask it
Developers and admins share the same org.What to look for
Agreeing who builds what, shared standards and naming conventions, documentation, and respect for declarative work.
Running the interview well
- 1Ask candidates to fix a non-bulkified trigger on screen; it reveals real experience quickly.
- 2Probe the Flow versus Apex decision to see whether they think about long-term maintenance.
- 3Check security knowledge: sharing, field permissions and injection risks are often overlooked.
- 4Ask about deployment and source control, especially for teams with several developers.
- 5Treat certifications as a signal, not proof; ask what they have built.
- 6Include a short integration question if the role connects Salesforce to other systems.
- 7Tell candidates which clouds and tools your org uses so they can give relevant examples.
Common questions
What questions are asked in a Salesforce developer interview?
Expect questions on Apex, governor limits, bulkified triggers, asynchronous Apex, security, Flow versus code, Lightning Web Components, integrations, testing and deployment, plus a coding exercise and scenario questions about real orgs.
What are governor limits in Salesforce?
They are limits on the resources a single transaction can use, such as the number of SOQL queries or DML statements. Salesforce enforces them so runaway code cannot monopolise resources on its shared, multitenant platform.
How do I prepare for a Salesforce developer interview?
Revise bulkification, trigger patterns, async Apex and security, build a small Lightning Web Component, and practise explaining when you would use Flow instead of code. Trailhead modules are a useful free resource.
Do I need a Salesforce certification to get a developer job?
Not always. Many employers value Salesforce certifications such as the Salesforce Certified Platform Developer credential, but practical experience and the ability to explain your code usually matter more.
What is the difference between a Salesforce admin and a Salesforce developer?
Admins configure the platform with declarative tools such as fields, page layouts, permissions and Flows. Developers write code (Apex, Lightning Web Components) and build integrations when configuration is not enough. The roles overlap.
What should I ask at the end of a Salesforce developer interview?
Ask which clouds the company uses, how deployments and source control work, how big the admin and developer team is, and what technical debt the org carries.
Save these questions for the Salesforce Developer candidates who can do the work
Cohesyve takes your Salesforce Developer job description, finds candidates, reaches out to them and runs an AI job simulation of the real work, then returns a ranked shortlist.
1,500+
assessments completed
50%
faster time-to-hire
5 min
from JD to assessment
14-day free trial · 10 candidates · Not charged until the trial ends
Preparing for a Salesforce Developer interview yourself? Practise on an AI job simulation of the role. 3-day free trial, cancel anytime.
From the blog