Real, anonymous reports from people who interviewed for Software Engineer at Engie Impact, newest first and distilled into what to expect across the loop.
Get your personalized Engie Impact Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
I had a couple of interview rounds that felt smooth and grounded in my background. The early conversations were interested in what I had led or completed before, and I ended up spending most of the time connecting my past projects to what the role would actually require. The atmosphere wasn’t hostile or overly stressful, and the questions stayed clearly technical.
During the on-site portion, I went through behavioral and technical questions across two rounds. The technical side came across as specific and practical, covering things like types of maintenance and even details such as types of pumps. By the end, I wasn’t selected, but it didn’t feel random—the whole set of interviews gave a consistent signal about whether my experience matched their expected depth. Honestly, I felt interested throughout, but the decision still landed as a straightforward “not this time.”
8 months ago
Average Positive Melbourne
My first contact was essentially HR-led: the discussion centered on my role motivations and how they matched what was on the job description. After that, I met with the manager and spent a good amount of time going deep into the responsibilities—what the work actually looked like day to day, and what expectations came with it. The tone was detailed and explanatory, and it genuinely helped me understand the scope.
Later, I completed the process with HR to finalize hiring steps. Even though I felt the conversations went smoothly, it still took a few weeks end to end, and then I was told I was unsuccessful. What stuck with me was that I received concrete feedback afterward, so even though it didn’t turn into an offer, it wasn’t a black box.
10 months ago
Average Positive Kampala
After a recruiter touchpoint, the process moved quickly into interviews where the technical side really took center stage. I had a live coding round w…
10 months ago
Average Positive Singapore
I only made it through a single interview session, and the format was simple. The day included a technical test meant to check my understanding of cor…
12 months ago
Easy Positive Bucharest, Bucuresti
My process was pretty straightforward and stayed lightweight. I started with a technical test, and after submitting it I moved into quick conversation…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Timeline
The interview process typically starts with HR-led discussions focusing on background and motivations, followed by a mix of technical assessments and managerial interviews. Candidates noted that the entire process can take several weeks, with multiple touchpoints and a structured flow.
Candidates experienced a variety of technical evaluations, including live coding sessions, take-home assessments, and discussions centered on practical applications of their skills, particularly in .NET and Laravel frameworks. The focus was often on core concepts and real-world problem-solving rather than abstract questions.
Live coding.NETLaravel
Behavioral & Fit Interviews
Behavioral interviews were common, emphasizing candidates' past experiences and how they align with the role's expectations. Interviewers sought to understand candidates' motivations and fit within the company culture through detailed discussions about previous projects and responsibilities.
Candidates reported a generally positive communication experience, with many receiving constructive feedback after interviews, regardless of the outcome. This transparency helped candidates understand their fit and the decision-making process.
Constructive feedbackTransparencyCommunication
Difficulty Level & Expectations
The overall difficulty of the interviews was described as average, with a focus on clarity and fundamental understanding rather than obscure or overly complex topics. Candidates felt that the process was fair and well-structured, even when they did not receive offers.
Average difficultyFundamentalsStructured process
Candidate Experience & Environment
The interview environment was generally described as calm and professional, with interviewers aiming to create a supportive atmosphere. Candidates appreciated the organized approach and the focus on understanding their skills and experiences rather than putting them under pressure.
Professional environmentSupportive atmosphereOrganized process