Real, anonymous reports from people who interviewed for QA Automation Engineer at Globant, newest first and distilled into what to expect across the loop.
Get your personalized Globant 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.
I experienced a longer, more segmented interview process than I expected. After initial scheduling, I ended up in multiple rounds that felt like repeated deep dives, and by the time it was done, it had stretched across several technical instances rather than staying compact. Even though I’d been told about the flow in advance, the timeline had some awkward gaps—there was a point where I didn’t hear back about the next stage right away after being informed about what would happen after the first call.
The technical questioning itself was detailed to the point where it sometimes felt like the interviewer was checking whether I’d studied a manual, not whether I could apply QA knowledge on real work. I remember feeling that several questions didn’t reflect my experience level as much as they measured textbook familiarity, and the cadence of questions across the instances made the whole thing feel like an extended interrogation. The difficulty was average-to-hard: I could follow the topics, but the depth and repetition wore me down.
10 months ago
Average Positive Pune
My journey started with a meeting to explain the selection process, and then the next step was a technical exercise followed by one-on-one interviews. After that, I went into a more structured sequence where technical discussion and role fit came up together, and part of the conversation was in English while the theoretical side was in Spanish.
In the technical rounds, the topics were very much centered on how I think about test automation and quality engineering. I got questions around Java OOPS concepts, along with practical details like loops and xpath, and I also had to cover basics of testing methodologies and the difference between functional and non-functional testing. There was a strong theme of “what would you do when something breaks,” including how I’d respond if an automated test script failed repeatedly.
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
