From Networking to Cloud Infrastructure: How Curiosity Became My Career

When people ask me how I became a Cloud Infrastructure Engineer, they often assume my journey started with cloud computing.

It didn't.

It started in college with a networking course.

Networking was one of the courses I took during my third year, and from the very first class, something clicked. I was fascinated by how computers and systems could communicate with one another. I loved understanding how everything connected behind the scenes, solving problems, and uncovering the mystery of how networks worked. There was something incredibly satisfying about connecting the dots.

I've always had an interest in technology, but studying computer networking gave that interest a direction. It wasn't just another course I needed to pass, it became something I genuinely looked forward to. I remember thinking, If I enjoy this so much, maybe this is what I'm meant to do.

By my final year, I had already decided that networking was the path I wanted to pursue. I started preparing for the CompTIA Network+ certification because I wanted to build a stronger foundation beyond the classroom. Around the same time, I was introduced to Cisco's CCNA courses, which opened my eyes to what a career in networking could look like.

I also have to give credit to one of my lecturers. The way he taught networking made all the difference. He didn't just explain concepts; he made them practical and exciting. Looking back now, I realize he played a significant role in helping me discover what I truly wanted to do.

During my industrial training, I had the opportunity to gain hands-on exposure to networking. Everything I had learned in class suddenly became real. Instead of reducing my curiosity, the experience made me even more passionate about the field.

I thought that because I had found something I loved, the rest of my career would naturally fall into place.

I was wrong.

After graduation, I found myself completely directionless.

People often think that once you've discovered your passion, everything else becomes easy. That wasn't my experience. I didn't know what certification to take next, what opportunities to pursue, or how to build a career around what I loved. I needed someone to guide me, to tell me, "This is your next step."

That guidance eventually came through a friend, who introduced me to someone already working in the industry. During our conversation, he suggested I consider infrastructure engineering. He explained that infrastructure would allow me to build on my networking knowledge while exposing me to different areas of technology.

To be honest, I didn't even know what infrastructure engineering was.

I simply held on to the advice and decided to explore it.

Looking back now, that conversation changed the trajectory of my career.

After graduation, I made a promise to myself. I didn't want to stay home waiting for opportunities to find me, and I didn't want to accept just any job simply to make ends meet. I wanted to build a career around something I genuinely loved.

So I started applying for internships, over and over again.

Thankfully, one of those applications paid off.

By God's grace, I was offered an internship as an IT Infrastructure Engineer.

That opportunity became the bridge between my passion for networking and my future in cloud infrastructure.

One thing that stood out during the interview was how much networking had prepared me. Most of the questions revolved around networking fundamentals—IP addressing, the OSI model, troubleshooting network issues, and understanding how systems communicate. Although there were questions I couldn't answer because I lacked practical experience, I answered the networking questions with confidence because I had built a strong foundation.

That foundation opened the door.

When I joined the company, I was given a learning roadmap. Within six months, I was expected to become familiar with several technologies and tools. I immersed myself in learning Linux, Bash scripting, Python, AWS, Terraform, Docker, and many other infrastructure technologies.

I was eager to learn.

Every new tool I discovered made me even more excited about the field. My manager noticed how quickly I was learning and was impressed by the progress I made within such a short period.

But behind that progress was a reality many people didn't see.

Even though I was doing the work, I didn't fully understand everything during my first year.

I was learning on the job, trying to connect concepts that were completely new to me. There were days when I questioned myself and wondered whether I was doing enough. Still, I refused to give up. I kept learning, asking questions, making mistakes, and trying again.

After about a year, everything began to click.

For the first time, I truly understood what infrastructure engineering was about. I could see how Linux, cloud platforms, automation tools, and networking all worked together. The technologies that once seemed overwhelming gradually became familiar.

As my confidence grew, so did my opportunities.

I began taking on freelance projects and side gigs, applying the skills I had developed beyond my full-time role. It was incredibly rewarding to see that the curiosity I had discovered in a college classroom was now creating opportunities I had once only imagined.

Of course, the journey wasn't without challenges.

After leaving my first role, finding another job became incredibly difficult. There were moments when I felt discouraged. I questioned whether I had made the right career choice because opportunities weren't coming as easily as I had hoped.

Then there was the reality of working in technology.

Learning never stops.

Just when you think you've mastered one tool, another one emerges. Technology evolves every day, and you have to evolve with it. There were moments when I felt overwhelmed by the constant pressure to keep learning. Sometimes I would pray and ask, "God, when will this end?"

Eventually, I realized something important.

It doesn't end.

Continuous learning isn't a phase in technology—it's the lifestyle. Once I accepted that, I stopped seeing learning as a burden and started embracing it as part of the career I had chosen.

That mindset prepared me for my next opportunity.

Today, I work as a Cloud Infrastructure Engineer, managing cloud services, maintaining servers, ensuring system availability, and helping keep critical infrastructure running reliably. Every day, I draw on the networking foundation that first sparked my passion years ago.

When I reflect on my journey, I realize networking wasn't just another course I took in university.

It was the beginning of everything.

It taught me to think critically, solve problems, and understand the invisible systems that keep technology running. More importantly, it introduced me to a career that has continued to challenge me, stretch me, and open doors I never imagined possible.

If there's one lesson I've learned, it's this: your first passion doesn't always define your final destination, but it can become the foundation that leads you there.

For me, networking was that foundation.

It led me to cloud infrastructure.

And this is only the beginning.