Four years of shipping, operating and fixing production systems.

I came into software from aeronautical engineering, and stayed because I wanted to understand how things actually worked. I have kept following that instinct further down the stack ever since — from building interfaces, to the services behind them, to the databases those services talk to, and eventually to the servers, containers and pipelines that carry all of it into production.

Since September 2022 I have worked as a software engineer at Amigosia, on marketplace, logistics, fintech and commerce platforms that real users depend on. That has meant designing and building full-stack web and mobile applications with Angular, React, React Native and Node.js; modelling and tuning data in PostgreSQL, MongoDB and SQL Server; putting Redis in front of the paths that needed it; and deploying the result to AWS and Azure through Docker, Kubernetes and CI/CD pipelines I built and maintain — often working directly with clients in the United States and Qatar.

It has also meant the less photogenic work: tracing a production incident back to its cause at an inconvenient hour, rewriting a query whose plan fell apart once the table grew, configuring Nginx and process managers so a restart does not drop requests, and adding the logging that made the next problem faster to find than the last one.

What I have taken from that is fairly simple. The interesting part of software engineering is rarely getting something to work. It is making something that keeps working — under load, under change, and under whoever inherits it. That belief shapes how I design systems, which technologies I reach for, and how much I am willing to add before asking whether it is really needed.

Outside of feature work I mentor junior developers and interns, and I spend my own time on system design, cloud-native architecture, DevOps automation and, more recently, AI-assisted engineering workflows.