Real, anonymous reports from people who interviewed for Software Engineer at Xebia, newest first and distilled into what to expect across the loop.
I went through a Java/DSA-focused process that moved into architecture discussions and felt like a harder system-design check.
I found the process very challenging and sometimes unfair-feeling: either the interviewer dynamic was negative or the rounds were tightly controlled and time-pressured.
Candidates can expect multiple technical interviews focusing on core programming, data structures, algorithms, and sometimes specific technologies like Java, SQL, or Kafka. The difficulty level can vary, with some reporting a high bar for technical knowledge and problem-solving skills.
There is a significant emphasis on system design, particularly around microservices and architecture discussions, where candidates must clearly communicate their design choices and trade-offs. This aspect is critical for candidates to prepare for, as it can heavily influence the outcome.
Many candidates reported varied experiences with interviewer behavior, ranging from supportive to adversarial, which can significantly impact the interview process. Candidates should be prepared for potentially negative dynamics and ensure they communicate effectively under pressure.
Some candidates experienced rounds involving client representatives, which added complexity to the evaluation process. Understanding client expectations and being able to communicate effectively in these scenarios is important.
The interview process can be lengthy and sometimes lacks clear communication regarding timelines and outcomes, leading to confusion or frustration for candidates. It's advisable to seek clarity on the process and follow up proactively.
Candidates often reported receiving little feedback after interviews, even when they progressed through multiple rounds. This lack of closure can be disheartening, so candidates should be prepared for potential ambiguity regarding their performance.
