The payment-risk cutover trades a fixed retirement date against proof that rare events preserve exposure balances.
The customer needs to end parallel Teradata operations, while risk control needs evidence that duplicate and late events do not change governed results.
Who you’d be doing this for
“Risk asked why two accounts moved after close, and I can’t point to one trusted replay yet.”
Babatunde Nwachukwu · Payment Risk Data Engineer
Operates the datasets that risk analysts use for daily exposure and exception reporting.
What is at stake
A few duplicate and late events change account balances even though daily totals match. You must weigh the retirement deadline against evidence that risk reporting stays trustworthy.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- retirement deadline vs account-level proof
- parallel-run cost vs controlled migration scope
- streaming freshness vs reconciliation certainty
- production access vs audit evidence
Why Databricks
Lakeflow pipelines must carry governed payment-risk data from legacy warehouse workloads into production operations without leaving customer teams dependent on parallel systems.
Written with these in mind
Not your kind of problem? 107 more at Databricks, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.