Engineering task library · Version 5 Work that feels like work. 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
Practice briefs Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Completing a ticket does not issue a credential.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Pattern topics identify design choices to practice. Read the ticket's acceptance criteria and justify the simplest suitable approach. Tags are not capability or ownership evidence; an untagged ticket has no curated pattern topic assigned.
Field counts and the engineering field filter use each project's primary field. Estimated ticket labels can span multiple fields.
Backend 60 Data engineering 50 Platform engineering 50 Security 50 Frontend 60 Mobile 50 Developer tooling 50 Quality engineering 50 Applied AI 50 Integrations 60 Real-time systems 50 Accessibility 50 System design 60 Performance engineering 50 Database engineering 50 Distributed systems 60 Site reliability 50 Cloud infrastructure 50 Networking 50 API design 50 Storage systems 50 Compiler and language tooling 60 Embedded and edge 50 Privacy engineering 50 Systems programming 60 DevOps 60 CFRAME-107 Bug Expert
Sequence 0 after 65535 is rejected as old, while delayed frames sometimes overwrite current readings. Define a bounded modular-order window.
Estimated field mix
Embedded and edge 50% Networking 30% Distributed systems 20% An emulated device-link framing libraryCFRAME-108 Task Advanced
Parsing outruns downstream processing and queues grow indefinitely. Bound accepted-frame buffering.
Estimated field mix
Embedded and edge 40% Performance engineering 40% Networking 20% An emulated device-link framing libraryCFRAME-109 Bug Intermediate
Bytes from a previous connection combine with a new header after reconnect. Clear session-owned parsing state.
Estimated field mix
Embedded and edge 60% Networking 40% An emulated device-link framing libraryCFRAME-110 Chore Intermediate
Debug logs contain complete sensor payloads even when only corruption rates are needed. Emit bounded categories.
Estimated field mix
Embedded and edge 40% Site reliability 30% Privacy engineering 30% An emulated device-link framing libraryCTIMER-101 Bug Foundational
Moving the emulator wall clock backward extends a running job forever. Measure elapsed timeout against monotonic time.
A deterministic edge-job scheduler emulatorCTIMER-102 Task Foundational
A zero interval creates an immediate callback loop. Enforce a documented supported interval range.
A deterministic edge-job scheduler emulatorCTIMER-103 Task Intermediate
Long cache refreshes cause catch-up bursts because scheduling alternates between fixed-rate and fixed-delay behavior. Choose fixed-delay for this job class.
A deterministic edge-job scheduler emulatorCTIMER-104 Bug Advanced
A cancelled timer callback runs after a replacement job is registered. Bind callbacks to registration generation.
A deterministic edge-job scheduler emulatorCTIMER-105 Task Advanced
Cache refresh and cleanup run simultaneously and contend for the same fixture directory. Add scoped single-flight admission.
Estimated field mix
Embedded and edge 70% Performance engineering 30% A deterministic edge-job scheduler emulatorCTIMER-106 Story Intermediate
A failed maintenance job retries forever and hides the original error. Add attempt limits and a terminal visible outcome.
Estimated field mix
Embedded and edge 70% Site reliability 30% A deterministic edge-job scheduler emulatorCTIMER-107 Bug Expert
Restarting after a long pause runs every missed interval at once. Persist minimal schedule state and coalesce missed runs.
Estimated field mix
Embedded and edge 70% Storage systems 30% A deterministic edge-job scheduler emulatorCTIMER-108 Task Advanced
Frequent urgent cache checks prevent cleanup from ever running. Add bounded fairness to the ready queue.
Estimated field mix
Embedded and edge 60% Performance engineering 40% A deterministic edge-job scheduler emulatorCSEARCH / Frontend Build navigable search and result recovery for a public directory.
CFORM / Frontend Repair conditional fields, draft recovery, and deliberate submission.
CROUTE / Mobile Keep synthetic visit notes reliable through offline use and process restarts.
CDOWN / Mobile Manage resumable public-content downloads and safe local playback state.
CLINK / Mobile Handle deep links, expired sessions, and interrupted navigation using local identity stubs.
CCAL / Accessibility Make scheduling interactions operable with keyboard, magnification and assistive technology.
CTABLE / Accessibility Give charts, sortable tables and exports equivalent understandable information.
CMODAL / Accessibility Make dialogs, menus, toasts and nested workflows predictable across input methods.
CPRES / Real-time systems Model ephemeral team presence with expiry, reconnects and scoped fan-out.
CLIVE / Real-time systems Keep a synthetic service-status board ordered and replayable over server-sent events.
CAUCT / Real-time systems Coordinate expiring seat holds and live availability in a local simulation.
COBJS / Storage systems Build a local multipart-upload coordinator with scoped identities and integrity checks.
Take the brief into your own workflow. For engineers Practice scoped changes, keep a portable implementation and verification record, and learn to explain operational tradeoffs. Choose a ticket whose prerequisites you can provide.
For companies 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.