Graduate Engineering Trainee GET applicants have rated the interview process at ALSTOM with 4 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 67.9% positive. This is according to Glassdoor user ratings.
Candidates applying for Graduate Engineering Trainee GET roles take an average of 1 day to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at ALSTOM overall takes an average of 31 days.
Common stages of the interview process at ALSTOM as a Graduate Engineering Trainee GET according to 1 Glassdoor interviews include:
IQ intelligence test: 17%
Background check: 17%
Personality test: 17%
Skills test: 17%
Group panel interview: 17%
Presentation: 17%
Here are the most commonly searched roles for interview reports -
Started by resume shortlisting, then a GD with a group of six people; concluded with a technical interview round where the major focus was just my resume and what I studied in my engineering life, and finally an HR round.
Interview questions [1]
Question 1
Questions only related to your resume and what you've studied.
The interview process typically started with an online application, followed by an initial phone screening with an HR representative. This led to one or more technical and behavioral interviews with the hiring manager and team members. The final stage involved waiting for the decision and receiving an offer
I applied through college or university. The process took 1 day. I interviewed at ALSTOM (Mysore)
Interview
My interview with Alstom was highly resume-focused, where the interviewer asked me detailed questions based on the technologies and skills I had listed. The discussion involved several cross-questions, often challenging me to justify why I chose one approach or technology over another. In addition to that, I was tested on core computer science fundamentals such as object-oriented programming concepts, operating system basics like heap vs stack and memory leaks, as well as standard data structures and algorithms problems including linked lists and valid parentheses. There was also an emphasis on security awareness, with questions about hashing vs encryption and DoS attacks. While I missed one question on Java garbage collection, I was able to handle most areas confidently, and the interviewer seemed impressed with the depth of my reasoning and clarity of answers.