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 81 of 115
Renaming an attachment currently moves its physical file and breaks another reference. Store display names on references.
Estimated field mix
Equal bytes across organizations share observable lookup results. Restrict deduplication to the tenant boundary.
Estimated field mix
Documents can attach blobs before upload verification ends. Require available status before creating a reference.
Estimated field mix
Cleanup deletes bytes immediately when count reaches zero, leaving no recoverable decision record. Add a pending-deletion state.
Estimated field mix
A document attaches a blob while cleanup deletes its file. Coordinate reference admission and deletion eligibility.
Estimated field mix
Permission errors are swallowed and metadata says Deleted while bytes remain. Persist retryable failure state.
Estimated field mix
A process dies after file removal but before metadata commit. Recovery must distinguish absent bytes from an untouched blob.
Estimated field mix
The sweeper repeatedly scans the full blob table. Add indexed bounded batches without skipping concurrent tombstones.
Estimated field mix
Cleanup counts only current document references and breaks retained versions. Include every retained reference authority.
Estimated field mix
Operators report savings from tombstoned bytes that still exist. Separate eligible, attempted and acknowledged removal totals.
Estimated field mix
Delimiter-based records fail when values contain newlines. Add a length-prefixed binary record format.
Estimated field mix
Empty buffers are interpreted as Not found. Return explicit presence separate from byte length.
Estimated field mix
138 matching projects · Page 6 of 12
Reconcile local order state with a simulated provider under duplicate and delayed delivery.
Keep customer records consistent across a local application and a simulated CRM.
Reconcile availability and event changes across a scheduling app and a local calendar provider.
Define customer-facing reliability indicators and actionable budget policies.
Diagnose and recover delayed background work without duplicating effects.
Verify that database and object-store backups can reconstruct a coherent service.
Protect essential reads when optional workloads saturate a service.
Prepare a small service for a predictable launch surge through capacity and dependency review.
Make storage growth and transfer costs inspectable without compromising retained records.
Validate infrastructure changes as bounded plans with drift and recovery context.
Replace static service credentials with bounded workload identity and tested rotation.
Promote immutable application artifacts through environments with inspectable provenance.
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.