RepostedThe Walt Disney Company logo

The Walt Disney Company · Phone screen → Onsite

In process

Disney Ads and Principal SWE Loops: 4 Experiences (Part 11 of 18)

Software engineer · Full-time3 years experienceReported Oct 18, 2024
Shared byjanebeingjane

Disney experienced SWE interviews in 2024: Senior Ads and Principal onsites with ad-system designs, graph and prefix coding, plus a 2018 behavioral round.

At a glance

Coverage: 3 experienced full-time software engineer reports from January to August 2024 (Senior Ads, Principal, and one title not given), and one 2018 report in History.

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 — EXPERIENCED: frontend 2025, then a separate fullstack section for 2024.
  • Part 11 (current) — 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; individual titles and teams stated below

What came up

These 3 current reports share this role scope; the 2018 report is in History.

Topic Reports Last seen
Coding / data structures 3 Aug 2024
Behavioral questions 2 Feb 2024
System design 2 Feb 2024
Technical fundamentals 1 Feb 2024

Questions we found

Algorithms / Data Structures

Question Reports Last seen
Merge N sorted lists 1 2024 Q1
Tentative LC2655 reference: Find Maximal Uncovered Ranges 1 2024 Q3
Top three word suggestions for each query prefix 1 2024 Q1
Generate a random connected undirected graph and print a shortest path 1 2024 Q1
Song pairs whose total duration is divisible by sixty 1 2024 Q1
Find marked hub vertices within a graph radius 1 2024 Q1

System Design

Question Reports Last seen
Ad impression count aggregator 1 2024 Q1
Partner ad delivery with a cap or fixed pacing 1 2024 Q1
Client-triggered ad serving in live video 1 2024 Q1
Advertiser application for publishing advertisements 1 2024 Q1

API Coding

Question Reports Last seen
Read data from a supplied API URL 1 2024 Q1

Candidate timelines

01: A short phone report with an encoded problem number

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

The August 2024 report gives only a problem number, written to be read backwards. It most likely means LeetCode 2655, Find Maximal Uncovered Ranges. The post supplies no statement, inputs, approach or follow-up to independently confirm the intended variant. Treat the linked exercise as the identified practice lead, rather than a recovered full interview prompt. No hiring outcome was given.


02: Senior Ads onsite: suggestions, measurement and an advertiser app

Interview period: 2024 Q1 (as reported) · Report: 2024-02-09 · Role: Senior software engineer, Ads · Cohort: Experienced Full-Time

The candidate was invited onsite less than a week after the phone screen. Five rounds were spread over two days:

  1. Coding asked for the first three matches for every prefix of a search word, using cat, carpet, car, camera and apple with camera as the query. The candidate proposed a trie, then implemented brute force when the interviewer preferred the simpler option. Another task fetched data from a supplied API URL; the endpoint and expected result were not retained.
  2. An ad-impression count aggregator, with the interviewer guiding the candidate through components and scaling.
  3. Relational versus nonrelational databases, React hooks, merging N sorted lists, and database design. The candidate sketched two tables, explained @ManyToOne, and discussed JPARepository functions used by the team.
  4. A missed design session was rescheduled for a 30-minute oral discussion the next day: an advertiser-facing app for publishing ads. As the proposed leader, the candidate walked through requirements, system flow, services, database storage and information advertisers would supply.
  5. Hiring-manager discussion of the resume, past projects, expectations for the new job and general BQ.

The interviewers gave immediate feedback. A verbal offer arrived on the Friday after the Wednesday onsite; a later reply confirms accepting it. The role was Senior and Ads-related.


03: Principal: graphs, song pairs and two difficult ad-system rounds

Interview period: 2024 Q1 (as reported) · Report: 2024-01-08 · Role: Principal software engineer · Cohort: Experienced Full-Time

A LinkedIn recruiter approached the candidate about a Principal-engineer backfill. The phone task was to generate a fresh random connected undirected graph with N vertices and print a shortest path between two vertices.

The five onsite rounds ran in this order:

  1. Behavioral questions, then partner ad delivery that either maximizes delivery up to a cap or serves at a fixed rate such as 10,000 per hour. The candidate steered toward a generic rate limiter, which was not the interviewer's intended design.
  2. About 20 minutes of BQ, then song-duration pairs whose total is divisible by 60. The candidate solved it in roughly five minutes and chatted for another half-hour; feedback was positive.
  3. A manager behavioral interview, also with positive feedback.
  4. Client-triggered ad serving at live-video ad breaks. Feedback said scalability was not handled well.
  5. Hub vertices within a radius of a given starting vertex, with a node field identifying hubs. The first version used unit-distance edges; the follow-up gave edges different distances. Feedback was positive.

The candidate attributed the rejection to the two design rounds. Both ad-design links lead to a broader ad-serving practice; the two interview briefs are kept distinct here.



Common questions

What system design does Disney ask Ads engineers?

Ad systems: an impression count aggregator and an advertiser publishing app (02), and partner ad delivery with caps or pacing plus client-triggered ad serving in live video (03).

What coding does Disney ask Principal engineers?

A random connected graph with a shortest path, song pairs divisible by 60, and hub vertices within a radius with weighted edges as a follow-up (03).

History (before 2023)

H01: A behavioral rejection with task-estimation questions

Interview period: 2018 Q4 (as reported) · Report: 2018-08-30 · Role: Software engineer; exact title not reported · Cohort: Experienced Full-Time

The second round was behavioral only. The interviewer asked four questions: how to handle a coworker who upsets you; what to do when a task takes longer than your estimate; how you estimate the time needed for work; and what to do when a new problem appears while you are already solving another. The candidate felt their answers missed the interviewer's expectations and was rejected.


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.