Jio Hotstar Frontend Interview Experience | SDE 2

Recently, I interviewed for the SDE 2 Frontend role at JioHotstar. I wanted to share the complete experience because the process was quite long, involved multiple reschedules, and ultimately ended in rejection for reasons that did not seem related to technical performance.

I’m sharing this experience so that others preparing for frontend roles can understand:

• What kinds of rounds were asked
• How the interview process was structured
• What expectations companies may have beyond technical skills
• How non-technical factors can sometimes influence outcomes

This was one of the more unusual interview experiences I have had.

The process itself was significantly longer than most frontend interview loops I’ve experienced.

Interview Process Overview

The process included:

1. Frontend Technical Round
2. Machine Coding Round
3. Hiring Manager Round
4. Planned Bar Raiser Round (Never Happened)

Round 1: Frontend Technical Interview

Interviewer: Senior Software Engineer

This round focused heavily on:

• JavaScript fundamentals
• Problem solving
• Real-world frontend understanding
• Deep project discussions

Project Discussion

A large portion of the interview revolved around projects mentioned in my resume.

The interviewer went deep into:

• Architectural decisions
• State management choices
• Performance optimization
• Scalability considerations
• Frontend challenges faced during implementation

This discussion felt more practical than theoretical, which I appreciated.

JavaScript Coding Questions

I was asked two JavaScript coding questions.

The interview also included discussions around:

JavaScript Fundamentals

Topics included:

• Event loop
• Async behavior
• Execution order
• Promise handling
• Microtasks vs macrotasks

The interviewer specifically focused on understanding whether I genuinely understood JavaScript internals rather than memorized outputs.

Overall Experience of Round 1

The round went very well overall.

The interviewer seemed satisfied with:

• My problem-solving approach
• JavaScript fundamentals
• Communication
• Project depth

One positive point mentioned during the interview was that my understanding of core JavaScript concepts was strong.

Hey New Readers 👋

If you’re new here, make sure to check out my Frontend Army publication — a collection of 50+ detailed Frontend interview experiences covering JavaScript, ReactJS, Machine Coding, System Design, DSA, and real interview insights from top tech companies.

Great resource for anyone preparing for Frontend Engineer interviews 🚀

Round 2: Machine Coding Round

Interviewer: Engineering Lead

This round was more frontend engineering-focused and involved practical UI implementation.

Initial Discussion

The round again started with:

• Resume discussion
• Current projects
• Frontend architecture discussions

The interviewer spent significant time understanding:

• My ownership level
• Product understanding
• Decision-making process

Machine Coding Task: Create a Dropdown Component

The core machine coding task was:

Build a Dropdown Component

At first glance, this may sound simple, but the discussion became much deeper.

The interviewer focused on:

• Component architecture
• Reusability
• Accessibility
• Keyboard navigation
• State handling
• Edge cases
• Performance considerations

Areas Discussed During the Round

1. Accessibility

This became a major discussion point.

Topics included:

• Keyboard navigation
• ARIA attributes
• Focus management
• Screen reader support

2. State Management

The interviewer asked:

• Controlled vs uncontrolled component design
• Managing open/close state
• Handling outside clicks
• State synchronization

3. Performance Optimization

Questions included:

• Avoiding unnecessary re-renders
• Memoization opportunities
• Event listener cleanup
• Rendering optimization

Overall Feedback From Technical Rounds

Both technical rounds went very smoothly.

The interviewers were interactive and positive during discussions.

At this stage, I genuinely felt the process was moving toward a successful outcome.

Long HR Gap & Communication Issues

After completing the technical rounds, there was no communication for a long period.

I had to follow up multiple times regarding updates.

Eventually:

• I was reassigned to a new HR representative
• The new HR informed me that the next step would be the Hiring Manager round
• It was communicated as the final round before the Bar Raiser

Multiple Reschedules

The Hiring Manager round was then:

• Scheduled
• Rescheduled
• Rescheduled again

The reason communicated was:

• Interviewer's medical issues

This extended the overall process significantly.

By this point, the interview process had already stretched close to two months.

Hiring Manager Round: Unexpected Direction

When the Hiring Manager round finally happened, the conversation took a completely different direction from what I expected.

Instead of focusing heavily on:

• Frontend architecture
• Engineering challenges
• Technical depth

The discussion became centered around:

• Relocation concerns
• Long-term retention assumptions
• Team stability concerns

Important Context Shared During the Round

During the discussion, it became clear that:

• The original role I had interviewed for was already filled
• HR had mapped me to another team
• That team had only one opening available

This completely changed the nature of the discussion.

Main Concern Raised

The Hiring Manager was concerned about relocation.

Current Situation

• I was working in a hybrid setup
• My current company is based in Noida

Offered Role

• Hybrid role in Bangalore

The Hiring Manager expressed concerns that:

• I may not be comfortable relocating
• I might leave the company soon
• The team would need to hire again

My Response During the Discussion

I explained clearly that my interest in the role was driven by:

• Opportunity to work on systems operating at Hotstar scale
• Career growth
• Learning opportunities
• Exposure to large-scale frontend engineering challenges

However, the discussion increasingly felt less like a technical evaluation and more like convincing the Hiring Manager that I would stay long-term.

Final Outcome

Verdict: Rejected

The rejection did not appear to be related to:

• Technical performance
• Machine coding ability
• JavaScript knowledge

Instead, the implicit reason seemed tied to:

• Relocation assumptions
• Retention concerns
• Team stability considerations

Final Thoughts

Despite the rejection, the technical rounds themselves were genuinely good learning experiences.

What I appreciated:

• Deep JavaScript discussions
• Practical frontend machine coding
• Accessibility-focused conversations
• Real-world component design discussions

What was frustrating:

• Extremely long timeline
• Multiple reschedules
• Role change midway
• Final rejection based on concerns unrelated to technical capability

Overall, this experience reinforced an important reality of modern hiring:

Interview outcomes are not always determined purely by technical performance. Sometimes organizational constraints, hiring risks, and assumptions play an equally large role in final decisions.

I’d genuinely appreciate hearing if others have faced similar experiences during frontend interviews at large product companies.