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 41 of 115
A tablet retries saved edits with new request IDs, so the server creates duplicate inspection findings.
Estimated field mix
A contractor loses project access while offline, then reconnects with a batch of previously authorized edits.
Estimated field mix
The sync service treats every concurrent change as either a blanket overwrite or a blanket conflict.
Estimated field mix
The server applies a change, loses the response, then reapplies it after the tablet reconnects.
Estimated field mix
Two inspectors change a safety finding from different base revisions and last-write-wins hides one observation.
Estimated field mix
A reviewer resolves a conflict while a third offline proposal arrives, silently discarding the new observation.
Estimated field mix
A tablet that missed a deletion resubmits its old finding and recreates content the team intentionally removed.
Estimated field mix
An inspection references a photo before its interrupted upload completes, producing broken evidence links in the field report.
Estimated field mix
The tablet stores a local cursor before receiving server confirmation and skips updates after a crash.
Estimated field mix
A tablet says all synced even though uploaded changes contain unresolved conflicts and a pending attachment.
Estimated field mix
A configuration change adds a checker while a run is in progress, so the completion predicate changes halfway through.
Estimated field mix
A timed-out policy checker returns an empty findings list, which the aggregator interprets as passed.
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.