Discord Interview Process: Skills Test, Values & Attitude

Discord is where communities live in real time. A server, called a guild in the codebase, is carved into text and voice channels. Hundreds of millions of people send messages there, drop into voice, and watch presence dots flip between online, idle, and offline as friends come and go. Underneath sits a stack built for exactly that load. An Elixir gateway holds a live WebSocket for every connected client, a message store on ScyllaDB keeps trillions of rows ordered by channel, and a homegrown WebRTC layer in C++ carries voice. Interviewing here means showing you can build inside those constraints, which come down to real-time fan-out, consumer scale, and a young community that the product designs safety and belonging around. The loop flexes by team and level, but the spine below is consistent across candidate reports.

The loop itself is small and practical, and it leans on a philosophy Discord states plainly: it wants to see whether you can do the actual job, not whether you can recite trivia. Coding happens on your own machine with every resource open. System design is anchored in the real-time messaging and voice problems Discord solves every day. And the behavioral portion breaks into two named rounds that probe belonging and cross-functional collaboration rather than culture-fit clichés. Four threads run through all of it: real-time systems, consumer scale, operational ownership, and a community-first mission that Discord frames as creating space for everyone to find belonging.

The Discord angle

Coding runs on your own laptop, in your own IDE and language. You are told to use every resource in the room, including Google, the API docs, and the interviewer as a teammate. This environment sets Discord apart, and it changes what is being graded. The bar is not whether you memorized an algorithm; Discord's own line is that it will not ask you to build a self-balancing red-black tree or list RAID levels from memory. The interviewer watches whether your code compiles and runs, whether you reason about runtime and tradeoffs, and whether you make it testable. Above all, they watch how you refactor when the requirements evolve mid-round. The signature applied problem is a Premium question, and the round is designed to keep changing on you: handle clock skew, then make it distributed, then bound the memory. Grinding pattern-matching in a locked-down assessment tool is the wrong prep for this.

The Pipeline

Four stages carry you from first contact to a decision. There is a recruiter screen, then a technical phone screen Discord sometimes calls the skills test. A virtual onsite of four to five rounds follows, then a debrief that a hiring manager leads. End to end it commonly runs about three to five weeks, and it can compress or stretch with scheduling and team availability. Round counts and the exact mix are team-specific, so read the numbers below as the shape of a typical loop rather than a fixed template.

• Onsite rounds: 4 to 5. Roughly 45 minutes each, often in a single day. The modal loop is one or two coding rounds, one system-design round for mid-level and up, and the two behavioral rounds (Values and Attitude), plus a team or role-specialty round. Frontend roles add a React coding round.
• Coding setup: Open-resource, your IDE. You code on your own laptop, in your own language, with Google, the docs, and the interviewer all fair game. Graded on whether it compiles and runs, tradeoff awareness, testability, and how you refactor as requirements change. CoderPad or HackerRank appears at the phone-screen stage.
• Where: SF HQ, hybrid. Discord is hybrid-first out of its San Francisco headquarters, with an Amsterdam engineering presence and a limited number of mostly-US fully-remote roles. Interviews are remote-friendly. Not a remote-default company.
• End to end: ~3 to 5 weeks. From first recruiter contact to a decision, per candidate reports. The debrief and committee tend to land within days of the last round. Variable by level and team, and by how quickly scheduling lines up.

The Discord angle

System design here is real-time messaging and voice at consumer scale, and interviewers reward reasoning that tracks Discord's own architecture. A generic Kafka-and-load-balancer answer underperforms; a grounded one stands out. Message storage means the ScyllaDB store, where rows are bucketed by channel and time so a single partition stays small. A Rust data-services layer in front coalesces a burst of reads for a celebrity post into one database hit. Fan-out means the Elixir gateway, where a session process per connection talks to a guild process per server. A large guild is mostly passive members, so relays cut roughly ninety percent of the work. Voice means a WebRTC selective forwarding unit that forwards each speaker rather than mixing, so it scales past the point where peer-to-peer would collapse. The follow-ups probe failure modes: a celebrity guild goes viral, a data center flaps and half a million clients reconnect at once. Reading Discord's engineering blog before the loop is unusually valuable preparation.

Laid out in order, the path runs through these stages.

The Discord angle

Behavioral is two named rounds, Values and Attitude, and the Attitude round deliberately puts you in front of people from outside engineering. Leaders run the Values round. "Why Discord" has to be genuine there, you talk through feedback and conflict, and knowing the mission and how the company makes money is expected. The Attitude round pairs you with two employees from different departments, often non-engineers, and asks about collaboration and what you care about beyond code, which is the community-first culture applied as a screen. Both rounds weight what you shipped, with concrete ownership and outcomes, over rehearsed culture-fit lines. Trust and safety is a load-bearing pillar here because the user base skews young and servers get large, so folding user protection into your stories reads as understanding the product. And to be clear, you do not need to be a gamer to pass; coaching fake enthusiasm tends to backfire.

The Levels Ladder

Discord does not publish an official IC title ladder, so the rungs below are approximate and should be held loosely. The one firmly labeled rung is L3, Senior Software Engineer, which is the mid-anchor and the primary independent-execution bar. Titles above Senior are inferred and get fuzzier as they climb, so do not treat Lead, Senior Staff, or Principal here as confirmed names. The years-of-experience hints are directional industry norms, not Discord minimums; the company levels on demonstrated scope, not time served. Scope is the real axis, and the loop deepens inside its existing rounds as the level rises rather than piling on new ones.

The Discord angle

Discord is still a private company, so the equity in any offer is paper. There is no ticker and no public shares as of mid-2026. Discord filed confidentially for a US IPO in January 2026, and that debut has slipped. Until it prices, grants are almost certainly double-trigger RSUs, which need both the time vest and a liquidity event before they convert to something sellable. The mark to value them against is the roughly eight-billion-dollar secondary price, not the fifteen-billion peak from 2021; a down round landed in between. What that means for an offer is concrete. Discord runs a base-heavy structure: a genuinely high liquid base, a negligible bonus, and illiquid RSUs on top. So a dollar of base is worth more than a dollar of Discord equity today. Level is the master lever because each rung is a large jump, and pushing base is unusually rational here. The compensation lesson works the numbers and the levers in detail.

What Makes the Discord Loop Different

Strip away the recruiter call and a handful of things define what it feels like to interview here. They all trace back to one fact. Discord is a real-time communication platform at consumer scale with a young community, and it hires people who can build inside those constraints and own what they ship.

Why Open-Resource Coding Changes Your Prep

One framing is worth fixing before you prepare a single answer. The open-resource round is not a trap to catch you leaning on the docs; leaning on the docs is exactly what it invites. The interviewer is watching how you work the way you work at a job: read an API, wire up a small thing, run it, and adjust when a new requirement lands. So practice by building runnable code under time pressure with the reference material open, not by drilling puzzles in a bare editor. Treat the follow-ups as the main event, because the round is designed to evolve. The person who calmly reshapes a rate limiter into a distributed one scores where the person who freezes does not. Narrate your tradeoffs as you go and pull the interviewer in as a collaborator. The problems vary, but the structure you bring does not, and that structure is what the coding section drills.

What This Guide Covers

The rest of the guide turns each stage into concrete preparation, built around what Discord asks. Interviewing for an internship or as a new grad? The internship and new-grad lesson covers how the early-career loop differs.

Common questions