Zillow Software Engineer interview typically runs 8 rounds: HR, live coding, take-home, behavioral, refactoring, system design, and team-fit interviews. It usually takes about a month, with slow scheduling and practical, production-style screens.
$125K
Avg. Base Comp
$248K
Avg. Total Comp
6-8
Typical Rounds
3-5 weeks
Process Length
We’ve seen Zillow lean hard toward production-minded problem solving rather than interview theater. Multiple candidates described live coding that felt collaborative and grounded in real work: parsing text into structured output, handling rational conditions, and solving straightforward tasks carefully instead of chasing clever algorithms. Even the question set reflects that pattern — first non-repeating character, duplicate detection, LRU cache, binary tree validation, and common-ancestor style problems are all familiar, but the bar is in how cleanly and calmly you implement them under discussion.
A recurring theme is that Zillow wants engineers who can work with imperfect code and imperfect requirements. One candidate called out a refactor exercise on messy legacy code, and that lines up with the company’s broader product surface: a large, data-heavy marketplace where maintainability matters. We’ve also seen the technical conversation extend into Python data structures, PEP8, standard library usage, OOP basics, cloud, and databases, which suggests they care about whether you can make sensible engineering tradeoffs, not just pass a narrow coding test.
The most Zillow-specific signal shows up in system design. Candidates repeatedly mentioned prompts tied to property search, location, and Zillow’s broader ecosystem, which means generic backend diagrams won’t carry you far. What seems to make or break people here is whether they can connect architecture choices to a real consumer product with messy data, search relevance, and scale. In our experience, the strongest candidates are the ones who can explain why a design fits Zillow’s domain, not just how it works.
Synthetized from 3 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 Zillow process.
I got reached out to by a recruiter on LinkedIn, and the process ended up being pretty structured. It started with a profile interview, then a technical screen that was live coding but not really LeetCode-style. The first coding round felt more like a production scenario: they gave me an input/output setup and wanted me to talk through how I’d approach it before jumping into code. In my case, I was working from a plain text file and had to explain how I’d turn that into the expected output. After that, I had a second technical coding round a couple of weeks later, which was still in the same vein — practical problem solving rather than puzzle questions.
Once I got past the coding screens, the later rounds were with the team. There was a legacy code maintenance interview, which was basically a refactor exercise on messy code, and that one felt very realistic. They wanted to see what I would clean up first, how I’d think about conventions, and how I’d improve the code without trying to rewrite everything. I was also asked about Python data structures, PEP8, standard library functions, and some OOP basics, plus a bit of cloud and database knowledge. The behavioral interview was with the engineering manager and was pretty standard STAR format. The final round was system design, and the prompt was to whiteboard a property search system that also had to fit into Zillow’s broader ecosystem. Another version of the design question I heard was framed around designing a system based on your location, so the design round definitely seemed to be about practical product thinking. Overall, it was a solid process but fairly long, and after the onsite I was ghosted. The main takeaway for me was to prepare for production-style coding, refactoring under time pressure, and a system design that is specific to Zillow’s domain rather than generic backend architecture.
Prep tip from this candidate
Practice explaining your approach out loud on input/output coding problems, especially when the prompt is a file-processing or production-style task rather than a LeetCode problem. Also be ready for a refactor round on messy legacy code and a Zillow-specific system design around property search and the company ecosystem.
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 Zillow
Write a function to determine whether or not two rectangles overlap.
| Question | |
|---|---|
| Find the First Non-Repeating Character in a String | |
| Google Maps Improvement | |
| Nearest Common Ancestor | |
| Sum to Zero | |
| Find Duplicate Numbers in a List | |
| Target Value Search | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Binary Tree Validation | |
| Optimal Host | |
| Messenger Payments | |
| Unified Live Comments | |
| LRU Cache 1 | |
| Reddit-like Notifications | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Weighted Keys | |
| Merge Sorted Lists | |
| Raining in Seattle | |
| Employee Salaries | |
| Delivery Estimate Model | |
| User Experience Percentage | |
| Maximum Profit | |
| P-value to a Layman | |
| Download Facts | |
| Sum to N | |
| Session Difference | |
| Integer to Roman | |
| Distance Traveled | |
| Over-Budget Projects |
Synthesized from candidate reports. Individual experiences may vary.
The process often begins with a recruiter reaching out, sometimes via LinkedIn. Candidates then complete an initial profile or HR-style interview to review background, role fit, and basic expectations. This is a live pairing-style coding round focused on practical problem solving rather than LeetCode puzzles. Interviewers may present input/output or production-like scenarios and expect candidates to talk through their approach before coding.
A follow-up coding interview typically comes later, sometimes after a couple of weeks. It stays in the same practical vein, emphasizing clean implementation, careful reasoning, and day-to-day engineering judgment. Some candidates reported a take-home coding assignment as part of the process. This appears to be another practical exercise rather than an algorithmic test, likely used to evaluate code quality and problem-solving outside a live interview.
Candidates may be asked to work through messy or legacy code and explain what they would clean up first. The focus is on refactoring strategy, conventions, maintainability, and improving code without rewriting everything. This round is typically a standard behavioral interview in STAR format with the engineering manager. Expect questions about collaboration, communication, and how you handle engineering tradeoffs.
The final technical round is a system design interview tailored to Zillow’s domain. Candidates reported prompts such as designing a property search system or a location-based product, with an emphasis on practical product thinking and how the design fits into Zillow’s ecosystem.