Disney+ Hotstar (JioStar) logo

Site Reliability Engineer Interview Experience at Disney+ Hotstar (JioStar)2025

Disney+ Hotstar (JioStar)

Selected 4 rounds Mar 2025 Off Campus
A

Anonymous

3-6 Years · Experienced

Posted 18 months ago — the hiring process may have changed since.

General SRE Pattern

No specific, verified real Hotstar/JioStar SRE-titled candidate account was found (searches surfaced real Hotstar SDE accounts but none role-matched to SRE/DevOps). Built from generally reported real SRE loop patterns applied to Hotstar's known engineering focus on high-concurrency live-streaming events, referenced in real company materials. This entry is a reconstruction, not a first-hand transcript.

Application Story

Candidates apply through the JioStar careers page for this SRE role and move through an online assessment, two technical rounds, and an HR round over about two weeks.

Preparation Journey

Given Hotstar's well-known engineering challenge of handling record-setting concurrent viewership during live cricket matches, preparation should focus specifically on scaling for sudden, extreme, predictable-timing traffic spikes rather than generic cloud reliability topics.

Why Selected / Rejected

Being able to reason concretely about capacity planning for a scheduled event with a known start time (a cricket match) rather than an unpredictable traffic spike is exactly the distinction interviewers care about, given Hotstar's business is built around exactly that pattern.

Resume Tips

For an SRE role at a live-streaming company, be ready to reason specifically about scheduled, predictable-timing traffic events, not just generic autoscaling - the two require meaningfully different infrastructure strategies.

01Round
MEDIUM

Online — MCQ + Coding

60 minutes Remote

Covers Linux fundamentals, basic networking, and a coding problem asking candidates to process a stream of viewer-count events and compute a rolling maximum concurrent viewership over a sliding time window. The expected approach uses a monotonic deque to keep the operation efficient rather than recomputing the max on every new event.

02Round
HARD

Technical

60 minutes Remote

Focused on capacity planning for a scheduled live cricket match expected to draw record concurrent viewership. A strong approach pre-provisions compute and CDN edge capacity well ahead of match start based on historical viewership data for similar high-profile matches, combined with a real-time dashboard tracking actual viewership against the forecast so the team can react if actual demand exceeds the pre-provisioned plan. Interviewers push on how to handle the specific moment right at match start when a huge fraction of viewers join within the same one or two minutes, asking about connection ramp-up handling at the load balancer and origin server level.

03Round
MEDIUM

Technical

45 minutes Remote

Covers adaptive bitrate streaming concepts and how a CDN handles serving different quality levels to viewers with different network conditions, plus an incident scenario: a specific region's viewers are reporting buffering while other regions are fine. A good diagnostic order checks whether that region's specific CDN edge nodes are overloaded or misconfigured before assuming an origin-level problem.

04Round
EASY

HR Round

20 minutes Remote

Closing discussion on compensation, notice period, and confirming comfort with on-call responsibilities specifically around major live sporting events, which are the highest-stakes operational windows for the platform.

Comments

Loading comments...

Questions Asked at Disney+ Hotstar (JioStar) in the Site Reliability Engineer Interview

Online — MCQ + Coding Round

Covers Linux fundamentals, basic networking, and a coding problem asking candidates to process a stream of viewer-count events and compute a rolling maximum concurrent viewership over a sliding time window. The expected approach uses a monotonic deque to keep the operation effici

Technical Round

Focused on capacity planning for a scheduled live cricket match expected to draw record concurrent viewership. A strong approach pre-provisions compute and CDN edge capacity well ahead of match start based on historical viewership data for similar high-profile matches, combined w

Technical Round

Covers adaptive bitrate streaming concepts and how a CDN handles serving different quality levels to viewers with different network conditions, plus an incident scenario: a specific region's viewers are reporting buffering while other regions are fine. A good diagnostic order che

HR Round Round

Closing discussion on compensation, notice period, and confirming comfort with on-call responsibilities specifically around major live sporting events, which are the highest-stakes operational windows for the platform.