Pick a focused question that fits your time, stack, and interview goal.
How much time do you have?
Show one-drill sessions you can finish now.
118 results across 1 active filter
Page 1 of 5
Uses traces and saturation evidence to locate retry amplification, queue growth, exhausted workers, and failing fallback paths.
Uses traces to separate unclear goals, bad tool interfaces, missing state, contradictory results, poor termination, and retry amplification.
Diagnoses an AI regression by decomposing request stages, configuration changes, token growth, retries, routing, tools, retrieval, caching, and provider behavior.
Reproduces failing cases, compares versioned traces, isolates the first changed component, mitigates impact, and adds regression coverage.
Traces a missed answer through source ingestion, parsing, chunking, filtering, query construction, retrieval, fusion, and ranking.
Builds a reproducible evaluation harness that records immutable cases, versioned outputs, deterministic checks, calibrated graders, slices, and release decisions.
Builds a schema-constrained extraction boundary that distinguishes refusal, malformed output, semantic invalidity, and safe bounded repair.
Builds a hybrid retrieval pipeline that enforces tenant scope before ranking, assembles a bounded context, and verifies returned citations.
Chooses delegation patterns based on who owns the user interaction, context, final answer, permissions, and failure handling.
Separates the current model input from authoritative workflow state and selectively retained information across runs.
Combines exact lexical matching with semantic recall and explains why hybrid retrieval often needs measured fusion and ranking.
Separates application instruction attacks from attempts to bypass a model's safety behavior and explains their overlapping defenses.
Handles a poisoned retrieval corpus by freezing ingestion, tracing provenance, switching immutable index versions, rebuilding clean data, and proving recovery.
Combines restrained autonomy, curated tools, durable state, approval, memory, recovery, MCP trust, evaluation, and operational controls.
Connects product success, layered evals, calibrated graders, release gates, guarded rollout, traces, monitoring, feedback, and incident learning.
Combines governed ingestion, authorized hybrid retrieval, reranking, grounded generation, citations, evaluation, observability, and fallback.
Combines threat modeling, injection containment, data minimization, tenant isolation, tools, audit, incident response, and governance.
Combines explicit trust boundaries, provider access, state, execution modes, resilience, budgets, versioning, and operations into a restrained design.
Uses workflow traces to distinguish planning failure, stale observations, retry ambiguity, and missing terminal conditions in a looping agent.
Uses versioned traces and evaluation slices to locate whether a RAG regression came from ingestion, retrieval, context assembly, or generation.
Breaks results down by meaningful user, task, risk, language, input, and system dimensions instead of trusting one average.
Explains how decoding settings reshape token selection and why they must be tuned against task-specific evaluation rather than folklore.
Separates development and held-out cases, controls access, detects duplication, and validates improvements on fresh traffic.
Abstracts stable application needs while exposing valuable capabilities deliberately instead of enforcing a false universal model API.