Real, anonymous reports from people who interviewed for QA Engineer at Disney+HotStar, newest first and distilled into what to expect across the loop.
My recruiter coordination initially sounded fine, but the actual flow turned messy. After the first round, I didn’t get clear feedback on how I’d done, yet I still got moved into a second interview. That second interview had an extra layer of confusion: HR called me during the process to clarify details from my first round, which made the whole thing feel like there wasn’t internal alignment.
After an HR screening, I moved through a structured sequence that felt very “process-driven”: a telephonic interview, then a coding round, followed by a design patterns round, and finally a manager-level conversation that focused on basic architecture. The recruiter had set expectations around how they would make a decision, including how my performance would feed into compensation and whether I’d get an offer.
The interview process typically follows a structured sequence starting with an HR screening, followed by multiple technical rounds including coding and design discussions, and ending with a hiring manager or HR round. Candidates noted that while the flow was generally predictable, there were instances of miscommunication and scheduling issues that affected the overall experience.
Candidates experienced a mix of coding and design questions, but some felt that the technical assessments were not fully aligned with QA/SDET expectations, often leaning towards general data structures and algorithms rather than specific testing or automation topics. This disconnect led to confusion and frustration during interviews.
The level of engagement from interviewers varied significantly, with some candidates reporting a positive, supportive atmosphere while others experienced rushed or hostile interactions that undermined their performance. This inconsistency impacted candidates' perceptions of the interview process as a whole.
Candidates expressed concerns about the lack of clear communication and timely feedback throughout the process. Many felt uncertain about their performance due to insufficient updates, which contributed to a sense of disorganization and frustration.
The difficulty of the technical questions varied, with some candidates finding them challenging yet fair, while others felt that the questions did not accurately reflect the role's requirements. Candidates noted that preparation was essential, as the interviews demanded a solid understanding of both theoretical and practical aspects of QA.
Some candidates reported a take-home assignment that involved practical testing scenarios, which was generally well-received. However, subsequent rounds sometimes shifted to a more verbal questioning format that felt less structured and more extractive, leading to mixed experiences.