Lead systems developer in South Africa. I work across claims and assistance platforms, the integrations that feed them, and the reporting people make decisions from.
Most of my job is finding where the same thing lives in five places, and turning it into one.
Designing a core platform that sits above two established claims systems and gives them shared master records: one record per supplier, one claim spine for cases that move between systems, one identity per person, and one definition of every scheme and product.
SQL Server, cross-database modelling, data reconciliation
A multi-screen WhatsApp Flow that takes a policyholder from first notice of loss to a complete claim: peril, incident details, damage, address lookup and a summary to confirm. Backed by an encrypted data-exchange endpoint and a webhook that lands submissions straight into the claims system.
WhatsApp Business API, C# / ASP.NET Core, PHP, Google Places
A reporting set covering volume and spend, turnaround against SLA, quality and rejections, and panel compliance, built on a verified crosswalk between two supplier masters. Validating against live data caught a satisfaction score that was understated by more than twenty points.
T-SQL, Power BI
Took a learning-management web app from prototype to production on Windows servers, with a repeatable deploy script, and designed the academy's sub-brand identity from the parent brand.
React, Vite, PHP API, SQL Server, IIS, PowerShell
Moved a production IIS server hosting thirteen application pools, resolving certificates, missing server modules and per-site permissions along the way, and scripted the permissions so the next migration is one command.
IIS, ARR, PowerShell
Schema dumps and documentation drift. Before I conclude a column doesn't exist or a join is right, I test it against the real data.
Half of good reporting is knowing what a value means. "Not rated" stored as 0 will quietly wreck an average if nobody asks.
If I had to fix it by hand once, the next person gets a script, a skill file, or a query they can run without me.
When a snake turns up in a garage, a garden or a pool pump, I catch it and move it somewhere it can get on with its life.
Most of the job is calm handling and keeping people at a safe distance. The rest is explaining that the snake wants to be there even less than they want it there.
I play, and lately I build. My latest is a co-op 3D game about raking up every leaf on a property, in a single HTML file, with a small LAN server so a few people on the same network can play together.
It turns out game physics and claims data have something in common: both look fine until someone pokes at the edge cases.