Each of these is a real decision Reddit is working through, written so you can make the call yourself — incomplete information, someone who pushes back, no answer key.
Reddit operates a community-based discussion platform organized into topic-specific subreddits where users post, comment, and vote, and moderators manage communities. It serves individuals seeking information and peer perspectives, and monetizes primarily by selling native advertising and marketing tools to brands, retailers, and agencies. Its community of users generates over 100B events per day, each of which is ingested into a data warehouse that sees 55,000+ daily queries. Reddit develops with Go, Python, Postgres, Redis, Thrift and GraphQL and deploys to Docker and Kubernetes on AWS. Its monolith legacy stack, R2, is pretty much in the critical path for every Critical User Journey at Reddit.
Your first one is free. No card.
28 live right now.
The rest
Decide on limiting scheduling while removals and warnings continue
Scheduled posts from affected professional accounts are drawing removals and account warnings in certain communities. You have to weigh publishing continuity against the risk of making moderator distrust harder to reverse.
Choose context or filters for Trends while one test slot remains
Conversation saves from Trends results have fallen to 11% as managers struggle to judge threads quickly. You must weigh richer community context against a fast research surface and one experiment slot.
Route suspicious posts without delaying verified publishers
Engineers must reconstruct evidence across systems while some verified publishers miss scheduled posting windows. You must decide what AI can assemble and suggest without taking the severity decision away from the engineer.
Trace a failed search to its cause within 30 minutes
Selected failed research sessions need an engineer-confirmed cause within 30 minutes in 80% of pilot cases. You have to weigh faster investigation against evidence engineers can trust before changing a GraphQL or Redis path.
Add a community module for new readers, but prove it beyond clicks
Sixty-three percent of sparse-signal mobile readers view fewer than two communities in their first week. You must weigh a new discovery path against the home-feed space and relevance it displaces.
Commit a guardrail threshold while real posts are blocked
Benign post-composer blocks rose from 0.18% to 0.61% while attempted bypasses still appear in review queues. You must weigh a durable shared security boundary against the cost of excluding legitimate contributors.
Recover fresh posts before ranking sees a thinner feed
Eligible posts under two hours old reach retrieval only 58% of the time during high-activity windows. You must weigh broader fresh inventory against the latency budget that keeps the home feed responsive.
Prepare integrity cases without trusting a drafted verdict
Engineers are rebuilding case context by hand while suspicious mobile vote patterns remain unresolved. You must decide what AI can assemble and what an engineer must still judge.
Lead readers to a second discussion without slowing the home feed
Logged-out readers are leaving after one discussion instead of finding a related community or thread. You have to weigh deeper discovery against a focused reading experience and home-feed performance.
Protect home-feed votes while breaking discussions surge
Manipulated upvotes are pushing low-quality posts into mobile home feeds during a high-attention news cycle. You must weigh rapid enforcement against the risk of burying genuine community discussion.
Restore video after comments without breaking the home feed
Video starts after returning from comments have fallen below the expected 97% threshold for the affected app version. You have to weigh a narrow client fix against the risk of disturbing home-feed playback.
Surface creative fit without narrowing community choices
Advertisers repeatedly revise community selections after early delivery because creative fit is not predicted today. You must weigh a helpful setup signal against recommendations that could overconstrain legitimate campaign choices.
Decide whether to promote the model despite a 2.3% cohort drop
Offline calibration improved 4.1%, while measured conversion value fell 2.3% for two major cohorts. You must weigh a potentially valuable model promotion against budget shifts that will be costly to unwind.
Restore contextual matches before the next embedding refresh
Eligible contextual matches fell from 98.0% to 91.8% after a feature refresh. You must weigh a targeted pipeline correction against an adjacent retrieval change that costs the same deployment window.
Trace release breaks while migration apps keep moving
Release-breakage reports are arriving with conflicting clues about API and GraphQL changes. You have to weigh faster triage against the evidence engineers need before acting.
Stage moderation apps without opening them to every community
Porting developers cannot limit early moderation apps to trusted communities. You must weigh a simple installation path against controls that make pilots safe enough to trust.
Commit to a storage cutover before moderators lose their saved rules
Saved moderation settings intermittently return old values after apps confirm a write. You must weigh migration speed against a one-way move of community state.
Stop duplicate jobs while retries still recover
Retryable failures are causing scheduled apps to perform the same moderator action twice. You have to weigh reliable recovery against an execution record developers can trust.
Test ranking of communities in shadow until precision hits 75%
Managers open an average of 17 communities before saving a useful conversation for broad-topic research. You have to weigh a helpful ranked shortcut against evidence, latency, and the risk of overstating community fit.
Stop overpredicting for small communities without losing adoption
Small-community posts are missing predicted engagement by 22 percentage points and driving more dismissed guidance. You have to weigh recommendation coverage against a permanent model-policy change under incomplete evidence.
Recalibrate keyword results as saves fall after the new representation
Saved conversations from monitored keyword results fell from 14% to 11% after a representation change. You have to weigh tighter relevance against coverage and release capacity.
Give schedulers a safe warning before enforcement blocks posts
Accounts facing enforcement friction retry scheduling 2.7 times before abandoning the flow. You must weigh useful pre-publish guidance against revealing signals that abusers could exploit.
Commit to a bot block without silencing verified publishers
Suspicious publishing traffic rose 6.4-fold in 18 hours across professional accounts. You must weigh community protection against false blocks that disrupt legitimate organic publishing.
Recover report access before tomorrow’s reporting cycle
Authorized report requests are failing at 1.8% after session refreshes. You must weigh a contained guardrail against an IAM rollback in one release window.
Connect research to publishing without guessing what managers need
Managers export disconnected monitoring and publishing data 2.4 times more often when using both surfaces. You have to weigh a focused first view against broader reporting expectations.
Choose access rules before incomplete reports reach customers
Eligible monitoring queries are returning incomplete results for newly migrated accounts. You have to weigh durable coverage against authorization boundaries that cannot be loosened later.
Recover scheduled posts before their publishing windows close
3.2% of accepted schedules missed yesterday's publishing window. You have to weigh a fast retry correction against duplicate-post risk.