Slack · Primly Community

Slack frontend engineer interview: what the rounds look like in 2026

corp_refugee · 5 replies

Just wrapped up a Slack frontend engineer interview loop. I'm a React/TypeScript person with 4 years of experience (mid-level, targeting L4) and this is my full breakdown. The frontend-specific context was hard to find so hopefully this helps.

The loop was 5 rounds:

1. Recruiter screen. 30 min, totally standard. She asked me to confirm I was okay with hybrid (SF-based), which I knew going in.

2. Technical phone screen. This was JavaScript/React focused, not general LC. They gave me a small component to build live in a shared editor. Think: a toggle component with specific accessibility requirements (ARIA labels, keyboard nav). The interviewer cared about how I thought about edge cases, not just whether it worked. I also got a JS question about closures and async behavior. If you're rusty on the JavaScript event loop, fix that.

3. Coding round (onsite). More algorithmic than the phone screen. LC medium level. Nothing frontend-specific, just data structures. I got a sliding window problem. I think this exists to make sure frontend engineers can also think algorithmically. Don't skip Leetcode entirely just because you're coming in as frontend.

4. Frontend system design. This was the most interesting round. Prompt was something like: design a real-time notification system for a web client. I talked about WebSockets vs. SSE, state management approaches (Redux vs. Zustand vs. context), optimistic updates, reconnection strategies, and accessibility. They pushed me on performance: what happens with 10k users all getting a notification simultaneously? Make sure you can talk about debouncing, virtual scrolling, and rendering performance. They also asked about testing strategy.

5. Behavioral round. With an EM. Standard behavioral stuff: conflict with a coworker, time you pushed back on a product decision, how you approach code review. I used STAR for all of them. One question that threw me: "tell me about a time you prioritized DX (developer experience) over a feature request." Wasn't expecting that but made sense for Slack's engineering culture.

Overall the process felt frontend-literate, which I appreciated. Some companies interview frontend engineers like they're backend engineers who happen to know React. Slack actually tested relevant things.

Offer: came 12 days after onsite. Still deciding.

5 replies

pivot_pat

The DX prioritization question is a great one to prep. It's subtle because most behavioral questions are about conflict with people, not about tradeoffs in what you build. I'd never have thought to prep that angle.

ops_omar

WebSockets vs SSE is such a classic frontend system design prompt. Anything that's real-time, expect it. Good addition to mention reconnection strategies, that's where a lot of candidates fall flat.

remote_swe_42

Did they ask you to rate yourself on any specific frameworks or tech, or was it just inferred from the resume?

frontend_fran

Inferred from resume mostly. The recruiter confirmed I was React-primary at the start of the process and all the frontend rounds were React/JS-centric. I wasn't asked to rate myself on a scale or anything like that.

brand_ben

Accessibility in the phone screen round is a green flag honestly. Shows they care about the actual product, not just 'can you code.'