Bound assistant time and token reservations per request
Repeated retries can exceed the budget for a single support question.
Estimated field mix
- Applied AI70%
- Backend30%
Preparing the next view without exposing private workflow data.
Design a system. Diagnose tail latency. Ship a migration. Recover a failed rollout. Pick a focused ticket or follow a project through its delivery phases.
1380 tickets · 138 projects · 26 engineering fields · Four difficulty levels
Field counts and the engineering field filter use each project's primary field. Estimated ticket labels can span multiple fields.
1380 matching tickets · Page 49 of 115
Repeated retries can exceed the budget for a single support question.
Estimated field mix
A single answer score hides whether failures came from missing documents or unsupported generation.
Estimated field mix
A document grant is revoked after its chunks have been cached.
Estimated field mix
A prototype can sound ready for unrestricted customer support despite its small synthetic corpus.
Estimated field mix
Empty strings currently mean both absent values and extraction failures.
Estimated field mix
A corrected document is uploaded under the same filename and the old result appears current.
Estimated field mix
The provider returns a supplier address that appears nowhere in the document.
Estimated field mix
Binary floating point produces an apparent mismatch on an otherwise consistent invoice.
Estimated field mix
An invoice note contains instructions to mark every field verified.
Estimated field mix
Two upload retries consume duplicate provider budget and occasionally attach the older result to the newer run.
Estimated field mix
A large upload queue can exceed the tenant's configured processing budget.
Estimated field mix
Staff corrections overwrite the extracted values, making later disagreement impossible to investigate.
Estimated field mix
138 matching projects · Page 2 of 12
Repair public-service booking across keyboard use, zoom, timeouts, and changing availability.
Improve navigation, text adaptation, annotations, and revision recovery in an internal document reader.
Build a bounded live coordination room with ordered events, reconnect recovery, and clear authority.
Reconcile synthetic vehicle locations, assignment changes, and stream interruptions in an operations dashboard.
Build a local release assistant that prepares reviewable plans and survives interrupted release steps.
Shorten a local monorepo check loop while retaining correctness when inputs, dependencies, or tools change.
Build a deterministic checkout regression suite around pricing, accessibility, payment failures, and isolated test data.
Create a local webhook laboratory that reproduces duplicates, disorder, signature failures, and interrupted delivery.
Build a retrieval workflow that respects document access, cites exact revisions, and declines unsupported answers.
Build a routing assistant that suggests queues, validates model output, and preserves accountable human corrections.
Build a vendor inventory connector with stable identity mapping, resumable ingestion, reconciliation, and tenant-safe operations.
Build a calendar booking workflow with time-zone rules, conflict handling, idempotent provider calls, and safe reconnect behavior.
Practice scoped changes, keep a portable implementation and verification record, and learn to explain operational tradeoffs. Choose a ticket whose prerequisites you can provide.
Use realistic work to structure onboarding, internal practice, and conversations about engineering decisions. Each project names the delivery benefit. Agree scope and compensation before requesting company-specific work.
CSV contains one row per ticket. Map fields and issue types in your tracker; project grouping and dependency keys are descriptive. JSON preserves the complete project structure. These downloads do not synchronize with Jira.