Real, anonymous reports from people who interviewed for Software Engineer at Saint-Gobain, newest first and distilled into what to expect across the loop.
I had a generally average interview experience that leaned more on fit, motivation, and clear conversation, with a quicker timeline in some cases; one attempt failed early due to language screening.
I experienced a longer, more interview-heavy journey (often several rounds with different leadership) that felt average in difficulty but tiring in practice, spanning multiple days and sometimes ending with administrative or follow-up items.
Most candidates start with a recruiter or HR screening focused on background, motivations, and role fit, often with a conversational tone. This initial step can include language assessments that may lead to early rejections.
Candidates typically undergo a technical evaluation that may include coding assessments, aptitude tests, and discussions around core concepts like SQL and OOP. The technical rounds can vary in depth and format, sometimes involving group discussions or presentations.
Interviews often include multiple rounds with managers and higher-level leaders, focusing on both technical skills and cultural fit within the team. These discussions may probe how candidates would operate in a team setting and align with company values.
Some candidates experience an onsite interview or visit, which can include technical evaluations and interactions with various team members. This step is designed to assess fit within the physical work environment and team dynamics.
The interview process can be lengthy and multi-layered, often spanning several days with various stakeholders involved. Candidates noted that the structure can feel overwhelming, with some experiencing delays or lack of follow-up after interviews.
Behavioral interviews are a key component, often utilizing the STAR method to assess how candidates handle real-life scenarios. This aspect emphasizes communication skills and cultural alignment.