Skip to contentSkip to footer
  • Community
  • Jobs
  • Companies
  • Salaries
  • For employers
      Notifications

      Loading...

      Elevate your career

      Discover your earning potential, land dream jobs, and share work-life insights anonymously.

      employer cover photo
      employer logo
      employer logo

      Zillow

      Engaged employer

      About
      Reviews
      Pay and benefits
      Jobs
      Interviews
      Interviews
      Related searches: Zillow reviews | Zillow jobs | Zillow salaries | Zillow benefits | Zillow conversations
      Zillow interviewsZillow Software Development Engineer interviewsZillow interview


      Glassdoor

      • About / Press
      • Awards
      • Blog
      • Research
      • Contact Us
      • Guides

      Employers

      • Free Employer Account
      • Employer Centre
      • Employers Blog

      Information

      • Help
      • Guidelines
      • Terms of Use
      • Privacy and Ad Choices
      • Do Not Sell Or Share My Information
      • Cookie Consent Tool
      • Security

      Work With Us

      • Advertisers
      • Careers
      Download the App

      • Browse by:
      • Companies
      • Jobs
      • Locations
      • Communities
      • Recent posts

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor," "Worklife Pro," "Bowls" and logo are proprietary trademarks of Glassdoor LLC.

      Company Bowl sample

      Want the inside scoop on your own company?

      Check out your Company Bowl for anonymous work chats.

      Bowls

      Get actionable career advice tailored to you by joining more bowls.

      Followed companies

      Stay ahead in opportunities and insider tips by following your dream companies.

      Job searches

      Get personalised job recommendations and updates by starting your searches.

      Software Development Engineer Interview

      2 Apr 2018
      Anonymous interview candidate
      Seattle, WA
      No offer
      Negative experience
      Average interview

      Application

      I applied in-person. The process took 2 months. I interviewed at Zillow (Seattle, WA)

      Interview

      Overall, I would probably go through the process again but there is still very much room for improvement and lots to be weary about. PROS - Interviewers were very nice people. - All of the questions I was asked were fair. No curveballs or gotchas. CONS - I actually failed my first phone screen with feedback saying that they were looking for candidates with better coding skills. I'm not sure how that was the case since my code had optimal complexity and pretty clean code (as clean as it can be when you're used to) and this company should really just stick with canned, non-specific rejection emails. Plus, I was still hit up by a recruiter a month later and had a phone screen that I passed, so not sure my coding skills were that bad. - There was a big delay my second time around between talking to the recruiter and getting a phone screen. Probably about a month. - So for my second time around, the phone screen interviewer didn't say anything during the entire phone screen and I'm pretty sure he wasn't even on codepair link since I only saw my name up. It sounded more like he was just doing work or emails in the background. - Seemed like Zillow is a bit Google obsessed: same interview style questions, recruiters bragging that their engineers choose them over Google, and calling you for a rejection. Google and other big tech companies attract a certain, myopic kind of personality. And saying you have Google talent doesn't attract all of us. In fact, it's going to push some of us, like myself, away. And in reality, Zillow might be a reputable tech company in Seattle but it doesn't have the same clout in other cities, so no need to force that Google comparison. - Seemed as if some of the questions I was asked about a current employer were loaded questions, was asked if I was running away from anything, putting me in between a rock and a hard place of not talking poorly about a professional leadership but also not sounding congruent with some of that current employer's bad reputation. - Usually companies just email you to reject you. In this case, Zillow didn't get back for a week and made it over a phone call. Phone calls aren't that much longer than reading an email but it's still a general waste of time in comparison. Moreover, the feedback I got was, "We had another candidate whose experience was better for the role but all the interviewers wanted you to know that they still see you being a great fit for Zillow." This just comes across as fake because if Zillow really meant that, then they'd follow-up with another onsite for a different role. It's at this point when I see why companies give canned rejection emails. In general, I just think that Zillow is walking this line between trying to have Google-tier technical talent but also being the greatest place to work with the nicest people and this sincerity comes off as phony and forced because they're still a huge tech company. Will probably interview with them again in the future, but will just be a bit weary.

      Interview questions [1]

      Question 1

      Leetcode Style Tech Questions/System Design/Behavioral
      Answer question
      12

      Other Software Development Engineer interview reviews for Zillow

      Software Development Engineer Interview

      18 Dec 2021
      Anonymous employee
      Los Angeles, CA
      Accepted offer
      Positive experience
      Average interview

      Application

      I applied through an employee referral. The process took 4 weeks. I interviewed at Zillow (Los Angeles, CA)

      Interview

      Had a 30 min zoom audio interview and was given 1 LC question, then two weeks later was notified I made it to the final round which consist of 2 one hour interview. For the first interview I was given two LC type question and solved it and for the second interview I was given just one question. All LC type question. Was given the offer about 2 weeks later. Whole process was about a month and so

      Interview questions [1]

      Question 1

      Signed an NDA so can’t say
      Answer question

      Software Development Engineer Interview

      24 Aug 2021
      Anonymous interview candidate
      No offer
      Neutral experience
      Average interview

      Application

      I applied online. The process took 2 weeks. I interviewed at Zillow in Aug 2021

      Interview

      I got contacted by a recruiter after my 3rd application. They set up a typical HR phone screen to talk about the job and my background. The recruiter seemed new to their job and just read straight off the job description and asked scripted questions without really introducing themselves. They didn't seem to know much about tech and couldn't answer any of my questions about the position besides what was listed on the job description. I thought it might have been an intern doing the call. I was moved to the next stage for a ~1 hour technical Hackerrank screen. The technical screen started off with very brief introductions and moved straight to coding without any behavioral questions like others on here said they received; I'm not sure if I passed the vibe check immediately so they decided to pass on the behaviorals or what.(?) I was asked 2 questions that were around LC medium. The first question I misunderstood to start (find Fibonacci sum, but I thought it was just regular Fibonacci until I was corrected) and ended up solving in O(n) time after a little fumbling. The interviewer asked if there was a faster approach, to which I said I didn't think so. I looked it up after the interview and there is an O(log(n)) solution that involves recognizing a math trick, but I doubt anybody who doesn't already know the answer going in to the interview would recognize it. I think this question was poor and doesn't have any real life application to what your average developer would ever do. The second question I recognized two possible approaches. I stated how I would do the slower O(n) brute force approach and what it's run time would be, and then proceeded to code the faster O(log(n)) binary search approach. I got the faster approach correct-ish with one mistake that I fixed after a hint from the interviewer. I wrote some test cases prior to fixing the mistake and they all passed, so in hindsight I was missing a single test case. The interviewer tried a little to guide me to recognize that I was missing the test case, but I think the stress of the interview situation and their hints being a little too vague for me to pick up on caused me to not recognize the missing test case. I was beating myself up about that when I realized it an hour after the interview had ended, but hoped they would overlook a minor mistake and give me a chance at an onsite (that's why we work in teams, right? to help catch mistakes?). Unfortunately I got a rejection email the next day. It sucks to be rejected for not having pre-hand knowledge of a problem and/or not being perfect in another problem in a 40 minute interview, but I guess it is what it is :(.

      Interview questions [1]

      Question 1

      Fibonacci sum and a modified binary search.
      Answer question
      2

      Software Development Engineer Interview

      23 June 2021
      Anonymous interview candidate
      Seattle, WA
      No offer
      Negative experience
      Difficult interview

      Application

      I applied online. The process took 1 week. I interviewed at Zillow (Seattle, WA)

      Interview

      HR Screen, Tech Screen, 4 hour on-site. Each on-site interview had at least 1 LC medium, barely any mobile questions which I applied for. I had a more practical interview at Google. Won’t be applying again because how on earth are they finding mobile engineers by asking them to memorize the iterative Fibonacci sequence. Waste of my time tbh

      Interview questions [1]

      Question 1

      Array, 2d Array, iterative Fibonacci
      1 Answer
      2