WrapDrive – Salesforce Developer Interview Questions​

CompanyWarpDrive
Focus AreaSalesforce Developer
Questions7+
Topics5

WarpDrive Salesforce developer interview experience, shared by a real candidate.

What's Covered

Topics covered in this interview.

01Lightning Web Components1
02SOQL & Data1
03Apex & Triggers2
04Salesforce Core Concepts1
05General & Experience2

All Interview Questions

Every question asked in this interview, listed one by one.

1LWC life cycle hooks.
2Query: Fetch all Account which has no Contacts records.
3Can you call future method from batch?
4Trigger: Write a trigger on Contact, when record is inserted, Contact Mobile value should be automatically copied into the Contact Other Phone. If Other Phone is empty. 
5Explain Role and Profile?
6How many YOE you have?
7Any offer you hold currently?

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.

Apex questions

  • What is the difference between Batch Apex, Queueable Apex, Future methods and Schedulable Apex?
  • When would you use a List, a Set and a Map?
  • What is the order of execution when a record is saved?
  • 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?

Triggers questions

  • What is a trigger handler framework, and why use one?
  • Can you make a callout from a trigger? How?
  • How do you bulkify a trigger?
  • Why can you not update the records in Trigger.new directly inside an after trigger?

Lightning Web Components questions

  • How do you pass data from a parent component to a child component?
  • What is Lightning Message Service and when would you use it?
  • What is the difference between a wired Apex call and an imperative Apex call?
  • How do you refresh data on the screen after a record changes (refreshApex)?

SOQL and Data questions

  • What is a selective query, and why does it matter for large data volumes?
  • What is the difference between WITH SECURITY_ENFORCED and WITH USER_MODE?
  • How do you query deleted records (ALL ROWS)?

General and experience questions

  • What was the most challenging issue you solved recently, and how did you solve it?
  • How do you approach debugging a production issue?
  • How do you decide between a declarative and a programmatic solution?

Concepts to Revise

Based on the questions on this page, these are the areas most worth revising.

Apex

  • Governor limits for SOQL, DML, CPU time and heap size
  • Bulkification: no SOQL or DML inside loops
  • Sharing keywords and how they affect record access
  • Asynchronous Apex: future, queueable, batch and schedulable
  • Test classes: test data, System.assert, Test.startTest and Test.stopTest
  • Collections and wrapper classes

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

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 Apex, Triggers and Lightning Web Components. Spend most of your revision time there, then cover the remaining topics lightly.

  • Practise explaining governor limits and bulkification with a real example from your own project.
  • Write a trigger with a handler class from memory, then test it with 200 records to prove it is bulk safe.
  • 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.

Leave a Reply