Salesforce Apex is used for building custom business logic that point-and-click automation cannot handle — record triggers, batch and scheduled jobs, web service callouts, integrations with external systems, custom APIs, and complex validations. It is a strongly typed, Java-like language that runs natively on Salesforce servers, so developers usually reach for Apex when flows, validation rules, and standard configuration reach their limits.

Most Salesforce Apex interview questions revolve around triggers and bulkification, governor limits, SOQL and SOSL, the Order of Execution, test classes and code coverage, exception handling, and asynchronous Apex such as future, Queueable, batch, and scheduled methods. Interviewers rarely stop at definitions — expect scenario questions like "what happens to your trigger if 200 records are inserted at once", so prepare one hands-on example for every concept.

Salesforce Apex trigger interview questions usually test before vs after triggers, trigger.new and trigger.old, recursion control, the trigger–handler pattern, and mixed DML errors. Build a small project in a free developer org — for example, duplicate prevention and automatic field updates on Account — write one trigger per object with a separate handler class, cover it with test classes, and practise explaining what happens during bulk inserts and updates.

Salesforce Flow is the declarative automation tool used to build business processes without code — screen flows for users, record-triggered flows, scheduled flows, and autolaunched flows. It is important in automation because Salesforce has made Flow the primary automation tool and is retiring Workflow Rules and Process Builder, so admins, consultants, and developers are all now expected to build and maintain automation in Flow.

Salesforce Flow Builder is the drag-and-drop editor used to create and edit flows. You place elements like Get Records, Decision, Assignment, Loop, and Update Records on a canvas, connect them with logic, define resources such as variables, formulas, and text templates, and test everything with the debug option before activating the flow.

Salesforce Flow Orchestration is used to coordinate multi-step, multi-user processes that cannot finish in a single run. Unlike a normal flow, an orchestration is organised into stages and steps, can pause and wait for a person to complete a work item, and then continues automatically — useful for onboarding, order fulfilment, and approval processes that span multiple teams or take place over several days.

Open the flow in Flow Builder, click Debug, and pass the record IDs or input values the flow expects — you can then step through each element and see the values stored in variables at every stage. For record-triggered flows that fail silently, check Paused and Failed Flow Interviews in Setup and enable debug logs on your user to identify the exact element and error message.

You cannot delete a Salesforce flow while it is active, so go to Setup → Flows, deactivate the flow or its active version first, and then delete the version or the entire flow. If the flow is referenced by another flow, process, or installed package, remove that dependency first, and always download the flow metadata before deleting so you can restore it later.

There is no direct download button in the UI, so you export a Salesforce flow as metadata using VS Code with the Salesforce Extensions, Workbench, or any metadata retrieval tool by pulling the Flow component through a package.xml file. Keep the retrieved XML in version control — it acts as a backup and can be deployed to a sandbox or another org via change sets or a DevOps pipeline.

Typical Salesforce Flow interview questions cover the difference between record-triggered, scheduled, screen, and autolaunched flows, before-save vs after-save record updates, avoiding recursive flows, subflows, error handling, and when to choose Flow over Apex. Interviewers in India often add a live scenario — such as updating a related record when an opportunity is closed-won — so build a few such flows end to end instead of only reading theory.

Lightning Web Components (LWC) is Salesforce's modern, JavaScript-based framework for building custom user interfaces on the Lightning platform. It is built on standard web technologies like custom elements and ES modules, performs faster and lighter than the older Aura framework, and is used to create custom record and app pages, embed components inside Flow screens, and build Experience Cloud sites.

Enable Debug Mode for your user in Setup so the JavaScript loads in readable form instead of minified code, then use the browser developer tools — console logs, breakpoints, and the network tab for Apex call errors. The Salesforce Lightning Inspector Chrome extension and the VS Code debugger for Lightning components make it easier to inspect component state and step through the code.

Frequent Lightning Web Components interview questions cover the @api, @track, and @wire decorators, lifecycle hooks such as connectedCallback and renderedCallback, communication between components using custom events and Lightning Message Service, reactive vs non-reactive fields, and calling Apex imperatively vs through wire. Many companies also include a short live-coding task, such as building a searchable table that saves a record, so practise small components in a developer org.

Strengthen HTML, CSS, and modern JavaScript first — arrays, objects, promises, and modules — because Lightning Web Components basics are essentially web standards applied to Salesforce. Then follow the beginner LWC learning path on Trailhead, deploy simple components like a form, a search bar, or a related list to a free developer org, and only after that move on to data integration with Apex and superbadges.

Agentforce is Salesforce's agentic AI layer for building AI agents that can answer questions and take actions on your Salesforce data — configured through topics, actions, and instructions rather than heavy code. Beginners usually start with the Agentforce modules on Trailhead inside a playground or trial org, and it helps to be comfortable with Flow first, because most agent actions are built on top of flows and Apex.