Elastic Software Engineer Interview Questions
& Process

The interview process began well, with early conversations focusing on cultural alignment and long-term project involvement. Things shifted during the technical phase. In this technical session, it was actually encouraged to use AI to speed up iteration, emphasizing the 'what' and 'why' over the 'how.' I followed this advice in the sandbox exercise, focusing on modern problem-solving. However, despite adhering to these guidelines and earlier assurances, I was ultimately rejected for not having enough React knowledge. No specific technical details or feedback were given. It's confusing to be told to prioritize 'problem-solving speed' and then get filtered out for lacking specific framework syntax or recall. I finished the exercise with nearly 10 minutes to spare. My advice to candidates: be cautious. You might hear that architecture and adaptability are valued and that not knowing the specific tech stack is acceptable, but you could still be screened out by a rigid 'framework-first' approach that clashes with leadership's stated philosophy. If you're not an expert in the 'trendy' frameworks, your skills might not be valued here, which makes me question the claim of 'total freedom to propose and implement changes.' My advice to the company: ensure your interviewers are on the same page. If your engineers publicly advocate for AI and high-level design, your final hiring criteria shouldn't default to a basic syntax check. Rejecting a candidate for a reason they were explicitly told wouldn't be an issue, especially when they deliver the solution early, is a waste of everyone's time and harms your company's image.

I was contacted by a recruiter about an open position in Elastic's Spanish office. The first step was an HR interview, followed by a hiring manager interview. It seemed okay, but things got weird afterward. They said feedback would come within the week (the HM interview was on Monday). No feedback came, so on Friday, I pinged the recruiter on email and LinkedIn, and they didn't reply. The next week, I emailed the hiring manager asking for feedback, positive or negative, but still no answer. So, basically, Elastic's recruiting process is a masterclass in ghosting. I'd really recommend not wasting your time with this company, but hey, maybe you'll have better luck :)

The interview process involves three main interviews, not counting the initial HR chat. Each of these interviews has two interviewers, which is a great way to cut down on bias. The interviewers really know their stuff, not just technically but also how to interview well. They look at more than just whether you know a specific library; they're assessing broader things. For me, this was one of the best interview experiences I've had, no matter how it turns out. You can tell the company's values are a big part of how they interview.