Real, anonymous reports from people who interviewed for Software Engineer at Slack, newest first and distilled into what to expect across the loop.
I went through a mostly technical but fairly structured Slack Software Engineer process over a few weeks, with moderate difficulty.
I applied for a Slack Software Engineer role and found the process relatively smooth and even “cool,” with an easier overall feel.
The interview process typically begins with a recruiter screening call to discuss the candidate's background and alignment with the role, often followed by a hiring manager conversation that delves into experience and team fit.
Candidates generally face online assessments that include coding challenges, often in a HackerRank or LeetCode format, with varying difficulty levels that can significantly influence progression in the interview process.
A common component is a take-home code review task, where candidates are assessed on their ability to review and critique code, which may require clear communication of their thought process and suggestions.
The final interview loop often includes multiple technical interviews focusing on system design and coding problems, where candidates are expected to demonstrate problem-solving skills and project experience.
Behavioral interviews are a key part of the process, assessing candidates on past experiences and cultural fit within the team, often using the STAR method to structure responses.
Candidates noted varying experiences with communication throughout the process, with some reporting excellent guidance and feedback, while others faced issues with follow-up and clarity on next steps.
