🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
As a Cloud Network Engineer your primary responsibility will be ensuring that our GCP network environment is stable, secure, resilient, and agile to accommodate current and future project needs. This will involve partnering with your Cloud Network Delivery peer group in operational support, technical design, and driving best-of-breed technical standards into the environment in an evolving fashion. As this role is part of our continued growth and technical evolution in our cloud environments, agility is a must have regarding being able to handle context switching through project delivery and operational support response. With a relentless focus on our customers, high-quality engineering, and a curiosity driven approach this role is critical to propel and shape our technical future. Design and support GCP network environments by leveraging cloud native services such as Network Connectivity Center (NCC), Cloud VPN, Cloud Load Balancers, VPC Constructs, and Service Networking.Provide consistent design patterns to support a wide array of connected services such as SaaS providers, on-premise systems, and internal GCP services.Participate in an on-call rotation and act as an escalation point as needed to support production environment needs.Deliver projects through cloud network constructs to support ongoing business requirements for a variety of internal stakeholders.Clearly articulate and communicate how technical components can support various environments within our cloud platform to peer groups, partner teams, and internal stakeholders.Interface with vendor teams to shape and adopt future product offerings within the GCP network space. Bachelors Degree or equivalent practical experience.7 years of experience in network engineering roles.5 years of experience in delivering GCP network environments.Expert level understanding of GCP service networking constructs such as Private Service Access and Private Service Connect.Advanced understanding of GCP Network Connectivity Center (NCC).Advanced understanding of GCP load balancing offerings (Internal vs External | Scope | Traffic Type).Advanced understanding of Cloud VPN, Interconnect, and Proxy based connectivity offering within GCP.Advanced understanding of TCP/IP stack with the ability to diagnose, interpret, and deliver solutions based on packet captures.Advanced understanding of packet-flow decision process with a focus on path determination, packet overhead constraints, fragmentation, and flow manipulation.Experience in delivering Cloud CDN solutions with a focus on cache vs origin delivery optimization.Experience delivering Infrastructure As Code solutions.Experience with Jira and ServiceNow.Ability to deliver baseline health monitoring to accommodate error budgeting and target specific SLI and SLO measurementsSelf-starting capabilities and the ability to thrive in an autonmous environment .
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.