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 82 of 115
Startup trusts offsets without reading record boundaries. Rebuild the index only from validated records.
Estimated field mix
Put returns success before the log flush completes. Define durable acknowledgement using the filesystem adapter.
Estimated field mix
A crash leaves a partial final record and startup refuses every key. Recover the valid prefix conservatively.
Estimated field mix
Rebuilding the index resurrects deleted keys because deletion only changed memory. Append durable tombstones.
Estimated field mix
A multi-key update survives restart with only half its changes. Add one bounded batch commit marker protocol.
Estimated field mix
Repeated updates grow the log. Write a compacted generation from one consistent logical view.
Estimated field mix
Crashing during compacted-file replacement leaves no selected log. Add a recoverable generation manifest.
Estimated field mix
Support has no way to identify damaged record offsets safely. Add a read-only inspection command.
Estimated field mix
Backup folders contain unnamed files with no declared schema. Add a bounded manifest describing required objects.
Estimated field mix
A backup includes partial uploads and later calls them missing documents. Inventory only committed archive references.
Estimated field mix
Copy completion alone marks backup success. Stream verification of every required object before success.
Estimated field mix
A document changes while backup runs and the manifest references an uncopied blob. Define one consistent capture boundary.
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.