About
I'm a senior backend engineer. I've been doing this since 2015, mostly on high-traffic distributed systems across fintech, e-commerce and IoT — and mostly on the parts nobody notices until they stop working. I work primarily in PHP and Laravel, and in Go.
I'm currently a senior software engineer at Toters Delivery.
Before this
At Foodics I moved between backend teams — reliability, payments, kiosk, architecture — as priorities shifted, which in practice meant being pointed at whatever was most on fire and getting useful quickly.
The work I'm proudest of there was a ground-up reliability rebuild of the Foodics Online platform. Critical production tickets dropped by more than 80%, from around 450 a month. Separately, service latency went from roughly 11 seconds to under 500ms — profiling slow queries, upgrading infrastructure, and refactoring service dependencies one module at a time — which is what finally stopped peak-hour outages during high-load merchant campaigns. I also helped establish backend observability and was among the first onto the on-call rotation, which is a fast and slightly painful way to find out whether your alerting is any good.
On the payments side I drove a four-years-overdue upgrade of our Checkout.com integration, which carried about 90% of user transactions. On the architecture side I joined the architects' team applying domain-driven design to carve out well-defined backend subdomains, moving business logic out of client apps and into the backend, and co-designed a Customer Data Platform service as the single source of truth for customer data during a monolith-to-microservices decomposition.
Before Foodics I spent four years at Robusta Studio, where I led the company's first move into IoT and into the Saudi market. I moved from Scrum Master to project tech lead over that time. A lot of the work was architecture and server-side development, but the part that stuck with me was the other half: mentoring junior engineers, running a workshop on folding testing into the development workflow, automating enough of the backend hiring process to take real load off the hiring committee, and giving more than ten internal talks on things like web security, authentication, code analysis and non-functional testing.
What's here
Write-ups of problems that took longer than they should have. Reliability and performance work, payments integrations, the occasional note on Go or Laravel, and the specific evidence that changed my mind about something I believed.
Elsewhere
The fastest way to reach me is email. Happy to hear about anything here — corrections especially.