← Back to Directory

Discord interview notes, page 1 of 4

Mid-sized

Most of these Discord write-ups come from Software Engineers (35), then Product Managers (3) and Backend Engineers (1). The most reported rounds are the technical phone screen (23), the system design round (8), the recruiter screen (3) and the behavioral / leadership round (2).

40 interview notes · updated Jul 2026

Discord·Software Engineer·Technical Phone Screen

Apr 2026
Interviewed for a Data Engineer role at Discord, got a Python coding question that looked trivial at first glance. The case-insensitivity part is where people probably trip up.
  • Write a Python function that counts how many times a given character appears in a string, where the comparison is case-insensitive.

“Seemed easy and I almost wrote a one-liner without thinking.”

View Post

Discord·Software Engineer·Recruiter / HR Screen

Apr 2026
Screener for a data science role at Discord. Pretty light on technical stuff, more of a fit conversation to figure out where you're looking and why.
  • What other companies are you interviewing at, and what draws you to those particular roles or teams?

“I was a bit guarded at first because it felt like a trap for negotiation leverage.”

View Post

Discord·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Interviewed for a PM role at Discord, and the prompt was basically just 'improve Discord.' That's it. No guardrails, no context, just a blank canvas which sounds fun until you're actually sitting there trying to figure out where to even start.
  • How would you improve Discord?

“Wide open question and I think that's kind of the point.”

View Post

Discord·Software Engineer·Technical Phone Screen

Apr 2026
Discord software engineer interview with a technical question about working with AI-generated code. Pretty niche topic but makes sense given how much tooling has shifted lately.
  • How do you verify AI-generated code before merging it? Walk through your review process, what tests you add, any static analysis you use, and how you decide to trust AI suggestions over time.

“This one took me a second to frame properly.”

View Post

Discord·Software Engineer·Technical Phone Screen

Apr 2026
Discord SRE-style interview where they drop you into a live CPU spike incident and expect you to work through it out loud. The interviewer plays the role of an on-call engineer feeding you data as you ask for it. Felt more like a real incident than a test, which was both cool and stressful.
  • You get paged: CPU usage on a production service has suddenly spiked. Walk through how you'd respond, from first alert to root cause and fix. You can ask for any metrics or logs you want.

“The open-ended format tripped me up at first because there's no single right answer to anchor to.”

View Post

Discord·Software Engineer·Technical Phone Screen

Apr 2026
Discord interview for a backend engineering role, two-stage coding exercise built around a Python asyncio chat server. The first part was a straightforward broadcast server, the second added rooms, DMs, and command parsing. Pretty meaty for a single session.
  • Build a TCP chat server using Python asyncio that accepts multiple concurrent clients and broadcasts messages from any one client to all others. Handle client disconnects cleanly without crashing or leaking state.
  • Extend the chat server to support named rooms: clients can join and leave rooms, and messages should only be delivered to others in the same room.
  • Add private messaging (DMs) and a command parser that handles /join, /leave, and /msg from the raw client text stream.
  • Walk through how you'd structure concurrency here: per-client tasks, cancellation on disconnect, and keeping the transport layer separate from chat-room state.

“The broadcast logic itself wasn't hard but I fumbled the disconnect handling more than I'd like to admit.”

View Post

Discord·Software Engineer·Onsite - System Design / Architecture

May 2026
Discord engineering manager interview that came down to a single system design prompt. Pretty stripped back, no fluff.
  • Design and implement a TCP-based chat server.

“This sounds like a warmup but it really isn't once you start pulling at the threads.”

View Post

Discord·Software Engineer·Hiring Manager Screen

May 2026
Interviewed for a data science role at Discord, and the one question I remember most was about personal growth and learning. Pretty light on technical depth for what I expected.
  • How do you approach personal growth and learning?

“Rambled a bit about reading and side projects.”

View Post

Discord·Software Engineer·Technical Phone Screen

May 2026
Data modeling and SQL round at Discord for a Data Engineer role. The session was 45 minutes and focused entirely on designing a schema for video call logs and then writing queries against it. Pretty heads-down technical, no behavioral stuff at all.
  • Design a data model for video call logs, capturing both client-side and server-side data. What tables and columns would you use?
  • Write a query to find the number of video calls per country per day.
  • Extend the previous query to show the number of video calls per country per day for rolling windows of 7, 14, and 30 days, for each date present in the database.

“They gave some scaffolding upfront: a video table with user_id, video_id, call_duration, number_joins, number_rejoins, and timestamp, plus a user table with user_id and country.”

View Post

Discord·Software Engineer·Technical Phone Screen

May 2026
Database deep-dive question at Discord for a software engineering role. Just one question but it had a lot of surface area to cover.
  • Walk me through the databases you've worked with. For each one, what was your level of involvement, what was the use case, what kind of scale were you dealing with in terms of data volume or request throughput, and did you handle any operational work like schema design, query optimization, replication, or backups?

“This looks like a straightforward resume question until you realize they want actual numbers.”

View Post