The recruiter reached out and was very positive, coaching me well. I met with my would-be direct manager and had great rapport and more positive vibes. The next level was the technical interview. This is where the process fell apart.
I feel that the person who interviewed me had specific knowledge of one area and kept going there. I was able to talk about everything he asked at various levels of detail. I was under the impression that this role was not "that technical" and felt that the customer-facing and consulting aspect was more important, which I felt like I nailed. He asked questions that seemed open-ended but obviously, he wanted more specific answers. I was coached to ask at the end how I did and if I could do the job. I got a positive response, basically an acknowledgement that I could do the job. Then, a few days later, I got an email saying "no thanks." I emailed the hiring manager to thank him for the opportunity and never got a response.
I don't feel like the technical interview was a fair assessment and is very arbitrary for filtering talent.
Explain to me how you would design a web site. What components are needed, etc.
Explain cloud to me.
The following metrics were computed from 1 interview experience for the Elastic Solutions Architect role in Denver, Colorado.
Elastic's interview process for their Solutions Architect roles in Denver, Colorado is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Elastic's Solutions Architect interview process in Denver, Colorado.