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 3 of 5
The email provider times out after accepting a request; retrying blindly sends the same message twice.
Estimated field mix
One workspace event targets 50,000 hypothetical members and the proposed transaction attempts to create every delivery row at once.
Estimated field mix
Marking an in-app alert read currently suppresses an unrelated email retry by changing one shared status column.
Estimated field mix
A launch generates a burst of alerts, but the architecture plan ignores provider quotas and retry traffic.
Estimated field mix
A user disables a channel while thousands of queued intents wait for provider quota, exposing ambiguous preference timing.
Estimated field mix
The launch plan describes exactly-once delivery and confirmed readership even though the provider contract supports neither.
Estimated field mix
The design says all audit history must be instantly searchable, but reviewers usually inspect the last week and rarely retrieve older cases.
Estimated field mix
A budget proposal counts raw event bytes but omits index, replica and manifest overhead.
Estimated field mix
The team proposes a new search cluster before checking whether bounded PostgreSQL search and object retrieval satisfy the workload.
Estimated field mix
An exported audit file has no trusted count or content identity, so operators cannot tell whether a partial upload is complete.
Estimated field mix
A search result is edited directly to correct an event, creating a version of history absent from the source archive.
Estimated field mix
An audit search hit contains a raw object key; clients can request other tenants' segments by changing that key.
Estimated field mix
6 matching projects · Page 1 of 1
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.
Evolve a long-lived account module while preserving tenant boundaries, client contracts, and a credible route back from partial migration.
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.