Sapient – Salesforce developer interview questions

CompanySapient
Focus AreaSalesforce Developer
Questions14+
Topics5

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

What's Covered

Topics covered in this interview.

01Lightning Web Components1
02SOQL & Data3
03Apex & Triggers5
04Salesforce Core Concepts2
05General & Experience3

All Interview Questions

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

1how will you put the Visualforce page and LWC page in record detail section
2What is  DML in Constructor
3Database.satefull can you share info throughout transaction
4What is mixed DML error
5Tell me test method for  API
6With sharing and without sharing in triggers
7Can we call a future from Batch?
8Can we do callouts from the Batch?
9If in after trigger context any exception occurs then record get saved to the database or not?
10Shall we assign profile or permission set to access all objects in org?
11How to hide each other records (same profile and same role them how can you implement)
12Difference between view all and modify all
13What is view state error?
14How will you handle exceptions?

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 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?
  • What does @AuraEnabled(cacheable=true) do?
  • How do you handle exceptions in Apex, and what is a custom exception?

Triggers questions

  • What are the trigger context variables?
  • What is the difference between before and after triggers, and when do you use each?
  • What is the difference between Trigger.new and Trigger.newMap?
  • What is a trigger handler framework, and why use one?

Integration questions

  • What are Platform Events, and when would you use them?
  • What is Change Data Capture?
  • What is OAuth, and which OAuth flows are used with Salesforce?
  • What is a Connected App?

Security and Administration questions

  • What are permission set groups?
  • How do you share records using Apex managed sharing?
  • What is a validation rule, and how can you bypass it for specific users?

General and experience questions

  • How do you decide between a declarative and a programmatic solution?
  • Which best practices do you follow in Apex and LWC?
  • How do you handle code reviews and technical debt on your team?

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

Integration

  • REST versus SOAP and when to use each
  • Named Credentials and external credentials
  • HttpRequest, HttpResponse and callout mocks
  • Platform Events and Change Data Capture
  • OAuth flows and Connected Apps
  • Apex REST with @RestResource

How to Prepare

The questions on this page lean towards Apex, Triggers and Integration. 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.
  • Know one integration end to end: authentication, callout, error handling and testing with a mock.
  • 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.

This Post Has 2 Comments

  1. vivek

    Good job Keep it up

Leave a Reply