Salesforce Consultant interview questions, with worked answers

How to use these questions

Many Salesforce interviews include a scenario or a short live demo. Talk through it in order: who the users are and what they need, the objects and fields, who may see what, which automation, how you would test and release it, and how you would know it worked. Then tell them about a real org you improved.

What a Salesforce consultant is expected to know

• The platform: SalesforceConfigure objects, fields, page layouts, permissions and automation, and know what the platform does out of the box. configuration, Sales CloudSet up leads, opportunities, forecasts and quotes so that the sales process in the system matches the real one. and Service CloudSet up cases, queues, service levels and knowledge articles for a customer service team..
• Automation: FlowBuild automation with Flow, test it, and know when a requirement has outgrown it. and when a need calls for ApexRead what a developer's Apex code does and write the requirement it must meet, even if you do not code..
• The data: the data model, data migrationPlan, clean, map and load records into Salesforce, without duplicates and with the owners checking them. and integrationsUnderstand how Salesforce exchanges data with the ERP, the website and other systems..
• The people: requirementsTurn what a sales or service team says into user stories with clear acceptance criteria., testing and adoptionHelp users adopt a new process with training, simple guides and support after release..

Tools come up side by side and none is a must: Data Loader or other import tools for data, Jira for stories, Git with Salesforce's DevOps Center or another release tool for changes, Lucidchart or Miro for process maps, and Excel for mapping files. Panels want the design sense more than the tool.

Requirements and design

How do you gather requirements from a sales team that says it just wants Salesforce to work?

What they check: turning vague wishes into clear needs.

Short answer: "I watch a few sales reps work for an hour, ask what slows them down and what their manager needs to see, and write user stories with acceptance criteria. I play them back to the stakeholders, rank them with the sales lead, and start with the few that save the most time."

The full answer: "Make it work" usually means fewer fields and fewer clicks, not more features.

A weak answer: "I ask them to list every field they want." Follow-up: "The head of sales and the reps want opposite things." Say what you do.

How would you design the data model for a new process, and when do you create a custom object?

What they check: a data model that lasts.

Short answer: "An object is like a table: accounts, contacts, opportunities and cases are standard ones. I use a standard object when it fits the meaning, because reports, features and future releases expect it. I create a custom object only for something the standard does not describe, such as a contract site visit, and I decide the relationships and the record owner before the fields."

The full answer: A wrong relationship is cheap to change on day one and expensive after a year of data.

A weak answer: "I create a new object for each request." Follow-up: "The business wants to track partners." Say which object you would use.

How do profiles, permission sets and the sharing model decide who sees what?

What they check: security by design.

Short answer: "A permission set gives a user rights to objects, fields and features on top of a minimal profile, so rights follow the job, not the person. The sharing model decides which records a user sees: the default for each object, then the role hierarchy, sharing rules and teams to open access where needed. I start private where data is sensitive and open it on purpose."

The full answer: Most data leaks in a CRM are permissions given broadly to save time.

A weak answer: "Everyone gets the same profile." Follow-up: "Two sales teams must not see each other's deals." Say how you set it up.

When do you build a flow, and when does a requirement need Apex?

What they check: knowing the limits of clicks and code.

Short answer: "A flow is automation built in Salesforce's visual tool: updating records, sending alerts, guiding users through screens. I use Flow first because admins can read and change it. Apex, Salesforce's programming language, is for complex logic, large volumes or integrations that Flow handles badly. Either way I keep one automation per object and event where possible, so they do not fight each other."

The full answer: The question is who will maintain it in two years.

A weak answer: "I always ask a developer." Follow-up: "The flow hits limits on a bulk import." Say what you change.

What is a validation rule, and how do you stop rules from getting in the users' way?

What they check: data quality without frustration.

Short answer: "A validation rule stops a record from saving when the data breaks a condition, such as a closed deal without a reason. I add one only when the data matters for a report or a process, write a clear message that says how to fix it, and check that imports and integrations can still save their records."

The full answer: Ten rules that block users teach them to type anything to get past.

A weak answer: "I make every field required." Follow-up: "Sales reps enter dummy values to save." Say what that tells you.

Data, integration and releases

How would you plan a data migration into Salesforce, including duplicates?

What they check: a careful, checked load.

Short answer: "I agree which records move and who owns them, clean and merge duplicates in the source first, map the fields, and keep the old system's IDs so records stay linked. I load in order, accounts before contacts before opportunities, test in a sandbox, check counts and samples with the business, and set duplicate rules so new duplicates are caught."

The full answer: A migration that brings the old mess along wastes the new system.

A weak answer: "We import everything and clean later." Follow-up: "Two regions spell the same customer differently." Say how you match them.

How do you approach an integration between Salesforce and an ERP system?

What they check: clear ownership of data across systems.

Short answer: "I agree which system owns which data, for example customers in the ERP and opportunities in Salesforce, which direction each flows, how often, and what happens on an error. I specify the fields and the API calls with the integration team, keep within the platform's limits, and make sure someone watches the errors after go-live."

The full answer: Two systems that both think they own a customer will disagree forever.

A weak answer: "The integration team handles it." Follow-up: "Orders appear in Salesforce a day late." Say where you look.

How do you use sandboxes and move changes safely to production?

What they check: discipline in releases.

Short answer: "A sandbox is a copy of the production org for building and testing. I build in a developer sandbox, test with users in a fuller copy, and move the changes with a release tool and version control rather than by hand. Every deployment has a list of what changes, a test plan and a way back."

The full answer: Changes made directly in production are how orgs end up nobody understands.

A weak answer: "Small changes I make straight in production." Follow-up: "A deployment breaks a report on Monday morning." Say what you do.

How do you prepare for the three Salesforce releases a year?

What they check: keeping an org healthy over time.

Short answer: "I read the release notes for the features we use, test our key processes in a preview sandbox before the release reaches production, and note new features that could replace custom work. I tell users what changes for them in a short note."

The full answer: A release is also a chance to retire something you built yourself.

A weak answer: "Salesforce handles releases." Follow-up: "A release changes how a screen looks for the service team." Say how you prepare them.

The clouds and the users

How do you set up the lead and opportunity process in Sales Cloud for a sales team?

What they check: the sales process in the system.

Short answer: "I map how a lead is qualified and converted, then the opportunity stages with clear exit criteria, the probability and the forecast categories, the products and price books, and who approves discounts. Each stage should mean the same to every rep, so the forecast can be trusted."

The full answer: A pipeline report is only as good as the stage definitions behind it.

A weak answer: "I copy the stages from the last client." Follow-up: "Deals sit in one stage for months." Say what you change.

What would you build in Service Cloud for a customer service team?

What they check: service processes, not only sales.

Short answer: "Cases that come in by email, web form or chat; queues and assignment rules so the right agent gets each case; service levels with escalations; knowledge articles agents can send; and a console view with the customer's history. I start with the case lifecycle and the measures the service manager is judged on."

The full answer: Agents judge the system by how many clicks a case takes.

A weak answer: "Service is like sales with cases." Follow-up: "Urgent cases wait behind simple ones." Say how you fix it.

How do you design reports and a dashboard that managers actually use?

What they check: reporting that drives decisions.

Short answer: "I ask each manager which decisions they make each week and which numbers they need for them, then build a few reports from data that is reliably entered. A dashboard shows those numbers on one screen, with filters for each team, and I check after a month which parts are used."

The full answer: A dashboard nobody opens is a sign the question was never asked.

A weak answer: "I build every report they ask for." Follow-up: "The numbers differ from finance's." Say where you look.

Users are not using the system. How do you raise adoption?

What they check: the human side of CRM.

Short answer: "I find out why: too many fields, no value for the rep, or no habit from the managers. I remove what nobody needs, give reps something back such as a quicker quote or a useful view, train by role, and ask managers to run their meetings from the dashboard. Then I watch logins and data quality."

The full answer: People use a CRM that saves them time; they avoid one that only reports on them.

A weak answer: "Management should make it mandatory." Follow-up: "The strongest seller refuses to use it." Say what you try.

You inherit an org full of technical debt. Where do you start?

What they check: calm clean-up with priorities.

Short answer: "Technical debt is the cost of old shortcuts: unused fields, overlapping automations, code nobody owns. I take stock first, find what is used and what breaks most, then clean up in small, tested steps, starting with the automations that conflict. I document as I go and agree with the business what can be retired."

The full answer: You earn the right to clean up by fixing what hurts the users first.

A weak answer: "I would rebuild it from scratch." Follow-up: "Nobody knows what a trigger does." Say how you find out.

Where can AI help in Salesforce, and what must be in place first?

What they check: sober use of new tools.

Short answer: "Salesforce builds AI into the platform, from summaries of cases and calls to agents that answer customers. They need clean data, clear permissions and well-written knowledge articles, or they repeat the mess. I would start with a narrow use case, check the answers with the team, and agree with the data protection team what data the AI may read."

The full answer: AI on poor data gives confident wrong answers faster.

A weak answer: "AI will replace the admin." Follow-up: "An AI summary misstates a customer's complaint." Say how you would catch it.

Senior rounds

As a senior Salesforce consultant, how would you coach a Salesforce administrator?

What they check: building the team.

Short answer: "I give them real stories of growing size, review their designs before they build, and explain the reasons behind security and data model choices. I let them run a small workshop with me in the room. When their work needs few changes, they own an area, and I point them to the next certification if they want one."

The full answer: A senior consultant on the way to Salesforce solution architect is judged by the health of the whole org, not only by their own builds.

A weak answer: "Admins handle the tickets." Follow-up: "Their flows work but are hard to read." Say how you coach them.

Your CV for these questions

Each Salesforce line on your CV invites the questions above: which cloud, what you built, what changed. Give each one a line that makes a lead consultant want the story:

Hold your CV against a Salesforce consultant job with the free score; then prepare the org story for the area it finds thin, from the users' problem to the release.