The Walt Disney Company Software Engineer interview typically runs 4 rounds: recruiter screening, hiring manager interview, technical interview, and director interview. The process usually takes about 3 to 7 weeks and is notably conversational and low-pressure.
$128K
Avg. Base Comp
$173K
Avg. Total Comp
4
Typical Rounds
3-8 weeks
Process Length
Our candidates consistently describe Disney’s software engineer interviews as surprisingly conversational, and that’s the real signal: they care less about whether you can perform under pressure and more about whether you can explain your experience clearly and make sensible tradeoffs. One candidate who received an offer said the technical discussion felt relevant to the actual work, with no gotcha-style questions and a team that was understanding when they didn’t know something. Another candidate said the panel spent most of the time on resume walkthroughs, motivation, and comparing technologies they had used before. That tells us Disney is listening for engineers who can connect past work to the role without overselling it.
A recurring theme is that the company seems to evaluate fit from multiple angles at once. The broad panel in one experience included engineers and a product owner, which made the conversation feel less like a single interviewer probing for a right answer and more like a group checking whether the candidate’s thinking holds up across different perspectives. We’ve also seen that clear opinions on tools and tradeoffs matter more than memorized syntax: one candidate was explicitly asked for the positives and negatives of one technology versus another. The candidates who did best came across as practical, grounded, and easy to work with — not flashy, just credible about how they solve problems and why they choose one approach over another.
Synthetized from 2 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the The Walt Disney Company process.
This ended up being one of the smoother interview processes I’ve had. I started with an initial recruiter screening over video, then moved into a video interview with the hiring manager. After that came an in-person technical interview at the office, and the last step was a video interview with the director of engineering. The whole process moved pretty quickly at first — I finished the interviews in about 3 to 4 weeks — but then there was a longer wait to hear back, closer to another 3 to 4 weeks.
What stood out most was how kind everyone was throughout. The technical round felt relevant to the actual work and didn’t have any gotcha-style questions. They seemed more interested in whether I could think through problems and fit the role than in trying to trip me up, and they were understanding if I didn’t know something. That made the in-person technical interview feel much less stressful than I expected. The recruiter was also really involved and advocated for me a lot, which I appreciated.
I ended up getting the offer, and I’m excited to join the team. My main takeaway is that this process felt more like a practical conversation about the job than a high-pressure coding gauntlet, so it’s worth preparing to discuss your experience clearly and to talk through technical questions in a straightforward way.
Prep tip from this candidate
Be ready for an in-person technical round that stays close to the work you’d actually do, rather than trick questions. Also expect a final director interview and some patience after the interviews, since the feedback loop took several weeks.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at The Walt Disney Company
Implement the k-means clustering algorithm in python from scratch
| Question | |
|---|---|
| 2nd Highest Salary | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Rolling Bank Transactions | |
| P-value to a Layman | |
| Employee Salaries | |
| Prime to N | |
| Largest Salary by Department | |
| Monthly Customer Report | |
| Raining in Seattle | |
| Find the Missing Number | |
| Address Schema | |
| Liked Pages | |
| Employee Salaries (ETL Error) | |
| Permutation Palindrome | |
| Integer to Roman | |
| One Element Removed | |
| Size of Joins | |
| Session Difference | |
| The Brackets Problem | |
| Basic Regex | |
| Flatten N-Dimensional Array to 1D Array | |
| Paired Products | |
| Google Maps Improvement | |
| Centralized Event Ingestion | |
| Hurdles In Data Projects | |
| Nearest Common Ancestor | |
| Popular Actions | |
| Identifying User Sessions |
Synthesized from candidate reports. Individual experiences may vary.
The process starts with an initial recruiter call, usually over video or Zoom. In one experience it was very brief and mostly a formality, while in another it served as the first screening before moving the candidate forward.
Next is a video interview with the hiring manager. This conversation is largely conversational and focuses on your background, why you want the role, and how your experience aligns with the team’s needs.
Candidates then complete a technical round, which may be in person at the office or conducted as a broader technical panel. The questions are practical and experience-based, centered on problem solving, tradeoffs between technologies, and discussing past work rather than LeetCode-style coding.
The final stage described is a video interview with the director of engineering. This round appears to be a final fit and technical discussion before the decision is made.