Applied online. A couple of days later, I got an email from a recruiter asking to schedule a brief phone interview. I scheduled it for the next available time, which was two weeks later.
On the day of the phone screen, I received a call from the recruiter from a private number, a minute behind schedule. I answered, and the person on the other end of the line quickly asked if I had time for the interview, as if they were in a rush.
Of course, I had time, and they asked me to tell them about some of the work I'd done. I started going into details about my work, and it was just silent on the other end of the line. Well, actually, it sounded like this person was in a call center, and the connection was really crummy, but the recruiter didn't seem interested at all.
After that, they asked me, "Why Slack?" and told me that the interview process after this involved a brief chat with the hiring manager and then a technical challenge that was due a week after it was given. After that, if they liked you, they would fly you out to do more interviews.
Unfortunately, I received an email a day later saying that I wasn't moving forward.
Overall, it wasn't a bad experience, but it didn't really seem personal, or like they cared, which was surprising.
Why Slack?
The following metrics were computed from 2 interview experiences for the Slack Applications Engineer role in United States.
Slack's interview process for their Applications Engineer roles in the United States is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for Slack's Applications Engineer interview process in United States.