Round 1: HackerRank Test

After about one week of applying for the role, we got a notification of a HackerRank test conducted by the company. The test was of 150 minutes and there were 4 questions:

Section 1: MCQs (41 questions)

From the total span of 150 minutes, we were given 95 minutes to solve the MCQs. Within these, there were sections which comprised of almost every technical subject you can think of including- DBMS, SQL, OOP, COA, C++, Java, Algorithm, Quants, Verbal, and Logical. Each section of these subjects were time based. Eg. for quants there were 4 questions to be solved in 7 minutes and 5 debugging questions to be solved in 18 minutes. So, this was the drill for this section.

Please Note: It is important for you to maintain accuracy and precision in each section, because the cumulative score is based on that only.

Section 2: Coding (1 question)

Next was to solve a coding question in about 30 minutes. Everyone of my batch received different coding problems. I got the one that involved a lot of Object Oriented Programming(medium difficulty). Less than testing my coding skills in C++, they were actually testing my compatibility skills for writing an optimized code and modifying/debugging the existing one.

Although, I was unable to solve the question completely, my code successfully ran for 6/8 test cases.

Please Note: Even if you’re unable to solve the complete code, it is important that you show the examiner how well-verse you are with your problem-solving skills. Mention your approach in comments and try to run for more than 60% of the test cases. If you performance is good in the rest sections, you might be able to clear this.

Section 3: SQL (2 questions)

Finally, in this section we were given 2 SQL questions of medium to easy level. They were to be solved in about 25 minutes. One was a simple one that included the use of aggregate functions and range functions. Other one was a bit complex that involved almost 4 tables and usage of joins was repetitively complex. However, I was able to solve both and ran 100% test cases.

Please Note: If you want to clear this round, it is important that you solve at least 1.5 SQL questions.

Amdocs ASE On-Campus Interview Experience

Hi everyone,

In this interview experience, I’m going to be telling about my experience with Amdocs for the role of Associate Software Engineer as a part of my on-campus hiring drive.

Eligibility Criteria: No Active Back logs, CGPA>7.5

Similar Reads

Round 1: HackerRank Test

After about one week of applying for the role, we got a notification of a HackerRank test conducted by the company. The test was of 150 minutes and there were 4 questions:...

Round 2: Technical Interview

Out of almost 85 students, only 13 students got invited for the technical interview. The platform was MS teams, so you should be familiar with using it as you may have to share your screen and perform live coding....

Round 3: Group Discussion

After the technical interview round, only 7 students were shortlisted out of 13. Moving further, we were invited for a virtual GD round. Again, it was an MS teams call with everyone on the same call and a panel of almost 5-6 experts. Each one of them was judging something or the other. We all were given a topic ‘ Rise of Generative AI’ and we were asked to talk about it and discuss our views on the same. This went on for about 40 minutes....

Round 4: HR Discussion

If you have cleared the GD, it’s pretty much just to discuss your offer and work preferences. Of the 7 students, 5 received the offer to work with Amdocs. It went on for about 15-20 minutes and involved just basic discussion about my location preferences and salary structure....