Salesforce Developer
Interview Questions.

What 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.

What 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.

What 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.

What 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.

What 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.

What 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.

What 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.

What 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.

What 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.

What 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.

What 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.

What 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.

What 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.

What 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.

What 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.