Cloud - Cloud Engineer Interview Experience - Remote, Oregon
Process
Initial contact was from the recruiting team, who were very communicative through the interview process.
Following an HR screen, the interviews consisted of four one-hour-long technical interviews, which were largely discussion-based, and three half-hour-long executive interviews.
This provided ample opportunity to meet and interact with the team throughout the process.
Questions
What do you think would be challenging about working on a globally distributed team?
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the Elastic Cloud - Cloud Engineer role in Remote, Oregon.
Success Rate
Elastic's interview process for their Cloud - Cloud Engineer roles in Remote, Oregon is incredibly easy as the vast majority of engineers get an offer after going through it.
Experience Rating
Candidates reported having very good feelings for Elastic's Cloud - Cloud Engineer interview process in Remote, Oregon.
Elastic Work Experiences
- 5.0World-class distributed work environmentPrincipal Software Engineer • Current EmployeeFebruary 2, 2021Pros: Great culture, leadership, and freedom of work.Cons: Timezones suck. So does it not being able to see your co-workers beyond a Zoom call.
- 5.0Supportive, Flexible, But DistributedEducation Engineer • Current EmployeeDenver, Colorado, United StatesJuly 7, 2017Pros: Super environment to work in - flexible, supportive.Cons: Highly distributed - it's also a benefit. But with spread-out employees comes challenges to keep us all communicating. Elastic does a great job of addressing this.
- 4.0A great company that truly cares about its employeesSoftware Engineer III • Former EmployeeNew York, New York, United StatesAugust 2, 2021Pros: - Great benefits - Space Time (a week of hacking/improving your domain) - Volunteering time - Competitive compensation - 2x a year company/team outings - Fully distributed/remote - Make your own scheduleCons: This is all subjective and is based on my own unique situation/experience. * Management/Leads sometimes pressure the release of new features instead of fixing/maintaining existing code/bugs/features. * The measurement of your performance is heavily tied to the amount of pull requests and activity shown on your GitHub profile. * You will have to do a lot of customer support as a software engineer. Probably around 70% of my time went into SDHs.
