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.
1345 results
Page 31 of 57
Builds system-specific adversarial testing around realistic assets, identities, channels, tools, and measurable impact.
Frames allocation reduction as measurement-driven API work rather than premature micro-optimization.
Uses constrained output where possible, deterministic parsing and validation, bounded targeted repair, and safe fallback.
Contains compromised AI capabilities, preserves evidence, scopes derived data and actions, remediates boundaries, and verifies safe recovery.
Reviews correctness, boundaries, failure behavior, capacity, security, observability, delivery, and recovery through concrete evidence.
Treats model changes as controlled releases using versioned configuration, fixed evaluations, shadow or canary traffic, monitoring, and rollback.
Uses explicit capability and risk policy to route by task while preserving evaluation, version attribution, budgets, and fallback semantics.
Tracks trust, versions, integrity, provenance, review, and rollback across models, adapters, prompts, datasets, tools, and parsers.
Establishes server trust, audience-bound authorization, least privilege, capability filtering, approval, and safe handling of untrusted results.
Uses workload identity, separate control and data planes, least privilege, scoped model access, and auditable administration.
Treats actions as public mutation endpoints with server validation, fresh authorization, idempotency, transactions, and safe errors.
Protects knowledge ingestion with source trust, provenance, validation, quarantine, review, versioning, and rollback.
Builds a readable request with stable instructions and clearly delimited, provenance-aware untrusted inputs.
Classifies tools by consequence and applies distinct permissions, validation, confirmation, idempotency, and audit controls.
Combines deterministic invariants, severity-aware quality thresholds, slice protection, baseline comparison, and guarded rollout.
Coordinates admission stop, task cancellation or draining, resource closure, and bounded termination.
Sizes per-instance database concurrency from workload and database capacity instead of equating more connections with more throughput.
Separates user-visible progress from validated completion and prevents partial JSON or tool arguments from triggering side effects.
Explains a practical Git workflow for a .NET team using branches, pull requests, code review, and protected main branches.
Designs explicit ESM boundaries with focused exports, controlled side effects, and dependency direction that supports safe bundling.
Combines semantic queries, keyboard interaction, focus assertions, and automated checks while retaining manual assistive-technology review.
Tests asynchronous coordination through observable events and proves spawned tasks finish or cancel cleanly.
Tests user-observable urgent, pending, success, failure, interruption, and out-of-order behavior without scheduler coupling.
Maps assets, trust boundaries, untrusted content, model influence, actions, and abuse cases before selecting controls.