
Slack Data Scientist Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 7 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Slack.
Data Scientist
I had a take-home assignment that was a pretty straightforward SQL task, but the data felt real, and they wanted to see if I could clean it too. After that, I had a phone interview with the data science manager, which was mostly about culture fit. Then, for the on-site, it was about 4 interviews, covering stats, product sense, culture, and coding.
- Can you explain the difference in measuring uncertainty for click-through rates versus measuring clicks per person?
Data Scientist
The interview journey kicked off with two phone chats with the hiring manager. The first call was about my background and the role itself, and the second was a quick technical check. After that, I had a take-home assignment. Mine was pretty open-ended, more of a conceptual challenge, and I put about 6 hours into it. Then came the on-site. A cool part of the Slack interview process is that the on-site starts with a presentation to the hiring team about the take-home exercise, which sets a good vibe for the day. However, the rest of the on-site was rough. It went for nearly six hours straight, with absolutely no breaks between interviews to even rest or prep for the next chat. The only unscheduled pause I got was when the hiring manager was 15 minutes late, leaving me only 15 minutes for lunch, which was also technically an interview, so I couldn't really enjoy the food they gave me. It's obvious the quality of the afternoon discussions took a big hit because of this. Interviewers who weren't in leadership roles seemed more interested in talking about their own specific projects than evaluating me for the actual job.
No confirmed questions were included in this interview report.
Data Scientist
I applied for Data Science Manager but ended up interviewing for a Data Scientist role, and they were unclear why. The take-home test was pretty basic but could be a bit open-ended, so one could spend more than the suggested 3 hours on it. The onsite interviews were a bit of a mixed bag. The technical coding part was solid, and the interviewer was really helpful and put me at ease. However, the case study interview was a bit of a disaster; the interviewer didn't give good direction on what they were looking for, and I struggled to understand the requirements. Ironically, that's the interview they flagged as not going well, while the others were fine. Overall, the office vibe was great, and it seems like a really hot company to join right now, especially with their upcoming IPO. But, I wasn't overly impressed by the people I met or the tech stack they described.
- How would you write SQL to achieve a specific output, and then how would you use Python or pseudo code to do the exact same thing?
- Technical coding questions were asked.
- A case study interview was conducted.
Slack Data Scientist Interview Questions
Quoted word for word from Slack interview reports.
“Can you explain the difference in measuring uncertainty for click-through rates versus measuring clicks per person?”
Read reports →“How would you write SQL to achieve a specific output, and then how would you use Python or pseudo code to do the exact same thing?”
Read reports →“Regarding international expansion for Slack, how would you decide which country to prioritize?”
Read reports →“How would you measure the success of a specific Slack feature using the provided dataset? Assume nothing and verify everything.”
Read reports →“Tell me about a challenge you encountered in the last year and the steps you took to overcome it.”
Read report →Formats, difficulty and experience
Across all 7 Slack interview reports.