hi, I’m Richard
Technical Product Champion
and Quality Advocate.
12+ years keeping customers successful on fintech platforms — troubleshooting what broke, communicating clearly under pressure, and building systems so the same problem never reaches a customer twice.
(Scroll down & explore)
(Take a closer look at selected work)
selected work
- (01) Turning customer reports into permanent fixesCellulant · Senior QA Engineer in Test · 2025–now
- (02) An automation pipeline that cut customer-reported incidents 30%AZA Finance · QA Engineer · 2020–2024
- (03) Scaling a service desk without scaling headcountTracom Services · Service Management Specialist · 2017–2020
12+
Years across QA, support & service management
−30%
Customer-reported incidents via prevention pipeline (AZA)
−20%
Recurring production defects in 6 months (Cellulant)
−70%
Issue resolution turnaround (Tracom)
(Who am I)
Troubleshooting. Prevention. Retention.
I’m a Nairobi-based support operations and QA engineer with over ten years of experience across fintech and enterprise platforms — from service desks and enterprise go-lives to payments and FX platforms where a bug is someone’s money in flight.
My title says QA, but the work has been about converting customer pain into prevention — which is retention work under a different name. Every customer report gets traced to a root cause, and every root cause gets a system so it never reaches a customer twice.
(Notes from the field)
support writing
- (01) Defect leakage is a retention metricTickets, bugs, churn risk — same number, three costumes
- (02) Reproducing the unreproducibleWhen a customer’s bug won’t reproduce: observability, not persistence
- (03) Scaling support without scaling headcountEscalation rate as the KPI that predicts survival
- (04) What a job post on Instagram taught me about craftCraft is a trust signal — and a job post is a product demo
- (05) The step nobody wrote downA firewall, an API error, and the gap where support lives
(Contact details)
let’s prevent something
together.
Whether it’s a role, a tricky customer issue, or a stubborn bug that won’t reproduce — I’d like to hear about it.
Nairobi, Kenya (EAT, UTC+3) · comfortable with distributed teams across time zones