30 Salesforce Developer Interview Questions That Actually Matter in 2026
From junior to architect level, these are the Salesforce questions that separate the real developers from the admin-wannabes. Includes Apex, Lightning Web Components, SOQL optimization, and modern integration patterns.
I've been through 50+ Salesforce developer interviews across every major consulting firm, ISV, and end-client you can imagine. The questions haven't changed much, but the expectations have skyrocketed in 2026.
Companies want developers who can think beyond point-and-click. They need people who understand when to use declarative vs. programmatic solutions, can optimize SOQL queries, and won't break governor limits in production.
These 30 questions cover the core competencies that separate good Salesforce developers from great ones. I've included the "why" behind each answer because understanding the platform's architecture is what makes you valuable.
Question Categories & Difficulty Levels
- Apex Programming (1-10): Object-oriented concepts, collections, exception handling
- Lightning Web Components (11-15): Lifecycle, data binding, component communication
- SOQL & SOSL (16-20): Query optimization, relationship queries, limits
- Triggers & Workflows (21-25): Best practices, bulkification, automation tools
- Integration Patterns (26-30): REST/SOAP APIs, callouts, security
Apex Programming (Questions 1-10)
Core Apex Concepts
1. What's the difference between List, Set, and Map in Apex?
List: ordered collection with duplicates; Set: unique values; Map: key-value pairs for lookups
2. Explain the difference between == and .equals() in Apex.
== compares references for objects, values for primitives; .equals() compares actual content/values
3. What are governor limits and why do they exist?
Platform limits to ensure fair resource usage: SOQL queries (100), DML statements (150), CPU timeout (10s)
4. How do you handle exceptions in Apex? Give examples of built-in exception types.
try-catch-finally blocks; DmlException, QueryException, NullPointerException, LimitException
5. What's the difference between static and instance methods?
Static: belongs to class, no object needed; Instance: requires object instantiation, can access instance variables
Advanced Apex
6. Explain Apex sharing and security. What's runAs() used for?
System vs user mode execution; runAs() tests code execution as specific user for security testing
7. What are future methods and when would you use them?
Asynchronous execution with @future annotation; used for callouts, long-running processes, mixed DML operations
8. How do you implement batch processing in Apex?
Database.Batchable interface with start(), execute(), finish() methods; processes large data sets in chunks
9. What's the difference between Database.insert() and insert statement?
Database.insert() allows partial success with allOrNone parameter; insert statement fails entire transaction on error
10. Explain the use of with sharing, without sharing, and inherited sharing keywords.
Controls record-level security enforcement: with (enforces), without (ignores), inherited (uses caller's context)
Lightning Web Components (Questions 11-15)
11. What's the lifecycle of a Lightning Web Component?
constructor() → connectedCallback() → renderedCallback() → disconnectedCallback() → errorCallback()
12. How do you pass data between parent and child components?
Parent to child: @api properties; Child to parent: custom events with dispatchEvent()
13. What's the difference between @track, @api, and @wire decorators?
@api: public properties; @track: deprecated (use reactive properties); @wire: connects to Salesforce data
14. How do you handle events in Lightning Web Components?
Event handlers with addEventListener(), template onclick handlers, custom events with CustomEvent
15. How do you call Apex methods from LWC?
@wire for reactive data, imperative calls with import and .then()/.catch(), @AuraEnabled methods
SOQL & SOSL (Questions 16-20)
16. What's the difference between SOQL and SOSL?
SOQL: queries single object with relationships; SOSL: searches across multiple objects and fields with text search
17. How do you optimize SOQL queries for better performance?
Use selective filters, indexed fields, LIMIT clause, avoid wildcards in LIKE, minimize subqueries
18. Explain relationship queries in SOQL. Give examples of parent-to-child and child-to-parent.
Child-to-parent: Account.Name; Parent-to-child: (SELECT Name FROM Contacts) - uses relationship names
19. What happens when you exceed SOQL query limits?
LimitException thrown; use efficient queries, bulkify code, consider async processing for large datasets
20. How do you handle dynamic SOQL queries safely?
Use Database.query() with bind variables, String.escapeSingleQuotes() to prevent SOQL injection
Triggers & Workflows (Questions 21-25)
21. What are the different trigger contexts and when do they fire?
before insert/update/delete (validation), after insert/update/delete/undelete (related records), before/after delete
22. How do you write bulkified triggers?
Process collections, avoid SOQL/DML inside loops, use Maps for lookups, delegate logic to handler classes
23. What's the order of execution for automation tools?
Workflow rules → before triggers → validation → after triggers → assignment rules → auto-response → workflow field updates
24. When would you use Process Builder vs Flow vs Apex triggers?
Flow: complex logic, user interaction; Process Builder: simple automation (deprecated); Triggers: bulk processing, complex validation
25. How do you prevent recursive triggers?
Static variables to track execution, trigger handler patterns, check Trigger.isExecuting context
Integration Patterns (Questions 26-30)
26. What's the difference between REST and SOAP APIs in Salesforce?
REST: lightweight, JSON, stateless; SOAP: XML, stateful, more secure, supports transactions
27. How do you handle callout limits and timeouts?
100 callouts per transaction, 120s total timeout; use future/queueable for async, implement retry logic
28. Explain different authentication methods for Salesforce APIs.
OAuth 2.0, JWT bearer token, username-password, SAML assertions - OAuth preferred for security
29. How do you implement platform events for real-time integration?
Publish with EventBus.publish(), subscribe with trigger or Lightning components, decouple systems
30. What are the security considerations when exposing Salesforce data via APIs?
Field-level security, sharing rules, IP restrictions, API versioning, rate limiting, audit trails
Ace Your Salesforce Technical Interviews
Beyond knowing the answers, you need to articulate complex Salesforce concepts clearly under pressure. LastRound AI provides real-time guidance for technical interviews across all major platforms.
- ✓ Real-time Apex code suggestions and optimizations
- ✓ SOQL query optimization tips during interviews
- ✓ Lightning Web Component architecture guidance
- ✓ Integration pattern recommendations
Essential Interview Strategies
The "Why vs What" Approach
Salesforce interviews focus heavily on architectural decisions. Don't just explain what you'd do—explain why it's the right approach:
- Declarative first: "I'd start with Process Builder because... but if we need bulk processing, then triggers because..."
- Governor limits: "This approach uses fewer SOQL queries because..."
- Maintainability: "Future developers will understand this pattern because..."
- Scalability: "When we have 10,000 records, this solution will..."
Common Salesforce Interview Red Flags
Avoid These Answers:
- • "I'd write a trigger for everything"
- • "SOQL in loops is fine"
- • "Workflow rules are deprecated"
- • "Security isn't my concern"
Show You Understand:
- • Declarative vs programmatic trade-offs
- • Governor limit implications
- • Security and sharing models
- • Platform best practices
Role-Specific Focus Areas
Junior Developer:
- • Apex basics and syntax
- • Simple SOQL queries
- • Trigger context understanding
- • Lightning component lifecycle
Senior Developer:
- • Architecture patterns
- • Performance optimization
- • Integration strategies
- • Security considerations
Technical Architect:
- • Multi-org strategies
- • Data architecture
- • Governance frameworks
- • Enterprise patterns
The Salesforce ecosystem rewards developers who think like architects. Show that you understand the platform's constraints, leverage its strengths, and can build solutions that scale. Companies want developers who can grow with the platform, not just code against it.
