Real, anonymous reports from people who interviewed for Software Engineer at Michelin, newest first and distilled into what to expect across the loop.
After the recruiter call, I moved into a sequence that felt very structured and split between stakeholders. First I had a discussion with HR about logistics and the mission, then I joined a video call with the operational side where we talked through the business need, the solution space, and my past experiences. That was followed by a technical video session focused on the stack I’d used before, with questions around Java, Spring, Kafka, and Angular.
I began with a recruiter-focused screening and then moved into a more immersive day where the company was introduced alongside group work. I had an initial HR/personnel agency conversation, and after that I spent a full day at the company with other candidates, with activities facilitated on site. The format mixed group exercises with structured interactions, including some work designed to see how I collaborated and how I presented my thinking.
The interview process at Michelin typically begins with a recruiter call, followed by a structured series of interviews that may include HR, technical assessments, and managerial discussions. Candidates noted that the timeline can vary, with some experiencing quick follow-ups while others faced prolonged waiting periods.
Candidates reported a strong emphasis on technical knowledge during interviews, with questions covering a wide range of topics including programming languages, data structures, and algorithms. The technical rounds were often described as challenging, requiring both depth and breadth of knowledge.
Behavioral interviews focused on assessing cultural fit and interpersonal skills were common, with questions designed to evaluate how candidates handle real-world scenarios and collaborate with others. This aspect was often highlighted as crucial for understanding alignment with the company's values.
Some candidates participated in assessment centers that included group exercises and presentations, which tested teamwork and communication skills in a collaborative setting. This format allowed interviewers to observe candidates' interactions and problem-solving abilities in real-time.
Feedback during the interview process varied, with some candidates appreciating clear communication about each stage, while others felt left in the dark after interviews, particularly regarding follow-up and decision timelines. This inconsistency impacted the overall candidate experience.
Candidates described the overall difficulty of the process as demanding, often requiring stamina and resilience due to the multi-step nature and the intensity of technical and behavioral questioning. Many reflected on the importance of thorough preparation and managing expectations throughout the journey.