Software Engineer applicants have rated the interview process at Valeo with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 61% positive. To compare, the company-average is 65.8% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 39 days to get hired, when considering 72 user submitted interviews for this role. To compare, the hiring process at Valeo overall takes an average of 34 days.
Common stages of the interview process at Valeo as a Software Engineer according to 72 Glassdoor interviews include:
One on one interview: 22%
Skills test: 19%
Personality test: 11%
Background check: 11%
IQ intelligence test: 9%
Phone interview: 9%
Presentation: 7%
Group panel interview: 5%
Drug test: 5%
Other: 2%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 4 weeks. I interviewed at Valeo (Cairo, Cairo Governorate) in May 2020
Interview
Interview was spot on, was with a technical leader that knows what he is looking for. It was very calm and had a lot of back and forth brainstorming. a good experience but I think it was because of the interviewer.
I applied through college or university. I interviewed at Valeo (Cairo, Cairo Governorate) in Jun 2026
Interview
It was great; the interviewer was quiet but friendly. The questions were average. They asked in data structures, algorithms, and C++.
I hope it help people in the future and tank for all of you
Interview questions [1]
Question 1
If you have a base class pointer pointing to a derived class object, and you delete the pointer, what happens if the base class destructor is not declared as virtual?
A) Both base and derived destructors are called.
B) Only the derived class destructor is called.
C) Only the base class destructor is called, leading to a memory leak of the derived object's members.
D) A runtime exception is thrown.
It was good, the process was fast and it was through campus placements.
Asked questions regarding coding and oops concepts for a role graduate engineer trainee and then as a software engineer
Interview questions [1]
Question 1
Explain oops concepts and arrays related questions
It was a good experience overall. However a bit long process with a long waiting time between the different phases of the interviews, first started with an assesment then one technical interview, managerial, hr, final interview with the department manager.