Discord
Each of these is a real decision Discord is working through, written so you can make the call yourself — incomplete information, someone who pushes back, no answer key.
Discord is a freemium communications and community platform offering voice, video, text messaging, and screen sharing within topic-organized community servers and direct messages. It serves individuals and online communities, especially gaming and interest-based groups, and has more than 90M daily active users. It monetizes through paid subscriptions and server boosts, and its premium work spans surfaces like Nitro, Shop, Server Boosting, and User Identity, aimed at delivering value to subscribers without compromising the core experience for free users. Engineering work is primarily in web (React, TypeScript), mobile (React Native, with a small amount of Kotlin, Objective-C, and Swift), and backend (Python). Discord uses GCP, Cloudflare, and AWS for its cloud environments. It runs hundreds of experiments on any given day, turning experiment results into business decisions.
Your first one is free. No card.
17 live right now.
The rest
Trace message regressions while on-call needs answers
Reply and thread failures are splitting conversations across web and mobile, and engineers cannot yet agree where the break starts. You have to weigh faster incident traces against evidence strong enough for engineers to trust.
Give volunteers access for one event so it cannot outlast the event
Temporary event helpers are receiving broad permissions that can remain after the event ends. You have to weigh fast delegation against limits owners can understand and reverse.
Contain a leaked credential without breaking event message delivery
Message dispatch is degrading while a production credential may be used beyond its approved workloads. You must weigh a fast, irreversible containment move against continuity for communities in live events.
Restore on-call access while production alerts keep firing
Approved incident responders are being blocked from production even though their Access roles still exist. You have to weigh rapid recovery against the narrow, auditable permissions that protect production.
Prioritize urgent reports without mistaking volume for danger
Urgent reports are getting lost among repeated submissions in large servers. You must weigh faster routing against unfairly deprioritizing harm that arrives with little context.
Set report thresholds before harmful messages spread
Reported harmful messages are being marked low risk and remain visible in large servers. You must weigh faster removal against irreversible incorrect enforcement.
Retune invite checks before moderators drown in upheld appeals
Valid invite joins are producing a 4.8% false-positive enforcement rate. You must weigh faster legitimate access against preserving detection of abusive accounts.
Define a useful reply for 50 servers without tracking ordinary chat
Members repeat questions because moderators cannot see which support threads truly reached a useful answer. You must weigh usable resolution signals against the limits of interpreting community conversation.
Judge Quest labels before ranking locks in uneven delivery
Quest completions rose, yet large communities saw sharply fewer deliveries and the measurement totals do not agree. You must weigh fresher ranking signals against committing unreliable labels to intra-day training.
Align Quest conversions before advertisers rebuild their reports
Quest conversion totals differ across delivery and measurement for active campaigns. You have to weigh a fast pipeline correction against preserving auditable history and dependable ML inputs.
Turn chat threads into one plan so organizers stop reposting times
Organizers keep reposting times and attendance details because the current plan gets lost in channel traffic. You have to weigh lightweight coordination against the casual flow that keeps a server welcoming.
Choose an age-check flow that restores access without easing fraud
Eligible members are being locked out while suspicious new accounts appear to pass through. You have to weigh restored community access against a flow that fraudsters may learn to exploit.
Stop players leaving at platform choice while a friend is mid-session
Only 12% of mobile game presence opens currently become completed friend invites. You must weigh a clearer join path against the limited experiment slot needed to prove it works.
Keep answers in view while busy channels scroll past
Moderators in selected servers repeatedly repost answers that disappear in active channels. You have to weigh durable guidance against keeping the channel feeling like a live conversation.
Decide on rollback or one-way migration before weekend events
Opted-in members are missing time-sensitive server alerts while others receive unrelated pings. You must weigh reliable event delivery against the preference changes and safety exposure each path creates.
Stop duplicate reminders as members move between devices
Duplicate activity reminders reach 4.2% of recipients who switch between mobile and web. You must protect reminder reach while removing the extra ping that makes members mute them.