Zillow Software Engineer candidates report practical live coding, refactoring, behavioral discussion, and product-oriented system design; one recent candidate completed a recruiter call followed by a 75-minute CodeSignal backend exercise.
$186K
Avg. Base Comp
$247K
Avg. Total Comp
6-8 rounds
Typical Rounds
4-5 weeks
Process Length
Zillow Software Engineer interviews reported here emphasize practical implementation and communication more than classic puzzle-style coding. One candidate described a live CodeSignal backend exercise lasting about 75 minutes: they read requirements, clarified behavior, implemented a solution, and explained their reasoning. That report specifically highlights code structure, input validation, edge cases, duplicate records, ordering, and changing requirements. Practice narrating a clean implementation while you make trade-offs visible, rather than waiting until the end to explain them.
Other candidates described live coding built around input/output or day-to-day conditions, followed in some cases by a legacy-code refactor. For the refactor discussion, be ready to identify what you would clean up first, apply conventions deliberately, and improve code without assuming a wholesale rewrite is wanted. One report also named Python data structures, PEP 8, standard-library functions, OOP basics, cloud, and database knowledge.
Later conversations may include a standard STAR-style behavioral interview and a whiteboard design prompt around property search or location-based product needs. Connect design choices to search behavior, data ownership, scale, and integration constraints as you reason aloud. Reports vary in how much of the broader process a candidate personally completed, so use the sequence below as preparation coverage rather than a fixed itinerary.
Synthesized from 4 candidate 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.
First, I had a recruiter interview. She explained the company and role and asked about my salary expectations. After that, I moved to a backend coding interview through CodeSignal. The prompt was a practical backend-style coding problem rather than a pure algorithm puzzle. I was asked to read the requirements, clarify the expected behavior, implement the solution, and explain my reasoning while coding.
The evaluation focused on how I structured the code, handled edge cases, validated inputs, and communicated trade-offs. I also had to think about cases such as empty input, invalid requests, duplicate records, ordering, and preserving correctness as requirements changed.
There was no separate take-home assignment. The CodeSignal round was live and lasted about 75 minutes. I was still waiting to hear back afterward.
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 | |
| Employee Salaries | |
| Monthly Customer Report | |
| Weighted Keys | |
| Merge Sorted Lists | |
| Raining in Seattle | |
| Over-Budget Projects | |
| Delivery Estimate Model | |
| Bagging vs Boosting | |
| Top 3 Users | |
| User Experience Percentage | |
| Job Recommendation | |
| Maximum Profit | |
| Month Over Month | |
| Integer to Roman |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial recruiter conversation that covered the company and role; one candidate was also asked about salary expectations. Use this stage to give a concise account of your background and clarify the role’s technical focus.
Candidates report practical live coding rather than a pure algorithm puzzle. One recent report describes a 75-minute CodeSignal backend exercise requiring requirement reading, clarification, implementation, and explanation of reasoning.
One candidate reported a second coding discussion after the first screen, also framed as practical problem solving. Be prepared to explain an approach before coding and to keep the implementation organized as requirements are clarified.
A candidate who progressed to team interviews reported a legacy-code maintenance exercise. They were asked what to clean up first, how to apply conventions, and how to improve messy code without rewriting everything.
One candidate reported a STAR-style engineering-manager conversation and a final whiteboard system-design prompt about property search within Zillow’s ecosystem. You may need to tie design decisions to practical product constraints while communicating trade-offs.
