Skip to content

Back to the catalog

Search-Aware Reinforcement Learning for Multi-Component Query Understanding in Roblox Game Search
arxiv.orgpaper

Search-Aware Reinforcement Learning for Multi-Component Query Understanding in Roblox Game Search

This paper presents a distill-then-RL framework for query understanding (QU) in Roblox's game search, where an LLM is first supervised fine-tuned via teacher-student distillation to produce schema-compliant outputs (intent classification, query expansion, etc.), then optimized with reinforcement learning using component-specific rewards derived from live interaction with the search engine rather than a single end-to-end reward. On Roblox search, this component-specific RL raises NDCG@20 by 8.9 points over the SFT baseline and 3.5 points over end-to-end reward training, showing that decomposed, search-aware rewards better capture how each QU component affects downstream retrieval and ranking.

TL;DR RL with per-component, search-engine-coupled rewards improves multi-task query understanding for Roblox search, beating both SFT-only and single-reward RL baselines on NDCG@20.
Document

What it claims

Beyond the headline NDCG@20 gains (+8.9 over SFT, +3.5 over a single end-to-end reward) that the summary already states, the page establishes two things the summary omits: the reward is decomposed into seven distinct signals, and the small final model outperforms its much larger SFT teacher on downstream search quality while meeting the latency budget in shadow traffic. None of the rewards require ground-truth labels — all are computed from the query, the QU output, and live search results (an RLAIF setup with LLM judges).

How it works

The QU model emits a single JSON plan with ordered fields: accept_game/accept_ip (grounding decisions), intent (closed vocab, selects retrieval route), normalized_query, fanout_queries (recall expansion), negative_terms (exclusion filtering), and attributes (11 slots, e.g. genre/recency/multiplayer, mostly closed-vocab). The search engine consumes this plan directly.

The seven rewards:

  1. Formatting {0,1} — rule-based JSON/schema/vocab validity; if it fails, all others are skipped and R=0.
  2. Search utility [0,1] — executes the plan, LLM judge labels top-k relevance, computes NDCG. N/A when intent=none.
  3. Query normalization {0,1} — judge checks typo repair without token drop/over-compression.
  4. Intent {0,1} — judge sees the retrieval route and retrieved items to check the declared intent.
  5. Fanout utility [0,1] — per-lane score s_i = NDCG_i − λ·(J_s,i + J_l,i)/2 with λ=0.3, penalizing both search-result overlap and lexical (Jaccard) overlap against the normalized query and other lanes. N/A when no fanout emitted.
  6. Attributes [0,1] — F1 over the 11 slots via judge annotations.
  7. Negative terms {0,1}.

Composite reward is the equal-weighted mean (w_k=1) over active (non-N/A) rewards.

Evidence

Reward-quality claim: the LLM-judged NDCG proxy (reward 2) was validated against ground-truth relevance on the subset of training queries with a target-game label — lists ranking the target higher get higher judged NDCG, "though with substantial variance." Authors treat it as a useful but noisy signal.

How to use it

The paper compares four RL objectives (Table 1) you could pick between:

  • DPO (offline, pairwise preference)
  • GR-DPO (offline, groupwise preference)
  • GRPO (on-policy, group advantage)
  • GDPO (on-policy, decouples per-component normalization before aggregation, preserving relative differences across reward dimensions)

Offline methods pre-sample a fixed completion set per query; on-policy re-samples each step.

Limits

  • No numbers per RL method — the fetched text cuts off mid-Section 3.4; the page does not state which of the four objectives produced the +8.9 result, nor absolute NDCG values, model sizes, or latency figures.
  • The exact search mechanics, coupling, and full prompts are withheld for confidentiality, so the reward-to-engine interaction cannot be reproduced directly.
  • The search-utility reward is an acknowledged noisy proxy (high within-bucket variance).
  • All results are on Roblox game search only; generalization is asserted, not tested.

Organisations named here

  • Roblox

Technologies named here

  • Transformer

Techniques named here

  • Distill-then-RL paradigm
  • Teacher-student supervised fine-tuning
  • Component-specific reward optimization