Opendoor Senior Fullstack Interview Experience Seattle
Interview Experience
I applied for a senior fullstack position in Seattle Recruiter Screen: Literally asked me nothing, just talked about the interview process Tech screen: Part 1) Build a key value store that suppors ope
Full Details
I applied for a senior fullstack position in Seattle Recruiter Screen: Literally asked me nothing, just talked about the interview process Tech screen: Part 1) Build a key value store that suppors operations add, update, delete Part 2) Support operations isExpired, sleep(time), setTTL(ttl) Interviewer seemed to hate his life. React Interview 1: Build a react app that makes a web request for a list of images and renders rows and columns dynamically as window size changes while keeping images the same size. Very CSS focused which I wasn't prepared for since I am a mobile dev. React Interview 2: Part 1) Debug a rendering issue with the scabble board. It's a css margin issue on the p tag. Part 2) Make a network request for game data and render the scrabble board. They asked me to implement the first two buttons here https://scrabble-interview.vercel.app/frontend/game
System Design Design Job Queue for Opendoor ops tasks (essentially design Jira). Imagine 100s of people using the same Jira board. If someone marks a task complete, everyone else should see the changes in real time.
Behavioral Very conversational, none of that "Tell me about a time you..." STAR bullsh*t. Mainly just talking about a couple projects I worked on.
Result FAILED. I don't know css at all, I didn't think the react interviews would be so focused on css. I know react very well, but in a mobile context only, so no css.
Topics
About Opendoor Interview Reports
This question was reported by a candidate who interviewed at Opendoor. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Opendoor are the higher-signal extractions to take from this report.
For broader preparation context, the Opendoor interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Opendoor reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Opendoor Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Opendoor reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.