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 99 of 115
A predictable artifact URL lets one member retrieve another member’s completed export.
Estimated field mix
A member signs out all sessions after an account concern, but a previously issued export link remains usable longer than the product policy allows.
Estimated field mix
Completed exports expire after a day, but failed assembly objects remain indefinitely under a different prefix.
Estimated field mix
The happy-path export looks correct, but nobody has reviewed shared records, access revocation and abandoned files together.
Estimated field mix
A single email-enabled flag suppresses booking confirmations when a member opts out of product announcements.
Estimated field mix
The database stores only the latest boolean, so support cannot tell which choice text the member saw.
Estimated field mix
An autosave race restores a checked box after the user turns it off and navigates away.
Estimated field mix
An audience list was built yesterday. A member who opted out this morning still receives the queued announcement.
Estimated field mix
An operator edits a queued campaign from a booking reminder into promotional content while retaining the original operational tag.
Estimated field mix
Preference events reach a delivery replica out of order. A delayed older opt-in restores eligibility after a newer opt-out.
Estimated field mix
The settings page promises instant cancellation even when the provider has already accepted a message that cannot be recalled.
Estimated field mix
A support page returns all members’ preference histories after checking only that the requester has any staff role.
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.