Salesforce Admin Interview Questions & Answers 2026

"7/10 candidates fail the Admin round… not because they don't know Salesforce, but because they can't explain REAL scenarios." That's from a LinkedIn post in January 2026. The figure is the poster's claim, not a study, but it matches how I think about hiring.

This page collects the salesforce admin interview questions I'd expect at three levels: fresher, 2-5 years and senior. Each has a short, correct answer you can say out loud.

My argument is simple. A memorised definition gets you through the first five minutes. The offer goes to the person who can say what they'd do, why, and what could go wrong.

Key takeaways

• Salesforce admin interview questions in 2026 are mostly scenarios, so practise explaining decisions and trade-offs, not reciting definitions.
• Know security and the sharing model cold: profiles, permission sets, org-wide defaults, roles and sharing rules come up at every level.
• Flow is now the automation answer, because Salesforce ended support for Workflow Rules and Process Builder on 31 December 2025.
• Mid-level and senior candidates should expect Agentforce questions: subagents, actions, testing and the Einstein Trust Layer.

What Salesforce admin interviews test in 2026

Interviewers are checking judgement more than vocabulary, and the level changes what judgement means.

Agentforce questions now come up in many mid-senior admin interviews, and the topics are predictable: subagents (formerly topics), actions, Testing Center and Data 360.

Level	What the interviewer is really testing	How to prepare
Fresher	Do you know the vocabulary, and can you reason about simple data?	Build a small app in a free Developer Edition org and be ready to show it
2-5 years	Can you handle a scenario and explain trade-offs?	Rehearse three real problems you solved, including one that went wrong
Senior	Can you design, govern and say no?	Prepare one org-wide decision with options, risks and outcome

Skip the exam dumps you'll find online. They're against the certification rules, and they train recall, not judgement. Use the official Trailhead modules and the Administrator credential page instead. Still preparing for the exam? Here's my 6-week Admin certification plan.

Salesforce admin interview questions for freshers

Freshers should be able to explain the data model, the basic security layers and simple automation in plain words.

1. What are standard and custom objects? Standard objects ship with Salesforce, such as Account, Contact, Lead, Opportunity and Case. Custom objects are ones you create, and their API names end in __c. The Object Reference lists the standard ones.

2. How do Lead, Account, Contact and Opportunity relate? A Lead is an unqualified prospect. On conversion, Salesforce creates an Account and a Contact, and optionally an Opportunity, and maps the lead's fields across. An Account is the company, a Contact is a person at it, and an Opportunity is a potential deal.

3. What's the difference between a profile and a permission set? Every user has exactly one profile, which sets baseline access such as object and field permissions. Permission sets add access on top, and a user can have many. The usual advice is a minimal profile plus permission sets, bundled into permission set groups. The Data Security module covers this.

4. What's the difference between a role and a profile? A profile controls what a user can do, such as create or edit an object. A role controls which records they can see by placing them in the hierarchy. People mix these up, so say it plainly.

5. What are org-wide defaults? They set the baseline record access for each object. The options include Private, Public Read Only and Public Read/Write, and some objects offer others, such as Controlled by Parent. Start with the most restrictive setting the business can live with, then open access up with roles, sharing rules and manual sharing.

6. Lookup or master-detail? In a master-detail relationship, the child record is required to have a parent, inherits the parent's sharing and owner, is deleted with the parent, and the parent can have roll-up summary fields. A lookup is looser: the parent is optional and the child keeps its own sharing. An object can have up to two master-detail relationships, which is how you build a many-to-many with a junction object. See the Data Modeling module.

7. What's a validation rule? Give an example. It blocks a save when a formula evaluates to true and shows your error message. This one stops a Closed Won opportunity with no amount:

AND(
  ISPICKVAL(StageName, "Closed Won"),
  ISBLANK(Amount)
)

8. Page layout or record type? A page layout controls which fields and related lists appear. A record type lets one object offer different picklist values, business processes and layouts to different users. Use a record type when the process genuinely differs, not just the screen.

9. What are the report formats? Tabular, Summary, Matrix and Joined. Use Summary to group and subtotal, Matrix to group by rows and columns, and Joined to combine report blocks. Mention bucket columns for categorising values without a new field.

10. Data Import Wizard or Data Loader? The Import Wizard is browser-based, suits smaller loads (up to 50,000 records) and handles common objects. Data Loader handles larger volumes and supports insert, update, upsert, delete and export. If you need to match on your own key, use an external ID field with upsert.

11. What happens to deleted records? They go to the Recycle Bin, where they stay for 15 days before being permanently deleted.

Salesforce admin interview questions for 2-5 years of experience

At this level you'll be asked "what would you do if…" and the answer should name a trade-off.

12. A Flow or a Process Builder? Flow. Support for Workflow Rules and Process Builder ended on 31 December 2025. Existing automations still run, but new work belongs in Flow, and the Migrate to Flow tool in Setup helps convert old ones.

13. Which Flow types should you know? Screen flows for user interaction, record-triggered flows for data changes, schedule-triggered flows for batch jobs, autolaunched flows called from elsewhere, and platform-event-triggered flows. For record-triggered flows, say when you'd use before-save: it updates fields on the triggering record without an extra DML operation, so it's faster.

14. How do you stop a Flow hitting limits? Flows run inside the same transaction as everything else, so they share the governor limits. Typical synchronous limits are 100 SOQL queries and 150 DML statements per transaction. Never put Get Records or Create/Update Records inside a loop. Collect records in a collection variable and write once.

15. How do you debug a failing Flow? Use the debug tool in Flow Builder, add fault paths to data elements, and send failure emails or log to a custom object. Say you'd test with a batch of records, not one, because bulk behaviour is where flows break.

16. A manager is above a user in the role hierarchy but can't see their record. Why? Common causes: the object's Grant Access Using Hierarchies setting is switched off (possible on custom objects), the manager lacks object-level read permission on their profile or permission sets, or the record is private through some other control. A role hierarchy gives record access, never object permission. This is exactly the sort of scenario that trips candidates.

17. How do you stop duplicates? Set up matching rules and duplicate rules, choosing whether to block or only alert. Explain the business trade-off: blocking protects data quality but can frustrate sales reps, so many teams start with alerts.

18. What are the sandbox types? Developer, Developer Pro, Partial Copy and Full. Developer and Developer Pro copy metadata only. Partial Copy adds a sample of data, and Full is a complete copy. Storage and refresh intervals differ, so check Salesforce Help's sandbox licence page before quoting numbers.

19. How do you move changes between environments? Change sets work between connected orgs, such as a sandbox and its production org. For teams that want version control, DevOps Center is Salesforce's tool for that. Name one you've actually used.

20. What's an approval process, and when is Flow better? An approval process routes a record through approvers with entry criteria, steps and actions on approve or reject. Use it for formal, auditable sign-off. Use Flow when the logic is conditional and doesn't need that structure.

21. How do you track who changed what? Field history tracking records changes on up to 20 fields per object. The Setup Audit Trail shows setup changes for the last 180 days. Say which one answers which question.

22. How do you load related data in the right order? Parents first, then children. Use external IDs so child records can find their parents without you pasting 18-character Salesforce IDs into a spreadsheet.

My take: Don't answer scenario questions with a feature name. Say what you'd check first, what you'd change, and what you'd tell the user. That's the whole difference between a certified admin and a hireable one.

Salesforce admin interview questions for senior admins

Senior questions are about design, governance and risk, so lead with the decision, not the click path.

23. Design the sharing model for a company with three regions. Start with Private org-wide defaults on sensitive objects, build roles to mirror reporting lines, add criteria-based sharing rules for cross-region needs, and use permission sets for functional access. Then talk about the cost: more sharing rules mean more recalculation and harder troubleshooting.

24. What's data skew and why does it matter? Ownership skew happens when one user owns a very large number of records, and account skew when one account has a very large number of children. The usual guidance is to be careful beyond roughly 10,000. Both can cause locking errors and slow sharing recalculation. Fixes include spreading ownership across users or integration users and restructuring accounts.

25. How would you migrate an org off Process Builder? Inventory every automation first, because most orgs have overlapping logic, and the order of execution in Salesforce decides which of those automations fires first. Consolidate to one record-triggered flow per object where sensible, convert with the Migrate to Flow tool where it fits, test in a sandbox with bulk data and deploy in stages. Say you'd retire duplicates, not just convert them.

26. How do you govern an org with years of technical debt? Audit unused fields, reports and automations. Agree naming conventions, document each flow's purpose, and set a rule for who may change production. Governance is a habit, not a project.

27. How do you secure the org beyond profiles? Multi-factor authentication, session and login IP settings, least-privilege permission sets, regular access reviews, and monitoring of setup changes. The principle: nobody gets access "just in case".

28. Declarative or code? Click first, code when declarative gets hard to maintain or hits limits. Flow is powerful, but a flow with 80 elements that nobody understands is worse than 30 lines of well-tested Apex. Be honest about where you'd bring in a developer.

29. Write a query for accounts with no contacts. Admins aren't always asked, but it signals data fluency:

SELECT Id, Name
FROM Account
WHERE Id NOT IN (SELECT AccountId FROM Contact)

The SOQL reference covers the syntax.

Agentforce questions for Salesforce admins

Expect to explain how an agent is configured, tested and kept safe, because admins are the people who'll run them.

30. What are an agent's building blocks in Salesforce? An Agentforce agent is organised around subagents (formerly topics), the jobs it can handle, instructions (how to handle them) and actions (what it can actually do, such as running a Flow, Apex or a prompt template). Start from the Agentforce material on Trailhead.

I explain agents to business leaders as having six parts, like a new hire: a brain (the model), a job description, tools, knowledge, a trigger and guardrails. In Salesforce terms, subagents and instructions are the job description, actions are the tools, Data 360 or Knowledge is the knowledge, the channel or event is the trigger, and permissions plus the Trust Layer are the guardrails. That mapping is my own, not Salesforce's wording, but it makes a good interview answer.

31. What is the Einstein Trust Layer? Salesforce's set of protections around generative AI requests, including masking of sensitive data, toxicity detection, audit trail and zero data retention agreements with its model providers. Read the Einstein generative AI documentation before quoting details, because features change by release.

32. How would you test an agent before go-live? Write realistic test utterances, include awkward and out-of-scope ones, and use the Testing Center to run them in bulk and review results. Then pilot with internal users before customers.

33. What access should an agent have? As little as the job needs. My own rule when I build agents: read-only first, a human approving anything that sends, pays or changes data, and promotion only once it has earned it. Agents should earn promotions, just like people. At Techila, our Agentforce build for Armakuni works this way: the agent answers technical FAQs and routes cases, and escalates to a human with full context when expertise is needed.

My take: An admin who can explain why an agent shouldn't have write access on day one is more valuable than one who can recite every Agentforce feature. Guardrails are the job.

What I look for as a hiring founder

I look for people who can reason about a problem they've never seen, not people who've seen the questions before.

Techila's own interview and assessment questions once ended up on the internet, and candidates walked in knowing the answers. We built a pool of hundreds of thousands of questions and now generate each test in real time, adaptive to how the candidate is doing. That became Talent IQ at talentiq.app. The lesson: someone can memorise 30 leaked questions, but nobody can memorise hundreds of thousands. Interviewers who've been burned think the same way, so expect follow-ups that push past your rehearsed answer.

I also lead the Bareilly Trailblazer Community Group, and my view is that credibility in the Salesforce community comes from helping people. So I notice candidates who've answered someone else's question, written up a fix or taught a session.

When we hire at Techila for our US customers, communication sits right next to technical skill on the list. The other two things we look for are experience working with US customers and being comfortable working US Eastern Time hours. For an admin, much of the job is explaining a sharing rule or a broken flow to a business user who doesn't care how Salesforce works. Practise your answers out loud, as if to that person.

How to prepare for a Salesforce admin interview this week

Try this week:

• Build one small app in a Developer Edition org (objects, a validation rule, one record-triggered flow, a report) and be ready to walk through it.
• Pick three questions above and answer each out loud in 90 seconds, including one thing that could go wrong.
• Write down one real problem you solved, what you tried first and what you'd do differently.
• Read one Agentforce module on Trailhead and explain subagents, actions and testing to a friend.

If you're a leader building AI skills in your team, one of my sessions covers how to give agents a job description and the right guardrails.

Frequently asked questions

What are the most common Salesforce admin interview questions?

Security and the sharing model come up almost every time: profiles versus permission sets, org-wide defaults, role hierarchy, sharing rules. After that come validation rules, Flow, reports and data loading. Expect at least one scenario question where you must explain your reasoning.

How should a fresher prepare for a Salesforce admin interview?

Learn the core objects and security concepts through Trailhead, then build a small project in a free Developer Edition org. Showing a working app and explaining your choices beats listing certifications. Practise answering aloud.

Are Agentforce questions asked in Salesforce admin interviews?

Increasingly, especially at mid-senior level. Be ready to explain subagents (formerly topics), actions, testing and the Einstein Trust Layer, and to say how you'd limit an agent's access.

Is Flow or Process Builder asked in 2026 interviews?

Flow. Salesforce ended support for Workflow Rules and Process Builder on 31 December 2025, so interviewers expect you to build in Flow and to know how to migrate older automations. Be ready to discuss before-save flows, bulk behaviour and fault handling.