10 Discord Platform Engineer (New Grad) Interview Questions (2026)

Discord's Platform Engineer new-grad loop in 2026 is a recruiter screen, an OA, and a 4-round virtual onsite with extra emphasis on bot platform, slash commands, OAuth flows, and rate limiting. Platform engineers own the developer-facing surface — the API, the bot ecosystem, and the integrations that thousands of community-built tools rely on.

By Alex Chen, Founder, InterviewChamp.AI · Last verified 2026-05-25

Loop overview

Platform-track new-grads see an extended loop. Recruiter → OA → phone screen → onsite with two coding rounds, one platform-design round (bot architecture, slash commands, webhooks, OAuth), and one behavioral. Expect questions about API versioning, backward compatibility, rate limiting at scale, and developer experience. Backend is Elixir/Erlang and Rust; the API gateway layer is the typical entry point for platform engineers.

Behavioral (3)

Why platform engineering at Discord specifically?

Frequently asked

Outline

Tie to interest in developer tools, bot ecosystem, API design, or community-driven product. If you have built a Discord bot or contributed to a Discord library, mention it. Show you understand platforms are products with their own users (the developers).

Tell me about a time you wrote something that other people built on top of.

Frequently asked

Outline

STAR. Platforms are about leverage — code others use. Pick a real moment: an open-source library, a class project that teammates extended, a campus tool. Be specific about how others extended your work.

Tell me about a time you debugged a tricky API integration.

Occasionally asked

Outline

STAR. API debugging is a daily reality on platform teams. Pick a moment where the bug was at the boundary (auth, rate limits, schema mismatch, timing). Walk through methodology — reproduce, log diff, isolate, verify.

Technical (2)

Implement a rate limiter for an API where each bot has its own rate limit, AND there is a global rate limit across all bots.

Frequently asked

Outline

Two-layer token bucket: per-bot bucket + global bucket. On request: try to consume from both. If either is empty, return 429 with retry-after. Walk through distributed enforcement (Redis with atomic Lua script that decrements both buckets in one round-trip). Discuss the X-RateLimit-* headers convention.

Given a stream of API requests, identify abusive bots that are making too many requests.

Frequently asked

Outline

Per-bot counter with sliding window. Flag if requests/minute exceeds a threshold. Discuss false positives (legitimate bots with bursty traffic). Use percentile-based thresholds (top 0.1 percent) rather than fixed counts. Walk through automated mitigations: temporary 429, then permanent ban if pattern persists.

System / object-oriented design (3)

Design the slash-command system. How does a bot register a command and receive an interaction when a user invokes it?

Frequently asked

Outline

Bot registers commands via REST API (global commands cache for ~1 hour; guild commands propagate instantly). User invokes; client sends interaction to Discord; Discord dispatches a webhook to the bot's interaction endpoint (or via gateway for WebSocket bots). Bot must respond within 3 seconds OR defer + send a follow-up within 15 minutes. Walk through interaction tokens, ephemeral responses, permissions. Discuss the tradeoff between webhook and gateway dispatch.

Design a webhook delivery system that retries failed deliveries.

Frequently asked

Outline

Queue per destination URL. On webhook fire: enqueue. Worker picks up, POSTs to URL, on success: ack and discard. On failure: requeue with exponential backoff (e.g. 1s, 5s, 30s, 5min, 30min). Discuss dead-letter queue after N retries. Walk through idempotency (include a delivery-id header so receivers can dedupe). Discuss DDoS protection — slow consumers should not stall fast ones.

Design the interactions endpoint for a bot. How do you handle 10x traffic spikes?

Occasionally asked

Outline

Stateless HTTP endpoint. Behind a load balancer. Auto-scale horizontally on CPU/RPS metrics. Queue interactions if the bot's downstream is slow — defer the interaction within 3 seconds, process async. Walk through rate-limiting upstream (Discord can shed load to bots that are overwhelmed). Discuss circuit breakers.

Domain knowledge (2)

How does OAuth2 work, and how would you design the OAuth flow for a third-party app that wants to read a user's Discord guilds?

Frequently asked

Outline

Authorization Code flow. App redirects user to Discord with client_id + scopes (e.g. identify, guilds). User approves; Discord redirects back with a code. App exchanges code + client_secret for access_token + refresh_token. Walk through token expiry, refresh, PKCE for public clients (no client_secret), state parameter for CSRF prevention.

How would you handle API versioning?

Frequently asked

Outline

Discord uses path-based versioning (/api/v10/...). Discuss the tradeoffs vs header-based versioning. Walk through deprecation policy (announce, dual-support, sunset). Show empathy for bot developers — breaking changes have massive blast radius across thousands of community bots. Discuss feature-flagging for opt-in changes.

Discord interview tips

Build a Discord bot before your loop. Hands-on experience with slash commands, OAuth, and webhooks transforms the system-design round.
Read Discord's developer documentation cover to cover. Platform interviews reward depth on rate limits, gateway intents, interaction tokens.
API versioning and backward compatibility come up. Practice articulating deprecation tradeoffs.
Coding rounds are still standard data structures + algorithms. Do not skip leetcode practice for platform-domain knowledge.
Compensation per Levels.fyi 2026 matches generalist SWE band at Discord. The platform track is a specialization, not a separate level.

Frequently asked questions

How is Platform Engineer different from generalist SWE at Discord?

Same compensation, but the platform track owns the developer-facing surface — API, bot ecosystem, OAuth, webhooks. Generalist SWEs own the chat/voice fabric and client apps. Some platform engineers later move to generalist roles and vice versa.

Do I need to have built a Discord bot to interview for Platform Engineer?

Not strictly required, but it is the single highest-leverage prep you can do. The system-design round directly references slash commands, interactions, webhooks. Having shipped a real bot makes your answers concrete.

What languages does Discord's platform layer use?

Elixir/Erlang for the gateway, Rust for performance-critical paths, Python for tooling, TypeScript on the client. Interview is language-agnostic; pick the one you know best.

Does Discord ask system design for new-grad Platform Engineer?

Yes. The system-design round typically covers a platform topic — slash command dispatch, webhook delivery, rate limiting, OAuth flows.

Does Discord sponsor visas for Platform Engineer new-grad?

Discord has sponsored H-1B and OPT in past US cycles. Confirm with your recruiter for 2026.

Practice these live with InterviewChamp.AI

Real-time AI interview assistant that listens to your loop and helps you structure answers under pressure.

Practice these live with InterviewChamp.AI →