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 39 of 115
A query endpoint interpolates client-provided JSON paths and operators into SQL.
Estimated field mix
The database query for arrays and null values differs subtly from the API contract, making support reports inconsistent.
Estimated field mix
New readers assume every document has a valid owner and UTC creation instant, but quarantined legacy rows still violate that assumption.
Estimated field mix
The team wants to remove legacy JSON fields immediately after switching reads, which could break old clients during a rollback.
Estimated field mix
The scheduler table stores only owner name and expiry, so an old owner can appear identical to a later process with the same name.
Estimated field mix
Two instances disagree about lease expiry because their local clocks differ by several seconds.
Estimated field mix
The design adds a lease but assumes every downstream operation automatically knows whether its caller is still leader.
Estimated field mix
Two instances see an expired lease and both believe they became the active scheduler.
Estimated field mix
A delayed renewal from an earlier process extends the newest owner's lease row while reporting success to the stale process.
Estimated field mix
A scheduler pauses past expiry, then resumes a previously prepared plan after another instance has taken over.
Estimated field mix
A new leader repeats the current maintenance period and creates a second plan for the same logical occurrence.
Estimated field mix
A scheduler renews its lease while stuck on one task, so the status page incorrectly reports healthy processing.
Estimated field mix
138 matching projects · Page 10 of 12
Stage, validate and switch synthetic software images in an A/B slot emulator.
Deliver and acknowledge bounded synthetic configuration changes through a local gateway emulator.
Explain and reduce quote latency under a mixed workload without weakening pricing correctness.
Tune a tenant-scoped PostgreSQL inbox using plans, representative distributions and reversible changes.
Investigate browser loading, rendering and interaction costs while preserving usable scheduling workflows.
Make a bounded catalog import stream, recover and report progress under explicit resource limits.
Measure cache value, prevent refill storms and bound staleness without hiding origin failures.
Implement explicit retention clocks, protected exceptions and bounded purge recovery.
Coordinate scoped profile removal, derived-store cleanup and truthful completion reporting.
Build a scoped asynchronous export, redact unrelated records and expire its downloadable artifact.
Version user choices, enforce purpose-specific dispatch checks and recover delayed preference updates.
Build an allowlisted telemetry boundary, useful aggregates and controlled diagnostic access.
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.