Most interviews cover a mix of declarative and programmatic topics: Workflow Rules vs Flows, profile vs permission sets, OWD and sharing, order of execution, SOQL and SOSL, trigger best practices, governor limits, async Apex, and integration basics. Scenario questions like "how would you design X" are increasingly common, so prepare short, structured answers for each topic and back them with examples from your own projects or practice orgs.

Salesforce interview questions for freshers focus on fundamentals — CRM concepts, objects and fields, relationships, record types, profiles, OWD, basic flows and SOQL. For 5 years experience, interviewers expect design-level depth: trigger frameworks and bulkification, choosing between async Apex options, integration design and error handling, security at scale, data migration, deployment and DevOps practices, plus detailed project walkthroughs where you justify your technical decisions.

Experienced candidates are usually tested on end-to-end order management, discounts and promotions, context and pricing rules, EPC modelling, OmniScript and FlexCard design, integration procedure performance, deployment, and troubleshooting production issues. Interviewers also expect industry scenarios from communications, energy, insurance or health clouds, so be ready to explain a complete business flow you have built and the design trade-offs you made.

Practise explaining complete business scenarios from requirement to solution — for example, designing an OmniScript for customer onboarding, building an integration procedure that aggregates data from multiple objects, or handling an order modification with promotions. Structure every answer as requirement, components used, data flow, error handling and testing. Rehearsing scenarios from telecom, energy or insurance use cases makes your answers far more convincing.

Frequently asked ones include OmniScript vs FlexCard, types of DataRaptors and when to use each, integration procedures vs remote actions, how the OmniStudio Index works, element reuse, error handling, performance optimization and deployment of OmniStudio assets. Interviewers often follow up with "how would you troubleshoot a slow integration procedure", so prepare real optimization examples like caching, reduced looping and moving logic into integration procedures.

Focus on product catalog and attributes, pricing procedures, context rules, advanced rules, promotions and discounts, order management, asset management and batch amendments. Also understand how Vlocity CPQ differs from Salesforce CPQ and how pricing calculations flow through the cart. Scenario questions around applying promotions correctly or fixing a misfiring context rule are very common.

Prepare REST vs SOAP, when to use Bulk API, Streaming API, Platform Events and Change Data Capture, named credentials and OAuth flows, callout limits and how to handle them, error handling and retry strategies, external IDs and upsert, middleware basics, and the standard integration patterns. Be ready to walk through an end-to-end integration you have built, covering authentication, security, monitoring and failure handling.

The four core patterns are Request and Reply for synchronous real-time responses, Fire and Forget for near real-time processing without waiting for a response, Batch Data Synchronization for scheduled large-volume data movement, and Remote Call-In when external systems call Salesforce to create or update data. Choose based on latency needs, data volume and whether the external system needs an immediate response, and always design around governor limits.

Start with REST and JSON fundamentals, then complete the API-related Salesforce learning modules and read the integration documentation. Practise in a developer org using Postman or Workbench: make callouts, handle responses, set up named credentials, then build inbound endpoints and experiment with Platform Events. Once comfortable, study integration patterns and learn one middleware such as MuleSoft to understand enterprise-scale design.

Build deep hands-on mastery of APIs, authentication standards like OAuth 2.0, SAML and JWT, integration patterns, and data synchronization strategies. Learn at least one middleware, then move into designing cross-system solutions and documenting them. Formal credentials along the integration and application architect paths help validate your knowledge, but architects are judged on design thinking, so practise writing solution designs that cover security, scalability, limits and error handling.

Expect questions on decorators like @api, @track and @wire, lifecycle hooks such as connectedCallback and renderedCallback, communication between components through custom events and Lightning Message Service, reactivity, composition and slots, Lightning Data Service, and refreshApex. Since LWC is JavaScript-heavy, interviewers also test closures, promises, async/await and array methods, so revise core JS along with component concepts.

Common ones cover trigger best practices and bulkification, trigger vs flow decisions, order of execution, SOQL and DML governor limits, exception handling, test classes and coverage requirements, and the differences between future, Queueable, Batch and Scheduled Apex. You should also be able to explain a real bug or performance issue you have fixed, since experienced interviewers rarely stop at definitions.

Interviewers typically ask about the Database.Batchable interface and its start, execute and finish methods, choosing the right batch scope size, stateful vs stateless behaviour, chaining batches using Queueable, scheduling batch jobs, monitoring through AsyncApexJob, and per-transaction limits inside execute. Prepare a use case explaining why Batch Apex was the right choice over Queueable or Scheduled Apex for large data volumes.

Expect questions on what Agentforce is and how it differs from earlier Einstein bots, how agents, topics and actions work together, building custom actions with Flows and Apex, grounding responses with your data, the reasoning and planning layer, prompt builder, guardrails and the Einstein Trust Layer, and how agents are tested and deployed. Use-case questions around service and sales automation are also very common.

Prepare the record-level security model in full: OWD, role hierarchy, sharing rules, manual sharing, Apex managed sharing, account and opportunity teams, and territory management, along with profiles and permission sets for object-level access. Interviewers love debugging scenarios like "a user cannot see a record, how do you find out why", so practise a step-by-step troubleshooting approach and understand With Sharing vs Without Sharing behaviour in Apex.