Job Description
Experience: 3-5 Years.
Location:- PAN India
Mandatory Skills: Cisco Routing and Switching .
Network Technical Program Manager (TPM) – RNDS Support will support OCI’s Region Networking Deployment & Scaling (RNDS) organization, including Network Region Build (NRB) and Network Scaling, by providing program management, execution oversight, and cross-team coordination to ensure timely and reliable delivery of network infrastructure. Network TPMs will:
i. Own end-to-end execution of new region builds, child site expansions, and scaling projects across commercial, government, and sovereign realms.
ii. Develop, manage, and track program schedules (Kickoff to handoff) including cabling, rack intake, power-on, IP allocations, circuit delivery, fabric turn-up, and validation milestones.
iii. Coordinate dependencies across NRB, Scaling, NRE, GNOC, Construction, Colo vendors, Network Automation (NA), Network Management (NM), Capacity
Internal - General Use Planning, and Supply Chain. iv. Manage intake, automation workflows, Network rack validations, and PD- driven configuration delivery.
v. Track risk, escalate blockers, lead war-room or recovery calls, and provide executive-level status reporting.
vi. Ensure timely delivery of backbone and metro circuits, transport readiness (DWDM/optical), and IP address planning.
vii. Oversee documentation, runbooks, BOMs, rack layouts, IP schemas, Visio/NetBox artifacts, and completion for handoff to operations. viii. Drive process improvements, automation adoption, RCA follow-ups, and cross-functional alignment with engineering and operations teams. ix. Execute Jira/Smartsheet tracking and maintain project artifacts in Confluence and OCI document repositories. x. Support 24×7 follow-the-sun delivery model, including early-morning/late- evening calls for global region builds as required. A. Description of Deliverables – Role D i. Region build and scale-out project plans, Gantt/Smartsheet dashboards, schedules, and weekly progress updates. ii. Completed risk registers, decision logs, and escalation summaries for each active project. iii. Network rack readiness reports including cabling, power validation, IP assignments, and bootstrap status.
iv. Circuit readiness tracker (ordered, delivered, LOA/ROA, test & activation). v. Handoff packages to GNOC/NRE including rack lists, IP worksheets, circuit inventory, BOMs, and validation results. vi. RCA documentation and preventive action items after high-severity incidents or build delays. vii. Updated workflows, automation feedback, and process improvement recommendations. viii. Runbooks, onboarding documents, and KT sessions for OCI full-time teams. B. Acceptance Criteria – Role D A deliverable will be considered complete and accepted when the following criteria are met: i. Project Schedules: Region or scaling build schedules updated weekly, with dependencies, milestones, and risks tracked in OCI-approved systems (Jira/Smartsheet/Confluence). ii. Delivery Execution: All critical path milestones (rack power-on, cabling validation, IP assignments, circuit activation) align with NRB or Scaling timelines shared with the vendor. iii. Documentation Packages: Program artifacts (rack lists, IP plans, diagrams, circuit tracking, BOMs) completed, stored in the designated OCI repository, and