In my experience supporting backend and operational processes, I’ve learned how important it is to keep things running smoothly behind the scenes, especially when multiple teams rely on the system. When I was the Quality Management Team Lead at ECX, we were building and maintaining a legacy educational app, and a big part of my work involved making sure the backend behaved the way users expected. I collaborated closely with the developers to understand how the system stored data, handled requests, and processed user actions, then tested each part to catch inconsistencies or performance issues. Because it was a legacy product, nothing was ever “plug and play”—I had to dig into logs, trace errors, validate API responses, and confirm that updates didn’t break existing features. Beyond testing, I also supported the operational side by coordinating with product, design, and engineering to ensure that releases were stable and user-ready. I often acted as the bridge between the technical team and non-technical stakeholders, translating backend problems into clear, actionable steps. This experience taught me how to work under pressure, communicate clearly, and maintain quality even when dealing with outdated systems. It also helped me develop a calm, problem-solving mindset, which I now bring into every backend or operations-related role I take on.

Essentially, by using schedules to manage my day

And using Excel sheets to document properly.

Yes, I do