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.
160 results across 1 active filter
Page 2 of 7
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 instruction authority while keeping provider-specific message roles separate from the application’s durable trust boundary.
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.
Balances AI quality, tail latency, and cost through explicit product thresholds, model choice, context control, caching, routing, and measurement.
Uses plans as bounded, revisable execution aids while preserving evidence, policy, and application-owned state transitions.
Handles token-budget overflow and incomplete generation through explicit prioritization, rejection, retrieval, summarization, continuation, and validation.
Separates provider refusals, safety blocks, token truncation, transport failure, and valid domain abstention.
Separates model and provider outcomes, applies bounded recovery, validates outputs, and exposes useful status and telemetry.
Treats prompts as observable behavior, removes secrets and authorization policy from them, and limits the consequence of disclosure.
Returns correlated, minimal, typed, and safely bounded tool results without confusing them with trusted instructions.
Uses explicit status and field semantics so absence, null, not-applicable, and insufficient evidence are not conflated.
Uses deadline budgets, transient-only bounded retries, jitter, idempotency, and propagated cancellation without retry storms.
Records attributable versions, decisions, evidence references, policy results, and side-effect receipts while minimizing content-rich logs.
Defines success, failure, step, time, token, cost, retry, and repetition limits with useful escalation behavior.
Combines production-shaped, expert-authored, edge, and adversarial cases with versioned labels and privacy controls.
Transforms conversational requests into bounded search inputs while preserving user intent, constraints, and traceability.
Balances retrieval precision, answer completeness, document structure, overlap, metadata, and model input limits.
Chooses among shared, provisioned, regional, data-zone, global, batch, or managed-compute patterns from workload and governance constraints.
Chooses a model from task-specific evaluation, operating constraints, safety, latency, cost, context, modality, and provider requirements.
Chooses among routing, sequential, parallel, evaluator-optimizer, and bounded agent loops from the task's dependency structure.