The Salesforce interview questions you are most likely to face in 2026 test four things: how the data and security model works (admin), how Apex behaves under governor limits (developer), how Lightning Web Components are built (front end), and how Salesforce connects to other systems (integration). This guide gives the common questions for each, short model answers, and the scenario questions that decide most interviews.
This post was first published in 2021 as a list of 71 questions. It has been rewritten for 2026: fewer, better questions, grouped by role, with answers checked against Salesforce's own documentation and links to deeper guides.
What do Salesforce interviewers actually test?
Interviewers test whether you can choose the right tool and explain the trade-off, not whether you can recite definitions. Very few interviews are a quiz. A good interviewer asks a definition, then pushes: why, when would you not, what breaks. Use this table to focus your preparation.
| Role | Core topics | What a strong answer shows |
|---|---|---|
| Administrator | Security model, data model, Flow, validation rules, reports | You choose the least powerful tool that does the job |
| Apex developer | Governor limits, triggers, order of execution, async Apex, tests | You write bulk-safe code and know why limits exist |
| LWC developer | Lifecycle hooks, decorators, wire service, events | You know when the framework re-renders and who owns data |
| Integration | Patterns, APIs, credentials, error handling | You match the pattern to volume, timing and failure modes |
| Consultant or BA | Requirements, process design, adoption | You ask questions before proposing a build |
Salesforce admin interview questions
Admin rounds focus on security, the data model, automation choices and sandboxes.
How does Salesforce control who sees what?
Access works at four levels, as Trailhead's Data Security module lays out: the organization (who can log in, from where and when), objects (create, read, edit, delete), fields (field-level security) and records. Object and field access are best granted with permission sets and permission set groups. Record access starts from org-wide defaults set as restrictive as possible, then opens up through the role hierarchy, sharing rules and manual sharing. The module also notes that these permissions apply to API calls too.
What is the difference between a lookup and a master-detail relationship?
In a lookup, each object can stand alone; the relationship is optional. In a master-detail relationship the detail record cannot exist without its master, deleting the master deletes the details, and the master controls who can see the detail's data (Trailhead, Object Relationships). Roll-up summary fields (COUNT, SUM, MIN, MAX) need master-detail; Salesforce Help's Object Relationships Overview says lookups don't support them.
When would you use a validation rule instead of a Flow?
Use a validation rule when you only need to block bad data with a clear message, for example a close date in the past on an open opportunity. Use a Flow when you need to change data or take an action. Both run inside the save, so knowing the order of execution helps you explain what fires first.
What replaced Workflow Rules and Process Builder?
Flow. Workflow Rules and Process Builder reached end of support on 31 December 2025, so new automation should be built in Flow Builder; our Salesforce Flow guide covers record-triggered, screen and scheduled flows. Expect a follow-up on before-save versus after-save flows.
What is a sandbox and which one do you use for UAT?
A sandbox is a copy of production for building and testing. Partial Copy suits most user acceptance testing; Full suits performance tests and data migration rehearsals. See our sandbox guide for the four types.
Apex developer interview questions
Apex rounds test bulk-safe code, governor limits, asynchronous Apex, testing and sharing.
- What are governor limits and why do they exist? Salesforce is multi-tenant, so each transaction has caps on queries, DML statements, CPU time and heap. Answer with an example of a limit you hit and how you fixed it. Our governor limits guide has the full table.
- What is the Apex heap limit, and how do you avoid a heap overflow? As of November 2026, Winter '27 raises the heap from 6 MB (synchronous) and 12 MB (asynchronous) to 10 MB and 25 MB, with all orgs getting the new limits from Spring '27. Avoid overflows by querying only the fields you need, processing large sets in SOQL for loops or Batch Apex, and clearing collections you no longer need.
- insert or Database.insert? A DML statement such as insert is all or nothing: one bad record throws an exception and nothing is saved. Database.insert(records, false) allows partial success; per the Apex Developer Guide's bulk DML exception handling, it returns a SaveResult for each record, and you read getErrors() on the failed ones instead of catching an exception.
- How do you write a bulk-safe trigger? One trigger per object, logic in a handler class, no SOQL or DML inside loops, collect IDs into a Set and query once into a Map. See Apex triggers and Apex collections.
- Before or after trigger? Before triggers change fields on the records being saved without extra DML; after triggers work with record IDs and related records.
- Future, Queueable, Batch or Schedulable? Future for simple fire-and-forget callouts; Queueable when you need to pass complex types or chain jobs; Batch for large data sets processed in chunks; Schedulable to run on a timetable.
- How do you test Apex? Create your own test data, test bulk cases (200 records), assert outcomes rather than just covering lines, and use Test.startTest and Test.stopTest around asynchronous work.
- with sharing, without sharing, inherited sharing? They decide whether the class respects the running user's record access. Default to with sharing or inherited sharing and justify any without sharing.
Lightning Web Components (LWC) interview questions
LWC rounds test lifecycle hooks, decorators, data access and how components talk to each other. These replace the old Aura-era "Lightning interview questions". Expect most of them in any front-end round.
- Name the lifecycle hooks. constructor(), connectedCallback(), renderedCallback(), disconnectedCallback() and errorCallback(), per the LWC lifecycle guide. connectedCallback runs when the component is inserted into the DOM and can run more than once, so guard one-time setup. errorCallback catches errors from descendants, not from the component itself.
- What do @api, @track and @wire do? @api makes a property or method public to a parent. Since Spring '20 all fields are reactive, so @track is only needed to observe changes inside an object or array. @wire provisions read-only data from a wire adapter or a cacheable Apex method. Salesforce's decorators reference covers each.
- Wire or imperative Apex? Wire for reads that should refresh when a reactive parameter changes (prefix it with $); imperative calls for writes, or when you control the timing, such as on a button click.
- How do components communicate? Parent to child through @api properties and methods; child to parent through custom events; unrelated components through Lightning Message Service.
- Why not update a property in renderedCallback? It can trigger another render and an infinite loop.
- What is view state? A Visualforce question for orgs with older pages: the state Visualforce keeps between requests. Our view state guide explains the limit and fixes.
Salesforce integration interview questions
Integration rounds test whether you can match a pattern and API to the volume, timing and failure modes. Start every answer with the pattern, then the technology. Salesforce's Integration Patterns overview names six:
| Pattern | What happens | Typical example |
|---|---|---|
| Request and Reply | Salesforce calls a remote system and waits for the answer | Credit check before saving an order |
| Fire and Forget | Salesforce starts a remote process and does not wait | Send a closed opportunity to the ERP |
| Batch Data Synchronization | Bulk create or refresh of data in either direction | Nightly product and price load |
| Remote Call-In | An external system reads or changes Salesforce data | Web portal creates cases through the REST API |
| UI Update Based on Data Changes | The Salesforce UI refreshes when data changes | Live status on a service console |
| Data Virtualization | Salesforce reads external data in real time without storing it | Showing invoice history held in the ERP |
- REST, SOAP or Bulk API? REST for most record-level work, SOAP where a strongly typed contract is required, Bulk API 2.0 for large asynchronous loads.
- How do you store credentials for a callout? In a named credential, which holds the endpoint URL (https only), linked to an external credential that holds the authentication. Salesforce Help marks legacy named credentials, which held both, as deprecated.
- How do you handle failures? Retries with backoff, an error log object or platform event, idempotent keys (external IDs with upsert) so a retry does not create duplicates, and an alert when a sync falls behind.
Scenario-based Salesforce interview questions
Scenario questions decide most interviews: name the tool, why, and what could go wrong.
- Sales managers must approve discounts over 20 percent. An approval process (or a Flow-based approval) with an entry criterion on the discount field, a validation rule to stop edits while pending, and an email alert.
- A trigger works in testing but fails on a data load. It is not bulk-safe: a query or DML statement inside a loop. Rewrite it to collect IDs and query once.
- Two departments need different fields and picklist values on the same object. Record types with their own page layouts or Dynamic Forms, plus picklist values per record type.
- Users can see records they should not. Check org-wide defaults first, then roles, sharing rules, public group membership and any "View All" permissions on profiles and permission sets.
- The ERP needs new accounts within a minute. Fire and forget through a platform event or an asynchronous callout from Flow or Queueable Apex, with a retry plan.
How to prepare for a Salesforce interview
Build something real, earn the credential for your role and prepare stories about problems you solved.
- Build something in a free Developer Edition org and be ready to explain the choices.
- Earn the credential for your role: Salesforce Certified Platform Administrator for admins, Salesforce Certified Platform Developer for developers.
- Prepare two stories about a problem you solved, with the trade-off you made.
- Know what is retired or legacy: Workflow Rules and Process Builder (end of support 31 December 2025; use Flow) and Salesforce Classic (legacy; use Lightning Experience).
- Read up on how the platform runs a save: the order of execution and validation rules come up in almost every admin and developer round.
- Ask the interviewer about their org: edition, size, release process. It shows you think like someone who will run it.
Getting help
Hiring rather than interviewing? Techila is a Salesforce Summit Partner. You can hire a Salesforce developer from our team, or talk to us about the skills your project needs.
Frequently asked questions
What are the most common Salesforce interview questions?
For admins: the data security model (org-wide defaults, roles, sharing rules, permission sets), lookup versus master-detail relationships, validation rules and Flow. For developers: governor limits, trigger design, the order of execution, asynchronous Apex and Lightning Web Components. Most interviews also include a scenario question.
How do I answer scenario-based Salesforce interview questions?
Restate the requirement, ask one or two clarifying questions, propose the simplest declarative solution first, then say when you would switch to code and why. Mention limits, security and testing. Interviewers score the reasoning more than the final answer.
What LWC questions are asked in Salesforce interviews?
The lifecycle hooks (constructor, connectedCallback, renderedCallback, disconnectedCallback, errorCallback), the @api, @track and @wire decorators, how parent and child components communicate, when to use the wire service versus an imperative Apex call, and how Lightning Data Service caches records.
What integration questions come up in Salesforce interviews?
Which integration pattern fits a requirement (request and reply, fire and forget, batch data synchronization, remote call-in, UI update based on data changes, data virtualization), which API to use for the volume, how named and external credentials store authentication, and how to handle errors and retries.
Do I need a certification to get a Salesforce job?
Not always, but many employers and partners ask for one. Salesforce Certified Platform Administrator is the usual first credential for admins and Salesforce Certified Platform Developer for developers. Hands-on work you can explain counts as much as the badge.