Sogeti logo
SogetiSoftware Engineer
Updated May 30, 2026

Sogeti Software Engineer Interview Experiences 2026

Real, anonymous reports from people who interviewed for Software Engineer at Sogeti, newest first and distilled into what to expect across the loop.

Get your personalized Sogeti 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.
Build my free plan
Hot & recentNewest first
4 months ago
Average Positive Lyon

I started with a conversation focused on motivations and how I wanted to develop, led by an active manager type of voice—direct but still casual. That set the tone: it wasn’t overly formal, and the recruiter-side contact felt easy to reach throughout.

After that, I went into a follow-up technical screen with programming tasks. The questions spanned from the basics of the technologies I mentioned to more hands-on problem solving, with a mix that even included quick, language-specific topics (for me that meant AngularJS) plus typical soft-skill interview questions afterward. When the process moved to deeper technical discussion, it leaned on concepts like architecture, design patterns, and how I’d think about APIs, and it also asked about the tools and techniques I’d used before.
> 1 year
Average Negative India

My timeline stretched longer than I expected, and it started like a standard multi-round pipeline. I first spoke with a recruiter, then later moved through several additional conversations that included a technical screen with a senior interviewer, an assessment step, and then a final formal-looking meeting with a manager and team lead. The people were generally nice and the process didn’t feel hostile at the surface level.

What threw me off was how the “final” round played out. I was told it would be more of a formality, but I still ended up getting technical questions in that last stage, which made the round feel heavier than promised. Even after I completed everything, communication lagged—I was left waiting and never really got clear closure.

Unlock every Software Engineer interview experience

Real Software Engineer interview experiences
  • Difficulty, sentiment and outcomes
  • New reports added every week
See all experiences
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.

What to expect

Distilled from the reports

Initial Recruiter Call

The interview process typically begins with a recruiter call focused on motivations, background, and a brief overview of the company. This initial conversation sets a friendly tone and helps candidates understand the company culture.

Recruiter callMotivationCompany culture

Technical Screening

Candidates can expect a technical screening that includes coding tasks and questions related to their stated technologies, often focusing on problem-solving and basic programming principles. The format may vary from live coding to take-home assessments.

Coding tasksProblem-solvingTechnical screening

Behavioral and Fit Interviews

Subsequent interviews often emphasize behavioral questions and fit assessments, where interviewers explore candidates' motivations, work styles, and alignment with company values. This part of the process tends to be conversational rather than combative.

Behavioral questionsFit assessmentConversational style

Technical Depth and System Design

Later stages may involve deeper technical discussions, including system design and architecture questions, where candidates are evaluated on their reasoning and ability to articulate complex concepts. This round can be more challenging and exploratory.

System designArchitectureTechnical depth

Communication and Follow-Up

While the interview process itself is generally organized, candidates have reported issues with post-interview communication, including delays in feedback and lack of closure after interviews. This can lead to frustration and uncertainty.

CommunicationFeedback delaysPost-interview experience

Overall Experience and Outcome

Candidates describe the overall experience as straightforward and low-pressure, although some noted variability in the structure and expectations across different interviewers. The outcome often hinges on both technical skills and cultural fit.

Interview experienceOutcome variabilityCultural fit