RepostedThe Walt Disney Company logo

The Walt Disney Company · Phone screen → Onsite

In process

Disney Experienced SWE, More Loops: 6 Experiences (Part 9 of 18)

Software engineer · Full-time3 years experienceReported Sep 13, 2026
Shared byjanebeingjane

More Disney experienced SWE interviews, 2025–2026: design on tickets, social feeds and runways, plus Spring Boot builds and data-structure coding.

At a glance

Coverage: 6 experienced full-time software engineer reports (exact titles not given; one on a streaming team), April 2025 to September 2026.

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 (current) — EXPERIENCED · SWE: 2026 array Set; 2025 ad filtering, backend and design.
  • Part 10 — 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.

Software engineering; exact title not reported

What came up

These 6 candidate accounts share the role/cohort scope stated above. Counts apply to this section only.

Topic Reports Last seen
Coding / data structures 4 Sep 2026
Projects / work experience 2 Sep 2026
Concurrency / database writes 1 Sep 2026
System design 4 Jan 2026
Frontend implementation 1 Jan 2026
Backend implementation 2 Sep 2025
Behavioral questions 2 Aug 2025

Questions we found

Algorithms / Data Structures

Question Reports Last seen
Resizable array-backed set without hashing 1 2026 Q3
Reverse Linked List 1 2025 Q3
Single-rule ad filter with AND and OR 1 2025 Q4
LRU Cache 1 2025 Q4
Flatten a tree, then reconstruct it from the flattened output. 1 2025 Q3

Behavioral (BQ)

Question Reports Last seen
Describe your most impactful project. 1 2026 Q3

System Design

Question Reports Last seen
Recommendation feature API design 1 2025 Q3
Ticketmaster ticket booking system design 1 2025 Q1
Instagram system design with search, likes and feeds 1 2025 Q3
Twitter-like platform with a ranked paginated dashboard 1 2025 Q4
Efficient airport operations with two runways 1 2025 Q1

Project Coding

Question Reports Last seen
Movie title/year browser with sorting and search 1 2025 Q4
Add an API to a Spring Boot application 1 2025 Q3
Spring MVC endpoint for the course with most students 1 2025 Q3

Concurrent Coding

Question Reports Last seen
Concurrent buffered batch writer for a database batch API 1 2026 Q3

Candidate timelines

01: An array-backed set, then a batch-writer misunderstanding

Interview period: 2026 Q3 (as reported) · Report: 2026-09-13 · Role: Streaming software engineer; exact title not reported · Cohort: Experienced Full-Time

The September 2026 phone screen opened with the candidate's most consequential project. The interviewer initially expected Java; the candidate used Python.

For the first task, the candidate had to implement a resizable set backed by an array, without a hash function. They began with a fixed-capacity list that could grow and shrink with the data, explained operation costs, and discussed a hash-based index as an optimization. They also considered multithreading before the interviewer introduced the second task. That discussion should not be read as permission to ignore the original no-hashing requirement.

With roughly 20 minutes remaining, the interviewer moved to a concurrent buffered writer that would send batches to a database. The candidate implemented a thread pool that issued individual writes. Only late in the discussion did the interviewer make clear that the database already exposed a batch API and that the buffer and batching were central. There was not enough time to rewrite the solution. The candidate was rejected.

The account also discusses experience spanning a data center and AWS. The precise buffer API, flush policy and failure semantics were not disclosed, so that second exercise is described here without a practice link.


02: An ad-filter phone screen and a ranked social-network onsite

Interview period: 2025 Q4 (as reported) · Report: 2026-01-12 · Role: Software engineer; exact title not reported · Cohort: Experienced Full-Time

The report was posted in January 2026 and labels the interviews as 2025 Q4. The phone task was a single-rule advertisement filter. Ads had an ID, target locations and an age; the rule could contain locations and minimum/maximum age, combined with AND or OR. Returned IDs had to preserve input order. In the reported example, a minimum age of 21 and US location under AND accepted A (age 21, US/CA), rejected B (age 13, US), and rejected C (age 25, CA). Case handling and several boundary conventions were not stated.

The onsite design was a Twitter-like platform with a ranked, paginated dashboard. It included creating/deleting tweets, viewing one's own or another account's tweets, following other accounts, liking/unliking posts from accounts one did not follow, and follower/following lists. A personal dashboard returned the top X items. Ranking signals discussed included follow relationships, total and recent likes, recency, and accounts recently followed, recently viewed or frequently viewed. The proposed tables were tweets (tweet_id, text, account_id, date_time), follows (follow_from_account_id, follow_to_account_id, date_time), likes (tweet_id, liked_from_account_id, date_time), and accounts (account_id, date_time).

Other onsite work included an LRU cache and a frontend movie browser supporting title/year sorting and search over JSON data. Behavioral discussion was mentioned without the individual questions. No final result was supplied. The practice exercises spell out runnable interfaces and edge cases that the original report leaves open.


03: Two team loops: Spring Boot pairing, trees and Instagram

Interview period: 2025 Q3 (as reported) · Report: 2025-09-09 · Role: Software engineer; exact title not reported · Cohort: Experienced Full-Time

This September 2025 report covers one candidate's loops with two teams. Both hiring-manager interviews included projects, behavioral discussion and Java/Spring or garbage collection.

The first team asked the candidate to add an API to a Spring Boot application in a pair-programming session. A 90-minute slot lost about 20 minutes to the interviewer's late arrival; the candidate describes roughly 40 minutes of coding. Remaining discussion touched behavioral topics and design patterns. That team did not move forward. The source does not provide the original endpoint specification; the linked exercise is a bounded practice reconstruction.

The second team asked the candidate to flatten a tree, described as similar to LeetCode 430 but involving a tree, then reverse a linked list. A roughly two-minute frontend debugging task had no disclosed defect. A fourth, bonus question asked them to reconstruct the tree from the flattened output. The tree practice explicitly includes information needed for reconstruction; the original report does not specify that representation.

System design covered Instagram-style search, likes and feeds, followed by project and behavioral discussion with a director. The candidate said three tasks were expected and the reconstruction was additional, rather than four mandatory coding rounds.


04: A Spring MVC course endpoint and recommendation APIs

Interview period: 2025 Q3 (as reported) · Report: 2025-07-21 · Role: Software engineer; exact title not reported · Cohort: Experienced Full-Time

The candidate had been told to expect 90 minutes, but the actual interview lasted about an hour: roughly half coding and half design. They downloaded a Java/Spring repository from GitHub and shared their IDE.

The task was to return the course with the most enrolled students, using supplied Course and Student entities and insertion code, and adding the relevant entity/controller/service pieces. About 20 minutes went to configuration problems. The candidate outlined an approach but did not finish the implementation.

The design half covered APIs for a recommendation feature. The candidate specifically distinguished feature/API design from inventing a recommendation algorithm. The result was rejection.


05: A phone-screen pass after an unnamed BFS problem

Interview period: 2025 Q2 (as reported) · Report: 2025-08-15 · Role: Software engineer; exact title not reported · Cohort: Experienced Full-Time

The August 2025 phone account reports about five minutes of introductions, ten minutes of general behavioral questions and 30 minutes on an unnamed medium BFS task. The recruiter said the candidate passed that same day and arranged an onsite. A follow-up identifies Santa Monica.

The state, required output and example for the BFS task were not disclosed, so there is no defensible practice match. A separately posted August 15 onsite account also mentions BFS, but the retained evidence does not explicitly establish that these are the same candidate. These two reports therefore are not presented as a proven single hiring timeline.


06: An onsite with ticketing and two-runway airport discussion

Interview period: 2025 Q1 (as reported) · Report: 2025-04-17 · Role: Software engineer; exact title not reported · Cohort: Experienced Full-Time

The April 2025 report calls the virtual onsite four rounds, but individually describes only Ticketmaster-style ticket booking, how to make an airport with two runways operate efficiently, and a hiring-manager/behavioral conversation. The airport question was an open discussion; the source does not specify a scheduling algorithm or performance target. A fourth technical question and a final result were not disclosed.



Common questions

What system design does Disney ask software engineers?

Ticket booking and an airport with two runways (06), a ranked Twitter-like platform (02), an Instagram-style feed (03) and a recommendation API (04).

Does Disney ask Spring Boot in interviews?

Yes, in two reports: add an API to a Spring Boot application while pairing (03), and a Spring MVC endpoint for the course with the most students (04).

Keep practicing

In this series

Sources: Anywhere useful interview info can be found.

0 total reactions. Your reactions: none.
0 comments

Comments

0

No comments yet — be the first to share what you know.