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 48 of 115
Eligibility failures appear visually below the form but keyboard users receive no useful indication.
Estimated field mix
The delivery provider accepts a booking but the checkout request times out.
Estimated field mix
Automated cases miss interactions between edited addresses, browser back navigation, and refreshed quotes.
Estimated field mix
The team has thirty minutes for the release gate and cannot run every browser combination.
Estimated field mix
Reviewers cannot distinguish current results from screenshots copied from an earlier build.
Estimated field mix
The rollback plan restores code but says nothing about orders already using the new delivery model.
Estimated field mix
Two guides share a title but describe different product releases.
Estimated field mix
A highly relevant private guide appears in another tenant's search results.
Estimated field mix
Answer citations point to chunks that cannot be located in the original guide.
Estimated field mix
The model double returns a plausible answer with a nonexistent citation.
Estimated field mix
Two authorized sources disagree about the retention setting and neither is marked superseded.
Estimated field mix
A guide includes text telling the assistant to reveal other documents.
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.