About Me

My Journey

I started my professional journey at Hewlett Packard Enterprise (HPE) as a Technical Support Engineer. It was my first real exposure to production systems — Linux servers, enterprise environments, real customers, and real consequences when things went wrong. Every day, I learned how systems fail, how they recover, and how critical stability is in the real world.

But somewhere along the way, I realized something important. While I was good at fixing problems, what truly excited me was understanding why they existed. I found myself more interested in the logic behind applications than the symptoms they produced. After my shifts, I would open my laptop again — not to resolve tickets, but to write Python code.

I began building small scripts, then moved on to Flask applications, learning how requests flow, how data is handled, and how systems behave under load. I explored Linux deeply, automated repetitive tasks, and slowly introduced myself to DevOps concepts. Writing code felt different. It felt like progress.

At one point, I gathered the courage to speak to my manager about moving into a development role. The response was honest — there was no immediate possibility. It wasn’t rejection, but it was a pause. That moment stayed with me. I realized that if I waited, I would remain where I was. So instead of waiting for permission, I decided to prepare myself for the role I wanted. I doubled down on learning. I strengthened my foundation in Python, worked extensively with Flask, and improved my understanding of data handling using Pandas and NumPy.

Today, my goal is clear. I want to move into a development-focused role where I can combine my support experience with my passion for building software. I bring with me a strong respect for system reliability and clean code. This career shift is a deliberate choice driven by the belief that I can create more value by building solutions rather than only supporting them.