I had a phone screening split into two parts.
The first part involved Java technical questions and basic concepts such as Overload vs. Override.
The second part was a little more difficult, where I was asked a scenario question: What happens if I have a website that is running slow? How can I improve its functionality?
It was essentially a troubleshooting question, asking what else could be done if a certain approach didn't improve the system.
In all, it lasted 40 minutes.
The interview was split into three parts.
The first part consisted of behavioral questions, such as "What's a project where you demonstrated leadership?"
The second part was technical, where I was asked an assortment of Java and SQL questions, including "abstract class vs. interface" and "indexing within SQL."
The third part was a relaxed discussion about the team's current work.
The following metrics were computed from 8 interview experiences for the Disney Software Engineer role in Seattle, Washington.
Disney's interview process for their Software Engineer roles in Seattle, Washington is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Disney's Software Engineer interview process in Seattle, Washington.