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 90 of 115
A slow-started job is blamed on execution time because metrics combine queue delay and work duration. Separate them.
Estimated field mix
Engineers cannot explain why a job was skipped after restart. Export bounded state transitions without running jobs.
Estimated field mix
The byte-array stub permits writes that real flash-like storage would reject. Declare and enforce the chosen emulator model.
Estimated field mix
Truncated synthetic records are indistinguishable from valid short payloads. Add explicit length and integrity fields.
Estimated field mix
Retried uploads mint new event IDs and duplicate accepted readings. Persist identity with the original record.
Estimated field mix
A record appears readable before its body finishes writing. Introduce a commit-marker protocol compatible with the emulator.
Estimated field mix
Startup stops at partial data and loses earlier committed events. Scan the valid committed prefix conservatively.
Estimated field mix
Page wrap overwrites unacknowledged events. Separate writable capacity from reclaimable pages.
Estimated field mix
A cut during page-header activation leaves two pages claiming to be newest. Resolve generations through a declared ordering rule.
Estimated field mix
The gateway erases a page after sending bytes, before the receiver acknowledges them. Gate reclamation on durable acknowledgements.
Estimated field mix
A metadata write for every status poll causes unnecessary emulated erase work. Batch only nonauthoritative counters.
Estimated field mix
Debugging currently boots the journal and may erase pages. Add a read-only page inspector.
Estimated field mix
138 matching projects · Page 7 of 12
Manage short-lived review environments with bounded resources and safe cleanup.
Move a service endpoint while accounting for caches, negative answers, and resolver behavior.
Correct proxy behavior for trusted forwarding, connection reuse, and streaming cancellation.
Operate authenticated service connections through expiry, rotation, and trust changes.
Fetch approved external resources through a bounded provider-neutral network boundary.
Diagnose address-family, packet-size, and routing failures in an authorized local lab.
Evolve a partner API with explicit compatibility, deprecation, and client migration contracts.
Design bulk record imports with explicit operation state, item errors, and recovery semantics.
Expose a changing catalog through bounded filters, stable cursors, and explicit consistency.
Design scoped partner credentials with revocation, safe errors, and client lifecycle controls.
Expose event subscriptions with immutable envelopes, bounded delivery, and safe replay.
Make spreadsheet-like stock editing predictable across validation and concurrent updates.
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.