How to Answer: "Why Do You Want to Work at Discord?"

"Why do you want to work at Discord?" is asked at a company whose product most engineering candidates already inhabit: Discord is where gaming communities, friend groups, open-source projects, and half the internet's niche interests actually live, built on some of the most admired real-time infrastructure in consumer software (the Elixir, Rust, and Python stack serving hundreds of millions of users' messages, voice, and presence). That familiarity sets the bar: interviewers distinguish server members from server builders in one follow-up, and candidates who demonstrate product sense (understanding why a feature matters to a gamer or a community) are explicitly reported to stand out.

Discord's identity supplies the strong answer: communities rather than feeds (no ads, no algorithmic timeline: the business is subscriptions), real-time engineering as the core competence, and a product culture that takes fun seriously.

What the Interviewer Is Listening For

1. Builder-grade product familiarity. Running a server, moderating a community, building a bot, or living in the developer ecosystem: verifiable engagement beyond membership. A bot you built is the single best artifact this answer can contain.
2. Community-shaped product sense. Discord's design decisions serve belonging (spaces you join, not content pushed at you), and its revenue is Nitro subscriptions rather than attention harvesting. Candidates who articulate why that model changes the engineering (you optimize for the community's health, not engagement extraction) engage the company's actual thesis.
3. Real-time engineering attraction. Voice latency, presence fan-out, message delivery at enormous concurrency: the infrastructure is famous, and naming the layer that draws you signals substance.
4. Ownership temperament. Discord's interviews reportedly value candidates who navigate ambiguity and own problems without hand-holding; motivation with that texture fits.

A Three-Part Structure

Part 1: The platform hook (2 to 3 sentences). Your genuine Discord life, ideally with a built artifact.

Part 2: Your evidence (3 to 4 sentences). Background that maps: real-time systems, chat or voice infrastructure, consumer product engineering, with numbers.

Part 3: The direction (1 to 2 sentences). What you would build.

Sample Answer

"I have moderated a 30,000-member game-modding server for four years and built its custom bot (role automation, raid protection, an LFG matcher), which means Discord is not just my daily product: its API surface is a codebase I maintain against. That experience is my hook: I have felt exactly where the platform delights (permissions are genuinely well designed) and where it strains (raid moderation at scale is still duct tape, and I have opinions). Professionally I build real-time infrastructure: I own the WebSocket layer at a collaboration company, where I rebuilt presence fan-out to handle 10x connection growth while cutting delivery latency 60 percent, so Discord's engineering blog posts read like my job at a scale I want to grow into. And the business model matters to me: engineering for subscriptions means optimizing for communities being healthy rather than engaged-at-any-cost, which is the consumer-software job I actually want. I would aim for the real-time infrastructure or safety tooling side."

A moderator-builder's verifiable history, directly transferable evidence with numbers, and the business model engaged as an engineering preference.

Mistakes That Sink This Answer

• Member-level familiarity. "I use Discord with my friends" is the modal answer; building, moderating, or bot-writing is the differentiated one.
• Feed-company framing. Growth-hacking and engagement-metric vocabulary misfits a subscriptions business built on community health.
• Gaming condescension. The gaming DNA is the culture's pride; treating it as a phase the company should outgrow misses badly.
• Infrastructure tourism. Admiring the famous stack without any real-time evidence of your own invites depth questions the answer cannot survive.

Prepare the Rest of the Loop

This question opens a loop whose signature is building a working service live. See What is the Discord interview process like? for the structure, Top Discord behavioral interview questions for the values and attitude territory, and Grokking Modern Behavioral Interview for the evidence-based method.