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 50 of 115
Document-level success hides whether the extractor frequently invents totals or simply leaves them for review.
Estimated field mix
Reviewers need a consistent way to handle ambiguous dates and unsupported fields.
Estimated field mix
Alerts and deployment records disagree about timestamp formats.
Estimated field mix
A related-service lookup exposes another team's restricted incident notes.
Estimated field mix
A broad query attempts to retrieve days of raw logs.
Estimated field mix
An error message contains text requesting privileged configuration reads.
Estimated field mix
The generated summary invents a deployment that never happened.
Estimated field mix
A latency spike follows a deployment but also overlaps a dependency outage.
Estimated field mix
An older slow response overwrites the summary after a recovery event arrives.
Estimated field mix
Several operators refresh the same incident and trigger duplicate model calls.
Estimated field mix
The team needs a useful assessment that does not equate fluent prose with correct incident analysis.
Estimated field mix
Operators must continue handling incidents when the assistant is down.
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.