Real, anonymous reports from people who interviewed for QA Automation Engineer at Luxoft Singapore, newest first and distilled into what to expect across the loop.
Get your personalized Luxoft Singapore QA Automation Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
My journey started off with something that immediately threw me off: there wasn’t really a real phone screen. Instead, I was asked to fill out an information sheet as if it belonged to the recruiter. Then the first substantive step was a technical interview with the QA team, and it leaned heavily on on-the-spot automation coding.
What stood out was the mismatch between terminology and what I’d actually expect to use day to day. A lot of it felt overly formal, almost like I was being tested on vocabulary rather than how I’d work in a real QA environment. Still, I pushed through because the questions were presented as if they were very “by the book.”
> 1 year
Average Negative Ciudad de Mexico
In my case, the process felt like it suffered from a couple of avoidable mismatches. I’d applied for a role in the QA/SDET lane, but I didn’t hear back through the portal after applying. I only got contact after reaching out directly by email, and later I realized some parts of the interview experience may have been impacted by how it was staffed.
I was interviewed in English, but the interviewer’s English seemed limited to me, and I couldn’t shake the feeling that it may have affected how my answers came across. On top of that, I was evaluated by someone who felt like a Java developer rather than a QA/SDET-focused interviewer, which was unusual given the role. I never received detailed feedback; I only learned the rejection after I followed up and asked for a response.
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
