Fifteen common Salesforce admin interview questions
- Standard versus custom objects?
- Lookup versus master-detail relationships?
- Explain the Salesforce security model from org to record level.
- Profiles versus permission sets versus permission set groups?
- What are organisation-wide defaults, role hierarchy and sharing rules?
- How would you restrict reps to their region's accounts?
- Which automation tool would you use today, and why Flow?
- Record-triggered flow: before-save versus after-save?
- What are validation rules? Give an example.
- How do you import and deduplicate data?
- Report types and dashboard components — how do they work?
- Sandbox types and how you deploy changes?
- What are governor limits, and why do they matter to admins?
- How do you gather requirements from a business team?
- Tell me about a process you automated.
Data model
| Concept | Answer |
|---|---|
| Lookup relationship | Loose link; child can exist without parent; separate sharing |
| Master-detail | Tight link; child deleted with parent; inherits sharing; enables roll-up summaries |
| Junction object | Custom object with two master-detail relationships for many-to-many |
| Record types | Different picklist values, page layouts and processes for one object |
| Formula fields | Calculated, read-only values |
The security model
Access is layered. Organisation-level controls cover login hours and IP ranges. Object and field access come from profiles and permission sets — Salesforce recommends minimal profiles with access granted through permission sets and permission set groups. Record access starts from organisation-wide defaults (the most restrictive baseline), then opens up through the role hierarchy, sharing rules, teams and manual sharing. For “reps see only their region's accounts”: set account OWD to private, build roles by region, and add criteria-based sharing rules where needed.
Automation
- Flow is the primary declarative automation tool; Workflow Rules and Process Builder are retired for new automation, so migrating them to Flow is a common topic.
- Before-save record-triggered flows update fields on the triggering record efficiently; after-save flows handle related records, emails and other actions.
- Validation rules block bad data, such as requiring a close-lost reason when stage is Closed Lost.
- Approval processes route records for sign-off.
- Governor limits cap resources per transaction, so avoid queries and record updates inside loops even in Flow.
Data, reports and deployment
Use the Data Import Wizard for simple imports and Data Loader for large or complex ones; match on IDs or external IDs, and set up duplicate and matching rules. Report types define which objects and fields reports can use; dashboards visualise source reports, with running-user settings controlling what viewers see. Build in a sandbox — Developer, Developer Pro, Partial Copy or Full — then deploy with change sets or source-based tooling, test in a staging sandbox, and document changes. See Salesforce coding interview questions for developer-side topics.
Working with the business
Admins succeed by understanding processes before configuring anything. Interview stakeholders, map the current process, identify the problem to solve, prototype in a sandbox, get feedback, then deploy with training. Interviewers like hearing that you push back on requests that add complexity without value.
A scenario to rehearse
“When an opportunity reaches Proposal stage, create a task for the account owner and notify their manager if the amount exceeds a threshold.” A strong answer uses a record-triggered flow on Opportunity, after-save, with entry criteria on the stage change rather than every edit, a decision element for the amount, a create-records action for the task and an email or notification action for the manager. Mention testing in a sandbox, handling bulk updates and documenting the flow's purpose.
Practising
Answer these out loud, in two minutes or less each, and expect a follow-up on every claim. A free AI interview assistant such as CoPilot Interview can run Salesforce admin questions as a mock interview built from your résumé and score each answer. Prepare two automation stories with the business problem, your Flow design and the outcome.
Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly. Everything else on this page applies whichever tool you use, or none.
Frequently asked questions
What questions are asked in a Salesforce admin interview?
Objects and relationships, the security model, profiles and permission sets, sharing, Flow automation, validation rules, data import and deduplication, reports and dashboards, sandboxes and deployment, governor limits and requirements gathering.
What is the difference between lookup and master-detail?
A lookup is a loose relationship where the child can exist independently with its own sharing. Master-detail is tight: the child inherits sharing, is deleted with the parent and enables roll-up summary fields.
Profiles or permission sets?
Use minimal profiles and grant access through permission sets and permission set groups, which is more flexible and is Salesforce's recommended approach.
Which Salesforce automation tool should I use?
Flow, for new automation. Workflow Rules and Process Builder are retired for new automation, and existing ones are being migrated to Flow.
Practise on real interview questions
Run 145 real interview questions across 10 tracks, answer out loud and see a structured answer to compare with yours. Free, no signup.
Try a practice question