2 min lesson
Quantify in the units a platform team respects
Talk this through in your own words. "You're telling an ingestion-scaling story. Which Result sentence is strongest for this role?" Finish with the next move.
Step 1 of 2
Quantify in the units a platform team respects
- Weak result
- "Made ingestion more reliable"
- Platform-grade result
- "Cut bronze ingestion failures from ~12/week to under 1, with a 15-minute freshness SLO"
- Weak result
- "Reduced our data costs"
- Platform-grade result
- "Compaction and Z-ordering, which sorts related rows together, dropped storage 40% and query cost ~30% at 800TB"
- Weak result
- "Scaled the pipeline"
- Platform-grade result
- "Took ingestion from ~200M to ~3B events/day on the same Dagster footprint"
- Weak result
- "Helped the data team"
- Platform-grade result
- "Turned a recurring backfill request into a self-serve partition the team runs themselves"
| Weak result | Platform-grade result |
|---|---|
| "Made ingestion more reliable" | "Cut bronze ingestion failures from ~12/week to under 1, with a 15-minute freshness SLO" |
| "Reduced our data costs" | "Compaction and Z-ordering, which sorts related rows together, dropped storage 40% and query cost ~30% at 800TB" |
| "Scaled the pipeline" | "Took ingestion from ~200M to ~3B events/day on the same Dagster footprint" |
| "Helped the data team" | "Turned a recurring backfill request into a self-serve partition the team runs themselves" |
Replace adjectives with a number and its unit: events/day, TB, minutes or dollars. These figures are samples, so use your own real ones.
Prepare two stories that mirror the charter exactly. One "I was the first / I built it from scratch" story: the founding-engineer signal. One "I turned recurring stakeholder pain into a self-serve primitive" story: the platform-as-product signal. If you only prep one, prep the from-scratch one, because that's the role.
"Our analytics ran on cron-driven Spark jobs with no ownership: ~2B events/day, no SLAs, no lineage and a Slack channel full of 'is the data fresh?'. Nobody had defined what good looked like, so I did. I wrote a bronze/silver/gold contract, set up Dagster software-defined assets with freshness checks and a 15-minute freshness SLO. After two quarters, ingestion failures went from about a dozen a week to under one and the 'is it fresh' questions stopped because the asset graph answered them. If I redid it, I'd have shipped lineage before the gold layer, not after. We debugged blind for a month."
Interviewers tend to read reasoning over heroics. "I pulled three all-nighters and saved the launch" can signal fragile process. Show the trade-off you reasoned through, cost against reliability and speed, and the durable fix you left behind.