Candidates describe Luxoft software engineer interviews as an HR or recruiter conversation, a technical interview matched to the project's stack, and sometimes a team lead, manager or customer conversation.
$110K
Avg. Base Comp
$125K
Avg. Total Comp
3-4 rounds
Typical Rounds
Not reported
Process Length
Candidates describe Luxoft software engineer interviews as driven by the project's stack rather than a fixed question list. Reported topics include C and C++ with Linux and drivers, C++ polymorphism, templates and lambdas, core Java with Spring Boot and Kubernetes, .NET and React, and basic Python and OOP for a junior role.
The formats differ widely. One candidate took a short written OOP test before an online C++ interview. Another had a roughly 90-minute interview with a lead engineer that moved quickly through dozens of questions on .NET, SQL, React and Web APIs. A Java candidate imported an existing project locally and fixed bugs in a live session, and a junior Python candidate had a technical interview of about 30 minutes.
Most accounts also include a less technical conversation, whether with HR, a product manager, a team lead or a customer hiring manager. One embedded candidate was asked practical questions about device trees, network problems and where to find logs on a Linux device. One junior candidate heard that some projects add a coding interview with the client.
Outcomes were mixed. Several candidates received offers, while others reported no offer, and some described long silences or a role being put on hold. Ask the recruiter which project and stack the role uses, prepare fundamentals in that language, and follow up in writing about next steps. One candidate noted the interviewer guided them when they got stuck, so talk through your reasoning.
Synthesized from 13 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Luxoft process.
The process had three main interviews: an initial HR assessment, technical interviews with team members, and a technical interview with the customer hiring manager. After that, HR extended an offer and the process moved into onboarding.
The HR round covered salary expectations, location, and general fit. The team technical interviews focused on C and C++, Linux, Linux drivers, and kernel experience. Questions included what volatile means in C, what a shallow copy is, what the diamond problem is, what a pointer is, and a coding challenge to sort an array in C.
The customer hiring manager interview focused on practical Linux and embedded-device experience. They asked what is important to write for nodes in a device tree, what to check when a device does not have an internet connection, and where to check logs on a Linux device.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Luxoft
Write a function to return True if two strings are anagrams of each other and False if they are not
| Question | |
|---|---|
| Target Indices | |
| The Longest Journey | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Merge Sorted Lists | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Random SQL Sample | |
| Raining in Seattle | |
| Top 3 Users | |
| String Shift | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Find the First Non-Repeating Character in a String | |
| Comments Histogram | |
| Minimum Change | |
| Flight Records | |
| Download Facts | |
| Prime to N | |
| Upsell Transactions | |
| Find the Missing Number | |
| Bagging vs Boosting | |
| Daily Retention Summary | |
| Scrambled Tickets | |
| P-value to a Layman | |
| First Touch Attribution | |
| Google Maps Improvement |
Synthesized from candidate reports. Individual experiences may vary.
Candidates describe starting with a recruiter, HR or product manager conversation, sometimes after LinkedIn outreach. One HR round covered salary expectations, location and general fit. Ask which project and stack the role involves.
Some candidates report an early assessment. One received a link to a written test on basic object-oriented programming, and another did a React coding assessment with multiple-choice questions. Other candidates went straight to a live technical interview, so this step is not universal.
This is the most consistently reported stage, and its content follows the role. One candidate was asked about volatile, shallow copies, the diamond problem and sorting an array in C. Another faced C++ polymorphism, templates, lambdas and the rule of five. A junior Python candidate got tuples versus lists and finding odd numbers, and a full stack candidate had a fast-paced session on .NET, SQL and React.
Several candidates describe a later conversation about the project and team. A junior candidate had a roughly 20-minute non-technical chat with a team lead. An embedded candidate met the customer hiring manager, who asked about device tree nodes, offline devices and Linux logs. A senior Java candidate's final round was a live session fixing bugs in an existing project.
Candidates reported offers, no offers and one declined offer. Several described slow or missing communication after interviews, and one said the role was put on hold after passing technical and managerial rounds. Follow up in writing and keep a record of the timeline agreed with the recruiter.
