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 20 of 115
A connector has not completed a refresh for six hours, yet its status is green because the last HTTP request succeeded. Define freshness from completed ingestion checkpoints.
Estimated field mix
The vendor replaces quantity with availableQuantity in its next API version. Demonstrate that the connector fails visibly, can resume with a new adapter, and preserves the old run history.
Estimated field mix
A booking form submits 01:30 on a daylight-saving fallback day without an offset. Store an instant plus display zone and explicitly handle ambiguous or nonexistent local times.
Estimated field mix
Two overlapping provider events produce a false free gap between them. Normalize busy intervals and apply the agreed booking duration and buffer.
Estimated field mix
A free/busy request times out and the connector treats an empty response as an empty calendar. Distinguish confirmed free time from unknown availability.
Estimated field mix
Two clients load the same available slot and submit together. Add an internal reservation transaction and a final provider availability check before creating an event.
Estimated field mix
The calendar provider creates the appointment but drops its response. Retrying with a new request identifier currently creates a second event. Preserve creation identity and reconcile uncertainty.
Estimated field mix
An agent reschedules a booking from an old browser tab after a colleague already moved it. Add revision-aware rescheduling and retain the original slot until the new operation is settled.
Estimated field mix
A client double-clicks Cancel while a support agent cancels from another screen. The connector must converge on one cancellation without allowing another tenant to cancel by event ID.
Estimated field mix
Ten jobs receive token-expired at once, all refresh, and a rotated token is overwritten by an older response. Serialize refresh by connector identity and persist credential revisions safely.
Estimated field mix
Provider notifications arrive twice, then a subscription expires and updates stop. Treat notifications as sync hints and maintain a separate reconciliation cursor and subscription deadline.
Estimated field mix
After reconnecting an account, operations cannot tell which bookings were created, moved, or cancelled during the outage. Build a scoped recovery list with safe identifiers and next actions.
Estimated field mix
138 matching projects · Page 4 of 12
Turn a document-processing brief into reviewable boundaries, contracts and failure probes.
Specify consistency, routing and recovery for a regional customer read experience.
Separate notification intent, delivery attempts and user-visible receipt semantics.
Choose storage, indexing and deletion semantics for a bounded audit archive.
Define fair scheduling, bounded work and recovery for a report service.
Replace a legacy customer key through additive schema changes and verified backfill.
Claim, renew and finish work without duplicate authority or stranded assignments.
Build a bounded backup inventory and rehearse restoration with consistency checks.
Make cross-organization relationships impossible through database and repository constraints.
Separate stable document fields from versioned bounded metadata and migrate safely.
Elect one active scheduler while preventing expired owners from mutating shared state.
Recover a multi-step return workflow across inspection, shipping and refund providers.
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.