Three candidates describe Redfin's Product Manager interviews: a recruiter and PM phone screen with behavioral questions, then for some an onsite with product design prompts about Redfin's own website and app.
$143K
Avg. Base Comp
$183K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidates describe Redfin's Product Manager interview as a behavioral phone screen followed, for some, by an onsite built around Redfin's own product. All three reported no offer, so the questions below show what to prepare for, not what leads to success.
Two candidates described the phone screen as straightforward. One said the interviewer followed a script through the resume and asked about adversity and going above and beyond. Another described a PM interviewer who asked mostly behavioral questions and nudged them toward stronger answers. Prepare cohesive stories about past projects, especially examples of handling adversity and going above and beyond, since those themes came up directly.
The onsite is where product critique and redesign prompts appeared. One candidate was asked to design a new Redfin mobile app on a whiteboard and to critique the website: what works, what to improve and which features to add. Another was asked to redesign a Redfin page and recalled it as a prompt to start from user needs. Bring concrete, specific observations about both the site and the app.
One candidate who was flown out for an onsite said interviewers repeatedly asked how a computer science background would affect them as a product candidate. If you come from engineering, prepare a clear case for how that background helps your product judgment.
Communication after interviews was thin in two accounts. One received a generic rejection email a week after the onsite. Another was told to expect a full loop and was then dropped without explanation.
Synthesized from 3 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 Redfin process.
I applied online and got an email the next day to schedule a phone screening. That call was pretty straightforward — the interviewer stuck to a script, walking through my resume and asking how my past experience aligned with the role. I got the typical behavioral questions: how I'd handled adversity, times I'd gone above and beyond. Nothing surprising there.
What caught me off guard was the onsite portion. They had me design a new version of the Redfin mobile app on a whiteboard, which felt more like a design exercise than a traditional product discussion. They also asked me to critique Redfin's website — what was working, what would I improve, what features would I add. I'd prepared for product sense questions, so I talked through my observations and offered concrete suggestions. The interviewers seemed engaged enough in the moment, but I walked out feeling uncertain about how my answers landed. A week later I got a generic rejection email with no feedback.
Prep tip from this candidate
Come prepared with specific critiques of Redfin's website and mobile app before the interview — they will absolutely ask you to evaluate their own product, and vague observations won't cut it. Have concrete UI/UX improvements ready to sketch or discuss in detail.
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 Redfin
You're building a model to predict home prices and you see that the prices in your training data are right-skewed. How would you handle this situation?
| Question | |
|---|---|
| Missing Housing Data | |
| Experiment Validity | |
| Longest Streak Users | |
| Button AB Test | |
| 2nd Highest Salary | |
| Top 3 Users | |
| User Experience Percentage | |
| Top Three Salaries | |
| Employee Salaries | |
| Over-Budget Projects | |
| WAU vs Open Rates | |
| Google Maps Improvement | |
| Distance Traveled | |
| Monthly Customer Report | |
| Size of Joins | |
| Month Over Month | |
| Pre-Launching Shows | |
| Instagram TV Success | |
| Group Success | |
| Demand Metrics | |
| Find the First Non-Repeating Character in a String | |
| Download Facts | |
| Session Difference | |
| Network Experiment Design | |
| Decreasing Comments | |
| Merchant Acquisition | |
| Uber Eats Success | |
| Third Purchase | |
| Hurdles In Data Projects |
Synthesized from candidate reports. Individual experiences may vary.
One candidate applied online and received an email the next day to schedule a phone screen. Another described a friendly recruiter who stayed in contact through the early stage. Timing beyond that is not clearly reported, so expect to be flexible and follow up politely.
Candidates report a fairly standard PM phone screen. One described a scripted walk through the resume and how past experience fits the role, with questions on handling adversity and going above and beyond. Another spoke with a PM who asked mostly behavioral questions and offered gentle steering.
Candidates who reached the onsite report product prompts about Redfin itself. These included designing a new mobile app on a whiteboard, critiquing the website and suggesting features, and redesigning a Redfin page starting from user needs. Prepare specific, concrete ideas rather than general observations.
One onsite candidate with a computer science background said interviewers repeatedly asked how that experience might hurt them as a product candidate. This is a single report, but engineers moving into product may want a clear, confident answer ready about why their technical depth helps.
All three candidates ended without an offer. One received a generic rejection email about a week after the onsite, and another was told to expect a full loop before being notified they were no longer considered. Candidates report little or no feedback, so you may not get an explanation.
