Real, anonymous reports from people who interviewed for QA Automation Engineer at Disney+HotStar, newest first and distilled into what to expect across the loop.
Get your personalized Disney+HotStar 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 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.
The scheduling also rubbed me the wrong way. Interview times kept landing during employee lunch hours (roughly 1–2 PM), and the experience felt slightly rushed from the interviewers’ side. Even when the discussions themselves were reasonably professional, the lack of consistent communication and structured coordination made it hard to know where I stood.
> 1 year
Difficult Positive India
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 coding stage leaned into problem solving with at least one question that was straightforward and another that was a step up—challenging enough that it pushed me to be careful with approach and details. The design round surprised me because I wasn’t just doing test-related discussion; I was asked to think through the architecture of an app like Swiggy. I even had to pause and confirm what the interviewer meant, since it sounded ambiguous whether I should focus on an automation framework architecture or the application architecture itself.
> 1 year
Easy Neutral India
My experience started with a positive vibe from HR and the tech team people I spoke with, and the process felt reasonably well communicated. I still n…
> 1 year
Average Negative India
I went into my interviews expecting a technical discussion, but the overall tone made it feel hostile and unprofessional at times. In one screening, t…
> 1 year
Average Positive Bengaluru
My process started with an HR call, and then the interviews moved quickly and smoothly. I ended up with a full set of rounds packed into about the sam…
Unlock every QA Automation Engineer interview experience
