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.
60 matching tickets · Page 4 of 5
A policy update changes the cancellation deadline for appointments sold under yesterday's terms.
Estimated field mix
A simulated outage leaves holds whose expiry jobs were never dispatched; operations needs a bounded reconciliation command.
Estimated field mix
A failed reschedule currently returns the target booking object, exposing the name and contact information of its owner.
Estimated field mix
Checkout commits successfully, then the connection closes. A customer retries while the expiry worker is also running.
Estimated field mix
Sales requested a formula textbox; evaluating arbitrary expressions would make quote behavior difficult to bound and audit.
Estimated field mix
Two promotions match the same part and the chosen discount depends on database return order.
Estimated field mix
A promotion with its end before its start passes draft review and can never apply.
Estimated field mix
A buyer accepts a quote after a promotion edit and receives a different total from the amount previously displayed.
Estimated field mix
An unusually broad rule set makes checkout evaluate thousands of predicates per item and blocks unrelated quotes.
Estimated field mix
A shared cache returns one customer's negotiated rate to another account requesting the same product list.
Estimated field mix
Sales wants to explain an unmet minimum quantity, but the current debug endpoint exposes every account's price rules.
Estimated field mix
A promotion revision fixes bulk orders but may unintentionally discount small carts.
Estimated field mix
6 matching projects · Page 1 of 1
Reconcile payment settlements against invoice records without hiding money movement or retry failures.
Build reservation and allocation behavior for a small retailer with two warehouses and unreliable checkout retries.
Resolve effective entitlements across scheduled and immediate plan changes.
Keep scarce appointment slots consistent through holds, confirmations and cancellation.
Version promotional pricing rules and make every applied discount explainable.
Evolve a quoting module as partner contracts diverge, while keeping calculations reproducible and abstractions proportional to the problem.
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.