mPHATEK Salesforce Interview Questions

CompanymPHATEK
Focus AreaSalesforce Developer
Questions14+
Topics6

mPHATEK System – Salesforce Developer Interview Questions

What's Covered

Topics covered in this interview.

01Flows & Automation2
02Lightning Web Components1
03SOQL & Data1
04Apex & Triggers5
05Salesforce Core Concepts1
06General & Experience4

All Interview Questions

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

1What is workflow?
2What are the actions in the workflow?
3What is a lightning component bundle?
4What are relationships in salesforce and explain those.
5What are the types of trigger and when to use this?
6What is apex?
7Batch apex?
8What are the methods of the batch and which interface is implemented in the batch?
9How to test Queueable Apex?
10What is the difference between profile and roles?
11What is the object in salesforce?
12What are the types of objects in salesforce?
13Type of controller in salesforce?
14And explain when to use that?

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

  • How do you handle exceptions in Apex, and what is a custom exception?
  • What is a SOQL for loop, and why is it useful for large result sets?
  • What is Database.Stateful in Batch Apex?
  • How do you read values from custom metadata types in Apex?
  • What is the difference between static and instance variables in Apex?

Flows and Automation questions

  • How do you debug a Flow?
  • What are the different types of Flow in Salesforce?
  • What is the difference between a before-save and an after-save record-triggered Flow?
  • When would you choose Flow over Apex?

Triggers questions

  • 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?
  • What are the trigger context variables?
  • What is the difference between before and after triggers, and when do you use each?

SOQL and Data questions

  • What is an external ID, and how is it used with upsert?
  • How do you query polymorphic fields such as WhoId and WhatId?
  • What are custom indexes, and when would you request one?

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

Flows and Automation

  • Screen, record-triggered, scheduled and autolaunched Flow types
  • Before-save versus after-save behaviour
  • Fault paths and error handling
  • Invocable Apex methods and Apex-defined variables
  • Subflows and reusable logic
  • Flow limits and bulk behaviour

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

How to Prepare

The questions on this page lean towards Apex, Flows and Automation and Triggers. 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.
  • Be ready to compare a Flow and an Apex solution for the same requirement and justify your choice.
  • Write a trigger with a handler class from memory, then test it with 200 records to prove it is bulk safe.
  • 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