Neo4j Interview Questions
& Process

The Neo4j interview process was quite lengthy, extending over two months and involving five interviews, and still had two more steps left. It felt like Neo4j didn't really consider how much time candidates invest in the process. The recruiter even sent emails on weekends and late at night, which, while not personally bothersome, suggested a company culture that might not prioritize work-life balance. There were also last-minute interview reschedules. The most frustrating part was after the fifth interview, I was told I'd proceed, then heard nothing for a week, only to receive an email stating the hiring team had a change of heart and I wasn't moving forward. This kind of poor candidate experience often mirrors the employee experience.

The interview process started with a recruiter call, then I spoke with the Team Lead about my experience and familiarity with graph databases and related tech. I was then given a week to complete a take-home assignment using any tech stack I wanted. After that, there was a session to discuss the solution and do some live coding to add features. The final rounds included behavioral interviews with the Hiring Manager and the VP of HR. The whole process felt very focused and purposeful. The team was clear about the day-to-day responsibilities and expectations, which was helpful. Sam from talent acquisition was supportive throughout. My first application didn't work out, but Sam stayed in touch and later connected me with this opportunity. He also explained what to expect in each round and gave quick feedback. I felt encouraged and supported. The company seems to have a great culture.

The interview process was quite standard. It started with HR, then a chat with the Hiring Manager, and concluded with a Pair Programming session. The Hiring Manager seemed to be the most knowledgeable person on the team and was upfront about their current progress. Heads up, the pair programming interview isn't typical; instead of guiding you through a solution, they tend to ask pre-planned questions designed to intentionally confuse you. This part also includes questions about SLIs and SLOs. It appears the interviewers have limited hands-on experience with implementing SLOs at Neo4j currently, as it's a developing area for them. Yet, they seemed confident in evaluating candidates with more real-world implementation experience. Real-world scenarios don't always align with textbook knowledge from sources like Google's SRE book. When asked about their experience setting up SLOs, they admitted to having none. So, don't be surprised if your practical experience is questioned by a team that hasn't yet built an SLO from scratch.

I had a nice, relaxed first call with the recruiter. Then, a second call with the hiring manager, who was friendly but also appropriately more technical. They kept me in the loop about what to expect, so no surprises. The recruiter was upfront about other candidates being further along and didn't want me to waste time on a third-round technical test that might end up being irrelevant. I found out a few weeks later that I didn't get the job, but I really appreciated them respecting my time.