Had a phone screen with a recruiter based in San Francisco.
It was a general chat, and I was given an idea of the upcoming interview process.
I was then given a take-home challenge via email, to work on over the next week. There was a lot of room in the challenge to put as much effort as I wanted and make it as feature-rich as I desired. I found the challenge to be a lot of fun.
Next, I had a 45-minute chat with the Hiring Manager via video.
I was invited on-site for a morning of interviews with a variety of people.
The on-site interviews were pretty standard, with a few key differences. I met with two people based in San Francisco via video chat, then two local people, followed by the Hiring Manager. All of these interactions seemed very friendly and almost laid-back. There was no quizzing of technical details or whiteboard coding challenges. It was mostly casual chats about architecture (and how to improve it), incidents (and how they are handled), employment history, team-based questions, and a few other topics.
All in all, I felt really good about the interview process and found it to be much better than the 'standard' procedure.
Diagram the architecture you're responsible for.
The following metrics were computed from 1 interview experience for the Slack Operations Engineer role in Melbourne, Australia.
Slack's interview process for their Operations Engineer roles in Melbourne, Australia is incredibly easy as the vast majority of engineers get an offer after going through it.
Candidates reported having very good feelings for Slack's Operations Engineer interview process in Melbourne, Australia.