AI / ML EngineerFoundationalAug 6, 2026
Repair fuel-station merchant resolution accuracy
Merchant names often look stable until payment descriptors change underneath them.
Consistency in reporting can pull against the need to recognize legitimate new transaction patterns.
“I need to know whether our fuel spend is actually where the report says it is.”
Konjit Ngugi · Regional Controller
Oversees card spend and reconciliation for a multi-site field-services company.
What pulls against what
- fast recovery vs. generalizable matching
- merchant coverage vs. false merges
- real-time latency vs. richer features
What is at stake
Incorrect merchant identities distort spend reporting and make controls less dependable for field teams
Why Ramp
At Ramp, this can matter because merchant-level visibility often underpins spending decisions.
Written for
Production ML engineerPayments data scientistApplied machine-learning practitioner
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.