Salesforce Developer
Interview Questions.
15 practice questions across 12 skills — each with what the interviewer is really listening for. Prepare with intent, not guesswork.
Free · No signup · Grouped by skill
How to use this page
Don't memorise answers. For each question, read what the interviewer is looking for, then practise answering out loud in your own words with a real example. The notes describe strong answers and common red flags — they are for your prep, not a script.
Salesforce Flows
1 questionHow do you decide between declarative tools (Flows) and Apex code for a requirement?
IntermediateWhat the interviewer is looking for: Strong answers favour declarative solutions when they suffice and reserve Apex for complex logic, respecting the 'clicks not code' principle. Writing Apex for everything a Flow could do is a red flag.
Apex
2 questionsWhat are Apex governor limits, and how do you write code that respects them?
AdvancedWhat the interviewer is looking for: Look for bulkifying code, avoiding SOQL and DML inside loops, and thinking in sets/maps. Queries or DML inside loops is a classic red flag that will hit limits.
A Flow and an Apex trigger both fire on the same object and conflict. How do you resolve it?
AdvancedWhat the interviewer is looking for: Strong candidates understand the order of execution, consolidate automation, and avoid recursive or conflicting logic. Not knowing the order of execution is a red flag.
SOQL
1 questionHow do you write an efficient SOQL query and avoid the anti-pattern of querying in a loop?
IntermediateWhat the interviewer is looking for: Strong candidates query once with the needed fields and filters, use relationships, and map results. Selective, indexed filters matter; querying per-record in a loop is a red flag.
Lightning Web Components
1 questionHow do Lightning Web Components communicate with Apex and with each other?
AdvancedWhat the interviewer is looking for: Look for wire/imperative Apex calls, events for child-to-parent, and properties for parent-to-child, keeping components focused. Not understanding the data flow is a red flag.
Unit Testing
1 questionWhy does Salesforce require test coverage, and what makes a meaningful Apex test?
IntermediateWhat the interviewer is looking for: Strong answers test real behaviour and bulk/negative cases with assertions, not just chase 75% coverage. Tests with no assertions written only to hit coverage are a red flag.
Data Modeling
1 questionHow do you design a data model on the platform for a new business process?
IntermediateWhat the interviewer is looking for: Look for appropriate objects and relationships (lookup vs master-detail), sharing implications, and scalability. Overloading standard objects or ignoring sharing is a red flag.
REST APIs
1 questionHow do you integrate Salesforce with an external system via REST APIs?
AdvancedWhat the interviewer is looking for: Strong candidates handle auth, callout limits, error handling, and asynchronous patterns for reliability. Synchronous callouts with no error handling are a red flag.
Requirements Gathering
1 questionHow do you gather requirements from business users who describe outcomes, not fields?
IntermediateWhat the interviewer is looking for: Look for translating business processes into objects and automation, asking about edge cases, and confirming understanding. Building exactly what is literally asked without probing is a red flag.
Salesforce Administration
1 questionHow do you decide what belongs to an admin (config) versus a developer (code)?
BasicWhat the interviewer is looking for: Strong answers collaborate with admins and keep solutions maintainable, not code-heavy where config works. Ignoring admin capabilities and coding everything is a red flag.
Problem Solving
1 questionHow do you manage deployments between sandboxes and production safely?
AdvancedWhat the interviewer is looking for: Look for source control, change sets or a CI tool, testing in a staging sandbox, and rollback awareness. Changing production directly is a red flag.
Communication
1 questionHow do you communicate a technical limitation to a stakeholder who wants the impossible?
BasicWhat the interviewer is looking for: Look for explaining constraints in business terms and offering alternatives, not just saying no. Overpromising to please, or a blunt refusal, are red flags.
Stakeholder Management
1 questionHow do you keep an org from accumulating technical debt over years of changes?
IntermediateWhat the interviewer is looking for: Strong answers advocate for standards, documentation, and periodic cleanup, and push back on quick hacks. Piling on quick fixes with no governance is a red flag.
Behavioural & role-general
2 questionsTell me about a complex Salesforce solution you built. What was the hardest part?
BasicWhat the interviewer is looking for: Look for a real challenge, the trade-offs, and lessons learned, with clear ownership. Vague descriptions with no technical depth are a red flag.
How do you keep up with Salesforce's three yearly releases and evolving best practices?
BasicWhat the interviewer is looking for: Strong answers cite release notes, Trailhead, and community, and test changes in a sandbox. 'I learn on the job' with no proactive habit is a weak sign in a fast-moving platform.