Software Developer applicants have rated the interview process at Thales with 2.3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 67% positive. To compare, the company-average is 79.8% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Developer roles take an average of 12 days to get hired, when considering 6 user submitted interviews for this role. To compare, the hiring process at Thales overall takes an average of 35 days.
Common stages of the interview process at Thales as a Software Developer according to 6 Glassdoor interviews include:
One on one interview: 50%
Skills test: 33%
Phone interview: 17%
Here are the most commonly searched roles for interview reports -
The interview went smoothly, they asked about the core concepts of Java and Spring framework. then a good English level is tested and appreciated during the recruitment process. They asked about whether I am able to have small (1 week) missions abroad. and, concluded with my ability to collaborate on multiple projects simultaneously.
Interview questions [1]
Question 1
The interview went smoothly, they asked about the core concepts of Java and Spring framework. then a good English level is tested and appreciated during the recruitment process. They asked about whether I am able to have small (1 week) missions abroad. and, concluded with my ability to collaborate on multiple projects simultaneously.
I applied online. I interviewed at Thales (Bucarest, )
Interview
Description of a software engineer interview process at Thales:
The interview would include a phone screen, take-home coding assignment, onsite whiteboard algorithms and system design, and behavioural interviews with engineers and hiring managers.
Interview questions [1]
Question 1
How would you design a system to track and display flight information for an airline?
Explain how you would implement a binary search tree data structure.
What experience do you have working in an agile development environment?
Describe a time you had to debug a complex software issue. How did you approach it?
What principles and patterns do you follow when designing a new software system?
HR interview call, followed by a coding challenge when I needed to interpret some code snippets read the code out loud and describe some design patterns, followed by a manager interview.