🎁 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 →
About the Role We're looking for a Lead Network Engineer, Architect - Observability to own the strategy and architecture behind how we see, understand, and act on the health of our global network. This is a senior technical leadership role for someone who has spent a decade or more in network engineering and now wants to define how a large, multi-region network gets monitored, correlated, and made predictable rather than reactive. You'll be the architect of our observability capability end to end, spanning monitoring platforms, telemetry, analytics, and the roadmap that ties it all to business outcomes like uptime, mean time to resolution, and cost avoidance. What You'll Do Observability Strategy and Architecture Own and advance a multi-year observability maturity roadmap for the global network Architect unified observability solutions spanning our monitoring platforms rather than siloed point tools Define predictive alerting and anomaly detection capabilities to move the organization from reactive to proactive Build observability use cases grounded in business goals, not just technical coverage Set observability best practices and standards used across regions Evaluate emerging observability and AIOps technologies and recommend where they fit Analytics and Cross-Tool Integration Design analytics workflows that combine data from multiple sources, such as wire data, infrastructure metrics, and flow analysis, into a coherent picture of network health Build predictive capacity planning models using historical performance data Create executive-level dashboards that correlate network health with business outcomes Develop anomaly detection and behavioral baseline analytics Design correlation logic across tools to speed up root cause analysis Advance visualization strategy across our reporting platforms Strategic Planning and Business Value Lead tool portfolio rationalization and cost optimization reviews Build business cases and ROI models for observability investments Quantify the business value of monitoring capabilities in terms leadership cares about, such as uptime, MTTR, and cost avoidance Lead proof of concept evaluations for new observability technologies Assess build versus buy decisions for observability platforms and capabilities Leadership and Collaboration Serve as the senior technical voice on observability across the global network organization Partner with regional network teams to ensure observability standards are adopted consistently Work with the NOC to operationalize telemetry, health checks, and alerting so findings turn into action Present observability strategy, roadmap, and business impact to executive stakeholders What You'll Bring 10-15+ years of network engineering experience, with significant time spent in observability, monitoring architecture, or network analytics Demonstrated experience architecting observability solutions across multiple platforms in a large, multi-site environment Strong background in network protocols and infrastructure (routing, switching, SD-WAN) sufficient to understand what's being monitored, not just how to monitor it Experience with monitoring and analytics platforms such as NetScout, DX NetOps, NetFlow, Grafana, and PowerBI, or direct equivalents Track record of building predictive or anomaly detection capabilities, not just dashboards Experience developing business cases, ROI models, and executive-level communication around infrastructure investment Strong stakeholder management skills, with the ability to work across regional teams and translate technical capability into business value Bachelor's degree in a related field or equivalent experience Why This Role Matters A global network is only as manageable as it is visible. This role defines how we see problems before they become outages, how we prove the value of what we monitor, and how we turn raw telemetry into decisions leadership can act on. has context menu Knowledge, Skills and Experience: 10 to 15 Years of relevant work experience. Bachelor's Degree with Network Engineering or Related field of study required. Other Education / Certifications: - Cisco Certified Internetwork Expert (CCIE) Data Center, CCIE Enterprise Infrastructure, CCIE Enterprise Wireless, CCIE Collaboration, Cisco Certified Design Expert (CCDE), F5 (or other load balancer) Certified Solution Expert, SNIA Storage Networking Certificate. Able to execute instructions and to request clarification when needed. Able to perform basic mathematical calculations. Able to recognize and attend to important details with accuracy and efficiency. Able to communicate clearly and convey necessary information. Able to create and conduct formal presentations. Able to interact
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.