Initial call with recruiter after submitting resume. It was a pleasant conversation.
I found him very technical for a recruiter. He seemed to be trying to get to know more about my background and distributed systems experience.
Since I was excited about the Elastic opportunity, I asked for a couple of weeks to prepare for the interview. I didn't get enough time to prepare, though, as I had a tough time at work and with family.
Series of interviews with engineers from Spain, France, and the US.
All of them were very humble, great engineers. They were core open-source contributors, and one of them was an Apache Software Foundation member.
Overall, it felt like a really engineering-driven organization. I enjoyed the conversations.
The last two rounds were with the Engineering Manager and VP of Engineering. Both were checking for cultural fit. I got to know more about the engineering culture and priorities for the organization. Finally, a compensation discussion with the recruiter, which lasted less than 20 minutes :)
Felt really good about the overall scheduling, given that I and the interviewers were in different time zones.
Distributed systems, system design, JVM
The following metrics were computed from 1 interview experience for the Elastic Cloud Engineer role in San Francisco, California.
Elastic's interview process for their Cloud Engineer roles in San Francisco, California is incredibly easy as the vast majority of engineers get an offer after going through it.
Candidates reported having very good feelings for Elastic's Cloud Engineer interview process in San Francisco, California.