Interview blog

Accenture Salesforce Developer Interview Questions

Written April 30, 2026Updated November 3, 202612 min read
pexels mikhail nilov 7682106

What Accenture's own hiring pages and job posts say about the process, and the Apex, LWC, trigger and security questions worth preparing.

Accenture does not publish its question bank, so any list of Accenture Salesforce developer interview questions is an informed guess. You can make that guess much better. Accenture's careers site describes the process: interviews by phone, video or in person, with the number of rounds depending on the role, and for some roles an online coding assessment of roughly 30 to 90 minutes. Its Salesforce job posts name the skills they want. Apex and Lightning Web Components (LWC) appear in every posting we read, and SOQL, Flows, REST integrations and the security model appear in several. Prepare those in depth, read your own posting's "must have" line, and know that Accenture prohibits using AI to generate your answers in interviews, and in assessments unless the assessment says otherwise.

What Accenture publishes about the process

Accenture's "hiring journey" page lists six steps: an email confirming your application, a recruiter review, an invitation to interview, the interviews themselves, a skills assessment for some roles, and the offer. It says plainly that "the number of interviews you'll have depends on the role."

The technical assessment is the part with the most detail:

  • What Accenture says — Why it matters
  • Completed online in one sitting, typically within 72 hours of the invitation — You choose when to sit it, so pick a quiet slot with a stable connection
  • Most take about 30 to 90 minutes, and the test submits automatically when time runs out — Watch the clock; the test submits automatically when time runs out
  • Accenture's assessment page points candidates to HackerRank's sample test and free community to practise the coding interface — Try the sample test so the interface is familiar before the real one
  • Scored automatically against set criteria, and it "does not replace interviews" — Passing gets you to the technical conversation, not the offer
  • If you do not pass, you wait at least 90 days to retake the same assessment — Treat the first attempt as the real one

Two more rules are easy to miss. Accenture's India page says candidates there "may have only one active application at any time", so choose the posting that fits you best rather than applying to five. And Accenture's AI guidance draws a clear line. For practice it says: "Use AI to rehearse common questions, get feedback, and boost your confidence." But using AI products during interviews to generate answers is prohibited, and so is using AI in assessments unless the assessment says otherwise. Accenture says it uses "proctoring tools and AI-detection methods" and that violations can lead to disqualification.

For the general Accenture process, including how to spot fake offers, see our Accenture interview process guide. The rest of this page is about the Salesforce-specific part.

Read the job post first

Your most useful prep document is the posting you applied to. In India, some of Accenture's Salesforce roles carry generic titles such as "Custom Software Engineer" or "Application Developer", and the Salesforce part sits in a line that reads "Must have skills : Salesforce Lightning Web Components". Search Accenture's job board by skill, not just by title, or you may miss them.

Here is what five live Accenture postings asked for when we read them on 18 October 2026:

  • Posting — Experience asked — Skills named
  • Salesforce Developer (CPQ), Chesterbrook, PA — At least 2 years of Salesforce development and 2 years of CPQ — Sales Cloud, Apex, LWC, REST API integrations, JavaScript; Platform Developer II or CPQ Specialist certification a plus
  • Salesforce Developer Sr., Monterrey — 4+ years — Apex, LWC, Visualforce, JavaScript, SOQL optimisation; must hold at least one Salesforce certification, such as Platform App Builder or Platform Developer I
  • Salesforce Developer, Madrid — 2+ years — Apex, LWC, Visualforce, REST/SOAP APIs, automation with Flow, Process Builder or Apex triggers
  • Salesforce Developer, Bucharest — Hands-on coding background — Apex, LWC, Flows; Agentforce or Einstein Copilot experience "a big plus"
  • Application Developer, Kolkata — 5+ years (posting minimum: 3) — LWC and Aura, pub-sub and Lightning Message Service, Lightning Data Service and wire adapters, Apex, SOQL/SOSL, governor limits, CRUD/FLS/sharing

The core is the same everywhere; the extras decide the deep-dive. A CPQ posting will get CPQ questions, and one that mentions Agentforce will probably get one about it. If your posting names something you have not used, prepare an honest answer about how you would learn it rather than bluffing.

The questions worth preparing

Grouped by the skills the postings name, each with what the interviewer is checking and a short answer to build on.

Apex and triggers

1. What are governor limits, and how do you write code that stays inside them?

They are checking whether you have written code for a shared, multi-tenant platform. Trailhead gives the numbers most interviewers expect: 100 SOQL queries per synchronous transaction (200 for asynchronous Apex) and 150 DML statements. Triggers run on batches of up to 200 records, so the answer is bulkification: assume every trigger receives a collection, query once outside the loop with WHERE Id IN :ids, and collect changes in a list for a single DML call.

2. Write a trigger that keeps a count of invoices on each account.

The classic live-coding task. Assume Invoice__c has a lookup field Account__c and Account has a number field Invoice_Count__c.

trigger InvoiceCount on Invoice__c (after insert, after update, after delete, after undelete) {
    Set<Id> accountIds = new Set<Id>();
    if (Trigger.new != null) {
        for (Invoice__c inv : Trigger.new) {
            if (inv.Account__c != null) accountIds.add(inv.Account__c);
        }
    }
    if (Trigger.old != null) {
        for (Invoice__c inv : Trigger.old) {
            if (inv.Account__c != null) accountIds.add(inv.Account__c);
        }
    }
    if (accountIds.isEmpty()) return;

    Map<Id, Account> updates = new Map<Id, Account>();
    for (Id accId : accountIds) {
        updates.put(accId, new Account(Id = accId, Invoice_Count__c = 0));
    }
    for (AggregateResult ar : [
        SELECT Account__c accId, COUNT(Id) total
        FROM Invoice__c
        WHERE Account__c IN :accountIds
        GROUP BY Account__c
    ]) {
        updates.get((Id) ar.get('accId')).Invoice_Count__c = (Integer) ar.get('total');
    }
    update updates.values();
}

What makes it strong: one query and one DML statement for any batch size. It reads Trigger.old as well as Trigger.new, because delete triggers only have Trigger.old, and because an invoice moved from one account to another must update both. It sets every touched account to zero first, so an account whose last invoice was deleted does not keep a stale count. The weak version loops over Trigger.new, queries inside the loop and ignores deletes.

Expect two follow-ups. "Where would this logic live in a real project?" Answer: in a handler class, with the trigger only calling it. "Why not a roll-up summary field?" Answer: roll-up summary fields need a master-detail relationship; with a lookup you need code or a flow.

3. Before trigger or after trigger?

Use a before trigger to validate or change values on the records being saved. Use an after trigger when you need system-set values such as the record Id, or when you are changing other records. Records in an after trigger are read-only.

4. How do you call an external system from a trigger?

Not directly. Trailhead is explicit that a callout from a trigger must be asynchronous, so the trigger is not blocked waiting for a response. Enqueue a Queueable class that implements Database.AllowsCallouts, or use a method marked @future(callout=true).

Asynchronous Apex

5. Future, Queueable or Batch: how do you choose?

Give trade-offs, not definitions.

  • A future method is the simplest, but its parameters must be primitives or collections of primitives (an sObject could change before the method runs), it cannot call another future method, and execution order is not guaranteed.
  • Queueable accepts non-primitive members such as sObjects, returns a job ID you can monitor, and can chain one child job.
  • Batch Apex is for large volumes: start, execute and finish, a default batch size of 200, up to 50 million records through a QueryLocator, and a fresh set of governor limits for each batch.

Lightning Web Components

6. Walk through the LWC lifecycle hooks.

constructor() runs first, before public properties are set, so do not read them there. connectedCallback() runs when the component is inserted into the DOM, and it can fire more than once. renderedCallback() runs after every render, so guard one-time work with a flag. disconnectedCallback() runs on removal, and errorCallback() catches errors thrown in descendant components' lifecycle hooks. The detail that separates strong answers: a child's renderedCallback() runs before its parent's.

7. What does `@api` do, and what should a component never do with it?

@api makes a field public, so a parent can set it. A component should not change the value of its own @api property. If it needs a normalised version, it stores that in a private property.

8. `@wire` or an imperative Apex call?

To wire an Apex method it must be cacheable, and a cacheable method cannot perform DML. So @wire suits reactive reads, and anything that saves data, or a read you want to trigger on a button click, should be called imperatively.

9. How do components talk to each other?

A parent passes data down through properties or calls a child's public methods. A child talks up by dispatching a CustomEvent; the best practice is to send primitives or a copy of the data in event.detail. For components that are not in the same hierarchy, the Kolkata posting asks for two patterns by name: a pub-sub module and Lightning Message Service.

Data, security and testing

10. SOQL or SOSL?

SOQL queries one object at a time and matches exactly by default. SOSL searches text across many objects in one query and matches on words. Use SOQL to retrieve records of a known object; use SOSL for a search box.

11. Explain the sharing model.

Start from object and field access, which Trailhead recommends managing with permission sets and permission set groups. Then the record-level layers: organisation-wide defaults set the most restrictive baseline, the role hierarchy opens records owned by people below you, sharing rules add exceptions for groups, and manual sharing lets an owner share a single record. Sharing rules only ever add access.

12. What do Salesforce tests need before you can deploy?

At least 75% of Apex code covered and every test passing. By default, tests cannot see existing org data, and test records roll back when the test finishes. @IsTest(SeeAllData=true) exists, but Trailhead calls it not a best practice; create your own test data.

Automation and integration

13. "Workflow rule or trigger?"

Older question lists still ask this, but the answer has changed. Salesforce stopped letting orgs create new workflow rules in Winter '23 and new Process Builder processes in Summer '23, and points new automation to Flow. Answer the modern version, Flow or Apex: declarative first, Apex when the logic, volume or error handling outgrows a flow. Then mention migration, because client orgs still run old automation, and the Madrid posting still lists Process Builder.

14. When would you use platform events?

For event-driven integration, where publishers and subscribers do not depend on each other. Apex triggers can subscribe to platform events, and external systems publish and subscribe through the Pub/Sub API. If the postings mention REST or SOAP, be ready to describe one integration you built end to end: authentication, error handling and what happened when the other system was down.

The behavioural round

Accenture's own tips page explains why this round matters for developers: "Many of our roles mean directly interacting with clients." Expect questions about how you work with people, not just code. Prepare short STAR stories (situation, task, action, result) for:

  • a requirement that changed late, and how you handled scope with the client or your lead
  • explaining a platform limit, such as a governor limit, to someone non-technical
  • a production bug you traced and fixed, and what you changed so it did not recur
  • why Accenture, tied to the kind of client work in your posting

For more on Accenture's later rounds, see our guide to Accenture managerial round questions.

What to do this week

  1. Copy the "must have" and "nice to have" lines from your posting and rank your confidence in each.
  2. If you get an assessment invite, book a quiet 90-minute slot inside the 72-hour window and try a HackerRank sample test first.
  3. Write the invoice-count trigger above from memory, without autocomplete, then add the handler class.
  4. Build one small LWC that calls Apex imperatively to save a record and shows a toast on success or error.
  5. Rehearse answers out loud. Accenture allows AI for practice, and Verve AI's Mock Interview has an AI recruiter ask you questions and gives you a performance report with feedback and scoring afterwards, and its job-description tool can generate practice questions from a pasted posting. For more coding practice, see our Salesforce coding interview questions.

Sources

  • Accenture hiring steps, assessment format, 72-hour window, 30 to 90 minutes, auto-submit, scoring, 90-day retake: https://www.accenture.com/us-en/careers/explore-careers/area-of-interest/journey-to-accenture
  • HackerRank sample test and India one-active-application rule: https://www.accenture.com/in-en/careers/explore-careers/area-of-interest/journey-to-accenture
  • Accenture rules on AI in interviews and assessments, proctoring and AI detection: https://www.accenture.com/us-en/careers/explore-careers/area-of-interest/ai-usage-job-search
  • Behavioural interview tip on client-facing roles: https://www.accenture.com/us-en/careers/explore-careers/area-of-interest/pro-tips
  • Posting, Salesforce Developer (CPQ), Chesterbrook: https://accenture.wd103.myworkdayjobs.com/AccentureCareers/job/Chesterbrook-955-Chesterbrook-Blvd-MS/Salesforce-Developer--CPQ-_R00331987
  • Posting, Salesforce Developer Sr., Monterrey: https://accenture.wd103.myworkdayjobs.com/AccentureCareers/job/Monterrey/Salesforce-Developer-Sr_R00360101
  • Posting, Salesforce Developer, Madrid: https://accenture.wd103.myworkdayjobs.com/AccentureCareers/job/Madrid-Torre-Chamartin/Salesforce-Developer_R00358441
  • Posting, Salesforce Developer, Bucharest: https://accenture.wd103.myworkdayjobs.com/AccentureCareers/job/Bucharest/Salesforce-Developer_R00359693
  • Posting, Application Developer (LWC), Kolkata: https://accenture.wd103.myworkdayjobs.com/AccentureCareers/job/Kolkata/Application-Developer_ATCI-5141953-S1895192-1
  • India "Custom Software Engineer" title with LWC as the must-have skill: https://accenture.wd103.myworkdayjobs.com/AccentureCareers/job/Hyderabad/Custom-Software-Engineer_ATCI-5375304-S1962852-1
  • Governor limits (100/200 SOQL, 150 DML), batches of 200, bulkification: https://trailhead.salesforce.com/content/learn/modules/apex_triggers/apex_triggers_bulk
  • Before and after triggers, Trigger.new and Trigger.old by event, async callouts from triggers: https://trailhead.salesforce.com/content/learn/modules/apex_triggers/apex_triggers_intro
  • Roll-up summary fields need master-detail: https://trailhead.salesforce.com/content/learn/modules/point_click_business_logic/roll_up_summary_fields
  • Future method parameters and limits: https://trailhead.salesforce.com/content/learn/modules/asynchronous_apex/async_apex_future_methods
  • Queueable Apex: https://trailhead.salesforce.com/content/learn/modules/asynchronous_apex/async_apex_queueable
  • Batch Apex: https://trailhead.salesforce.com/content/learn/modules/asynchronous_apex/async_apex_batch
  • LWC lifecycle hooks: https://lwc.dev/guide/lifecycle
  • @api and private properties: https://lwc.dev/guide/javascript
  • Component events and parent-child communication: https://lwc.dev/guide/events
  • @wire, imperative Apex and cacheable methods: https://trailhead.salesforce.com/content/learn/modules/lightning-web-components-and-salesforce-data/use-apex-to-work-with-data
  • SOQL and SOSL: https://trailhead.salesforce.com/content/learn/modules/apex_database/apex_database_sosl
  • Sharing model layers: https://trailhead.salesforce.com/content/learn/modules/data_security/data_security_overview
  • 75% coverage, test data rollback, SeeAllData: https://trailhead.salesforce.com/content/learn/modules/apex_testing/apex_testing_intro
  • Workflow Rules and Process Builder retirement timeline: https://www.salesforceben.com/salesforce-to-retire-workflow-rules-and-process-builder/
  • Platform events architecture: https://trailhead.salesforce.com/content/learn/modules/platform_events_basics/platform_events_architecture
  • Verve Mock Interview (AI recruiter, scored report): https://docs.vervecopilot.com/features/mock-interview
  • Verve job-description question generator: https://docs.vervecopilot.com/guides/linkedin-job-mock-interview
R

Ryan

CEO of Verve AI

Related reads

Explore related blog posts

How 8 Indian Firms Run the IT Services Interview Process
October 27, 2026Interview blog

How 8 Indian Firms Run the IT Services Interview Process

TCS, Infosys, Wipro, Cognizant, Capgemini, Accenture, HCLTech and Genpact compared: shared stages, real differences, what to prepare, and fake-offer signs.

Read story
Top 30 Most Common accenture salesforce developer interview questions You Should Prepare For
October 10, 2025Interview prep guide

Top 30 Most Common accenture salesforce developer interview questions You Should Prepare For

Read about top 30 most common accenture salesforce developer interview questions you should prepare for with practical tips and examples. A must-read for job seekers.

Read guide
TCS Interview Process: The NQT, Interview Rounds and How to Prepare
October 13, 2026Interview blog

TCS Interview Process: The NQT, Interview Rounds and How to Prepare

TCS interview process explained from TCS's own pages: the 190-minute NQT, Prime, Digital and Ninja tracks, and preparation.

Read story
Infosys Interview Process: What Infosys Publishes and How to Prepare
October 13, 2026Interview blog

Infosys Interview Process: What Infosys Publishes and How to Prepare

Infosys interview process, from Infosys's own pages: the proctored online assessment, its rules, interviews and fraud warnings.

Read story
Wipro Interview Process: What Wipro Publishes and How to Prepare
October 13, 2026Interview blog

Wipro Interview Process: What Wipro Publishes and How to Prepare

Wipro interview process: what Wipro officially publishes on programs, interviews and fraud, and what it leaves to your invitation.

Read story
Cognizant Interview Process: GenC, Lateral Hiring and How to Prepare
October 13, 2026Interview blog

Cognizant Interview Process: GenC, Lateral Hiring and How to Prepare

Cognizant interview process for GenC freshers and experienced hires: the published steps, assessments, checks and preparation.

Read story
Why Page Numbering In Word Matters More Than You Think
February 3, 2026Interview blog

Why Page Numbering In Word Matters More Than You Think

Discover why page numbering in Word impacts navigation, citations, professional formatting, and workflow efficiency.

Read story
How Can Entering Page Numbers In Word Make Your Documents And Interview Presentations Clearer
February 13, 2026Interview blog

How Can Entering Page Numbers In Word Make Your Documents And Interview Presentations Clearer

Learn how adding page numbers in Word improves navigation and clarity for documents and interview presentations.

Read story
How Can Paid For Advertising In The Local Paper Help You Win Interviews And Opportunities
March 3, 2026Interview blog

How Can Paid For Advertising In The Local Paper Help You Win Interviews And Opportunities

Learn how paid local newspaper ads boost your visibility, attract employers, and lead to interviews.

Read story

Walk into every interview prepared and confident

Get Started For Free

Available on Mac, Windows, browser and mobile