Discord Software Engineer interview questions

21 Software Engineers have shared notes from their Discord interviews, with the questions they were asked in each round. That is 95% of the 22 Discord interview notes on Screna AI.

21 Software Engineer interview notes

Discord·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Discord system design round for a backend/infrastructure role. The whole thing was basically one big question with three mandatory deep-dives baked in, so there was no hiding from the hard parts.
  • Design a Slack-style messaging platform that supports workspaces, channels (public, private, and DMs), threaded messages, mentions, search, presence indicators, and notifications.
  • How would you index messages to support fast channel scrolling, full-text search, and unread counts?
  • Walk through your database choice for this system. Why would you pick relational, NoSQL, or a split approach using a log store plus a key-value store? How would you partition by workspace or channel?
  • How does a sent message fan out to all channel members? Cover offline users and mobile push, large channels with many members, and how unread counts get updated.

“Big open-ended prompt and they let you run with it for a bit before steering toward the deep-dives.”

View Post

Discord·Software Engineer·Technical Phone Screen

Jun 2026
Discord SWE interview that went deep on concurrency debugging. One question, but it had a lot of layers and they clearly wanted a real story, not a textbook answer.
  • How do you debug race conditions in production? Walk through your general strategy and describe a specific race condition you found and fixed.

“This one bit me a little because I started with the theory stuff, logging and lock instrumentation and race detectors, and I could tell they were waiting for the actual story.”

View Post

Discord·Software Engineer·Technical Phone Screen

Jun 2026
Discord data engineer interview, got a SQL question that looked simple on the surface but had a specific aggregation requirement that tripped me up a bit.
  • Given a table with server_id, user_id, and timestamp columns, write a SQL query to find the average number of weekly server views for the year 2020. You need to first sum views per ISO week, then average those weekly totals.

“The two-step aggregation part is where I fumbled initially.”

View Post

Discord·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Discord SRE-style interview where they drop you into a live CPU spike scenario and you have to work through it in real time with the interviewer playing the on-call engineer. No coding, just systems thinking under pressure. Felt more like a war room simulation than a traditional interview.
  • You get an alert that CPU usage on a production service has suddenly spiked. Walk through how you'd respond, what information you'd ask for, and how you'd find and fix the root cause.

“This one runs long because it's open-ended and the interviewer feeds you data as you ask for it.”

View Post

Discord·Software Engineer·Technical Phone Screen

Jun 2026
Database deep-dive question at Discord for a software engineering role. One question but they really wanted to go broad and deep at the same time, which is a tough combo.
  • What databases have you worked with? For each one, walk through your experience level, the use case it served, the scale in terms of data volume and query load, and any operational work you did like schema design, query optimization, replication, or backups.

“This question sounds broad but they really mean business.”

View Post

Discord·Software Engineer·Technical Phone Screen

May 2026
SQL-heavy technical screen for a Data Engineer role at Discord. One question, but it had enough layers to keep me busy for a while.
  • Given tables for servers, server views, server joins, and messages, write a query that returns one row per server with the all-time count of views, joins, and messages. Servers with zero activity in any category should still show up with a 0.

“I went straight for separate subqueries aggregated by server_id and then joined them back to the servers table.”

View Post

Discord·Software Engineer·Onsite - System Design / Architecture

May 2026
Data engineering interview at Discord focused entirely on warehouse modeling for server activity data. One meaty design question that covered a lot of ground, felt more like a working session than a traditional interview.
  • Design a fact/dimension data model for Discord server activity, given raw event tables for server creation, server views, server joins, and messages. Define your dimension and fact tables, explain your grain choices, how you'd handle slowly-changing dimensions for users and servers, how you'd partition the data, and what query patterns the model is built to serve.

“This was the whole interview basically.”

View Post

Discord·Software Engineer·Technical Phone Screen

May 2026
Discord SWE interview included an on-call readiness question that felt pretty operational for what I expected to be a standard engineering screen. Not a lot of fluff, they wanted real specifics.
  • Do you have on-call experience? Walk through the rotations you've been part of, the kinds of incidents you've handled, the runbooks and tooling you used, and a specific incident you either led or took something meaningful away from.

“This one had more layers than I expected.”

View Post

Discord·Software Engineer·Technical Phone Screen

May 2026
Got a coding question for a Data Engineer role at Discord, basically a string manipulation problem that looks easy but has a sneaky case-sensitivity wrinkle to it.
  • Write a Python function that takes two strings and returns the words that appear in exactly one of them, treating words case-insensitively for comparison but preserving their original casing in the output.

“The case-preservation part is what gets you.”

View Post

Discord·Software Engineer·Technical Phone Screen

May 2026
Discord interview for a backend engineering role, two-stage coding exercise built around designing a chat server with Python asyncio. Pretty fitting given what the company actually builds, which made it feel less like a generic whiteboard and more like a real problem worth thinking through.
  • Design and implement a TCP chat server that accepts multiple concurrent clients and broadcasts messages from any one client to all others. Handle disconnects cleanly without crashing or leaking state.
  • Extend the server to support named rooms: clients can join and leave rooms, and messages are only routed to others in the same room. Also add private messaging between users and parse commands like /join, /leave, and /msg from the raw text stream.

“The broadcast part was fine, the disconnect handling tripped me up more than I expected.”

View Post