Last week, I interviewed with Thales for a software engineer position. The process consisted of the following stages:
Initial phone screen (30 minutes) I spoke with a recruiter who asked about my background, skills in Java and cloud platforms, and availability. They also shared more details about the team and projects at Thales.
Technical assessment (1 hour) I completed an online coding assessment that included data structures, algorithms, and object-oriented design problems, mostly in Java. One question involved writing a function to parse log files and identify anomalies.
Technical interview (45 minutes) I met with two engineers who reviewed my code from the assessment and asked follow-up questions. We discussed REST API design, multithreading, and how I would optimize a backend system for performance.
Final interview (1 hour) The last round included a hiring manager and a senior developer. We talked about my experience working on microservices, handling production issues, and my familiarity with CI/CD pipelines. They also evaluated my communication and problem-solving skills.
“Can you walk us through a project where you faced a major technical challenge and how you resolved it?”
The following metrics were computed from 1 interview experience for the Thales Senior Java Engineer role in Irvine, California.
Thales's interview process for their Senior Java Engineer roles in Irvine, California is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Thales's Senior Java Engineer interview process in Irvine, California.