System Engineer applicants have rated the interview process at Infosys with 2.4 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 85% positive. To compare, the company-average is 71.5% positive. This is according to Glassdoor user ratings.
Candidates applying for System Engineer roles take an average of 7 days to get hired, when considering 1,011 user submitted interviews for this role. To compare, the hiring process at Infosys overall takes an average of 14 days.
Common stages of the interview process at Infosys as a System Engineer according to 1,011 Glassdoor interviews include:
One on one interview: 28%
IQ intelligence test: 17%
Skills test: 13%
Personality test: 11%
Background check: 10%
Presentation: 7%
Group panel interview: 5%
Drug test: 4%
Phone interview: 2%
Other: 2%
Here are the most commonly searched roles for interview reports -
Basic HR Questions. In technical round basic questions regarding the programming language you are comfortable with. If worked on any project then questions regarding project. Also they might ask the logic for Fibonacci or similar question.
Interview questions [1]
Question 1
Explain OOP's concept.
Is java fully Object oriented?
Why is java case sensitive?
There was 2 rounds of interview. 1st round is aptitude. 2nd round was f2f interview. Interview was moderate level if you are well known about you resume and some basic coding questions.
The first round was aptitude. It was of medium level. Then HR round. He asked about my projects, ML concepts which I highlighted in my resume, the a lot of behavioural questions
Interview questions [1]
Question 1
Tell me about yourself.
Explain what is machine learning to a kid.
If you get opportunities for another more ML related roles, would yo go?
How do you see yourself in 5 years?
What if you are not satisfied with the tech Infosys teaches you?
The interview process was straightforward and highly accessible, focusing primarily on fundamental concepts. Candidates were asked basic Object-Oriented Programming (OOP) questions, requiring them to elaborate on core principles like inheritance, polymorphism, and encapsulation without diving into complex technicalities.