Slack Senior Software Engineer Interview Questions

1.Think about a recent design review or sprint planning meeting. Was there someone in the room who wasn't speaking up much? What did you do, and how did it change what the team built?

2.Tell me about a code review comment you wrote that you're genuinely proud of — one that was technically sharp AND landed well with the author. What did you actually write, and how did it change the PR?

3.Tell me about a time a customer complaint or support ticket made you stop and rethink something you'd already shipped. What did you actually change, and how did you decide where to draw the line on scope?

4.Walk me through a real technical disagreement you had with a partner team — not just a different opinion, but something that actually blocked or slowed your team's work. How did it end, and what would you do differently?

5.Tell me about a time you explicitly changed the structure of a meeting or planning process to make sure someone from a different discipline — a designer, a PM, a data analyst — had a real say in a technical decision. What did you change, and did it actually work?

6.Describe a code review where you caught something that the author, their tech lead, and automated CI all missed. How did you approach giving that feedback, and what happened after you raised it?

7.Slack's real-time messaging server needs to deliver a message to thousands of connected clients simultaneously. How would you think about the data flow from the moment a user hits send to the moment their colleagues see it appear?

8.You're reviewing a Go service and you notice it's making a synchronous database call inside a per-message hot path that runs tens of thousands of times per minute. The author says it's fine because the query is fast. What's your reaction, and how would you actually verify it?

9.Slack's workspace data is stored in sharded MySQL, sharded by workspace ID. A PM wants to build a feature that lets enterprise admins see a real-time dashboard of message activity aggregated across all their workspaces. How would you approach this, and what would you push back on?

10.You're building a new feature behind a feature flag in Slack's CI/CD pipeline, and you're about to ramp it from 1% to 50% of workspaces. What's your checklist before you move that dial, and what are you watching in the first 30 minutes after?

11.Slack Workflow Builder lets non-technical users define multi-step automations that can call external webhooks, post messages, and update records. Walk me through how you'd architect the execution engine for these workflows, with a focus on reliability and observability.

12.We're seeing intermittent message ordering violations in a high-traffic channel — messages that were sent sequentially by a single user occasionally appear out of order on some clients. Describe how you'd investigate this end-to-end and what architectural causes you'd look for.

13.Slack Connect lets two companies share a channel. How would you design the permission and visibility model so that when a user is removed from one org's workspace, they immediately lose access to the shared channel — even mid-session?

14.Design a presence system for Slack — the indicator that shows whether someone is active, away, or do-not-disturb. It needs to update in near-real-time across all of a user's open clients and their teammates' clients.

15.Design the search indexing pipeline for Slack messages. A message sent right now should be searchable within a few seconds, and the system has to handle both high write volume and retroactive index updates when a message is edited or deleted.

16.Slack Huddles are spontaneous audio calls that can start inside any channel or DM. Design the signaling layer that lets a user join an active Huddle and immediately hear the other participants — with join latency under 2 seconds.

17.Design Slack's push notification delivery system. A message sent in a channel should reach a recipient's mobile lock screen within 1-2 seconds, reliably, even when the recipient has Slack installed on three different devices.

18.Design the data model and sync protocol for Slack's unread state — the bold channel names, unread dots, and mention badges that tell a user exactly what needs their attention. It has to be consistent across a user's desktop, mobile, and web clients in real time.

19.Tell me about a time you had to convince a more senior engineer to change course on something they'd already committed to publicly. How did you approach it, and what happened?

20.Describe a time you stepped in to support a teammate who was visibly struggling — not just with a technical problem, but with workload, morale, or pace. What did you actually do?

21.Tell me about a time you owned a feature end-to-end alongside a PM and designer — and something they cared deeply about conflicted with what you thought was the right technical approach. How did you resolve it?

22.Have you ever shipped something you were proud of technically, but then watched users struggle with it? What did you do, and what did it change about how you work?

23.Tell me about a time you identified that your team's engineering practices — testing, code review process, deployment workflow, anything — were quietly creating problems, and you led the effort to fix them. What resistance did you hit, and how did you sustain momentum?

24.Describe a time when two teams you depended on were pulling your project in incompatible directions — different API contracts, conflicting priorities, or irreconcilable timelines. You didn't own either team. How did you get to a shared path forward?

25.Estimate how many messages Slack delivers per second on a typical weekday versus a weekend. Walk me through your reasoning.

26.Slack's 7-day retention rate for new free workspaces just dropped 3 points. What's the first thing you rule out, and how do you structure the investigation?

27.Slack Connect lets enterprises share channels with external partners. Estimate the incremental infrastructure cost of doubling the number of active Slack Connect channels over the next year.

28.Slack's typing indicator — the 'someone is typing' animation — is showing stale state for some users: it keeps spinning even after the message was sent. Walk me through how you'd diagnose and fix this.

29.Estimate how much latency Slack's message delivery adds end-to-end when the sender and all recipients are in the same AWS region versus when they're in different regions. What are the dominant terms?

30.Slack's search team tells you that message search relevance has degraded noticeably for large enterprise workspaces — their users are complaining that recent messages from active channels rank below old, rarely-accessed content. How would you approach re-ranking without a full index rebuild?