These are LLD questions of the kind Salesforce actually asks — the patterns reported from Salesforce's AI-engineering rounds, where design trade-offs, scale and failure modes matter as much as definitions. Treat this page as a mock interview: say every answer out loud before revealing it. If one surprises you, the lesson behind it is linked at the bottom.
Salesforce LLD concept questions
Salesforce's LLD rounds often ask for a rules engine: when a record changes, run a configurable set of business rules (e.g. 'if deal size > X, notify manager'). Design it.
Asked in
Different customers (tenants) on the platform need different sets of active rules for the same record type. How does this change the RuleEngine design above?
Asked in
The rules engine needs to call an external CRM API with a completely different method signature than what RuleEngine expects for 'send notification.' What pattern bridges this?
Asked in
How to use this page: Salesforce rarely asks something you've never seen — they ask a standard LLD concept and then push one level deeper ("why?", "what would you do if..."). Master the concept in the LLD course lessons, and the follow-up stops being scary.
Keep practising: SOLID Principles, Strategy Pattern, Design a Parking Lot and UML Diagrams cover what most Salesforce LLD rounds test.