Taro Logo

Senior JavaScript Engineer Interview Experience - Remote, Oregon

May 1, 2019
Negative ExperienceNo Offer

Process

I applied in May and was contacted by a recruiter exactly a month later. Then I went through all the rounds:

  • An initial call with the recruiter.
  • A chat with two engineers (technical portion).
  • A chat with the tech lead for the team I was applying for.
  • Finally, a chat with two engineering directors, just about two full months after applying.

The process was long, and due to my interviewers being in various time zones, I had to move my schedule around a bit to accommodate and work my way through the process. I won't argue that I should have gotten an offer or that the process was unfair; just that it was slow and, in the end, I wasn't even notified if I was selected or not. I was essentially ghosted.

I find it frustrating that I can put so much effort into an interview process and not even receive a simple rejection email with some feedback.

Because the process was so long, I was able to work fully through the full interview process with several companies, and I found that Elastic was the worst with communication, which is a shame because I think it would be a pretty cool set of products to work on.

Questions

Here's a fake pull request. How would you review it?

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the Elastic Senior JavaScript Engineer role in Remote, Oregon.

Success Rate

0%
Pass Rate

Elastic's interview process for their Senior JavaScript Engineer roles in Remote, Oregon is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral0%
Negative100%

Candidates reported having very negative feelings for Elastic's Senior JavaScript Engineer interview process in Remote, Oregon.

Elastic Work Experiences