Principal Network Architect

Select how often (in days) to receive an alert:

Digital Edge is a trusted and forward-looking data centre platform company, established to transform digital infrastructure in Asia. Backed by Stonepeak, a leading alternative investment firm specialising in infrastructure and real assets, Digital Edge has in excess of US$1 billion in committed capital.

Our mission is to bridge the digital divide across Asia Pacific by building the sustainable digital ecosystems of the future. Through building and operating state‑of‑the‑art, energy efficient data centres rich with connectivity options, we bring new colocation and interconnect options to the Asian market, making digital infrastructure deployment in the region easy, efficient and economical.

Founded in 2020 the company has grown rapidly across multiple markets in the region, and currently provides data centre and fibre services across China, India, Indonesia, Japan, Korea, and the Philippines. This role is an exciting opportunity to join our fast growing team as we further expand our footprint across Asia.

Our Values :

• Responsibility: We take ownership of our actions and outcomes.
• Innovation: We embrace change and create bold solutions.
• Strive: We show grit, resilience and relentless drive.
• Excellence: We pursue the highest standards in all we do.
• Respect: We act with integrity and treat others with dignity.

What we need:

Reporting to the Director of Digital Infrastructure Operations, the Principal Network Architect owns the end‑to‑end network architecture across Digital Edge’s WAN, backbone, data centre, interconnection and hybrid cloud environments. The role combines deep network expertise with a practical understanding of compute, operating systems, virtualisation, storage and application dependencies to deliver high‑performance, resilient services.

The architect will translate business and workload requirements into integrated designs, evaluate trade‑offs across infrastructure domains, and lead delivery with systems, platform, security and application teams. Success is measured by end‑to‑end service performance, availability, recoverability, operational efficiency and lifecycle cost.

Key responsibilities:

1. Holistic Infrastructure Architecture

• Own integrated architecture, reference designs, and roadmaps connecting physical and optical infrastructure, IP networks, compute, storage, and platforms.
• Map application flows and service dependencies; define capacity, latency, availability, security, recovery, and lifecycle cost requirements.
• Document design trade‑offs, migration plans, acceptance criteria and operational ownership for each architecture decision.
• Establish and govern network architecture standards, design principles and an architecture review process, ensuring new builds and expansions across the regional portfolio conform to approved designs.
• Develop CapEx and OpEx business cases, total cost of ownership models and multi‑year network budgets to support new data centre builds and capacity expansion.

2. Systems and Platform Design Considerations

• Apply a working understanding of Linux, server hardware, CPU and memory resources, virtualisation, and containers to network design decisions; hands‑on engineering of these platforms remains with the systems and platform teams.
• Assess how host networking, TCP/IP behaviour, NICs, MTU, virtual switches, load balancers, DNS, and time synchronisation affect service delivery.
• Account for storage access, I/O performance, replication, clustering, and backup traffic when designing bandwidth, latency, and recovery requirements.
• Engage systems and application specialists during design to understand host, storage, and service dependencies, and review workload test results to confirm network designs meet performance requirements.

3. Network Service Architecture and Technology Selection

• Architect WAN, backbone, data centre, internet and cloud connectivity as an integrated end‑to‑end design across sites, carriers and markets, supporting both IPv4 and IPv6.
• Select the appropriate routing, switching, overlay and transport technologies for each service type, such as internal infrastructure, customer interconnection, data centre interconnect and cloud connectivity, based on scale, resilience, latency, security, operational complexity and cost.
• Define routing and traffic‑control architecture principles, including domain hierarchy, policy, segmentation, traffic engineering and convergence, proving each principle with working reference configurations before engineering teams complete detailed design and rollout.
• Maintain a technology selection framework and service design patterns that map service requirements to approved technologies, reviewing