GrabChristian CoffrantBenchmark
Grab Bench: Evaluating AI on Grab-shaped production work
Summary
Grab Bench is a configurable evaluation harness for assessing AI systems on production-shaped work where plausible outputs can violate metric definitions, tool contracts, evidence boundaries, or hidden code invariants. It uses YAML configuration, task plugins, provider and modality checks, row-level records, model summaries, and deterministic scorers or LLM judges according to each task. Synthetic or redacted cases preserve production-relevant difficulty while protecting live data; profile reasoning requires ontology-valid JSON claims and faithful evidence IDs, while coding tasks exercise hidden tests and anti-gaming checks. The harness also records tokens, latency, skip reasons, configurations, and failure tags so teams can diagnose whether errors reflect unsupported claims, parameter drift, hidden invariants, cost, or capability gaps. It concludes that synthetic evaluations test contract adherence under controlled pressure but do not establish production uplift.
Context
Teams need to evaluate whether models preserve metric definitions, obey internal tool contracts, remain cautious with weak evidence, and maintain hidden repository behavior. Production traces and user records cannot be reused directly, while public leaderboards do not answer these product-specific questions.
Approach / What changed
Grab Bench uses configurable task plugins with synthetic or redacted cases, deterministic scorers or LLM judges, hidden tests, anti-gaming checks, row-level records, baselines, canaries, and versioned run metadata. Each task defines its own contract and failure taxonomy.
Takeaways
Passenger-profile cases require strict JSON, ontology-valid claims, existing evidence IDs, grounded support, calibrated confidence, and safe actions; fabricated IDs, cite-all behavior, or unsupported sensitive claims receive penalties or score caps.
Agentic coding evaluations test more than visible correctness: they include hidden workspace tests and checks for API compatibility, stateful invariants, idempotency, concurrency, cancellation, oversized patches, and other shortcut patterns.
The benchmark treats synthetic evaluation as evidence of contract adherence under controlled pressure, not proof of production uplift; live retrieval quality, user impact, and rollout decisions require separate evidence.
Source and freshness
- Source
- engineering.grab.com
- Published
- Added to Yomu
- Last updated
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.