Infrastructure Project Manager, Network & Lab Infrastructure
Location: Menlo Park, California (Onsite)
Contract
Role Summary
About the team
The team delivers network, security, and compliance services across a large global physical infrastructure footprint:
owned and leased data centers, edge and long-haul networks, and lab / R&D environments. On the labs side, the
team owns end to end network infrastructure for engineering labs supporting next generation AI compute platforms,
consumer hardware development, immersive capture systems, and production lab environments. Work is organized
into specialized delivery pods and spans multiple domestic and international sites.
About the role
This is a delivery-focused PM role, not a generalist one. You will own schedules, dependencies, and cross-functional
coordination for lab build-outs and network rack integration programs. You need to be genuinely conversant in network
infrastructure: enough to read a topology diagram, understand why an optics order is on the critical path, sit in a
design review without a translator, and push back when a plan does not hold up.
You will spend your time unblocking other people's work. Chasing the long-lead hardware, chasing the change
window, chasing the vendor who owes us a ship date. If being the squeaky wheel that keeps a program moving
sounds like the job, it is.
What you will do
Project intake, scoping, and schedule/milestone management for production lab build-outs, rack integration,
and wireless/AP deployment programs
Cross-functional coordination across Network Engineering, Data Center Operations, Security / NetSec,
Compliance, and OEM vendors
Hardware and logistics tracking: racks, switches, optics, structured cabling, capacity, and long-lead item risk
Change management and maintenance-window coordination, including config push windows and canary /
validation gates
Risk, issue, and dependency tracking with clear escalation paths
Status reporting and executive-level dashboards, plus a regular operations review and quarterly business
review cadence
Documentation and process normalization: runbooks, as-builts, Confluence or equivalent wiki, and intake
templates
Sprint-based delivery tracking in Jira against team OKRs, with epics and stories structured so progress rolls up
cleanly
Compliance and remediation program tracking, including device configuration remediation campaigns and
patch management readiness
Baseline technical knowledge we expect
Data center and campus network fundamentals: L1/L2/L3, VLANs and subnetting, IPv6, BGP basics,
structured cabling, optics and transceiver types
Fabric topology fluency: border leaf, spine, leaf, and campus gateway layers, and why redundancy at each tier
matters
Lab and test environment models, including network segmentation tiers and how each tier differs on internet
access, source code access, and wireless
Rack integration and provisioning workflows: device staging, cabling standards, DNS and certificate setup,
proxy integration, monitoring onboarding
Wireless infrastructure basics: AP density and placement, controller architecture, throughput planning for
high-density test environments
Data center operations and change-management process fluency (ITIL-style change control), including major
incident response, rollback, and post-incident review
Enough familiarity with network automation and config-as-code workflows (Ansible or similar, Git-based config
management, templated device configs, validation, canary, staged rollout) to track them as real milestones
rather than black boxes
Comfort reading operational telemetry from monitoring and log platforms (Grafana, Prometheus, Splunk, ELK
or equivalent) well enough to know whether a deployment is actually healthy
IP address management and device inventory concepts: address block hierarchy, device inventory graph,
asset lookup. Familiarity with NetBox, phpIPAM, Infoblox or similar
Firewall and ACL policy change basics, and how a policy change can gate a deployment
Program management skills
Building and holding a realistic schedule when hardware lead times and vendor dates are the constraint
Running intake so requests arrive scoped instead of arriving as a surprise
Driving action items owned by other people to completion without being handed authority
Reporting that leadership can read in thirty seconds and that engineers recognize as accurate
Clean backlog hygiene: every workstream tied to a tracked objective, no orphan work
Nice to have
Prior PM or TPM work inside a hyperscaler, cloud provider, carrier, or large enterprise network organization
Experience with multi-site or international lab and data center delivery
Familiarity with Arista EOS or Juniper Junos environments
Background in procurement or supply chain coordination for network hardware
Exposure to AI/ML or XR hardware validation environments
What success looks like in the first six months
Every active build-out has a schedule with named owners and real dates
Long-lead hardware risk is visible before it becomes a slip
Leadership has one place to see program status and does not have to ask
Intake, runbooks, and as-builts are normalized enough that a new engineer can pick up a site cold