I like the problems that only show up under load

I'm a full-stack engineer in Nairobi. For the past two years I've worked on high-traffic betting and gaming platforms — the kind where a slow query isn't a slow query, it's a support queue, and where every bug on the payment path is somebody's actual money.

Most of my work sits in the parts that only get interesting at scale. Streaming pipelines that have to make a decision before a transaction clears. A database that was fine for a year and then quietly wasn't. Payment integrations where the failure you have to worry about is the silent one. Frontend architecture that stops a team of engineers from stepping on each other every sprint.

I work in Go and Java on the backend, mostly around Kafka, Flink and PostgreSQL — and in Vue and Nuxt when the work reaches the browser. I care more about systems that degrade gracefully than systems that benchmark well on a good day.

I'm currently looking for full-stack or backend roles. If you're building something where the load, the latency or the money is the hard part, I'd like to hear about it.