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 2 of 5
An order with three lines and two refunds becomes six joined rows. The daily mart counts each captured amount several times although the ledger is correct.
Estimated field mix
A 23:30 Los Angeles sale appears on tomorrow's report because the mart groups UTC dates. Merchants cannot reconcile their register totals.
Estimated field mix
M-17 upgrades from Starter to Growth in June. Joining today's merchant record moves all earlier revenue into Growth and rewrites quarterly comparisons.
Estimated field mix
The nightly job filters on order creation date. A refund posted today against a six-week-old order never reaches the mart.
Estimated field mix
A noon backfill finishes after the nightly job. Its older snapshot overwrites May's newer partition and removes refunds received at 18:00.
Estimated field mix
A transformation passes SQL syntax checks while dropping one currency partition. The dashboard refresh succeeds and hides the revenue gap.
Estimated field mix
Removing merchant_id from an export request returns every merchant's sales because the support route passes filters directly to an analyst-wide query.
Estimated field mix
After a mart correction, May net sales changes and analysts need to know which rows moved. Build a synthetic before/after comparison and quantify the delta instead of assuming a target percentage.
Estimated field mix
Operators see a failed file name but cannot identify the original bytes or the parser version used.
Estimated field mix
A tiny compressed batch expands far beyond the ingestion worker's memory budget.
Estimated field mix
Two device models emit watt-hours and kilowatt-hours under the same field name.
Estimated field mix
A process dies after inserting rows but before marking the file complete; replay doubles reported usage.
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.