JioHotstar Interview Experience | Backend | Senior Software Development Engineer
Summary
I went through the interview process at JioHotstar for a Backend Senior Software Development Engineer role, which included HLD, LLD + coding, and a hiring manager round focusing on design and behavioral topics.
Full Experience
I recently went through the interview process at JioHotstar and wanted to share my experience. Hope this helps others preparing for similar roles.
1) HLD (High-Level Design) Round
Q1: Deep Dive Into a Past Project
The discussion started with a detailed walkthrough of one of my previous projects and quickly turned into a design-focused conversation.
Key areas discussed:
- How I ensured idempotency in the system
- Alternative ways to achieve idempotency
- How I handled concurrency
- Trade‑offs between different concurrency approaches
This round was very discussion‑heavy, so strong fundamentals and clarity about your own projects were crucial.
Q2: Designing a Scalable API
I was asked to design an API with a strong focus on scalability.
Key expectations:
- Handling high traffic
- Rate limiting
- Caching strategies
- Load balancing
- Fault tolerance
- Observability (logging and monitoring)
Q3: OTT Scheduling Service
I was asked to design a system where OTT shows move through the following statuses:
scheduled -> started -> running -> ended
Requirements:
- Schedules can be created anytime (up to a year in advance or on the same day)
- On each status change:
- Notify OTT users
- Notify third‑party systems (for example, Cricbuzz‑like platforms)
2) LLD + Coding Round
Problem: Centralized Config Service
Approach I followed:
- Discussed high‑level design and scalability
- Designed the database schema
- Implemented core components:
- Config storage
- Retrieval APIs
- Versioning and updates
- Basic LLD structure
The focus was on clean design, extensibility, and clarity rather than only coding speed.
3) Hiring Manager (HM) Round
This round was more behavioral and experience‑driven.
Topics discussed:
- Past projects and challenges
- How I handle difficult situations
- Trade‑offs I have made in real systems
- Problem‑solving approach in ambiguous scenarios
Please up‑vote, to motivate me to upload my other interview experiences :)
Interview Questions (3)
Design a Scalable API
Design an API with a strong focus on scalability. The design should address:
- Handling high traffic
- Rate limiting
- Caching strategies
- Load balancing
- Fault tolerance
- Observability (logging and monitoring)
OTT Scheduling Service Design
Design a system for an OTT platform where shows transition through the statuses scheduled → started → running → ended. Requirements:
- Schedules can be created up to a year in advance or on the same day.
- On each status change, the system must notify OTT users and also notify third‑party systems (e.g., Cricbuzz‑like platforms).
Centralized Config Service Design
Design a centralized configuration service. The design should cover high‑level architecture, scalability considerations, a database schema, and core components such as:
- Config storage
- Retrieval APIs
- Versioning and updates
- Basic low‑level design structure.