Salesforce developer with 5 years of experience applied at Accenture for role of Custom Software Engineer (Management Level 10). Interview scheduled at Saturday 7th March 2026. Somehow he was not able to clear the first round, interviewer has having 13 years of experience and asked difficult questions. Interview duration was 1 hour but she ended in 25 minuets.More details: Interview scheduled by consultancy name: archelonsCandidate completed application and received interview invitation from Accenture workday email. You can choose 3 slots for different dates and time. Interview will happen on Accenture Interview portalComment for HR/Consultancy Contacts
What's Covered
Topics covered in this interview.
All Interview Questions
Every question asked in this interview, listed one by one.
- Interview scheduled by consultancy name: archelons.
- Candidate completed application and received interview invitation from Accenture workday email.
- You can choose 3 slots for different dates and time.
- Interview will happen on Accenture Interview portal.
Preparing for a Salesforce developer interview?
Browse more real company interview experiences and hands-on Apex trigger patterns.
Quick answers to key questions
- Can users under Role B edit records owned by a user under Role A? Not through the role hierarchy. The hierarchy gives users access to records owned by the users below them in their own branch, not to a different branch. Users in another branch need access through OWD, a sharing rule, manual sharing or a team. Edit access also depends on the object permission and on whether the sharing gives read or read/write.
- Can we create a form with First Name, Last Name and Address without any customization? Yes. The standard Contact or Lead object already has those fields. For a form on a public web page, use the Web-to-Lead form that Salesforce generates in Setup, which needs no code.
- Trigger: when the Case Type changes to certain values, update another field. Use a before update trigger on Case. Compare
Trigger.newwithTrigger.oldMap, and when the Type has changed to one of the target values, set the other field on the record. No DML is needed in a before trigger.