Intervu is in beta — feedback welcome at support@intervu.io

Slack Staff Software Engineer Interview Questions

26 real practice questions for the lead-level Staff Software Engineer role at Slack (Communications / Productivity), spanning behavioral, technical, system design, leadership, and problem solving. Drive technical strategy, architect complex systems, and provide cross-team technical leadership. The first 3 questions below include what Slack interviewers actually listen for, plus likely follow-ups.

Practice these questions with AI feedback
Questions
26
Categories
Behavioral (6), Technical (6), System Design (2), Leadership (6), Problem Solving (6)
Difficulty mix
10 easy · 8 medium · 8 hard
Avg. answer time
~4 min

Behavioral Questions (6)

  1. 1.Tell me about a time you noticed a teammate who had relevant expertise but wasn't speaking up in a design discussion. How did you bring them in, and what changed because of it?

    easy~3 min

    What interviewers look for

    • Candidate identified a specific person who was quiet for a reason — introversion, seniority gap, async-remote dynamic, or domain intimidation — rather than just generically 'invited everyone to share'
    • The outcome was meaningfully different: the design changed, a risk was caught, or the teammate's subsequent engagement improved — showing that inclusion produced a better result, not just a warmer feeling
    • Candidate took a deliberate, considerate action: a direct async message, a named question in the meeting, a pre-meeting 1:1, or amplifying the person's earlier comment — demonstrating Slack's value of Courtesy in practice
    • Candidate reflects on what they learned about creating psychological safety and carries that practice into how they run recurring forums like RFC reviews or architecture syncs

    Likely follow-ups

    • How did you make sure that person's idea got credit in the final design doc or RFC, rather than getting absorbed into the group?
    • If the same person stayed quiet even after you tried to bring them in, what would you do next?
    • How has that experience shaped how you structure design reviews or async threads on your current team?

    Company context

    Slack's engineering culture explicitly values Inclusive Collaboration and Solidarity — the expectation that engineers lift teammates up rather than optimize for individual visibility. At the Staff level, Slack interviewers probe whether candidates actively create space for quieter voices in design reviews, RFC discussions, and code review threads, not just in retrospectives. Given Slack's async-first, remote-distributed team structure, the barrier to participation is real: an engineer who doesn't speak English as a first language, who is junior relative to the room, or who is in a misaligned time zone can easily be silenced. A Staff engineer at Slack is expected to notice and counteract that dynamic deliberately.

  2. 2.Tell me about a time you received code review feedback that you initially thought was wrong or overly nitpicky, but it changed how you write code going forward. What was the feedback, and why did it stick?

    easy~3 min

    What interviewers look for

    • Candidate can quote or closely paraphrase the actual feedback — not just summarize its category — showing they internalized it specifically rather than abstractly
    • Something caused the candidate to genuinely update their view — re-reading the feedback later, hitting the exact problem the reviewer predicted, or a subsequent conversation that gave them the reasoning behind the comment — not just social deference to a senior engineer
    • Candidate was initially resistant or dismissive, and can explain why: the feedback felt like a style preference, the reviewer seemed junior, the suggestion added complexity, or the candidate was under deadline pressure — showing self-awareness about their reaction
    • The change in practice is observable: the candidate now writes comments differently, structures error handling differently, names variables differently, or reviews for the same issue in others' code — demonstrating Craftsmanship as a compounding practice, not a moment
    • Candidate reflects on how the experience changed their relationship with code review as a growth tool, and how they now respond to feedback they disagree with in the moment

    Likely follow-ups

    • When you get feedback you think is wrong today, what's your default first move — push back in the PR thread, ask a clarifying question, or sit with it first?
    • Have you ever passed that same feedback on in a review of someone else's code? How did you frame it?
    • Is there feedback you still think was wrong even now, looking back? What do you do with that?

    Company context

    Slack treats code review as a first-class cultural artifact — the PR review task is the centerpiece of Slack's technical hiring process, and Code Review with Care is a named leadership principle. The implicit expectation is that engineers at Slack see review feedback as a learning mechanism, not just a gatekeeping step, and that they engage with feedback thoughtfully rather than defensively or deferentially. This question probes intellectual humility and the Craftsmanship value: the willingness to update your practices based on someone else's careful observation, even when your instinct is to dismiss it.

  3. 3.Walk me through a code review where you gave feedback that the author pushed back on hard. How did you handle it, and how did it resolve?

    medium~4 min

    What interviewers look for

    • Candidate gave feedback that was technically substantive — not just style nits — and can articulate exactly what the concern was: a correctness issue, a scalability risk, an abstraction boundary violation, a race condition, etc.
    • Candidate's feedback was written with Courtesy: specific, non-personal, explanation of reasoning not just assertion of opinion, and possibly included a suggested alternative or a question rather than a demand
    • When the author pushed back, the candidate engaged with the argument rather than deferring to seniority or digging in on ego — demonstrating Resolve Conflict Productively in the code review context
    • Resolution showed either the candidate updated their view based on new information (intellectual honesty) or the author agreed to a third path neither had initially proposed (collaborative problem-solving)
    • Candidate reflects on how the exchange improved their own approach to giving feedback — tone, framing, asking questions vs. stating conclusions

    Likely follow-ups

    • What did you actually write in the review comment? Walk me through the phrasing you used.
    • If this were a Slack PR review task and you had to model good feedback for an intern observing, what would you have done differently in how you framed it?
    • Was there a moment where you considered just approving to avoid the friction? What kept you from doing that?

    Company context

    Slack's hiring process famously uses a PR review task as the core technical assessment — candidates are evaluated not just on whether they catch technical issues but on the quality, tone, and constructiveness of the feedback they write. Code Review with Care is a named leadership principle at Slack: reviews should be technically sharp, respectful, and growth-oriented for the author. At the Staff level, the bar is higher: candidates should be modeling review culture for junior engineers and should be able to hold a technically difficult position while keeping the relationship intact. This question surfaces whether a candidate lives that principle under pressure.

  4. 4.Tell me about a time a piece of direct customer feedback — a support ticket, a user interview, a NPS comment — changed what your team built or how you prioritized it. What was the signal, and what did you do with it?

    medium~4 min

  5. 5.Describe a significant technical disagreement you had with a partner team — not your own team — where you were both convinced you were right. How did you break the impasse?

    hard~5 min

  6. 6.Tell me about a time you deliberately created space for a junior engineer or a new teammate to own something in a design or technical decision, even when you could have driven it yourself faster. What did you give up, and what did they produce?

    hard~5 min

Technical Questions (6)

  1. 7.Slack's real-time messaging server needs to fan out a single message to thousands of connected clients in a channel. How does that delivery architecture work at a high level, and where would you expect the bottlenecks to be?

    easy~3 min

  2. 8.Slack's MySQL data is sharded by workspace ID. A new feature request comes in that needs to aggregate message activity across all workspaces in real time. How do you think about this architecturally?

    easy~3 min

  3. 9.You're on-call and your observability dashboards show P99 latency on the message send API jumping from 40ms to 400ms. No deploys happened in the last six hours. Walk me through your investigation.

    medium~4 min

  4. 10.Slack Workflow Builder lets non-developers automate multi-step processes across integrations. How would you design the execution engine for workflows that include external HTTP calls, conditional branches, and retry logic — and what failure modes keep you up at night?

    medium~5 min

  5. 11.Slack Connect lets two companies share a channel, meaning messages from Company A's workspace are visible in Company B's workspace. Walk me through the data model and access control challenges this creates at the storage layer.

    hard~5 min

  6. 12.You're designing the rollout strategy for a change to how Slack's Electron desktop client handles message rendering — it affects every user on every platform simultaneously. The change improves performance but has a known visual regression on a rare edge case. How do you ship this?

    hard~5 min

System Design Questions (2)

  1. 13.Slack Huddles need to show a live 'who's listening' presence indicator — avatars that appear and disappear in real time as people join and leave. How would you design that presence layer?

    easy~3 min

  2. 14.Walk me through how you'd design the search index that powers Slack's message search — specifically, how you'd keep search results fresh within seconds of a message being sent in a large, active workspace.

    easy~4 min

Leadership Questions (6)

  1. 15.Think about a time you had to convince a PM or designer to slow down a feature because of a technical risk they didn't fully see. How did you make the case, and how did it land?

    easy~3 min

  2. 16.Tell me about a time you spotted a gap in your team's on-call health — toil, alert fatigue, a rotation that was burning people out — and actually fixed it. What did you change and how long did it take to stick?

    easy~4 min

  3. 17.Describe a time you inherited or stepped into ownership of a system that had no clear owner — the kind of thing where everyone assumed someone else was responsible. How did you establish ownership without being asked to, and what did you actually do with it?

    medium~4 min

  4. 18.Tell me about a time you drove adoption of a new engineering practice or standard across teams — not just your own team. What was the practice, how did you actually get people to change, and where did you hit resistance?

    medium~5 min

  5. 19.Walk me through a time you had to make and defend a major architectural decision while knowing you'd take the blame if it went wrong and the team would share credit if it went right. How did you stay in that position and keep the team behind you?

    hard~5 min

  6. 20.Tell me about a time the product you built or shipped caused real harm to users — a data loss, a privacy issue, an outage that hit customers hard — and you had to lead the response. Not just the technical fix, but the human side of it.

    hard~5 min

Problem Solving Questions (6)

  1. 21.Estimate the number of messages Slack processes per second on a typical Tuesday at 10am Pacific. Walk me through your reasoning.

    easy~3 min

  2. 22.Daily active message send rate in a workspace cohort dropped 8% week-over-week. No incidents, no deploys. What's your diagnostic process, and what do you rule out first?

    easy~4 min

  3. 23.Slack's notification delivery pipeline needs to guarantee that a message notification reaches a user's mobile device within two seconds, at the 99th percentile, even when the user has both iOS and Android devices. How do you think about sizing and architecting that pipeline end-to-end?

    medium~5 min

  4. 24.We want to add AI-generated channel summaries to Slack — the feature surfaces a TL;DR for a channel's recent messages when you return after being away. Estimate the infrastructure cost implications of running this at scale for all Slack workspaces.

    medium~5 min

  5. 25.Slack Connect lets companies share channels across organizational boundaries. If a user at Company A is deprovisioned mid-day, estimate how long the current architecture might tolerate their session remaining valid across all the shared channels they participate in — and what's the blast radius if that window is 15 minutes?

    hard~5 min

  6. 26.Slack is considering charging for message retention beyond 90 days as a paid feature. Walk me through how you'd estimate the engineering cost — storage, query performance, and operational overhead — of extending retention to unlimited for the top 1% of Enterprise Grid workspaces.

    hard~5 min

More Slack interview questions