Applications Developer applicants have rated the interview process at Accenture with 2.8 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 66.9% positive. This is according to Glassdoor user ratings.
Common stages of the interview process at Accenture as a Applications Developer according to 4 Glassdoor interviews include:
One on one interview: 22%
Presentation: 22%
Phone interview: 11%
Group panel interview: 11%
Skills test: 11%
Background check: 11%
Personality test: 11%
Here are the most commonly searched roles for interview reports -
I applied through other source. I interviewed at Accenture (Hyderābād) in May 2023
Interview
Interview was difficult a bit. Most of the questions were asked related to the current project only. They were asking the questions form the basic concept to the pro level. Scenario based questions were asked.
Interview questions [1]
Question 1
Most of the questions were asked from the current project only .
I applied through a recruiter. I interviewed at Accenture
Interview
First is the application stage, where you submit your CV or application form and the employer reviews your qualifications.
Next is often an initial screening, which may be a short phone or video call. This is usually to confirm basic details, your experience, and your interest in the role.
If you pass that, you move to a formal interview, which could be in person or online. This is where they ask more detailed questions about your skills, experience, and how you handle situations.
1. Initial Interview with HR.
2. Technical Interview - start with telling about myself, walkthrough experience and projects. Asks about Javascript Libraries and development tools. Challenges encountered
3. Job Offer
Interview questions [1]
Question 1
Can you walkthrough me to your expercience and previous projects.
I applied online. I interviewed at Accenture (New Delhi) in Mar 2026
Interview
The interview was intense and practical, focusing exclusively on hands-on Experience Cloud implementation rather than theoretical knowledge. The interviewer bypassed definition-based questions entirely, instead posing complex, real-time scenarios—such as designing user sharing models, configuring custom LWR templates, or troubleshooting license limitations—to evaluate actual project experience and implementation expertise.
Interview questions [1]
Question 1
How would you architect an Experience Cloud portal for 100k+ users?