Salesforce interviews reward people who can explain why they would build something a certain way, not just recite definitions. Whether you are aiming for an admin, developer, consultant or Agentforce-focused role, the same pattern shows up: a few fundamentals, a scenario question or two, and a conversation about trade-offs. This guide covers the roles, the skills worth building, the questions that come up most, and a practical way to prepare. Which Salesforce Role Fits You? Role What you do Interviewers look for Administrator Configure the org: objects, fields, security, flows, reports, user support. Data model, security model, Flow, and clear communication with business users. Developer Build custom logic and UI with Apex, Lightning Web Components and integrations. Apex, triggers, governor limits, SOQL, testing, LWC basics, integration patterns. Consultant / Business Analyst Turn business needs into a Salesforce solution and guide delivery. Requirements gathering, solution tr...
Salesforce interviews reward people who can explain why they would build something a certain way, not just recite definitions. Whether you are aiming for an admin, developer, consultant or Agentforce-focused role, the same pattern shows up: a few fundamentals, a scenario question or two, and a conversation about trade-offs. This guide covers the roles, the skills worth building, the questions that come up most, and a practical way to prepare.
Which Salesforce Role Fits You?
| Role | What you do | Interviewers look for |
|---|---|---|
| Administrator | Configure the org: objects, fields, security, flows, reports, user support. | Data model, security model, Flow, and clear communication with business users. |
| Developer | Build custom logic and UI with Apex, Lightning Web Components and integrations. | Apex, triggers, governor limits, SOQL, testing, LWC basics, integration patterns. |
| Consultant / Business Analyst | Turn business needs into a Salesforce solution and guide delivery. | Requirements gathering, solution trade-offs, stakeholder skills. |
| Architect | Design the overall solution, data, security and integrations. | Big-picture design, scalability, governance and justified decisions. |
| Agentforce / AI specialist | Configure and govern AI agents, topics, actions and grounding data. | Agent design, data quality, testing, guardrails. See our Agentforce Explained guide. |
Skills Worth Building First
- The data model: objects, fields, relationships, record types and when to use each relationship type.
- The security model: profiles, permission sets, sharing, and how access to records differs from access to objects and fields.
- Automation: Flow first, Apex when Flow isn't enough, and knowing how to explain the choice.
- SOQL and data handling: querying related data, avoiding queries in loops, and importing or cleaning data.
- Hands-on practice: a free Developer Edition org and Trailhead projects. Interviewers can tell when you've actually built something.
- Communication: explaining a technical decision to a non-technical person is part of almost every Salesforce job.
Common Interview Questions (With Answers)
1. What is the difference between a lookup and a master-detail relationship?
In a master-detail relationship, the child record depends on the parent. It inherits the parent's sharing and is deleted when the parent is deleted, and it enables roll-up summary fields. A lookup is looser: the child can exist without the parent, has its own sharing, and the relationship can be optional. Choose master-detail when the child has no meaning without the parent.
2. What is the difference between a profile and a permission set?
A profile is the baseline set of permissions a user has, and every user has exactly one. A permission set adds extra permissions on top and can be assigned to many users. The common modern approach is a minimal profile plus permission sets that grant what each role needs.
3. How does record access work in Salesforce?
Start with the organization-wide defaults, which set the most restrictive baseline. Then open access up with the role hierarchy, sharing rules, manual sharing and teams. Object and field permissions from profiles and permission sets still apply on top of record access.
4. When would you use Flow instead of Apex?
Use Flow for most automation because it is declarative, easier to maintain and easier for admins to change. Use Apex when you need complex logic, heavy data processing, or something Flow can't do. In an interview, explain that you start with the simplest tool that meets the requirement.
5. What are governor limits, and why do they exist?
Salesforce is a multi-tenant platform, so limits stop one customer's code from using too many shared resources. Examples in a single synchronous transaction include 100 SOQL queries, 150 DML statements and 50,000 rows returned by SOQL. Check Salesforce's documentation for the current numbers before an interview.
6. What does "bulkify" mean?
It means writing code that handles many records at once rather than one. Avoid SOQL queries or DML statements inside loops, collect the data first, run one query, and do one DML operation on a list.
// Not bulk-safe: a query inside the loop
for (Contact c : Trigger.new) {
Account a = [SELECT Name FROM Account WHERE Id = :c.AccountId];
}
// Bulk-safe: collect the IDs, query once
Set<Id> accountIds = new Set<Id>();
for (Contact c : Trigger.new) {
accountIds.add(c.AccountId);
}
Map<Id, Account> accounts = new Map<Id, Account>(
[SELECT Name FROM Account WHERE Id IN :accountIds]
);
7. What is the difference between a before trigger and an after trigger?
Before triggers run before the record is saved and are used to validate or change values on the records being saved, with no extra DML needed. After triggers run once the record has been saved and has an ID, so they are used to work with related records or things that need the saved ID.
8. What are the testing requirements for Apex?
To deploy Apex to production, you need at least 75% overall code coverage and all tests must pass. A good answer adds that coverage is a minimum and not the goal: tests should check results with assertions and cover single-record, bulk and negative cases.
9. What is the difference between "with sharing" and "without sharing"?
"With sharing" makes Apex respect the running user's record access. "Without sharing" ignores it. Use "with sharing" by default and only bypass it deliberately and for a clear reason.
10. How would you approach a scenario question?
Example: "Sales wants to be alerted when a high-value opportunity has had no activity for 14 days." Walk through it out loud: clarify the requirement, define "high-value" and "activity", suggest a scheduled or record-triggered Flow, decide who gets the alert, and explain how you'd test it. Showing the steps matters more than naming one right tool.
11. (Agentforce) How would you make sure an agent doesn't give wrong answers?
Ground it in trusted data, write specific instructions that forbid guessing, limit its actions and permissions, test it with edge cases and out-of-scope requests, define when it must hand off to a person, and monitor real conversations after launch. For the full process, read How to Build Your First AI Agent with Agentforce Builder.
A 4-Week Interview Prep Plan
- Week 1: Review the data model and the security model. Build a small app in a free org with objects, relationships and permission sets.
- Week 2: Practise automation. Build the same requirement in Flow and then, if you're a developer, in Apex. Write down when each is better.
- Week 3: For developers, practise SOQL, triggers, bulkification and tests. For admins and consultants, practise scenario questions out loud.
- Week 4: Do mock interviews, prepare two or three project stories, and review recent platform updates, including Agentforce. See Einstein AI vs Agentforce for the difference between the older and newer AI features.
Resume and Portfolio Tips
- Lead with outcomes, not duties. "Cut lead response time by building a routing flow" beats "Worked on flows".
- List your certifications with the year, and show hands-on projects next to them.
- Keep a short portfolio: a Trailhead profile, a GitHub repo with sample Apex or LWC, or a short write-up of a project you built.
- Prepare two stories using the format: situation, what you did, the result, and what you'd change.
Certifications: Do They Help?
A certification shows you've studied the platform, and it can help you get past the first screening. It matters less than being able to explain a project you built. A sensible order is Administrator first for most people, then a path that matches your role. If you're interested in AI, the Agentforce Specialist certification guide has a study plan.
Frequently Asked Questions
Do I need to code to get a Salesforce job?
No. Administrator, business analyst and many consultant roles are mostly declarative. Developer roles need Apex and Lightning Web Components.
How long does it take to get ready for a Salesforce interview?
If you already know the basics, four focused weeks is realistic. If you're new, plan for a few months of hands-on practice first.
What if I don't have professional Salesforce experience?
Build projects in a free Developer Edition org, complete Trailhead modules, and write up what you built. That shows initiative and gives you real answers to interview questions.
Where can I find more Salesforce guides?
Visit our Salesforce hub page for all of our Salesforce articles in a suggested reading order.
Conclusion
Salesforce interviews are usually less about memorising answers and more about showing clear thinking: pick the simplest solution, explain the trade-offs and show you've built something yourself. Combine hands-on practice with the questions above and you'll be well placed for most admin, developer and Agentforce roles. More interview and career guides are on our Tech Career & Interview Tips page.
Comments
Post a Comment