Software Engineer applicants have rated the interview process at Infosys 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 79% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 19 days to get hired, when considering 3 user submitted interviews for this role. To compare, the hiring process at Infosys overall takes an average of 29 days.
Common stages of the interview process at Infosys as a Software Engineer according to 3 Glassdoor interviews include:
Phone interview: 17%
One on one interview: 17%
IQ intelligence test: 17%
Skills test: 17%
Background check: 17%
Personality test: 17%
Here are the most commonly searched roles for interview reports -
It was easy, if you're applying on java know the technical questions, and the basics, like what is a constructor, they are very nice and and understanding. I have not been asked to code but answer the questions.
Interview questions [1]
Question 1
java know the technical questions, and the basics, like what is a constructor,
It’s goes well. Waiting for the update so hoping for good thing. Other than that everything good I felt. First round is Technical and followed by the manager round which is also quite good experience
Interview questions [1]
Question 1
Tell me about yourself ? What is your current project?
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.