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%
Loading noCV…
Preparing the next view without exposing private workflow data.
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 11 of 12
Evolve a quoting module as partner contracts diverge, while keeping calculations reproducible and abstractions proportional to the problem.
Build a bounded browser editor whose tree operations, history, subscriptions, and exports remain coherent under failures and repeated use.
Support two incompatible notification providers while keeping domain decisions, instrumentation, and overload behavior explicit.
Replace a growing set of warehouse eligibility switches with a small, bounded rule language that support can inspect and engineers can evolve.
Evolve a long-lived account module while preserving tenant boundaries, client contracts, and a credible route back from partial migration.
Coordinate return inspection, replacement stock, and refunds across controllable provider boundaries while keeping uncertain outcomes visible.
Build a bounded arena with explicit alignment, lifetime and corruption behavior.
Implement bounded scheduling, cancellation and shutdown without hidden liveness failures.
Build framed IPC, bounded buffering, process lifecycle control and restart-safe request identity.
Implement decoding, stack safety, resource budgets and compatible bytecode revisions.
Design a safe FFI contract with explicit ownership, error mapping and compatibility.
Wrap files, timers and readiness notifications with explicit partial-result and portability 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.