Three candidates describe HomeLight engineering interviews that mix CTO coding conversations, technical screens, system design and several manager conversations. All three ended without an offer, and two described slow or drawn-out decisions.
$145K
Avg. Base Comp
$180K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Three candidates describe HomeLight engineering interviews, and all three ended without an offer. Their roles differed (full stack, senior frontend and senior software engineer), so treat these as separate accounts rather than one fixed process.
The technical content was described as manageable. One candidate's first conversation was with the CTO: a simple coding problem, opened by a walkthrough of projects you've built. Another reported a recruiter screen, a tech screen, then an onsite with a system design interview and three non-technical interviews. A third described an architecture interview, a code challenge and a smaller coding exercise with the CTO.
One design question is worth practicing: how to hide or obscure a user's private information from an agent before the user has approved sharing. It treats consent and data access as part of the architecture, so expect privacy boundaries to come up in design discussions.
The harder part was the back end of the process. One candidate had more than seven interviews, including several with managers from other teams, and was told the code style didn't fit. Another was told the team saw them at mid-level rather than senior and then waited weeks. A third heard nothing for about two months before an automated rejection. Applicants may want to ask early how the team writes and reviews code, prepare a resume-backed case for their level, and ask for a decision date after each round.
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 Homelight process.
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 Homelight
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Top Three Salaries | |
| Employee Salaries | |
| Monthly Customer Report | |
| Weighted Keys | |
| Merge Sorted Lists | |
| Raining in Seattle | |
| Over-Budget Projects | |
| Bagging vs Boosting | |
| Delivery Estimate Model | |
| Google Maps Improvement | |
| Top 3 Users | |
| User Experience Percentage | |
| Rectangle Overlap | |
| Job Recommendation | |
| Maximum Profit | |
| Find the First Non-Repeating Character in a String | |
| Month Over Month | |
| Integer to Roman | |
| Download Facts | |
| Sum to N | |
| P-value to a Layman | |
| Session Difference | |
| Daily Retention Summary | |
| Groups of Anagrams | |
| Distance Traveled | |
| Nearest Common Ancestor | |
| Size of Joins | |
| The Brackets Problem | |
| Hurdles In Data Projects |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report different starts. One senior frontend candidate began with a recruiter screen, while a full stack candidate's first conversation was with the CTO, which opened with a project walkthrough and a simple coding problem. Be ready to explain what you built and why.
Candidates describe a tech screen, a code challenge, and a smaller coding exercise with the CTO. They generally called the technical content not very difficult. One full stack candidate reports three separate technical interviews over about six weeks, so the number of technical rounds may vary by role.
A senior frontend candidate reports a system design interview in the onsite, and a senior software engineer reports an architecture interview. One reported prompt asked how to hide a user's private information from an agent before the user approves sharing, so consent and data access may come up in design.
One candidate reports an onsite with three non-technical interviews that felt unstructured. Another reports repeated conversations with managers from different teams, walking through background and problem-solving approach, totaling more than seven interviews. Expect to explain your scope, ownership and impact.
All three candidates report no offer. Reported reasons included code style fit and a level mismatch, where one candidate was told the team saw them as mid-level. Two described long waits, including about two months of silence before an automated rejection. Ask about next steps and timing after each round.
