Salesforce Developer Interview Question Guide

This guide provides a comprehensive set of basic-to-intermediate interview questions for screening
Salesforce Developer candidates. It covers eight key topics – Apex, Lightning Web Components (LWC), Apex
Triggers, Admin Configuration, Security, Governor Limits (Apex), Sales Cloud, and Flows – each with an
overview of assessed skills and a series of labeled questions. Each question comes with a concise answer
hint for interviewers. The report also includes two practical sample tasks (easy and intermediate) with
acceptance criteria and estimated completion times, as well as a summary table of question counts and
difficulty distribution across topics. Reference links from Salesforce documentation, Trailhead, and
authoritative sources are provided for key concepts.

Apex (Programmatic Backend Development)

Apex is Salesforce’s server-side, strongly typed, object-oriented language (similar to Java) used to
implement custom business logic and data processing on the platform 1 . These questions assess
understanding of Apex syntax, classes, collections, SOQL, and fundamental coding practices.

• (Basic) What is Apex and why is it used? – Apex is Salesforce’s proprietary, strongly-typed OO language
used to write custom logic and automation on the platform 1 . It runs on Salesforce servers and
lets developers enforce complex business rules beyond declarative tools.
• (Basic) What is SOQL and how is it used? – SOQL (Salesforce Object Query Language) is used to query
Salesforce data in Apex. It has SQL-like syntax for selecting fields from a single object or related
objects 2 . For example, [SELECT Name FROM Account WHERE Industry = 'Tech'] retrieves
matching Accounts.
• (Basic) What is an sObject in Apex? – An sObject is a Salesforce object instance (like a row in a table).
Standard objects (Account, Contact, etc.) and custom objects are both sObjects. You use sObjects in
Apex to manipulate record data (e.g. Account acct = new Account(Name='Acme'); ).
• (Basic) What are List, Set, and Map in Apex? – These are built-in collection types. A List is an ordered
collection (like an array), a Set holds unique values, and a Map holds key-value pairs. For example,
List<Account> lst , Set<Id> idSet , and Map<Id, Contact> .
• (Intermediate) What is an Apex class and how do you define one? – An Apex class is a template for
objects and contains methods/variables. You define it with keywords like public class MyClass
{ ... } . Classes can have constructors, methods, properties, and inner classes.
• (Intermediate) What are static methods/variables in Apex? – static members belong to the class
rather than an instance. A static method or variable is shared across all instances. Use static for
utility methods or to hold state across trigger contexts.
• (Intermediate) How do you handle exceptions in Apex? – Use try-catch blocks. For example:

try {
// DML or other operations
} catch (Exception e) {

1
 // handle error, [Link]()
}

This catches runtime errors (governor-limit or other exceptions) and prevents uncaught failures.

• (Intermediate) What is a test class and why is it required? – A test class is Apex code annotated with
@isTest that exercises your code. Salesforce requires at least 75% code coverage from tests
before deploying Apex. Tests verify functionality and help catch issues early.
• (Intermediate) When should you use Batch Apex or @future methods? – Use Batch Apex for
processing large data volumes (millions of records) in manageable chunks. Use
@future(callout=true) for asynchronous callouts or to break up work; future methods run in a
separate context with their own limits.
• (Intermediate) How do you avoid hardcoding IDs or URLs in Apex? – Use Custom Settings ,
Custom Metadata , or labels to store such values. For example, store endpoint URLs in a hierarchy
setting and retrieve them in Apex, rather than hardcoding strings.

Lightning Web Components (Client-Side UI Development)

LWC is Salesforce’s modern UI framework built on web standards (HTML, CSS, JavaScript). These questions
test understanding of the component lifecycle, data binding, and communication between Apex and LWC.

• (Basic) What is a Lightning Web Component (LWC) and how does it differ from Aura? – LWC is Salesforce’s
lightweight, standards-based UI framework using modern JS. Unlike the older Aura framework, LWC
uses native web standards (ECMAScript modules, Shadow DOM, etc.), making it faster and easier for
web developers 3 . Salesforce encourages LWC over Aura for new components.
• (Basic) What are the main LWC lifecycle hooks? – Key hooks include constructor() ,
connectedCallback() , renderedCallback() , disconnectedCallback() , and
errorCallback() 4 . For example, connectedCallback() runs when the component is
inserted into the DOM; renderedCallback() runs after the component’s template has been
rendered 4 .
• (Basic) How do you call an Apex method from an LWC? – Annotate the Apex method with
@AuraEnabled(cacheable=true) and make it static . In the component JS, use the @wire
decorator or import the method for imperative calls. The wire service will automatically invoke the
method and cache results 5 .
• (Basic) What does the @api decorator do in LWC? – @api marks a public property or method. Public
properties can be set by a parent component, and public methods can be called from outside. This is
how you expose functionality or data (e.g. recordId) to other components.
• (Intermediate) How do components communicate in LWC? – Child-to-parent: dispatch a CustomEvent
from the child; parent listens and handles it. Parent-to-child: set a public @api property on the
child. For unrelated components: use the Lightning Message Service (pub-sub or LMS) to share
events across the app.
• (Intermediate) How do you retrieve Salesforce record data without writing Apex in LWC? – Use Lightning
Data Service or LDS (e.g. lightning-record-form / -view-form ) or the getRecord wire
adapter from lightning/uiRecordApi . These automatically get/save records and enforce
security without Apex code.

2
 • (Intermediate) What is refreshApex() and when is it used? – When using @wire to call Apex,
cached data may become stale. Calling refreshApex() on the wired property forces the wire
service to re-invoke the Apex and refresh the data in the component. This is useful after data
changes.

flowchart LR
A[Constructor()] --> B[connectedCallback()]
B --> C[renderedCallback()]
C --> D[disconnectedCallback()]
C --> E[errorCallback()]
classDef error fill:#fdd;

Apex Triggers (Data Change Automation)

Triggers execute Apex before or after records are saved. These questions check knowledge of trigger
contexts, best practices, and bulk data handling.

• (Basic) What is an Apex trigger? – A trigger is Apex code that runs before or after DML events (insert,
update, delete, undelete) on Salesforce records. Triggers allow you to perform custom logic (e.g.
validation or related record updates) when records change 6 .
• (Basic) When would you use a “before” trigger vs an “after” trigger? – Before triggers run prior to
saving the record. Use them to update or validate the record itself (since you can modify
[Link]). After triggers run after the record is saved (and has an Id); use them for operations
that require the record ID or for related records (e.g. sending email, logging, creating child records).
• (Basic) What are [Link] and [Link] ? – These are context variables in triggers.
[Link] is a list of the new versions of the sObject records (available in before/after insert,
update, undelete). [Link] is a list of the old versions (available in update and delete). For
example, [Link][0].Name is the new name in an update 7 .
• (Basic) How do triggers handle bulk operations? – Triggers can process up to 200 records at once in a
single execution context. Always write bulkified logic: loop over [Link] collections rather than
assuming one record. Avoid SOQL/DML inside loops and use collections to handle all records in bulk.
• (Basic) What is a trigger recursion and how can you prevent it? – Recursion happens if a trigger updates
a record and re-invokes itself (infinite loop). Use a static Boolean flag or a handler class to track if the
trigger has already run in this context, and skip logic on subsequent entries. This ensures the trigger
logic runs only once per transaction.
• (Intermediate) What is a trigger handler (helper) class? – A handler class is a best practice pattern
where you place trigger logic in a separate Apex class (not in the trigger body). The trigger (one per
object) then simply calls the handler class methods. This promotes reuse and cleaner code.
• (Intermediate) How do you bulkify a trigger? – Write logic to handle lists of records. For example,
accumulate record IDs into a Set, then perform one SOQL query on all those IDs outside of a loop.
Perform one DML statement on all modified records at once. Use maps, sets, and lists instead of per-
record processing.
• (Intermediate) What is order of execution for triggers? – Generally: validations (including duplicate
rules) run first, then before triggers, then system processes (workflow, processes, flows), then after
triggers, and finally post-commit actions. Understanding this helps troubleshoot conflicting
automation. (Salesforce docs detail the full order of execution.)

3
Admin Configuration (Declarative Setup)
These questions assess familiarity with core Salesforce setup: object/field design, page layouts, record
types, data import, and related configuration.

• (Basic) What is a lookup relationship vs a master-detail relationship? – A lookup is a loose parent-child

relationship between two objects (child can exist without parent). A master-detail is a stronger
relationship: the detail record’s ownership and sharing are controlled by the master. In master-detail,
deleting the parent deletes the child, and you can create roll-up summary fields on the master 8 .
• (Basic) What is a junction object? – A junction object is a custom object with two master-detail
relationships, used to create a many-to-many relationship between two objects. It has two parent
objects (e.g. connecting Account and Product) and can link multiple records of each side 9 .
• (Basic) What is a record type? – A record type lets you offer different business processes, picklist
values, and page layouts to users. For example, you might have two Opportunity record types for
different sales processes (with different stage picklists and layouts). Record types allow multiple
page layouts per object, tailored to profiles 10 .
• (Basic) What is a page layout? – A page layout controls which fields, buttons, and related lists appear
on a record’s detail page in Salesforce. For example, a page layout determines the “Details” and
“Related” fields tab shown to the user. You can assign different page layouts to different profiles/
record types 11 .
• (Basic) What is a Lightning record page? – A Lightning Page (via Lightning App Builder) defines the
arrangement of components on a record page in Lightning Experience. It can include fields, related
lists, Lightning components, and dynamic sections. Unlike page layouts, Lightning Pages are more
flexible and can show/hide entire sections or components based on filters or permissions 12 .
• (Basic) How can you make a field required? – Several ways: mark the field as required at creation (hard
requirement on every record via the UI), make it required on the page layout (soft requirement via
UI), set it as required in Dynamic Forms (Lightning App Builder), or use a validation rule to enforce it
conditionally. For example, you can make a field required if another field has a specific value 13 .
• (Basic) How can you import data into Salesforce? – Use tools like Data Import Wizard (built into
Salesforce UI, good for simple loads and small volumes) or Data Loader (a desktop client for large
volumes, up to millions of records). Another option is [Link] (a cloud tool). Data Loader can
import, update, or delete millions of records, whereas Import Wizard handles up to 50,000 records
with deduplication features 13 .
• (Intermediate) What is a validation rule? – A validation rule is a formula that enforces data quality by
preventing record save when the formula evaluates to true. For example, a rule could require an
email field to contain “@” or prevent a discount from exceeding 50%. If the rule fires, the record isn’t
saved and shows an error message.
• (Intermediate) What is a profile vs a permission set? – A profile is a user’s baseline set of permissions
(object CRUD, field-level access, system rights like “Modify All Data” etc.) 14 . Every user has one
profile. A permission set is an add-on that grants additional permissions to a user on top of their
profile. Use permission sets to give specific users extra access without creating new profiles 15 .
• (Intermediate) What is a role in Salesforce? – A role controls record-level visibility via the Role
Hierarchy. It determines which records (via ownership) a user can see beyond their own. Setting
roles allows data to be shared up and down the hierarchy. In combination with sharing rules, roles
open up record access while org-wide defaults are kept restrictive 16 14 .

4
Security (Access and Sharing)
This section checks understanding of Salesforce’s security model: profiles, permission sets, roles, and
sharing.

• (Basic) What is the difference between a Profile and a Permission Set? – A profile is mandatory and
defines a user’s baseline permissions (object CRED permissions, FLS, apps, etc.). A permission set is
optional and grants additional permissions on top of a user’s profile. In short, “profiles do,
permission sets add” 15 . For example, a permission set can give a single user extra object
permissions without changing their profile.
• (Basic) What is a Role and the Role Hierarchy? – A role opens up data visibility. Roles are arranged in a
hierarchy so that users higher in the hierarchy can see (and report on) records owned by users below
them. For example, a VP role can see all records owned by subordinates. Roles work together with
org-wide defaults and sharing rules to grant access.
• (Basic) What are Org-Wide Defaults (OWD) and the sharing rule “golden rule”? – OWD settings determine
the default record visibility for each object (e.g. Private or Public Read). The “golden rule” is to set
OWD to the most restrictive level (e.g. Private) 16 , and then open up access via roles, sharing rules,
or manual sharing. Permissions in Salesforce “open up access, not lock it down” 16 .
• (Basic) How do Roles and Sharing Rules differ? – A role hierarchy automatically grants visibility up the
chain (users see what their subordinates own). Sharing rules explicitly open access to users by role,
group, or territory across the hierarchy. For example, a sharing rule can share all records in a region
to a specific team, extending beyond strict hierarchy.
• (Intermediate) How do you restrict access to fields? – Use Field-Level Security (FLS) on profiles or
permission sets. FLS can make a field read-only or hidden for certain profiles. Even if a field is on a
page layout, FLS can still hide it. This ensures that users cannot edit or see fields they shouldn’t have
access to.
• (Intermediate) What is a Permission Set Group? – (If applicable in latest releases) A Permission Set
Group bundles multiple permission sets so they can be assigned as a single unit to a user. This
simplifies management when granting common permission combinations. [Not always asked but
good to know].
• (Intermediate) How do Login IP Ranges and Login Hours enhance security? – Profiles can specify
trusted IP ranges and allowed login hours. This restricts where and when users can log in. For
example, you can block logins outside corporate IPs or outside business hours, adding another
security layer.
• (Intermediate) What is the “View All Data” permission? – A powerful administrative permission often
granted only to System Administrators. It lets a user bypass sharing rules and see all records of an
object, regardless of ownership. This goes beyond “read” on objects and should be used sparingly.

Governor Limits (Apex) (Resource Management)

Governor limits are runtime restrictions to ensure fair use of shared resources. These questions check
awareness of common limits and how to design within them.

• (Basic) What are governor limits in Salesforce? – Governor limits are runtime limits enforced by
Salesforce to prevent any one tenant’s code from consuming excessive resources. Since Salesforce is
multi-tenant, limits (such as number of queries, CPU time, heap size, etc.) ensure that all customers
get fair share of resources 17 . If a limit is exceeded, the transaction fails.

5
 • (Basic) Why do governor limits exist? – Because Salesforce runs in a multitenant environment (many
orgs on shared servers). Limits prevent individual code from “hogging” CPU, memory, or database
resources 18 . For example, there can only be 100 SOQL queries in a synchronous Apex transaction
to avoid overloading the database.
• (Basic) Give an example of a per-transaction Apex limit. – One example is the SOQL queries limit: in
one Apex transaction you can execute at most 100 SOQL SELECT statements 19 . Another example
is DML statements: normally 150 per transaction. These are “hard” limits on synchronous Apex.
• (Intermediate) How can you avoid hitting governor limits? – Bulkify your code: move queries and DML
outside loops, use collection-based operations, and process records in batches. For example, instead
of querying inside a loop, query once for all needed records (using a Set of IDs). Use formulas, roll-
up summary fields, and declarative tools (Flows) where possible to reduce Apex usage.
• (Intermediate) What is Batch Apex and how does it relate to limits? – Batch Apex processes large
record sets in chunks (default 200 records per chunk). Each chunk has its own set of governor limits,
effectively allowing you to work with many more records than a single transaction permits. Use
[Link] to run such jobs for millions of records.
• (Intermediate) What is the @future annotation and how does it help with limits? – @future
methods run asynchronously in a separate transaction with separate limits. Use them for long-
running operations (like callouts) or to break up work. However, asynchronous methods have their
own limits and can’t return values directly.
• (Intermediate) How does Salesforce handle CPU time limits? – Each transaction is allocated a fixed CPU
time (around 10,000 ms synchronous). If CPU time is exceeded, a runtime exception is thrown. To
avoid this, optimize algorithms (avoid expensive loops, use efficient SOQL/DML, reduce JSON parsing
costs, etc.).
• (Intermediate) What happens if you exceed a governor limit during execution? – The transaction
immediately stops, rolls back any data changes, and throws an uncatchable exception. The only way
to handle a limit error is to avoid it in the first place (limits cannot be “caught” in a try/catch block).

Sales Cloud (Core CRM Functionality)

Sales Cloud questions focus on the sales CRM data model and processes. They assess knowledge of
standard objects and sales processes in Salesforce.

• (Basic) What is Salesforce Sales Cloud? – Sales Cloud is Salesforce’s CRM product for managing sales
processes. It helps companies track leads, opportunities, and accounts from prospecting through
closing deals. For example, Sales Cloud manages the journey from a Lead to a converted
Opportunity and includes features like quoting and forecasting 20 .
• (Basic) What standard objects are central to Sales Cloud? – Key objects are Lead (a potential prospect),
Account (a company), Contact (a person at an account), and Opportunity (a potential sale).
Typically, a Lead is converted into an Account/Contact/Opportunity 20 21 . Sales Cloud also uses
Campaigns, Products, Pricebook, and Quotes for more advanced sales operations.
• (Basic) What happens when you convert a Lead? – Lead conversion automatically creates a new
Account and Contact (if not existing), and optionally an Opportunity. The Lead record is then
removed. Conversion maps Lead fields to the new Account/Contact/Opportunity fields. This
streamlines turning a qualified prospect into an active sales record.
• (Basic) What is an Opportunity? – An Opportunity represents a sales deal. It is linked to an Account
and has fields like Stage (e.g. Prospecting, Negotiation), Amount, Close Date, and Probability.

6
 Opportunity stages reflect the steps in your sales process. When an Opportunity is won, it indicates a
successful sale.
• (Basic) What are Price Books and Products? – A Product is an item or service you sell. A Price Book
defines pricing for those products. Products are added to Opportunities (OpportunityLineItems)
using a specific Price Book entry. For example, if selling software seats, you’d create a Product “Seat”
and list it in the Standard Price Book with a price.
• (Intermediate) What is a Sales Path or Sales Process? – A Sales Process is the set of Opportunity
stages that your business follows (e.g. Prospecting > Qualification > Proposal > Closed Won). Record
Types and Picklist values often enforce different processes. A Path (in Lightning) is a visual guidance
tool on the UI, showing the key fields and guidance per stage.
• (Intermediate) How do you handle quoting to customers? – Salesforce has a Quotes object. You can
add Products to an Opportunity and then create a Quote to generate a PDF proposal. Quotes use
Price Books too. Multiple quotes can be created per Opportunity (e.g. Paper vs Electronic Quote).
• (Intermediate) How would you track sales performance? – Use Reports and Dashboards to track
metrics like Closed Won revenue or pipeline. Salesforce also has Forecasting features: you can set up
quota and territory forecasts. Additionally, use dashboards with charts (e.g. sales by stage or by rep)
to monitor performance.

Flows (Declarative Automation)

Salesforce Flow Builder is a powerful declarative automation tool. These questions test familiarity with flow
types, elements, and best practices.

• (Basic) What is Salesforce Flow and why is it important? – Salesforce Flow is the point-and-click
automation tool for business processes on the Salesforce platform 22 . It lets admins automate
tasks without code (e.g. updating records, sending emails) using a visual interface. Flows can range
from simple screen flows (guided UIs) to complex record-triggered automations.
• (Basic) What are the types of flows available? – Key types include: Screen Flows (interactive flows with
user screens), Record-Triggered Flows (triggered on create/update of records, before- or after-
save), Scheduled Flows (run at a scheduled time), and Autolaunched Flows (which can be launched
from buttons, Process Builder, or other flows without screens).
• (Basic) What is the difference between Screen Flow and Autolaunched Flow? – A Screen Flow includes
user interaction (forms/screens). An Autolaunched Flow runs in the background without screens
(e.g. for record updates or calls from Process Builder). Use Screen Flows for guided user input, and
Autolaunched Flows for behind-the-scenes automation.
• (Basic) How do you invoke a Record-Triggered Flow? – You set the flow to trigger on a specific object
and timing (e.g. “after insert” or “before update”). Once activated, the flow runs automatically when
those record changes occur. For example, a flow can auto-update related records whenever an
Opportunity stage changes.
• (Basic) What are Fault Connectors in a Flow? – Fault connectors are error-handling paths attached to
flow elements (like DML or callouts). If an element fails (e.g. validation fails on record update), the
flow follows the fault path, where you can handle the error (e.g. show a message or rollback). They
help keep flows from failing silently.
• (Intermediate) What is the 2000 iteration limit in Flow loops? – Salesforce Flow has a limit of 2000
iterations in a loop element per transaction 23 . This means a single flow cannot loop more than
2000 times. To handle larger collections, you might break up the logic into multiple flows or batches.

7
 • (Intermediate) When should you use a Before-Save flow vs After-Save flow? – Before-save record-
triggered flows are used for fast field updates on the same record (like a lightweight workflow). They
run much faster because they don’t incur extra DML. Use them to update fields on the triggering
record without additional actions. After-save flows are needed when you must perform actions on
related records or do anything that requires the record to be committed (e.g. sending emails,
creating child records).
• (Intermediate) What are Subflows and when do you use them? – A subflow is a separate flow that you
can call from another flow using the “Subflow” element. This promotes reuse of flow logic. For
example, if multiple processes need to perform the same steps (sending a notification, for instance),
you’d build that once as a subflow and call it where needed.
• (Intermediate) How can you invoke Apex from a Flow? – You can call Apex from Flow by creating an
@InvocableMethod in an Apex class. Once deployed, that method appears as an action in Flow. This
lets you perform custom logic in Apex (e.g. complex calculations or integrations) from a declarative
flow.
• (Intermediate) When should you use Flow instead of Apex? – Salesforce recommends using declarative
Flow when possible to simplify maintenance and allow non-coders to understand the process. As
Salesforce CTO Parker Harris noted, “Just because it’s possible to write code, doesn’t mean you
should.” If a requirement can be met by Flow (and won’t hit its limits), it’s best to use Flow. Apex
should be used for scenarios that Flow cannot easily handle 24 .

Question Summary and Difficulty Distribution

Topic Basic Count Intermediate Count Total Questions

Apex 4 5 9

Lightning Web Comp. 4 4 8

Apex Triggers 4 4 8

Admin Configuration 6 4 10

Security 4 4 8

Governor Limits 3 4 7

Sales Cloud 4 4 8

Flows 5 5 10

Total 30 34 64

Table: Number of questions per topic by difficulty.

Sample Practical Tasks

• Easy Task (Flow): “Update Contact Type via Flow.” Create a Record-Triggered Flow on the Contact
object. When a Contact is created or updated, if the Contact’s Account has Industry = “Technology”,
set a custom picklist field Customer_Type__c on Contact to “Tech Customer”.
Acceptance Criteria: The flow is before-save on Contact create/update, checks

8
 [Link] , and updates Contact.Customer_Type__c accordingly. The flow should be
active and handle bulk records. Estimated time: ~30 minutes.

• Intermediate Task (Lightning Web Component): “Account Search Component.” Develop an LWC
named accountSearch . This component has a search input and button. When the user enters text
and clicks search, call an Apex controller method that queries Accounts with
Name LIKE '%text%' . Display the resulting Accounts in a list (Name and Industry). Handle no-
results gracefully.
Acceptance Criteria: The LWC includes a text input and search button. On click, it calls a
@AuraEnabled Apex method to retrieve matching accounts. Matching accounts are displayed on
the page. If no matches are found, show “No results.” The component works without errors and
follows best practices (e.g. uses @wire or imperative Apex). Estimated time: ~45 minutes.

Sources: Official Salesforce documentation and Trailhead (Apex Developer Guide, Lightning Web
Components guide, Salesforce Help), plus authoritative blogs like SalesforceBen and ApexHours provided
the technical details and examples 1 6 7 11 14 19 20 22 .

1 What Is Salesforce Apex and How Does It Work? A Guide for Admins | Salesforce Ben
[Link]

2 3 6 9 10 11 12 13 17 20 21 24 50 Most Popular Salesforce Interview Questions & Answers

(Updated 2026) | Salesforce Ben
[Link]

4 Lifecycle Hooks | Create Lightning Web Components | Lightning Web Components Developer Guide |

Salesforce Developers
[Link]

5 Wire Apex Methods to Components | Work with Salesforce Data | Lightning Web Components
Developer Guide | Salesforce Developers
[Link]

7 apex - When can we use Trigger Context Variables? - Salesforce Stack Exchange
[Link]

8 30 Salesforce Admin Interview Questions & Answers | Salesforce Ben

[Link]

14 15 16 Learn Salesforce Roles and Profiles in 5 Minutes (Ft. Permission Sets) | Salesforce Ben
[Link]

18 19 What Are Salesforce Governor Limits? Best Practices & Examples | Salesforce Ben
[Link]

22 23 Top 50 Salesforce Flow Interview Questions You Should Know - Apex Hours
[Link]