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.
60 matching tickets · Page 5 of 5
The provider's callbacks are delayed, but frequent polling consumes the request budget.
Estimated field mix
Support needs to recover a calendar without deleting local reservations.
Estimated field mix
Provider A returns accepted plus a request ID; provider B returns queued with a nested reference. The existing mapper calls both delivered, even though neither acknowledgement confirms a recipient received the notice.
Estimated field mix
Pattern topics
Rescheduling logic imports provider B's request object and recognizes its numeric error codes. A provider SDK change now forces changes in domain tests that never make a network request.
Estimated field mix
Pattern topics
An invalid synthetic recipient passes provider selection and fails differently for A and B. Another path checks the notification preference only after the stub has already accepted the request.
Estimated field mix
Pattern topics
ReminderEmailProviderA and CancellationEmailProviderA have matching ProviderB subclasses. Adding a third notice type is multiplying classes even though formatting and transport are independent choices.
Estimated field mix
Pattern topics
Adapter A logs full payloads while B logs nothing on exceptions. The team cannot compare local attempt outcomes without exposing synthetic recipient and notice content in generic logs.
Estimated field mix
Pattern topics
Every scheduling handler must validate, format, select an adapter, initialize telemetry, call send, and map the result in the right order. One handler skips validation and another catches all failures as accepted.
Estimated field mix
Pattern topics
A transparent Proxy automatically repeats any timed-out call. The local stub can accept a notice and drop the response, so the hidden retry records two accepted deliveries while the application sees one success.
Estimated field mix
Pattern topics
Provider B returns transport failures for every synthetic request. Callers continue spending the full timeout on each attempt even though the service needs a short recovery window.
Estimated field mix
Pattern topics
Twenty stalled B requests consume the module's shared work pool. A's immediate responses cannot start, and callers keep adding pending requests until memory grows.
Estimated field mix
Pattern topics
The breaker, queue, telemetry, and adapter work in isolation, but a half-open probe can expire while queued and leave the circuit stuck. Another wrapper order records circuit-open rejections as actual provider attempts.
Estimated field mix
Pattern topics
6 matching projects · Page 1 of 1
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.
Reconcile local order state with a simulated provider under duplicate and delayed delivery.
Keep customer records consistent across a local application and a simulated CRM.
Reconcile availability and event changes across a scheduling app and a local calendar provider.
Support two incompatible notification providers while keeping domain decisions, instrumentation, and overload behavior explicit.
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.