Interview process review
I went through two rounds of interviews for this position:
HR interview (30 mins): This was a general discussion with basic HR questions and two simple technical questions, such as "How do you list files in Linux?" The conversation was smooth, and overall, it was a positive experience.
Technical interview (1 hour): This interview consisted of standard technical questions that felt very pre-prepared. Some of the questions included:
The difference between HTTP and HTTPS. The difference between SQL and NoSQL databases. For the final part, the interviewer asked me to solve a coding problem on LeetCode while they observed my process. The task felt unrelated to real-world applications, especially given the role I was applying for.
While I understand that coding assessments are part of technical evaluations, this approach seemed a bit outdated for this particular position. I provided detailed feedback to the HR representative afterward, hoping it would help refine their process for future candidates. However, the response I received was disappointing—it felt dismissive, implying that I needed to be "more capable" as a developer.
This was surprising, as the role I applied for wasn't even a developer position. I had hoped my feedback would lead to improvements in their candidate experience, particularly around making the process more aligned with real-world scenarios.
The following metrics were computed from 1 interview experience for the Sanctuary AI DevOps Engineer role in Vancouver, Canada.
Sanctuary AI's interview process for their DevOps Engineer roles in Vancouver, Canada is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Sanctuary AI's DevOps Engineer interview process in Vancouver, Canada.