Senior Infrastructure Project Manager

Projects are initiated by internal product teams (CDN, Cloud, Edge AI, DDoS) or by Technical Support on behalf of external customers. At this level, the PM owns more than Jira tracking: the quality of the plan, realistic timelines, a sound budget estimate, risk management, and coordination of several parallel work streams - architects, procurement, logistics, data centre engineers, and operations teams. We expect you to take on technically and organisationally complex projects - a large deployment at a new site, or a multi-vendor integration, and deliver them with minimal involvement from your manager, while proactively communicating status and risks. Projects you will run: • PoP build-outs and colocation - new sites, expansion of existing ones, racks and cage space in third-party data centres. • Server and network hardware deployments for internal product demand and for external customers (dedicated hardware, managed connectivity). • Capacity expansion, hardware refresh, and decommissioning. • Connectivity and interconnection procurement - IP transit, cross-connects, dark fibre, wavelengths, leased lines, in coordination with the Procurement team. • Migrations and relocations of physical equipment between sites. What You’ll Do End-to-end project ownership • Setting the project up in Jira (GI master ticket), breaking it down into tasks, and building a realistic schedule that accounts for dependencies. • Identifying the critical path and key risks at kick-off - without waiting for your manager to do it. • Orchestrating linked tasks across counterpart teams' Jira projects: IDS (architecture), PRO (procurement), DCI (on-site installation), HDWR (repair and replacement). Knowing where the work physically lives, and reporting on the active linked tickets, not just the master ticket. • Making operational decisions inside the project yourself. Escalating only what sits outside your authority: budget, priorities between projects, conflicts with other departments - and bringing a recommendation when you do. Budget estimation and approvals • Owning the project budget at the Initiation stage: reviewing the cost estimate built on the architect's specification - breakdown by NRC / MRC and by component (colocation, leased lines, hardware, small parts) - and benchmarking it against comparable past projects and reference cost tables. • Driving the project through the approval chain, tracking approval turnaround, and handling objections. • Reconciling budget plan versus actuals at project closure. Technical design and architecture • Briefing the Infrastructure Architects team (RFS / HLD / SDD) and contributing substantively to discussions on BoM, rack layout, power, and network. • The architect owns the specification - what is bought and where it is shipped. The PM controls it against the project's scope, timeline, and budget, and gets it approved. • Being able to tell a realistic technical plan from an unrealistic one, and challenging the design where it doesn't fit the project's constraints. Procurement • Raising requests to the Procurement team based on the architect's specification, setting the deadline and project context, and tracking execution. Vendor negotiations are run by Procurement. • Monitoring request and PO statuses, and escalating early when timelines are at risk. Logistics and delivery to site • Raising delivery requests to the Logistics team based on the architect's specification (what goes where), setting deadlines, and tracking execution. Shipping, customs, warehousing, and delivery to the data centre are run by the Logistics team. • Tracking ETAs and escalating early when delivery is at risk of slipping. On-site installation • Briefing the DCIM team on equipment installation: agreeing installation wi