My part was mostly on the backend side — APIs, integrations, data processing, automation, and the operational workflows around what happened when the system noticed something was wrong.
What I did
Helping monitoring events turn into notifications, escalations, and actions people could actually follow up on
I worked on Flask APIs and backend integrations that supported the monitoring flow, including data-processing requirements from the data analytics team. One part I remember clearly was prolonged packet loss: instead of stopping at detection, the system could send a Slack notification and, when the issue needed outside attention, create a support ticket for the relevant ISP or vendor.
A lot of the work happened inside a production system that was already running, so the job was often less about introducing something completely new and more about connecting existing pieces in a way that made the next step clearer. It was one of the projects that made me notice how often backend systems sit quietly between events, people, and other systems.
For internal projects, I keep the details broad enough to explain the work without exposing private data, internal processes, or anything that should stay inside the company.