Real, anonymous reports from people who interviewed for Software Engineer at Michelin, newest first and distilled into what to expect across the loop.
After a recruiter exchange, about a week later I went through a sequence that felt pretty typical. First I had a call with HR where we covered logistics like my availability and how the mission would run, and then we talked about my background and how it could map to what Michelin wanted.
My first step was a quick screening with an employment agency, and then the process moved into a full day on site with other candidates. The day included both group activities and individual conversations, with psychologists involved, and there was an explicit emphasis on how I would work with others—not just whether I could answer questions in isolation.
The interview process typically begins with an HR call focused on logistics, candidate background, and motivation for the role, providing a structured introduction to the company and its expectations.
Candidates can expect multiple technical rounds that assess coding skills, problem-solving abilities, and knowledge of relevant technologies such as Java, Spring, and SQL, with varying levels of difficulty.
Interviews often include behavioral questions and group exercises to evaluate teamwork and collaboration skills, emphasizing how candidates work with others under pressure.
The overall interview process is described as structured and multi-step, with clear checkpoints and feedback moments, ensuring candidates understand their performance and next steps.
While many candidates report a positive experience, some noted inconsistencies in communication and follow-up, particularly regarding feedback and final decisions, which can affect overall impressions.
The difficulty of the process varies, but many candidates found it challenging, with a strong emphasis on both technical depth and cultural fit, making it important to align closely with the company's needs.