The Walt Disney Company · Phone screen → Onsite
In processDisney Frontend and Fullstack: 4 Experiences (Part 10 of 18)
Disney experienced frontend and fullstack interviews, 2024–2025: React builds, code reviews, cart and feature-flag designs, and easy LeetCode questions.
At a glance
- Process: recruiter → coding or React rounds → system design, code review and behavioral rounds; one fullstack loop had three React interviews and a testing assignment (entries 01–04).
- Asked recently: shopping cart and feature flag designs and a code review for a junior author (01); Ransom Note and a React app review (02); Queue using Stacks and Valid Palindrome in both fullstack loops (03, 04).
- Difficulty: coding was LeetCode easy to medium; the lead frontend candidate later got an offer (01).
- Practise first: Implement Queue using Stacks, Valid Palindrome and the React shopping cart.
Coverage: 4 experienced full-time reports: 2 frontend engineers (lead frontend in Seattle; Disney+/Hulu streaming teams; 2025) and 2 fullstack engineers (one senior on Ads; 2024).
In this series
New Grad SWE / SDE
- Part 1 — NEW GRAD · SWE/SDE: 2026 hiring context; 2025-cohort return offer; older interviews.
- Part 2 — NEW GRAD · SDE1: 2022 OA, coding and hiring updates.
- Part 3 — NEW GRAD: SDE1 August 2022 back to 2021; fullstack kept separate.
- Part 4 — NEW GRAD · SDE/SDE1: 2021 graduate interviews, chronology continued.
Other New Grad roles
- Part 5 — NEW GRAD · OTHER ROLES: MLE assessment in 2025; scientist interview in 2019.
Hiring cohort unconfirmed
- Part 6 — COHORT UNCONFIRMED: 2026 SWE I reports, other SWE and DE accounts.
- Part 7 — COHORT UNCONFIRMED: SDE1, OA and Android accounts from 2021–2022.
Experienced Full-Time
- Part 8 — EXPERIENCED · SWE: 2026 Staff/Product and 2025 backend/Ads/Principal.
- Part 9 — EXPERIENCED · SWE: 2026 array Set; 2025 ad filtering, backend and design.
- Part 10 (current) — EXPERIENCED: frontend 2025, then a separate fullstack section for 2024.
- Part 11 — EXPERIENCED · SWE HISTORY: 2024 coding/Ads/Principal, then 2018 BQ.
- Part 12 — EXPERIENCED · SDE1: 2021–2022 early-career hires, not graduate hiring.
- Part 13 — EXPERIENCED · DATA ENGINEER: 2026 cloud and hybrid-pipeline interviews.
- Part 14 — EXPERIENCED · MLE: 2025 coding, SQL, feature stores and modeling.
- Part 15 — EXPERIENCED · OTHER ROLES: GenAI 2025, QA 2024 and data-team 2020.
- Part 16 — EXPERIENCED · BAMTECH: separate software and Senior DE screens in 2019.
Contract
- Part 17 — CONTRACT · DATA ENGINEER: 2025–2026, separate from full-time hiring.
Internship / Co-op
- Part 18 — INTERNSHIP: software/PPO, AI Product and Technical Artist; roles separated.
Roles in this part
- Frontend engineering
- Fullstack engineering
Frontend engineering
What came up
These 2 candidate accounts share the role/cohort scope stated above. Counts apply to this section only.
| Topic | Reports | Last seen |
|---|---|---|
| Code review / mentoring | 2 | Dec 2025 |
| System design | 1 | Dec 2025 |
| Behavioral questions | 1 | Dec 2025 |
| Coding / data structures | 1 | Nov 2025 |
| Projects / work experience | 1 | Nov 2025 |
Questions we found
Algorithms / Data Structures
| Question | Reports | Last seen |
|---|---|---|
| Ransom Note | 1 | 2025 Q3 |
Behavioral (BQ)
| Question | Reports | Last seen |
|---|---|---|
| Describe a past mentoring experience. | 1 | 2025 Q4 |
System Design
| Question | Reports | Last seen |
|---|---|---|
| Frontend feature flag system design | 1 | 2025 Q4 |
| Frontend shopping cart system design | 1 | 2025 Q4 |
Code Review / Mentoring
| Question | Reports | Last seen |
|---|---|---|
| Review frontend code and explain how you would help its junior author. | 1 | 2025 Q4 |
| Review a simple React app, identify issues and give feedback; the code was not retained. | 1 | 2025 Q3 |
Candidate timelines
01: Lead Frontend: mentoring, cart design, flags and a later offer
Interview period: 2025 Q4 (as reported) · Report: 2025-12-11 · Role: Lead frontend engineer, Seattle · Cohort: Experienced Full-Time
The candidate said the last two interviews were held in the Seattle office. The described second interview had four sessions: a senior technical program manager spent about 30 minutes on work and collaboration. A principal frontend engineer then presented poor-quality code and asked how the candidate would review it and mentor a junior engineer, including examples from past mentoring. The actual code and its defects were not preserved.
Two whiteboard discussions followed: shopping-cart frontend/system design and a feature-flag system. These are design conversations, rather than a claim that the candidate implemented the linked practice systems.
After the Friday interview, the hiring manager wanted an additional stakeholder conversation on Tuesday. In a December 23 follow-up, the candidate reported having signed the offer while the background check was still underway. That update belongs to the same candidate loop.
02: Two frontend teams, Ransom Note and an unexpected React review
Interview period: 2025 Q3 (as reported) · Report: 2025-11-20 · Role: Frontend engineer, Disney+/Hulu streaming teams · Cohort: Experienced Full-Time
This November 2025 account concerns one candidate interviewing with two streaming teams in parallel. One hiring manager combined general behavioral discussion with Ransom Note. The other hiring manager focused on past projects.
The recruiter had described LeetCode-style preparation, but the technical interview instead asked the candidate to review a simple React application. A December clarification says the job was to identify problems and give feedback. The app and its actual defects were not disclosed; the task cannot be reconstructed from that description. The process was still ongoing in the account. There is no verified basis to merge this person with the separate Lead Frontend report.
Fullstack engineering
What came up
These 2 candidate accounts share the role/cohort scope stated above. Counts apply to this section only.
| Topic | Reports | Last seen |
|---|---|---|
| Frontend implementation | 2 | Oct 2024 |
| Coding / data structures | 2 | Oct 2024 |
| Testing | 1 | Oct 2024 |
| Technical fundamentals | 1 | Oct 2024 |
| Projects / work experience | 1 | Oct 2024 |
| Backend implementation | 1 | Jan 2024 |
Questions we found
Algorithms / Data Structures
| Question | Reports | Last seen |
|---|---|---|
| Implement Queue using Stacks | 2 | 2024 Q2 |
| Valid Palindrome | 2 | 2024 Q2 |
| Longest Substring Without Repeating Characters | 1 | 2024 Q2 |
Project Coding
| Question | Reports | Last seen |
|---|---|---|
| React signup form with required-field validation and navigation | 1 | 2024 Q2 |
| Implement a React shopping cart | 1 | 2024 Q2 |
| React product catalog with joined names, sorting, filtering and tests | 1 | 2024 Q2 |
| React login with conditional navigation | 1 | 2024 Q1 |
| Spring Boot create and list users API | 1 | 2024 Q1 |
Candidate timelines
03: Fullstack: three React interviews, algorithms and a testing assignment
Interview period: 2024 Q2 (as reported) · Report: 2024-10-18 · Role: Fullstack engineer · Cohort: Experienced Full-Time
The October 2024 report labels the interview period as 2024 Q2. The first round mixed project, leadership and communication discussion with a React signup form containing name, age, email and password, required-field validation and navigation. CSS was not required. Algorithm questions included a queue using stacks, palindrome checking and the longest substring without repeated characters.
The second round discussed projects and when different microservice approaches fit. A React task joined product records to brand, category and color reference data, displayed IDs, titles, descriptions and the resolved names, and added sorting and filtering by those attributes. The candidate was also asked to write Jest tests reaching 90% coverage. The source calls the inputs five lists but names only four; the fifth is not recoverable. There is no verified runnable practice destination for that full testing assignment.
The third round asked for a React shopping cart and discussed coupling types, GraphQL error handling, logging and microservices. The candidate was rejected after that round. The account does not disclose every cart behavior, so the linked practice's complete behavior is not presented as the original specification.
04: Senior Ads fullstack: algorithm tradeoffs, React navigation and Spring Boot
Interview period: 2024 Q1 (as reported) · Report: 2024-01-18 · Role: Senior fullstack engineer, Ads · Cohort: Experienced Full-Time
The January 2024 interview opened with a discussion of frontend/backend balance: roughly 40/60 versus 30/70.
For palindrome checking, the candidate gave a two-pointer approach and then a recursive one; the code was not run against tests. For a queue using two stacks, they implemented both O(1) push with O(n) pop and O(n) push with O(1) pop, discussing the tradeoff.
Frontend work was a React login page with username and password: successful login should navigate home, and a failed login should not. The candidate sketched asynchronous API handling and history-based navigation; the interviewer explained another navigation approach. Backend work asked for Spring Boot POST/GET user endpoints to create and list users. A later reply confirms the candidate received and accepted the offer.
The interviewer gave positive feedback and asked the candidate to prepare Java fundamentals, coding, system design and backend-experience discussion for the final round.
Common questions
What does Disney ask frontend engineers?
System design on a shopping cart and a feature flag system, a code review with mentoring questions (01), Ransom Note and a React app review (02).
What coding questions repeat at Disney for fullstack roles?
Implement Queue using Stacks and Valid Palindrome each came up in both fullstack reports (03, 04), alongside React builds and a Spring Boot users API.
Keep practicing
- From these reports: Queue using Stacks and Valid Palindrome (03, 04), Ransom Note (02), React shopping cart and the other React and Spring Boot builds linked in entries 03–04, and the shopping cart and feature flag designs (01).
- Disney question banks: algorithms and system design (sign-in needed).
- Everything Disney in one place: the Disney interview page.
- More firsthand reports: the Experience feed.
In this series
- Part 1
- Part 2
- Part 3
- Part 4
- Part 5
- Part 6
- Part 7
- Part 8
- Part 9
- Part 10 (current)
- Part 11
- Part 12
- Part 13
- Part 14
- Part 15
- Part 16
- Part 17
- Part 18
Sources: Anywhere useful interview info can be found.
Comments
0No comments yet — be the first to share what you know.