Developer applicants have rated the interview process at Amdocs with 3 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 80% positive. This is according to Glassdoor user ratings.
Candidates applying for Developer roles take an average of 21 days to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at Amdocs overall takes an average of 23 days.
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 3 weeks. I interviewed at Amdocs (Pune) in Jun 2024
Interview
First the screening of resume happens.
After that you will have a technical round. Once cleared, there will be a managerial round, basic leadership and culture talks. Level of technical depends on the position you have applied/.
Interview questions [1]
Question 1
Explain your current project
Java OOPs concept
Collection Framework
JVM memory managment
Array programs /String programs
I applied online. The process took 1 week. I interviewed at Amdocs
Interview
2 step interview with first being general questions from HR, second being technical interview with managers to determine what position best fits your role. Questions were about SQL and basic scripting
Interview questions [1]
Question 1
Write an SQL query to join 2 tables together with an inner join
I applied online. I interviewed at Amdocs (Pune) in Aug 2024
Interview
I recently interviewed at Amdocs for a Java backend role. The process included an online coding test, two technical rounds, and an HR round. The coding test had DSA problems focusing on arrays and strings. In the technical rounds, I was asked about Java, Spring Boot, SQL, and real-time project scenarios, especially related to REST APIs and debugging. They also asked about my previous work experience and how I handled production issues. The interviewers were polite and gave time to explain my approach. Overall, it was a smooth and professional experience with a focus on problem-solving and backend fundamentals.
Interview questions [1]
Question 1
"How would you handle an API failure in a live production environment, and what steps would you take to debug it?"