Salesforce Administrator Interview Questions UK: 8 Real Questions and What Interviewers Want

Most Salesforce Administrator interviews in the UK follow a pattern, and knowing it beats guessing. Below are eight questions from our bank of 16, each with a note on what the interviewer is really after.

Eight Salesforce Administrator interview questions, and what the interviewer is thinking

1. How would you decide between profiles, permission sets and permission set groups when setting up access for a new team?

Why they ask: Access design is the core of an admin's job and mistakes create security and support problems.

2. Explain how record-level access works in Salesforce, from organisation-wide defaults through to sharing rules.

Why they ask: Sharing model knowledge is a standard test of whether someone can secure data properly.

3. Which Salesforce automation tool would you use today, and how would you migrate an old Workflow Rule or Process Builder process?

Why they ask: Workflow Rules and Process Builder are being retired, so they want to see modern Flow knowledge.

4. What is the difference between a validation rule and a required field, and can you give an example of each?

Why they ask: This checks whether the admin picks the right control for data quality.

5. How would you import 50,000 records into Salesforce while avoiding duplicates and protecting data quality?

Why they ask: Data migration is a routine but risky task that exposes careless habits.

6. Sales users are complaining that Salesforce is slow and cluttered, and they're skipping data entry. What would you do?

Why they ask: This tests whether the admin balances user adoption and governance.

7. Tell me about a time you automated a manual process in Salesforce. What was the impact?

Why they ask: They want evidence of delivering measurable business value as an admin.

8. What does a typical week look like for a Salesforce Administrator, and what makes someone good at it?

Why they ask: They want to confirm you understand the realities of the role beyond configuration.

A sample answer to question 1

How would you decide between profiles, permission sets and permission set groups when setting up access for a new team?

I'd keep profiles as lean as possible, ideally just login hours, default apps and the minimum object access, and then layer capability on with permission sets. Salesforce is retiring permissions on profiles, so building around permission sets is the sensible direction anyway. I'd map the team's job functions first, for example a sales rep, a sales manager and a support agent, and create a permission set per capability, such as 'Edit Opportunities' or 'Run Reports'. Where a role needs several of those, I'd bundle them into a permission set group, which makes onboarding a single assignment. I'd test with Login As in a sandbox and use the Field Accessibility viewer to confirm what each person can see. Finally I'd document the model so that the next admin can understand why each set exists, and review it quarterly to prune unused ones.

Common mistake to avoid: Cloning profiles for every team; Granting access without least privilege

Want the rest?

Full model answers, key points and common mistakes for all 16 questions are on the Salesforce Administrator interview questions page. The first five are free, no sign-up needed.