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 31 of 115
A design request says uploads should be instant but does not separate transfer time from extraction completion.
Estimated field mix
The first sketch lets the API parse uploaded documents and write arbitrary worker status into the upload row.
Estimated field mix
The team is choosing whether large document bytes should pass through the API or go directly to controlled object storage.
Estimated field mix
A retry currently moves a completed document back to processing because delivery events are mistaken for authoritative transitions.
Estimated field mix
An accepted upload can be stranded if the API commits metadata and crashes before calling the processing provider.
Estimated field mix
A provider times out after accepting work; blindly retrying may launch duplicate expensive processing.
Estimated field mix
Product wants frequent status updates, but the proposal polls the external parser on every customer request.
Estimated field mix
The design has no answer for how long a backlog takes to drain after the parser is unavailable for an hour.
Estimated field mix
Stakeholders disagree about queueing because one alternative is evaluated only on its happy path.
Estimated field mix
An existing local prototype parses in its request handler; the team needs an incremental path to the agreed boundary.
Estimated field mix
The regional-read proposal treats a public tracking estimate and an address-change confirmation as equally cacheable.
Estimated field mix
A proposal promises a faster dashboard without separating network time, database time and sequential request dependencies.
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.