Overall, an OK process, albeit pretty time-consuming. It probably took about a month and a half in total to go through all the stages, and I initially applied five months ago.
There were no trick questions, brain teasers, or white-board-style questions. The questions were fairly representative of everyday work.
Here's a breakdown of the interview stages:
The team manager and team members were pleasant to speak with. The recruiter, on the other hand, was another story.
They use a third-party recruiting company, and it was fairly difficult to get ahold of the recruiter I was assigned to. They went on leave a few times, and I was not aware of it on some occasions. After I got my on-site confirmed, the recruiter was supposed to give me more information about the format and what I should do to prepare. My main recruiter did not reach out. I reached out on multiple occasions and got no response back, so I went in blind. Turns out the person covering for my recruiter was supposed to tell me to have a development environment set up in advance. I didn't know this, so during my on-site, I scrambled and probably appeared very unprepared.
Despite all the time spent, I did not hear back about my rejection until I emailed them to ask.
Talk about past projects.
Talk about tech used in projects.
System design.
Pair-programming.
Behavioral/teamwork questions.
The following metrics were computed from 2 interview experiences for the Slack Software Engineer role in Vancouver, British Columbia.
Slack's interview process for their Software Engineer roles in Vancouver, British Columbia is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Slack's Software Engineer interview process in Vancouver, British Columbia.