Initial recruiter screen: probed a bit more than a typical recruiter screen. Asked me about five different times why I wanted to work for Slack, which I found strange. It felt like they were scoping for a "right" answer.
The recruiter said they would share my resume with hiring managers to see if there was interest. As the recruiter was internal (not third-party), I don't understand why this couldn't have been the first step in the process before potentially wasting both our time.
Phone screen with engineering manager: talked about past projects, soft technical questions, and why I want to work for Slack (again).
Homework assignment: reviewed some code with mistakes and left feedback. Left a bunch of comments, which took about two hours (I spent about an hour reading about best practices for things I was ambiguous about). Got rejected after a couple of days with no feedback.
Homework assignment
The following metrics were computed from 12 interview experiences for the Slack Software Engineer role in San Francisco, California.
Slack's interview process for their Software Engineer roles in San Francisco, California is very selective, failing most engineers who go through it.
Candidates reported having very negative feelings for Slack's Software Engineer interview process in San Francisco, California.

