Elastic logo

Elastic Cloud Engineer Interview Questions
& Process

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

Based on 5 interview experiences · FREE TO READ

5.4 Rounds average
Average Typical difficulty
80% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Elastic.

Showing 3 of 5
Elastic logo
Elastic

Cloud Engineer

Engineering · more than a year ago

Mid Average Positive experience Accept offer 6 rounds
Interview process
Recruiter call Technical screen Technical screen Technical screen Onsite Onsite Onsite Background check Offer
Interview formats
Behavioral Technical Coding System Design

The interview process kicked off with a recruiter screening. After that, there were 6 interviews in total: the first three were with technical folks, and the last three were with management. All interviews were done over Zoom. Technical interviews covered my background, coding discussions, some coding exercises (like dealing with HTTP requests and data sorting/filtering/grouping), and system design questions. Management interviews were mostly behavioral, though one got pretty technical. They really focused on cultural fit, which makes sense for a distributed company like Elastic. The whole thing took about 6 weeks. I felt the process was fair and aimed at finding engineers who can solve real problems, not just ace algorithm tests. My main gripes are the length of the process and that pay wasn't discussed until the very end.

Confirmed questions2 questions
  • Using a programming language of your choice, process data fetched via curl commands by filtering, grouping, and sorting it in various ways.
  • Describe how you would design and build a web service intended for high-volume traffic.
Elastic logo
Elastic

Cloud Engineer

Engineering · more than a year ago

Entry Average Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Technical

I was super keen to apply to Elastic because I've been a fan and user of their products for a while, and this role seemed to be a perfect match for my background. I figured it would be enough to at least land an interview. Initially, my application got no reply, so I ended up fixing some of their product issues on GitHub and then pinged a recruiter on LinkedIn. That got me an initial chat with a recruiter. After that, I had a technical interview where they asked about my programming language skills, among other things. The job posting mentioned 'experience with languages X or Y' as a must-have, and I had X. However, the interview heavily focused on languages Y and Z (which wasn't even mentioned in the job posting!). Even so, the conversation felt pretty good. The following week, I heard they went with other candidates who had more experience. Unfortunately, I didn't even get to the point of answering technical or coding questions. If the job description had actually reflected the questions they asked, I would have prepared very differently. Despite my excitement for the company and its offerings, the interview process left a sour taste.

Confirmed questions1 question
  • Could you describe your experience with ElasticSearch?
Elastic logo
Elastic

Cloud Engineer

Engineering

Mid Difficult Positive experience Accept offer 5 rounds
Interview process
Recruiter call Technical screen Onsite Background check Offer
Interview formats
Behavioral Technical

After sending my resume, I had an initial chat with a recruiter. It was a good conversation, and I thought they were quite technical for a recruiter, asking about my background and distributed systems experience. I requested a couple of weeks to prep for the interviews, but work and family stuff made it tough. Then, I went through several interviews with engineers from Spain, France, and the US. They were all humble and great engineers, some even core open-source contributors and one was an Apache Software Foundation member. It really felt like an engineering-focused company, and I enjoyed the talks. The last two interviews were with the Engineering Manager and VP of Engineering, focusing on cultural fit and learning about the engineering culture and priorities. Lastly, a quick compensation discussion with the recruiter, under 20 minutes. The scheduling worked out really well despite the different time zones.

Confirmed questions3 questions
  • Can you discuss your experience with distributed systems?
  • What are your thoughts on system design?
  • Could you elaborate on the JVM?

Elastic Cloud Engineer Interview Questions

Quoted word for word from Elastic interview reports.

Describe how you would design and build a web service intended for high-volume traffic.

Read reports

What challenges do you foresee in collaborating with a team spread across the globe?

Read reports

Could you describe your experience with ElasticSearch?

Read report

Can you discuss your experience with distributed systems?

Read report

Tell me about your past experience with distributed systems.

Read report

Formats, difficulty and experience

Across all 5 Elastic interview reports.

Interview formats

Technical 41.7%
Behavioral 33.3%
Presentation 8.3%
Coding 8.3%
System Design 8.3%

Interview difficulty

Easy 0%
Average 60%
Difficult 40%

Candidate experience

Positive 80%
Negative 20%