An average interview process, while not necessarily bad, often lacks the polish, consistency, or thoroughness of an ideal hiring experience. In such cases, the process might get the job done, but it leaves room for improvement in areas like candidate experience, evaluation depth, and alignment across the hiring team.
Interview questions [1]
Question 1
What is the difference between == and equals() in Java?
L3 interview:
Pretty inefficient process, with certain people having to wait 6+ hours, and I heard of one person who waited an entire day and had to come again the next day.
Interview itself was relatively standard,
stage 1: Asking leetcode mediums and expecting optimal solution, then moving to core cs concepts like oops and sql.
stage 2: Diving into projects, with questions on the tougher side, like specifics about the architecture of docker.
Interview questions [1]
Question 1
Sort an array containing elements from the set (0,1,2)
The interview was related to general software engineering questions. Design patters, unit and e2e testing, deplyment to cloud, frontend to backend comunication, team collaboration, requirements shaping, release process. The interview was conducted in a friendly manner.
I applied online. I interviewed at Infosys (Singapore)
Interview
first I had the screening round.
they like the profile but was not able to sponsor visa. Hence they said they will get in touch with me when the time is right.
Interview questions [1]
Question 1
Screening questions like do you possess this skill or not?