Salesforce interview questions cover predictable areas, such as security models, automation logic, data architecture, governor limits, object relationships. These topics come up across admin, developer and consultant roles at companies of all sizes.
The answers in this guide are written to build actual understanding of each concept. When an interviewer asks a follow-up question, candidates who understand the reasoning behind an answer hold up. Candidates who memorised a definition often do not.
This guide covers 50 commonly asked Salesforce interview questions and answers from real hiring rounds. Read through, understand the logic and you will be able to speak to any angle the interviewer takes.
Overview
| Area | What Gets Asked |
| General Salesforce | CRM basics, cloud, products, releases |
| Admin | Profiles, roles, sharing, automation, reports |
| Developer | Apex, SOQL, triggers, governor limits, LWC |
| Scenario-based | Real troubleshooting situations |
| Consultant | DevOps, adoption, data quality, project delivery |
The Salesforce interview questions and answers below progress from fundamental concepts to technical and scenario-based topics.
Salesforce Interview Questions and Answers
These Salesforce interview questions cover core products, architecture, editions and platform features.
1. What is Salesforce?
Salesforce is a cloud-based CRM. Companies use it to manage relationships with their customers, tracking leads, running sales pipelines, handling support cases and running marketing campaigns. Everything sits in one place instead of scattered across spreadsheets, inboxes and legacy tools.
It runs on a multi-tenant architecture. That means thousands of companies share the same servers, but their data stays completely separate. You access it through a browser with no software to install on your laptop.
2. What are the benefits of using Salesforce over older systems?
- No server costs: The old way needed buying, installing and maintaining physical servers. With Salesforce, that is someone else’s problem. You pay a subscription and get on with the work.
- Automatic updates: Salesforce pushes three major releases every year, including spring, summer and winter. New features land in your org without your IT team doing anything. No upgrade projects, no downtime.
- Works from anywhere: Browser or mobile app. A sales rep can update an Opportunity from a client’s office without needing to be at a desk.
3. What is the difference between Sales Cloud and Service Cloud?
Sales Cloud is for winning business. It handles the journey from a new Lead all the way through to a closed deal. You get pipeline management, quoting, forecasting and activity tracking.
Service Cloud is for keeping customers happy after they buy. Customers raise Cases by email, phone or web form. Agents handle those Cases using a knowledge base, live chat and SLA tracking.
Both products share the same platform and the same core objects like Account and Contact. Most companies use both.
4. What other Salesforce products should you know?
Beyond Sales and Service Cloud, interviewers expect you to name a few others. Salesforce tools make it easier to run campaigns, build partner and customer portals, connect systems, communicate as a team, and bring customer data into one place. Agentforce adds AI across all of these tools.
5. What is the Salesforce Platform?
This is the foundation all Salesforce products are created on. It also lets you create your own custom apps on top of Salesforce without the need to build infrastructure from scratch. You can do a lot with point-and-click tools like Flow Builder and Lightning App Builder. Apex is there when the requirement gets too complex for clicks, which is where many businesses use Salesforce development services for custom app logic and integrations.
6. What is AppExchange?
Salesforce’s marketplace for apps. Companies build products that plug directly into your Salesforce org, including e-signature tools, document generation, CPQ and data quality apps. Most companies use at least one AppExchange product. You install it, configure it and it works within Salesforce as if it were a native feature.
7. What is Salesforce Lightning?
Lightning is the current Salesforce user interface, released in 2015. Before it, Salesforce had a UI called Classic that had barely changed since 1999. Lightning brought a modern, component-based design where admins can customise almost every page. Classic still exists but Salesforce has made its direction clear. The future is Lightning.
8. How do Salesforce releases work?
Three major releases a year, including spring, summer and winter. They are automatic. Salesforce upgrades your org and you do not have to do anything. Sandboxes get the new release a few weeks before Production, which gives you time to test your customisations against the new version. Release notes come out in advance so you know what is changing before it hits.
9. What are the different Salesforce editions?
The main ones are Essentials, Professional, Enterprise and Unlimited. Higher editions unlock more API calls, more automation features, more custom objects and more storage. Enterprise is what most mid-to-large companies run on. Professional has real restrictions including limited Flow functionality and no full API access out of the box, which matters a lot in practice.
10. What is Customer 360?
It is Salesforce’s idea that every team in a company, including sales, service, marketing and commerce, should be looking at the same customer record with all the context in one place. Instead of the service team not knowing a customer is mid-negotiation on a renewal with sales, they can see everything. Data Cloud is the technical product that makes this work at scale.
Admin Salesforce Interview Questions and Answers
Admin-focused Salesforce interview questions cover security, permissions, automation, reports and data management.
11. What is the difference between a Profile and a Role?
This is one of the most common Salesforce SFDC interview questions. Get it exactly right.
Profile controls what a user can do. Object permissions (create, read, edit, delete), which fields they can see, which apps they can access.
Role controls what records a user can see. A manager can see all records owned by people below them in the role hierarchy. Someone at the bottom can only see their own.
Do remember profile is about actions, role is about visibility.
12. What are Permission Sets?
A Permission Set gives a user extra access on top of what their Profile gives. Instead of creating a dozen different Profiles for slight variations in access, you create targeted Permission Sets and layer them on. Salesforce is actively pushing companies to move all permissions out of Profiles and into Permission Sets entirely. Permission Set Groups let you bundle several Permission Sets together and assign them in one go. This is also the kind of setup where Salesforce admin services help keep user permissions clean and consistent.
13. What are Organisation-Wide Defaults (OWD)?
OWD sets the baseline. It answers one question if a user does not own a record, what access do they get by default?
- Private: They can only see records they own
- Public Read Only: They can see everything but edit nothing they do not own
- Public Read/Write: They can see and edit everything
You always start with the most restrictive OWD that makes sense for your business, then open access up from there using Role Hierarchy, Sharing Rules or Manual Sharing.
14. What are Sharing Rules?
Sharing Rules are used to expand access beyond the OWD. You can share records based on their owner or based on field values. For example, you could automatically share all Opportunities in the Closed Won stage with the Finance team. Sharing Rules simply add to access. They can never take it from them.
15. What is Field-Level Security?
FLS controls visibility and editability of individual fields. It is set on Profiles or Permission Sets. If a field is hidden via FLS, it does not show up anywhere, not on the page, not in reports and not through the API. Page layouts control what you see on screen but FLS is the actual security layer. A field hidden on a page layout can still be pulled via API if FLS allows it.
16. What are the types of relationships in Salesforce?
This topic appears frequently in Salesforce SFDC interview questions. Know these four:
- Lookup: If you delete the parent, the child stays. The two objects can have completely independent sharing settings.
- Master-Detail: Child cannot exist without its parent. Delete the parent and the child goes with it. Rollup summary fields (Count, Sum, Min, Max) only work on Master-Detail.
- Self-Relationship: The Account object is the most common example. An Account can have a parent Account.
- Hierarchical: only available on the User object. Used for management chains.
Companies may hire Salesforce developers to design relationships correctly before custom objects and automation start depending on them.
17. What is a junction object?
It establishes a many-to-many relationship between two objects. The junction object has a Master-Detail relationship to both. The built-in example in Salesforce is Opportunity Product (OpportunityLineItem). It sits between Opportunities and Products so one Opportunity can have many Products and one Product can appear on many Opportunities.
18. What are the different types of Salesforce Reports?
- Tabular: Raw rows of data, like a spreadsheet. Good for exports. Cannot group or add subtotals.
- Summary: Groups records by a field and adds subtotals. The most commonly used type day to day.
- Matrix: Groups by both rows and columns. Good for cross dimensional totals, for example revenue by region and by month.
- Joined: Puts two different report blocks next to each other. Good for comparing different objects’ data on one screen.
19. What is a Dynamic Dashboard?
A regular dashboard shows data from the perspective of the person who created it or a fixed user. A Dynamic Dashboard changes based on who opens it. One dashboard can show each sales rep only their own pipeline. This saves you from building 30 separate dashboards for 30 reps. Enterprise edition allows up to 3 Dynamic Dashboards per org.
20. What is a Sandbox?
A Sandbox is a copy of your Production org used for building and testing. You never make changes directly in Production. The four types are:
- Developer: Just configuration, no data. Free with most editions, used for building.
- Developer Pro: Same as Developer but more storage.
- Partial Copy: Your configuration plus a sample of Production data.
- Full: Exact mirror of Production, including all data. Used for performance testing and final user acceptance testing before major releases.
21. How many ways can you make a field required?
Four, and each one has a different reach:
- Field settings: Required at all times, everywhere, including API uploads via Data Loader.
- Page layout: Required only when the user is working in the UI. Data Loader bypasses this entirely.
- Lightning page with dynamic forms: Required based on conditions you set. UI only.
- Validation rule: The most flexible option. Required only when your formula evaluates to true. Works across UI and API.
22. Which tools do you use for importing data into Salesforce?
- Data Import Wizard: Web-based, 50,000 records maximum, standard objects such as Contacts and Leads. Great for one-off imports.
- Data Loader: Desktop application that can process millions of records. Works on any object. Better for jobs that run repeatedly and you want logs.
- Dataloader.io: Cloud-based, more capabilities than Data Loader, can schedule and do complex mappings. The free version is limited.
23. What is a Queue?
A Queue is a holding area for records that have not been assigned to anyone yet. New Leads or Cases come in and land in a Queue. Any team member who is part of that Queue can take ownership of a record and start working it. Queues work on Cases, Leads, Orders and custom objects.
24. What is the Order of Execution in Salesforce?
When you save a record, Salesforce runs through a fixed sequence. The simplified version you need for interviews:
- Values are applied
- Previous trigger fires
- Run system and custom validation rules
- Record saved to DB (not committed)
- Fires After Lighting
- Rules Assignment Workflow Procedure
- Run Flows triggered by records
- Changes committed to database.
- Emails and other future post-commit actions ways
25. What is the difference between Data and Metadata?
Data are the real records your business works with, including accounts, contacts, opportunities, cases.
Metadata is the configuration that tells you how your org works, including field definitions, page layouts, Flows, validation rules and Apex classes. Deploying from Sandbox to Production is moving metadata not data.
Developer Salesforce Technical Interview Questions
Developer-focused Salesforce interview questions test Apex, SOQL, triggers, governor limits and coding practices.
26. What is Apex?
Apex is Salesforce’s backend programming language. It is similar in syntax to Java. You reach for Apex when Flow cannot handle the requirement, including complex integrations, multi-level loops, custom email services or bulk operations that need very specific control. It runs on Salesforce servers.
27. What is SOQL?
Salesforce Object Query Language. It queries records from Salesforce objects. You use it inside Apex, inside Workbench or in the developer console. It looks like SQL but only works within Salesforce.
Example: SELECT Id, Name, Industry FROM Account WHERE Industry = ‘Technology’
The governor limit is 100 SOQL queries per synchronous transaction. Writing SOQL inside a loop is one of the most common mistakes and one of the most common interview topics.
28. What is SOSL?
Salesforce Object Search Language. The key difference from SOQL is that SOSL searches across multiple objects at once. If you search for “Acme” using SOSL, you can get back matching Accounts, Contacts and Leads in one query. SOQL can only search one object at a time. SOSL is useful when you do not know which object holds the record you are looking for.
29. What are Governor Limits?
Salesforce is a shared platform. Governor Limits stop any one company’s code from using up resources that other companies need. If your code crosses a limit, Salesforce throws a runtime exception and rolls back the transaction.
Salesforce technical interview questions limits you need to know:
- 100 SOQL queries per transaction (synchronous)
- 150 DML statements per transaction
- 50,000 records returned from a SOQL query
- 10 seconds CPU time for synchronous Apex
- 60 seconds CPU time for asynchronous Apex
30. What is an Apex Trigger?
Code that runs automatically when a record is created, updated, deleted or undeleted. Triggers run before the record is written to the database, which is useful for changing field values or blocking saves, or after, which is useful for updating related records.
Keep trigger code thin. The logic belongs in a handler class. One trigger per object.
31. What is recursion in a trigger and how do you stop it?
Recursion is when your trigger fires, does something that causes the same trigger to fire again, which causes it to fire again until you hit a governor limit or the stack depth error “Maximum trigger depth exceeded” at 16 levels.
The standard fix is a static Boolean in a handler class. Default it to true. When the trigger enters, check the value. If true, run the logic and flip it to false. Next time the trigger fires in the same transaction, it sees false and exits.
32. When do you use Flow and when do you use Apex?
Start with Flow. If Flow handles the requirement cleanly without performance issues, build it in Flow. It is easier to maintain, non-developers can read it and changing it does not require a deployment.
Bring in Apex when you need nested loops that would hit Flow limits, complex API integrations with conditional retry logic, custom email services or operations that need to run before validation rules in ways Flow cannot support. Good Salesforce development services teams always ask whether Flow can handle it before writing a line of Apex.
33. What is the difference between a before trigger and an after trigger?
Before the trigger runs before the record is written. The record is in memory but not saved yet. You can change field values on the record directly and those changes are saved automatically. You add errors here to block saves. The record ID does not exist yet if the record is brand new.
After trigger runs after the record is saved. The ID is available. Use this when you need to work on related records or send notifications based on the saved values.
34. What is bulkification?
Writing Apex that handles 200 records at once instead of processing them one at a time. When someone uploads 500 Contacts via Data Loader, your trigger receives all 500 in one call. If you put a SOQL query or a DML statement inside a loop, you will hit governor limits well before 500.
The pattern: collect all the IDs or values you need into a Set before the loop, run one SOQL query against that Set, build your update records in a List inside the loop and call DML once after the loop ends.
35. What is the difference between Visualforce and Lightning Web Components?
Visualforce is the old UI framework from the Salesforce Classic era. Tag-based markup, similar to HTML. It still works but Salesforce stopped investing in it.
LWC is the current standard. HTML, JavaScript and CSS. It follows modern web standards, which means a web developer who has never touched Salesforce can pick it up faster than Visualforce. All new UI development should be in LWC.
36. What is the difference between with sharing and without sharing?
With sharing means the Apex class respects the record-level security of the running user. You don’t see records you’re not supposed to see.
Without sharing means the class does not care about sharing rules. It runs with admin access regardless of who is logged in. Only use this if you have a scenario such as a background job processing records that would not normally be visible to the running user.
37. What is a Future Method?
An async method that executes after the current transaction has completed. You annotate it with @future . Typical examples are calling out to external systems (which you can’t do synchronously in a trigger) and handling Mixed DML scenarios where you want to do setup objects and non-setup objects in separate transactions.
But there’s one major limitation that you cannot call a Future Method from Batch Apex.
38. What is Batch Apex?
Batch Apex processes large volumes of records in chunks so you do not hit governor limits. It implements Database.Batchable and has three methods. start defines the query, execute processes each chunk and finish runs once everything is done. Governor limits reset with each chunk. Default chunk size is 200 and maximum is 2000.
39. What is the Mixed DML error?
If you are running DML on a mix of setup objects (User, Profile, PermissionSet) and non-setup objects (Account, Contact, custom objects) in the same transaction you will get this error. Salesforce does not permit this as a change to setup objects can trigger a recalculation of sharing, which cannot be done mid-transaction.
The solution is to move one of the DML operations to a @future method so that the two operations are in separate transactions.
40. What is Apex Test Coverage?
All Apex code must have at least 75% test coverage before any Apex can be deployed to Production. Write test classes that call your methods and use System.assertEquals to verify results.
Scenario-Based Salesforce SFDC Interview Questions and Answers
Scenario-based Salesforce interview questions assess practical troubleshooting and platform decision-making.
41. A user cannot delete a record. What do you check?
For SFDC interview questions and answers like this, work through the checks in this order:
Is the record a parent in a Master-Detail relationship with child records still attached? You cannot delete a parent while children exist.
Does the user’s Profile have Delete permission on that object?
Do you have an Apex Trigger with a before delete handler that is calling addError?
One thing to note for interviews is that standard Validation Rules cannot prevent record deletion. Only an Apex Trigger can do this.
Salesforce admin services are generally part of the daily org support for ongoing permission fixes and user-access issues.
42. You run a mass update and rows are failing. How do you troubleshoot?
First check the results file. Workbench and Data Loader both give you a row-by-row error log. Common causes:
- ID column missing or formatted wrong. Without the record ID, every row fails.
- Required fields not included in the CSV
- Picklist values that do not match exactly, including capitalisation
- Validation rules firing on fields you thought you were not touching
- Before-update triggers adding errors based on business logic
Always test five to ten records first. Catching a mapping problem at ten records costs nothing. Catching it after ten thousand is a much harder conversation.
43. A trigger is causing “Maximum trigger depth exceeded.” How do you fix it?
That’s recursion. The trigger is calling itself. The fix is a static boolean in a handler-class. Set it true at the start of execution. Check at the top of the trigger if it is true. If it is, set it to false. If that’s already false, leave. The trigger is not allowed to repeat because it disables its own switch on the first pass.
44. An integration is pushing data but records are not updating correctly. Where do you start?
So open Workbench, go to REST Explorer and try the same API call manually. Check the response body for what Salesforce returns. And just because it returns HTTP 200 doesn’t mean the update was successful. Check the Apex logs for any errors in the triggers or validation failures which could be silently rolling back the field values. Then check the field API names on the payload. If you mistype a single character in a field name, it will fail silently.
45. A batch job is hitting DML governor limits in the execute method. What is wrong?
DML statement is inside a loop. Each loop iteration involves a separate DML call. It hits the 150-DML limit (at 151 records processed) and blows up. The fix is to gather up all the records you need to update into a List inside the loop and then call the DML once after the loop is done.
Consultant Salesforce Questions Interview
This section covers delivery, adoption, DevOps, data quality and scope management.
46. What is the SDLC in a Salesforce context?
Plan, Analyse, Design, Build, Test, Deploy, Maintain. In Salesforce, building happens in a Developer Sandbox. Testing happens in QA and UAT Sandboxes. Deployment moves metadata from Sandbox to Production using Change Sets, Salesforce CLI or a DevOps tool like Gearset or Copado.
The most common mistake on smaller projects is skipping the UAT stage. That is usually where the client finds out the automation does not match how their team actually works.
47. How do you improve user adoption after a Salesforce rollout?
Three things that genuinely work:
Time the training right: Training people three weeks before go-live means they forget everything. Train them the week of launch, ideally the day before.
Find your champions: Identify one person per team who picks it up quickly and wants to help others. That person absorbs questions that would otherwise come to the admin all day.
Fix frustrations fast: If users are doing workarounds, there is a reason. Find it and fix it in the first 30 days. Working with a Salesforce consulting team during design prevents most adoption problems before go-live.
48. How do you keep Salesforce data clean?
Prevention is cheaper than cleanup.
Required fields stop records from saving without critical information. Picklists stop people typing whatever they want in text fields. Validation rules enforce business logic at the data layer. Duplicate rules and matching rules catch duplicates at the time of entry before they spread.
For orgs where the damage has already been done Cloudingo or DemandTools on AppExchange can deduplicate at scale
49. What is Salesforce DevOps?
It is applying software engineering practices to Salesforce delivery: version control, automated testing and structured deployment pipelines. Change Sets were the original deployment method and they still work, but they have no rollback, no version history and no automated testing integration.
Modern Salesforce teams use tools like Gearset, Copado or Salesforce DevOps Center. All changes live in Git. Every deployment goes through automated tests before touching Production.
50. What is scope creep and how do you handle it?
Scope creep is when new requirements keep appearing after the project scope was agreed. It is one of the most common reasons projects go over budget and over time.
The fix requires discipline from day one. Document the agreed scope in writing. Set up a simple change request process where any new requirement gets logged, sized and approved before work starts. Saying yes to everything mid-project without adjusting the timeline or budget guarantees a bad outcome for everyone involved.
How to Prepare for Salesforce Questions Interview Panels
- Say the answers out loud: Interview answers that read well on paper often fall apart when spoken under pressure. Practise with a timer.
- Know a real example for each concept: “I used this on a project where…” will always land better than a textbook definition. If you lack real project experience, Trailhead has hands-on challenges that give you something to reference.
- Think past the first answer: Interviewers do not want a definition. They want to see if you understand it. If you say “Master-Detail deletes the child when the parent is deleted,” the next question will be “when would that cause a problem?” Be ready for it.
- Be honest about gaps: Saying “I have not worked with that directly but here is how I would approach it” is a much better answer than bluffing. Teams that hire Salesforce developers through staffing models know the difference between confidence and knowledge.
Our Salesforce Expertise Across Regions
USA |
Australia |
Germany |
United Kingdom |
