Taro Logo

Cloud Engineer Interview Experience - United States

July 1, 2016
Negative ExperienceNo Offer

Process

I was really excited to apply to Elastic, having been interested in their products and using them for a while. This role seemed to line up well with my skills and experience, so I thought it would be enough to at least get an interview.

Initially, I got no response to my application, so I solved a few of their product issues on GitHub and reached out to a recruiter on LinkedIn, which was enough to get an initial conversation with a recruiter.

I then had a technical interview, in which I was asked about my programming language experience, among other things. The job description had mentioned "experience with languages X or Y" as being a requirement, and I had X. But this interview included a lot of questions about languages Y and Z (the latter was not even mentioned in the job posting).

Despite this, the conversation seemed to go pretty well. I heard the following week that they had gone with some others that had more experience. I never even reached the stage of answering technical or code questions, unfortunately.

If the job description had been more in-line with the questions I actually ended up being asked, I would have changed my preparation for the interview dramatically. Despite my enthusiasm for the company and its products, the interview process left a bad taste in my mouth.

Questions

What is your experience in using ElasticSearch?

Was this helpful?

Interview Statistics

The following metrics were computed from 4 interview experiences for the Elastic Cloud Engineer role in United States.

Success Rate

75%
Pass Rate

Elastic's interview process for their Cloud Engineer roles in the United States is incredibly easy as the vast majority of engineers get an offer after going through it.

Experience Rating

Positive75%
Neutral0%
Negative25%

Candidates reported having very good feelings for Elastic's Cloud Engineer interview process in United States.

Elastic Work Experiences