Detect static-build dependency cycles with a readable path
Recursive imports hang graph traversal. Detect cycles and return the concrete edge path.
Estimated field mix
- Compiler and language tooling60%
- Developer tooling40%
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 87 of 115
Recursive imports hang graph traversal. Detect cycles and return the concrete edge path.
Estimated field mix
Changing compiler options reuses output produced under older options. Hash normalized inputs and configuration.
Estimated field mix
Updating a shared module rebuilds it but leaves dependent pages stale. Traverse reverse dependency edges.
Estimated field mix
A failed transform writes a cache entry that future builds treat as success. Separate failure from reusable output.
Estimated field mix
Parallel transform completion changes manifest ordering and output hashes. Separate execution scheduling from canonical publication.
Estimated field mix
Readers see mixed old and new files during a build. Write a staging generation and switch a manifest pointer.
Estimated field mix
Editors emit many change events and a final delete can be swallowed by debounce. Track final invalidation intent per module.
Estimated field mix
Developers cannot distinguish cache misses from invalidation bugs. Emit structured decision reasons without source text.
Estimated field mix
Text search matches unrelated local functions named configure. Discover calls through the imported binding.
Estimated field mix
A prototype replaces examples inside strings and comments. Use syntax node kinds for candidate selection.
Estimated field mix
Spread arguments and reassigned bindings make transformation unsafe. Return explicit skipped reasons.
Estimated field mix
Wrapping arguments into an object could reorder side-effecting expressions. Preserve the old left-to-right evaluation order.
Estimated field mix
138 matching projects · Page 2 of 12
Repair public-service booking across keyboard use, zoom, timeouts, and changing availability.
Improve navigation, text adaptation, annotations, and revision recovery in an internal document reader.
Build a bounded live coordination room with ordered events, reconnect recovery, and clear authority.
Reconcile synthetic vehicle locations, assignment changes, and stream interruptions in an operations dashboard.
Build a local release assistant that prepares reviewable plans and survives interrupted release steps.
Shorten a local monorepo check loop while retaining correctness when inputs, dependencies, or tools change.
Build a deterministic checkout regression suite around pricing, accessibility, payment failures, and isolated test data.
Create a local webhook laboratory that reproduces duplicates, disorder, signature failures, and interrupted delivery.
Build a retrieval workflow that respects document access, cites exact revisions, and declines unsupported answers.
Build a routing assistant that suggests queues, validates model output, and preserves accountable human corrections.
Build a vendor inventory connector with stable identity mapping, resumable ingestion, reconciliation, and tenant-safe operations.
Build a calendar booking workflow with time-zone rules, conflict handling, idempotent provider calls, and safe reconnect 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.