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.
50 matching tickets · Page 3 of 5
A malformed timestamp makes the ingestion job fail with a stack trace and no indication of the source row.
Estimated field mix
A device sends a corrected cumulative reading two days late; a blind upsert destroys the value used in yesterday's report.
Estimated field mix
The hourly aggregate closes by arrival time and quietly ignores a delayed batch from an offline device.
Estimated field mix
Object storage contains yesterday's batches, but dashboard totals are low and no worker currently owns the missing jobs.
Estimated field mix
A conversion fix requires rebuilding a week of energy totals without obscuring what the previous dashboard showed.
Estimated field mix
A site with no recent readings is displayed as consuming zero energy, misleading dashboard consumers.
Estimated field mix
A report doubles subscription movement when a contract has two invoice lines in the same month.
Estimated field mix
A late payment makes the recurring-revenue chart dip even though no subscription changed.
Estimated field mix
A partner renamed subscription_id and the daily transformation published an empty table successfully.
Estimated field mix
Historical enterprise revenue changes whenever sales updates a customer's current segment.
Estimated field mix
The incremental model filters only creation time, so a corrected subscription end date never reaches the mart.
Estimated field mix
Deleting a cancelled subscription from the source erases the churn event from the report.
Estimated field mix
5 matching projects · Page 1 of 1
Ingest delayed, duplicated, and corrected parcel events into an explainable tracking timeline.
Replace a fragile daily sales query with versioned, reconcilable warehouse metrics.
Ingest compressed telemetry with explicit quarantine, lineage and replay.
Model subscription movement with explicit grains, revisions and data contracts.
Replicate a bounded preference dataset while preserving deletion and ordering semantics.
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.