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 1 of 12
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.
Ingest delayed, duplicated, and corrected parcel events into an explainable tracking timeline.
Replace a fragile daily sales query with versioned, reconcilable warehouse metrics.
Build a release workflow that can distinguish a healthy process from a safe application version.
Operate an asynchronous document pipeline through retries, poison jobs, worker loss, and tenant bursts.
Make partner access explicit across list APIs, batch commands, invitations, cached sessions, and exports.
Introduce explicit credential versions, safe rotation, redacted diagnostics, and recovery for a webhook integration.
Repair queue navigation, reply composition, and agent handoffs in a customer support workspace.
Make purchase requests accurate, recoverable, and reviewable across revisions.
Keep assigned maintenance work usable without reception and reconcile changes safely when connectivity returns.
Make saved journeys, departures, and service alerts useful when feeds or device permissions change.
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.