Climate Data Engineering
Hosted by R3i Ventures — Water & Climate
Environmental data is late, sparse and wrong in interesting ways. You will build an ingestion pipeline that survives all three, with tests, lineage and a quality contract — then hand it over to an operator who was not in the room while you built it.
Skills assessed
The six sprints
Each sprint has one named outcome. Your mentor signs it off, sends it back with written challenges, or fails it — the same three options the permanent team gets.
- W114 hrs · 3 tasks
Source archaeology
Outcome — A source profile documenting every way the feed misbehaves.
Ingest a raw week
BuildLand seven days of raw telemetry untouched.
4 hours
Profile the mess
ResearchNulls, duplicates, clock skew, unit drift — quantify each.
5 hours
Write the source profile
BuildThe document the next engineer will thank you for.
5 hours
- W214 hrs · 3 tasks
Contract & schema
Outcome — A published data contract with enforceable expectations.
Design the target schema
BuildGrain, keys, slowly-changing dimensions.
5 hours
Write expectations
BuildEncode the contract as executable checks, not prose.
5 hours
Contract review
ReviewNegotiate the contract with a downstream consumer.
4 hours
- W314 hrs · 3 tasks
Pipeline build
Outcome — An idempotent pipeline that can be re-run without fear.
Build ingestion
BuildIdempotent, replayable, with watermarking.
6 hours
Build transforms
BuildModelled layers with tests at each boundary.
6 hours
Failure drill
ReviewBreak it deliberately; document the recovery path.
2 hours
- W414 hrs · 3 tasks
Quality & observability
Outcome — Alerts that fire on real problems and stay silent otherwise.
Freshness and volume checks
BuildThresholds justified by the source profile, not guesses.
5 hours
Lineage graph
BuildEvery column traceable to a source field.
5 hours
Alert tuning
ReviewReplay two weeks of history; count false positives.
4 hours
- W514 hrs · 3 tasks
Consumer delivery
Outcome — A downstream analyst answers their question without your help.
Serving layer
BuildPublish the marts the consumer actually asked for.
6 hours
Consumer test
ReviewGive an analyst a question and watch, silently.
4 hours
Fix what you learned
BuildAct on the friction you observed, not what you assumed.
4 hours
- W614 hrs · 4 tasks
Handover
Outcome — A cold handover: the operator runs it with you on mute.
Write the runbook
BuildFailure modes, escalation, rollback.
5 hours
Cold handover drill
ReviewOperator runs an incident with you silent.
3 hours
Architecture review
PresentPresent the design and its trade-offs to a panel.
3 hours
Case study writeup
BuildPublish to your FutureFit skills passport.
3 hours
Ready to take the track?
Applications close two weeks before the Autumn 2026 cohort starts.