Neighborhoods.com logo

Neighborhoods.com Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 23 interview experiences · FREE TO READ

2.6 Rounds average
Average Typical difficulty
78.3% Positive experience

Which role are you interviewing for?

11 roles · 23 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Neighborhoods.com.

Showing 4 of 23
Neighborhoods.com logo
Neighborhoods.com

Customer Success Operations Support Specialist

Operations · more than a year ago

Entry Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Phone screen Group Offer
Interview formats
Behavioral Technical

The interview process had about 3-4 steps. First, a recruiter called to see if you were interested and a good fit. Then, a video call with the department manager to talk more about the role, your background, and a Q&A to understand you better and how you'd handle customer service situations. Next, a video call with the whole team to meet your future colleagues! Finally, a video call with the Director to officially welcome you to the team, as you're the top candidate and a job offer is coming soon.

Confirmed questions1 question
  • Can you share an instance where you dealt with a challenging customer and how you managed to resolve the situation?
Neighborhoods.com logo
Neighborhoods.com

User Experience Designer

Design

Mid Easy Positive experience Accept offer 3 rounds
Interview process
Recruiter call Onsite Background check Offer
Interview formats
Behavioral Presentation

I got referred to Neighborhoods.com by a friend, so there wasn't a formal application. Scheduling was super flexible since I was out-of-state, and the hiring manager made sure I felt good about the company before I came for the in-person. The whole thing felt pretty laid-back and open. It started with the founders and hiring manager telling me what they needed for the role, then we just chatted about how my research and processes could help them out. All three interviewers were clearly super into the company, which was a big plus for me, and they seemed really open to new ideas. My only thought is that it would have been cool to chat with other team members too (which we do now). It would have been nice to get a better sense of the overall company vibe beyond just the execs – I find people are more honest when their managers aren't around : )

Confirmed questions1 question
  • If we have a problem like 'X', what research and A/B tests would you suggest to tackle it?
Neighborhoods.com logo
Neighborhoods.com

Front End Engineer

Engineering

Mid Average Negative experience No offer 5 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Take home Presentation
Interview formats
Technical Coding Behavioral Presentation

The interview process included an initial HR call, followed by a phone interview with engineers. Then there was an onsite coding interview with engineers and another onsite interview with upper management. Lastly, I had to complete a take-home coding project. It was inconvenient that the technical and upper management interviews were on different days, as they were initially scheduled for the same day but I was informed on the day of that it needed to be rescheduled, requiring me to take another day off work. While the process started well with prompt and helpful responses, this declined over time. A major letdown was the lack of feedback after three technical interviews: a phone screen, an in-person coding challenge, and a take-home challenge. I was rejected with a vague email stating I didn't align with the position's needs. My request for feedback yielded only a single, arbitrary piece of information. It's disappointing that after a month-long process, more substantial feedback wasn't provided.

Confirmed questions1 question
  • Could you solve an algorithm problem?
Neighborhoods.com logo
Neighborhoods.com

Software QA Engineer

Engineering

Mid Average Positive experience No offer 3 rounds
Interview process
Recruiter call Technical screen Offer
Interview formats
Behavioral Technical

I had a three round interview process. The first interview was a conversation with the QA lead. The second was a technical interview with the QA lead and SWE lead. The third was offer negotiation with the director. The experience was very positive. The conversation flowed naturally. They asked detailed and direct questions, many investigative and clarifying questions pointed to my resume. They were very transparent about the company's current needs and pain points. Unfortunately, I didn't make the cut. But I would have been extremely happy to work under such a great QA lead. He is very considerate and open minded. It felt like I was already a great team member and leader.

Confirmed questions1 question
  • Do you have experience with WordPress?

Neighborhoods.com Interview Questions

Quoted word for word from Neighborhoods.com interview reports.

What are the advantages of using an object compared to an array for data storage?

Read reports

What are the reasons for preferring Typescript over Javascript?

Read reports

Explain a linear model so a non-technical person can understand it.

Read report

Could you explain what a linear model is to someone without any technical knowledge?

Read report

Can you tell me what attracts you to Neighborhoods.com?

Read report

Formats, difficulty and experience

Across all 23 Neighborhoods.com interview reports.

Interview formats

Behavioral 41.2%
Technical 27.5%
Presentation 11.8%
Coding 9.8%
System Design 5.9%

Interview difficulty

Easy 17.4%
Average 82.6%
Difficult 0%

Candidate experience

Positive 78.3%
Negative 17.4%
Neutral 4.3%

Reports by job function

Engineering 9
Operations 4
Marketing 3
Analytics 2
Design 2
Other 2