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 65 of 115
The team must decide whether every service implements egress checks or shares a constrained gateway.
Estimated field mix
A temporary import source should not become a permanent wildcard allowlist entry.
Estimated field mix
Support receives raw traces containing request payloads and personal hostnames.
Estimated field mix
The client log shows resolved addresses but not which one it attempted.
Estimated field mix
An unreachable IPv6 address delays a working IPv4 connection until a long timeout.
Estimated field mix
Small requests succeed while larger uploads stall without an application response.
Estimated field mix
Certificate failures on one network are blamed on the origin service.
Estimated field mix
The same service name maps differently in two authorized network contexts.
Estimated field mix
Running the diagnostic tool triggers the client's normal retry loop and floods the local test endpoint.
Estimated field mix
A new connection policy appears faster because the report excludes failed IPv6 attempts.
Estimated field mix
Support needs a useful report without raw packet payloads.
Estimated field mix
Support scripts force every connection failure into a known cause.
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.