After a recruiter call, the process moved into a technical screen and then a live coding stage for a problem that felt closer to regular production work than the typical LeetCode style. Once I finished that, I went through a larger set of team interviews with several different lenses: a system design exercise using a whiteboard format for a property search experience that also needed to fit into Zillow’s broader ecosystem, a refactoring round where I had to clean up a production codebase with messy code, a behavioral interview handled in a STAR style, and then a final greenfield coding round that was similar in spirit to the earlier screening.
Across these steps, it felt difficult mostly because each round shifted the goalposts. I wasn’t just implementing algorithms—I had to reason about design and integration, and then pivot quickly into reshaping existing code without getting lost. The scheduling and coordination also stretched things out: the full pipeline had a lot of components, and the experience had a distinctly “heavy” feel.
3 months ago
Difficult Negative Guadalajara, Jalisco
My interview process dragged out across a large number of steps—about eight distinct parts—starting with recruiter involvement and continuing through multiple technical and team-fit style rounds. I had a code challenge that I needed to complete as part of the process (including a take-home style component), then additional interview stages that mixed behavioral evaluation with refactoring and system design, plus potential team-fit discussions.
Even with so many steps, the experience didn’t feel like it built toward anything. People didn’t offer real closure, and I ultimately felt like I was left hanging. The hardest part wasn’t any single question—it was the overall lack of follow-through once I finished what they asked for.
4 months ago
Easy Negative Mexico
Coordination became the story of my process. I went through what felt like months of scheduling back-and-forth, and the interviews kept getting cancel…
6 months ago
Difficult Neutral Seattle, WA
My interview started with an internal recruiter vetting call, and then I moved into the technical portion. At the beginning of the technical session I…
7 months ago
Average Neutral Ciudad de Mexico
After the recruiter phase, my interviews followed a fairly structured arc with multiple technical steps. I ended up doing several rounds that combined…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Rounds
The interview process typically includes a recruiter call followed by multiple technical rounds, often featuring coding challenges, system design, and behavioral interviews. Candidates should expect a mix of LeetCode-style problems and real-world coding scenarios, with a focus on both implementation and design reasoning.
Candidates will face a variety of technical assessments, including live coding exercises and system design discussions, often requiring knowledge of real-world applications rather than just algorithmic problems. Be prepared for questions that may cover legacy code maintenance and system integration.
Live codingSystem designLegacy code
Behavioral Evaluation
Behavioral interviews are a significant part of the process, often using the STAR method to assess cultural fit and past experiences. Candidates should be ready to articulate their experiences and how they align with Zillow's core values.
STAR methodCultural fitPast experiences
Coordination & Communication Issues
Many candidates reported challenges with scheduling and communication, including last-minute cancellations and lack of follow-through after interviews. It is advisable to remain proactive in following up and managing expectations throughout the process.
Scheduling issuesCommunicationFollow-up
Overall Experience & Feedback
Candidates often felt the process was lengthy and lacked closure, with many not receiving feedback after interviews. Despite the structured nature of the interviews, the overall experience can feel draining, and candidates should prepare for potential ghosting after the final stages.
Lengthy processFeedbackGhosting
Expectations vs. Reality
There can be a mismatch between candidates' expectations of the interview format and the actual experience, particularly regarding the depth of technical discussions. Candidates should clarify the role's focus areas during initial conversations to align expectations.