HCL Salesforce developer interview experience, shared by a real candidate.
What's Covered
Topics covered in this interview.
01Lightning Web Components2
02SOQL & Data2
03Apex & Triggers1
04General & Experience6
All Interview Questions
Every question asked in this interview, listed one by one.
1How we can created Lookup component in lighting web components.
2Performance impact while using @track decorators in LWC.
3Write SOQL: Find all Accounts where Contact is linked.
4Write SOQL: Write Example for Dynamic SOQL
5Explain all trigger context variables.
6What is salesforce? How you are using salesforce in your current project.
7What is salesforce lighting? How it is difference from salesforce classic.
8Explain Old map & New Map
9Do you know about MCV architecture in Salesforce?
10How we can retrieve metadata using workbench like: Page Layout, Fields, Apps etc.
11What is the platform cache? Have you worked on it?
More Salesforce Interview Questions to Practice
The extra questions below are not from this interview. They cover the same topics and are commonly asked in Salesforce developer interviews, so they make good practice before your own round.
Triggers questions
- Why can you not update the records in Trigger.new directly inside an after trigger?
- How do you stop a trigger from running more than once on the same record (recursion)?
- How do you test a trigger with 200 records?
- What is the difference between addError on a record and addError on a field?
- What happens when a trigger and a record-triggered Flow run on the same object?
SOQL and Data questions
- What are the limits on the number of SOQL queries and rows returned?
- What is dynamic SOQL, and how do you prevent SOQL injection?
- What is the difference between a lookup and a master-detail relationship?
- What is an external ID, and how is it used with upsert?
Lightning Web Components questions
- How do you refresh data on the screen after a record changes (refreshApex)?
- What is Lightning Data Service, and which base components use it?
- How do you handle errors returned from an Apex call in LWC?
- What is the difference between document.querySelector and this.template.querySelector?
Apex questions
- How do you write a good test class, and what is the minimum code coverage for deployment?
- What is a wrapper class, and when do you use one?
- What does @AuraEnabled(cacheable=true) do?
General and experience questions
- How do you approach debugging a production issue?
- How do you decide between a declarative and a programmatic solution?
- Which best practices do you follow in Apex and LWC?
Concepts to Revise
Based on the questions on this page, these are the areas most worth revising.
Triggers
- Context variables: isBefore, isAfter, isInsert, isUpdate, isDelete, isUndelete
- Trigger.new, Trigger.old, Trigger.newMap and Trigger.oldMap, and in which events each exists
- One trigger per object with a handler class
- Preventing recursion with static variables
- addError to block a save with a message
- Testing triggers with single and bulk records
SOQL and Data
- SOQL clauses: WHERE, ORDER BY, LIMIT, OFFSET, GROUP BY, HAVING
- Relationship queries and subqueries
- Aggregate functions and AggregateResult
- SOSL versus SOQL and when to use each
- Dynamic SOQL and bind variables
- Lookup, master-detail and roll-up summary fields
Lightning Web Components
- Lifecycle hooks: constructor, connectedCallback, renderedCallback, disconnectedCallback
- Decorators: @api, @track, @wire and when each is needed
- Parent to child and child to parent communication using properties and custom events
- Lightning Data Service and the uiRecordApi functions
- Calling Apex: wire versus imperative, and cacheable methods
- Template directives: if:true, for:each, key and lwc:if
How to Prepare
The questions on this page lean towards Triggers, SOQL and Data and Lightning Web Components. Spend most of your revision time there, then cover the remaining topics lightly.
- Write a trigger with a handler class from memory, then test it with 200 records to prove it is bulk safe.
- Run relationship, aggregate and subquery examples in the Developer Console until you can write them without looking.
- Build one small component that uses @wire, an imperative Apex call and a custom event, and be ready to explain each part.
- Say your answers out loud. Interviewers listen for clear, structured explanations, not memorised definitions.
- Prepare one or two real examples from your own projects for the general questions.
Preparing for a Salesforce developer interview?
Browse more real company interview experiences and hands-on Apex trigger patterns.
