Real, anonymous reports from people who interviewed for Software Engineer at Luxoft, newest first and distilled into what to expect across the loop.
I went through an interview sequence that sounded typical on paper (tech, then manager, sometimes client), but the end experience was disappointing—often with no clear feedback or a client-dependent stop.
I went through a fairly standard Luxoft Software Engineer process (about three rounds) with friendly interviewers and a mix of basics, light coding, and experience discussion.
The interview process typically includes a recruiter screen, followed by a technical interview focused on coding and language fundamentals, and a final discussion with a manager or project lead. Some candidates experienced variations in the final steps, including client-dependent outcomes.
Candidates often faced technical interviews that emphasized language-specific knowledge, particularly in C++ or Java, with a mix of theoretical questions and live coding tasks. Expect a focus on OOP principles, algorithms, and real-time system concepts.
The quality of communication varied significantly, with some candidates reporting unprofessional behavior and poor organization, leading to a frustrating experience. Clear and respectful communication was noted as a positive aspect when present.
Many candidates reported a lack of closure after interviews, with delayed or no feedback, and some experienced cancellations or changes in role availability. Following up on the status of applications is advisable.
Candidates described a wide range of experiences, from supportive and well-structured interviews to disorganized and dismissive interactions. The overall tone and environment can greatly influence the candidate's perception of the process.
Be prepared for theoretical questions that may not align with practical experience, as some interviews included outdated or overly academic prompts. Candidates suggested brushing up on fundamental concepts and theory related to the role.
