Real, anonymous reports from people who interviewed for Software Engineer at Publicis Sapient, newest first and distilled into what to expect across the loop.
I went through a pretty compact process: a recruiter-style screening call was followed by an online technical assessment, and then I had a single technical round that was largely based on my resume with fundamentals mixed in. The first step was an online test that combined multiple-choice questions with coding problems, and I remember it feeling like a quick filter—once that cleared, the pacing shifted into more conversational problem-solving.
My interview journey leaned heavily into JavaScript and React. I ended up with two technical rounds where the first part focused on JavaScript and the second pushed deeper into React. The overall difficulty felt around the mid range—challenging enough that I couldn’t bluff my way through, but it wasn’t like everything was “gotcha.”
The interview process typically starts with a recruiter call, followed by an online coding assessment, and then one or more technical rounds. The structure is generally clear, with a focus on technical skills before behavioral discussions, although some candidates experienced scheduling issues.
Candidates reported a strong emphasis on core programming skills, particularly in Java, JavaScript, and React, with many technical rounds including data structures and algorithms (DSA) as well as practical coding tasks. The depth of questioning varied, but most candidates felt they were assessed on their understanding and application of fundamental concepts rather than obscure trivia.
Behavioral interviews often followed the technical rounds, focusing on cultural values, collaboration, and problem-solving scenarios. Candidates noted that these discussions were intended to gauge alignment with the company's values and working style, and they were often structured around the STAR method.
The overall difficulty of the interviews was described as moderate to challenging, with some candidates feeling pressured by the length and intensity of technical discussions. While some found the experience supportive, others reported issues with interviewer behavior and pacing that affected their performance.
Several candidates expressed frustration over a lack of feedback and communication after interviews, particularly when they did not receive offers. Instances of unclear next steps or delayed responses from HR were noted as negative aspects of the process.
Interviews often included practical coding tasks and real-world problem-solving scenarios, with a notable focus on applying knowledge in context rather than just theoretical questions. This approach was appreciated by candidates who felt it better reflected actual job responsibilities.