Candidates report Slack software engineer interviews that mix a recruiter screen, a take-home or build exercise, and a final loop with system design, coding and behavioral rounds. Formats varied between reports.
$193K
Avg. Base Comp
$240K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Slack software engineer candidates describe a process that leans practical. Two of the four reports mention a take-home code review of an example or buggy codebase. One candidate had 24 hours and was asked to reason about debugging a service that starts delaying responses. Another had four hours to review a feature in an example app, and felt the exercise tested both technical depth and how clearly they communicated feedback.
The final stage differed between reports. One candidate described a loop with system design, a coding round and two behavioral interviews. The coding round meant downloading a Slack-like chat app with a SQLite database and adding a feature such as private channels. Another reported a mini-app build, then a virtual onsite with four interviews, two of them system design. A third reported three virtual interviews covering collaboration, feature scoping and implementation, and language fundamentals, followed by team matching.
System design prompts were open-ended and product-flavored. Reports mention autocomplete, a system that ingests Slack message commands and calls third-party APIs, a mapping system, and an API for user search suggestions. Practice asking clarifying questions and talking through tradeoffs aloud. One front-end candidate was surprised by system design and web animation questions in a first interview described as a conversation about past work, so ask your recruiter what each round will cover.
Outcomes in these reports were mixed: one offer and three no-offers. One candidate was left without a result after the final loop despite following up twice, so keep your own notes on timing and next steps.
Synthesized from 4 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Slack process.
The process was fairly structured and started with a recruiter screening, which felt pretty standard and mostly covered my background and interest in Slack. After that I had a chat with a staff engineer, and then a technical challenge where I had to build a mini-app. That was probably the most hands-on part of the process and felt more practical than a pure algorithm exercise. The final stage was a virtual onsite with four separate interviews with the team, and two of those were system design rounds. One of the design prompts I got was how I would design a mapping system, so it was less about memorizing a template and more about thinking through product and architecture tradeoffs in real time.
The behavioral side was also present throughout, not just at the end. In the earlier conversations I was asked why I wanted to work at Slack, so it was clear they cared about motivation and fit as much as technical depth. Overall, the process felt fairly demanding because it combined a build exercise, multiple team interviews, and repeated system design discussions. I didn’t get an offer, but the interviews were professional and the expectations were clear. If you’re preparing, I’d focus on being able to talk through a product-oriented mini-app build and on practicing system design in a way that explains your reasoning, especially for open-ended prompts like mapping or similar infrastructure problems.
Prep tip from this candidate
Be ready for a hands-on mini-app build, not just coding questions, and practice explaining your approach in system design rounds where the prompt is open-ended, like designing a mapping system.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Slack
How would you investigate a SQL query suddenly running much slower than usual?
| Question | |
|---|---|
| Facebook Autocomplete | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Prime to N | |
| Top 3 Users | |
| Random SQL Sample | |
| String Shift | |
| Comments Histogram | |
| Largest Salary by Department | |
| Upsell Transactions | |
| Raining in Seattle | |
| Minimum Change | |
| Customer Orders | |
| Find the Missing Number | |
| Bagging vs Boosting | |
| Find the First Non-Repeating Character in a String | |
| Size of Joins | |
| Scrambled Tickets | |
| Weighted Keys | |
| The Brackets Problem | |
| Flight Records | |
| Rectangle Overlap | |
| P-value to a Layman |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial recruiter conversation about their background and interest in Slack. One candidate was asked why they wanted to work there. A front-end candidate found it rapid-fire, so prepare a concise story and questions of your own.
Reports describe a manager or staff engineer call after the recruiter screen. Content varied: behavioral questions, high-level design such as autocomplete, and, for one front-end candidate, system design, web animations and debugging performance issues. Confirm the focus with your recruiter.
Candidates report a practical exercise rather than a pure algorithm test. Formats included a timed code review of an example or buggy codebase (4 to 24 hours reported) and a mini-app build. Expect to explain your reasoning and give constructive feedback, and ask about scope if the prompt is ambiguous.
Candidates report a final loop of three to four interviews. Reported content included system design, a feature added to a Slack-like chat app codebase, behavioral rounds, collaboration, feature scoping and language fundamentals. Loops may vary by level and team.
One offer-receiving candidate reported team matching with hiring managers after passing the onsite. Others reported no offer, and one was left without a response after following up twice. Timing and communication may vary.
