Today we have Munachimso Nwaiwu, a Network Engineer at Google, sharing his story. He talks about how his childhood curiosity for tech led him to choose a unique career path and what a typical day at Google looks like for him.
If your career journey were a movie, what would the title be?
I’d call it ‘The Pilgrim’s Progress.’ Like Christian in the story, my career has been a series of new and different challenges at every step. But the key takeaway for me has been the assurance that help is always available if I ask. I’ve experienced it firsthand, though it’s still a lesson I’m learning.
Can you tell us about your journey into tech? What sparked your interest in network engineering?
I’ve always been drawn to engineering, though I wasn’t sure which discipline at first. My mum encouraged my technical curiosity from a young age. I still remember the sense of accomplishment when I figured out how to connect our play station. My parents were in the biological sciences, so I didn’t have direct exposure to tech, but I explored different engineering fields.
When applying to US universities, I discovered Computer Networking and IT. It felt right—I wasn’t as drawn to pure computer science, and networking answered a deep curiosity I had about how the internet actually works. I even remember my dad jokingly calling technology ‘white man magic,’ which made me even more determined to understand it.
My first networking classes were a revelation. Learning how data moves across the world almost instantly felt like uncovering a secret language. That challenge—understanding how everything connects—solidified my path toward network engineering.
Can you break down what network engineering entails for someone unfamiliar with the field?
Think of network engineering like building and maintaining a vast system of roads, but instead of cars, we’re directing information. We design the routes, choose the right ‘vehicles’ like routers and switches, and set the ‘traffic rules’—network protocols—to keep everything running smoothly.
Beyond building, we constantly monitor for ‘traffic jams’—network issues—and fix them quickly to keep data flowing. Security is also key, protecting the network from cyber threats. And with technology advancing, automation is playing a bigger role, helping us manage these complex systems more efficiently.
At its core, network engineering is about creating and maintaining the digital infrastructure that keeps the world connected.
What does a day in the life of a network engineer at Google look like?
Every day at Google is unique, given the sheer scale of the network. My work revolves around maintaining infrastructure and developing new improvements.
Mornings usually start with meetings, collaborating with technical program managers and engineers to discuss project updates, brainstorm ideas, or troubleshoot issues. After that, I dive into hands-on technical work like debugging, analysing traffic, or implementing network changes. Given the scale, even small errors can have a huge impact, so careful planning and testing are crucial.
Afternoons often focus on longer-term projects, designing workflows, automating operations, and integrating new applications. Collaboration is key, and we rely heavily on monitoring systems to ensure network performance. It’s a constant learning experience, and I love the challenge.
Can you share the key moments or decisions that helped you land your role at Google?
I joined Google through the Network Operations Residency Program (NORP), designed for new grads passionate about network engineering. From my first networking class in college, I was hooked; I knew this was the field for me.
To build a strong foundation, I pursued industry certifications like CompTIA Network+ and CCNA, which deepened my understanding of networking fundamentals. My internships at Meta and Lenovo gave me hands-on experience. At Meta, I analysed large networks to optimise performance, while at Lenovo, I worked on high-bandwidth, low-latency HPC networks.
These experiences, along with my certifications and passion for networking, made me a strong candidate for NORP.
What advice would you give to young Africans aspiring to work at global tech companies like Google?
Master the fundamentals. Companies like Google prioritise deep understanding over just knowing the latest tools. They want innovators, not just users.
You might build a complex network with cutting-edge protocols, but if you can’t explain how two computers communicate at a fundamental level, you’ll fall short. A strong grasp of core principles, whether in networking, software engineering, or any tech field, makes learning new technologies easier. The reverse isn’t always true.
If possible, learn networking basics. Understanding how computers communicate is valuable across roles like DevOps, cloud, and backend engineering. And beyond technical skills, strong communication and collaboration are just as critical for success.
What skills or tools are essential for anyone looking to excel in network engineering?
Several technical skills and areas of expertise are crucial for a successful network engineer. While a comprehensive list could include areas like routing protocols, network security, cloud networking, and specific hardware/software proficiencies, one skill set stands out as particularly vital: the ability to effectively problem-solve and troubleshoot.
These two skills, while often grouped together, are distinct. Problem-solving involves designing solutions to identified network challenges, often confirming the theoretical effectiveness of those solutions beforehand. Troubleshooting, on the other hand, is what happens after implementation when things don’t go as planned. It’s the art of diagnosing and resolving unexpected network issues in a live environment, often a large-scale system where everything is interconnected. It’s about figuring out what’s wrong when everything should be right. This ability to pinpoint the root cause of a problem, often under pressure, is a hallmark of a skilled network engineer.
A strong foundation in networking fundamentals is essential for both problem-solving and troubleshooting. A deep understanding of the OSI model, in particular, is an excellent starting point. It provides a structured framework for understanding how network communication works and helps in systematically isolating problems when they occur. By understanding each layer’s function and how they interact, network engineers can more effectively troubleshoot issues and develop appropriate solutions.
What resources do you recommend for someone looking to get into network engineering?
Instructors like Professor Messer, David Bombal, and Keith Barker share invaluable knowledge on YouTube and Udemy, often for free. For blogs and podcasts, I recommend Network Lessons, Router Alley, and The Art of Network Engineering.
The best part? You don’t need physical devices to practice; tools like Cisco Packet Tracer and GNS3 let you build virtual networks.
I’m so passionate about networking that I started my own blog, networksbymuna.com, where I share my study notes for the CCNP exam. It’s my way of helping others while reinforcing my own learning.
Want to read more career stories like this? Subscribe to the Level Up Newsletter.
