Network Planner

We need to output HTML fragment with sections: About the role (maybe "About The Role" heading), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real content. From posting: - About the role: there is a section "About The Role" with bullet points (list). So we need

About The Role

then

• ... each bullet. - Responsibilities: The "What You'll Do" section includes bullet points under "We are seeking ..." Actually "What You'll Do" includes a paragraph then bullet list under "Capacity Procurement:" etc. Those are responsibilities. So we can have

  Responsibilities

  with list. - Requirements: The "Who You Are" section includes bullet list of required qualifications/experience. That's requirements. - Qualifications: Could be education etc. Might be part of requirements. But we can separate: maybe "Qualifications" for degree etc. However we must avoid thin sections. Could combine. - Skills: maybe list of specific skills like wavelength, dark fiber, forecasting, vendor management, analytical, communication, project management, tools proficiency. - Benefits: There's a list under "What We Offer" with bullet points of benefits. So include

  Benefits

  with list. - Pay: There's salary range: "The base salary range for this role is $134,000 to $179,000." Also mention discretionary bonus, equity awards. So we can include Pay section with that info. - Schedule: Not mentioned. So omit. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO, legal, etc. Also remove "Wondering if you're a good fit?" maybe not needed? It's not substantive? Could be considered fluff but maybe keep? It's not a list; it's a paragraph encouraging. Might be considered filler but not disallowed. However we can keep as part of About the role? Probably better to omit as it's not specific content. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The "Wondering if you're a good fit?" is not boilerplate but maybe considered fluff. Safer to omit. Also remove "Why CoreWeave?" section? It contains culture description; could be considered substantive? Might be considered fluff but maybe keep as part of About the role? The instruction: "Prefer a few substantive sections over many thin ones." The culture section is not a list; could be a paragraph. Might be okay to include as part of About the role? But we already have About The Role section with responsibilities. Could add a paragraph after heading about culture. However we need to preserve ALL substantive information; not invent or summarize away detail. The culture description is substantive? It's about company values. Might be considered relevant. But we can include as a

  under About The Role or separate section? There's no heading for culture. Could add a

  after the list. But we must not create sections with filler. The culture paragraph is not a list; it's prose. Could be included as

  under About The Role. Similarly "What We Offer" includes benefits list; we already have Benefits. Also there is a paragraph about base salary range etc. We'll put under Pay. Also there is paragraph about discretionary bonus, equity awards, comprehensive benefits program. That's part of Pay/Benefits. We need to ensure we don't duplicate content. Let's extract sections: About The Role (list): - Capacity Procurement: Collaborate extensively with telecommunications vendors and our internal network architecture team to identify, evaluate, and procure new backbone network capacity (wavelength and dark fiber) between various locations, aligning with business requirements and network growth forecasts. - Solution Review & Design: Critically review proposed capacity solutions from vendors, ensuring optimal technical fit, cost-effectiveness, and adherence to network design principles. This includes meticulously identifying and ensuring circuit diversity to enhance network resilience and minimize single points of failure. - Capacity Management: Proactively monitor, manage, and optimize existing network circuits and infrastructure. This involves tracking utilization, identifying bottlenecks, and planning for upgrades or reconfigurations to maintain service quality and prevent capacity exhaustion. - Network Planning & Forecasting: Develop and maintain long-term capacity forecasts for the backbone and edge network, leveraging historical data, business projections, and technological advancements. Translate forecasts into actionable network expansion plans. - Vendor Relationship Management: Foster strong relationships with telecommunications vendors, negotiating favorable terms and ensuring timely delivery of procured services. - Technical Documentation: Maintain accurate and comprehensive documentation of network designs, circuit inventory, capacity utilization, and planning activities. - Cross-functional Collaboration: Work closely with engineering, operations, and product teams to understand their requirements, provide technical guidance, and ensure seamless implementation of network expansions. - Problem Solving: Identify and resolve complex technical issues related to network capacity, diversity, and performance. - Industry Trends: Stay abreast of emerging network technologies, industry best practices, and vendor roadmaps, incorporating relevant advancements into future network planning. Responsibilities: Actually the above list is responsibilities. The "What You'll Do" heading could be considered Responsibilities. So we can use that list as Responsibilities. But we also have "About The Role" heading with same list? Actually the posting has "About The Role" then the list. So that is the responsibilities. So we should treat that as About The Role (maybe it's description). The "What You'll Do" is earlier: "We are seeking an experienced and highly motivated Network Planner to join our Infrastructure Capacity - Network Backbone & Connectivity team. In this role, you will be responsible for the strategic planning, procurement, and management of our core network connectivity, ensuring its continued expansion, reliability, and efficiency. You will play a key role in supporting the growth of our backbone network, working with cutting-edge technologies to deliver high-capacity and resilient connectivity." That's a paragraph describing role. Then the list under "About The Role" details responsibilities. Thus we can have:

  About The Role

  We are seeking an experienced and highly motivated Network Planner to join our Infrastructure Capacity - Network Backbone & Connectivity team. In this role, you will be responsible for the strategic planning, procurement, and management of our core network connectivity, ensuring its continued expansion, reliability, and efficiency. You will play a key role in supporting the growth of our backbone network, working with cutting-edge technologies to deliver high-capacity and resilient connectivity.

  ... list items ...
  Then Responsibilities maybe not needed separate; but we could keep About The Role as description and responsibilities as list. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include both About The Role and Responsibilities if we have distinct content. But we could treat the list as Responsibilities and the paragraph as About The Role. That seems fine. Thus:

  About The Role

  We are seeking an experienced and highly motivated Network Planner to join our Infrastructure Capacity - Network Backbone & Connectivity team. In this role, you will be responsible for the strategic planning, procurement, and management of our core network connectivity, ensuring its continued expansion, reliability, and efficiency. You will play a key role in supporting the growth of our backbone network, working with cutting-edge technologies to deliver high-capacity and resilient connectivity.

  Responsibilities

  (list items)
  Now Requirements: The "Who You Are" list includes required experience etc. That's requirements. We could also have Qualifications for degree etc. But we can combine. Better: Requirements: list of required experience (proven experience, etc). Qualifications: education degree. Skills: list of specific skills (wavelength, dark fiber, forecasting, vendor management, analytical, communication, project management, tools proficiency). However many of those overlap with requirements. Given instruction to prefer few substantive sections over many thin ones, we could combine Requirements and Qualifications into one section maybe "Requirements". But we need to follow headings list; we can omit Qualifications if not distinct. But we have to include sections only when posting has real specific content. The posting includes "Proven experience (typically 5+ years) in network planning for large-scale telecommunications or cloud/content networks." etc. That's requirements. Also includes "Bachelor's degree in Electrical Engineering, Telecommunications, Computer Science, or a related field. Equivalent practical experience will also be considered." That's qualifications. Could be separate but thin. Might be okay to have both. Skills: "Preferred Experience with specific vendor equipment (e.g., Ciena, Nokia, Infinera, Cisco). Knowledge of IP routing and switching principles. Familiarity with network automation concepts. Experience working with international carrier markets (EMEA and/or APAC) and the fiber/subsea landscape relevant to CoreWeave's global backbone expansion." Also proficiency in network planning tools. Those are skills/preferred. Thus we can have:

  Requirements

  list of required items (the bullet points under "Who You Are" up to "Ability to manage multiple projects...")

  Skills

  list of preferred/experience items: "Proficiency in network planning tools and software (e.g., GIS systems, FiberLocator, capacity management platforms) is highly desirable." "Preferred Experience with specific vendor equipment (e.g., Ciena, Nokia, Infinera, Cisco)." "Knowledge of IP routing and switching principles." "Familiarity with network automation concepts." "Experience working with international carrier markets (EMEA and/or APAC) and the fiber/subsea landscape relevant to CoreWeave's global backbone expansion." Also maybe "Strong analytical and problem-solving skills..." but that's already in requirements. We'll avoid duplication. But we need to ensure we don't duplicate content. The "Who You Are" list includes many items: proven experience, demonstrated experience with wavelength/dark fiber, extensive experience in forecasting, solid understanding of network architecture principles, experience working directly with telecommunications vendors, strong analytical and problem-solving skills, excellent communication and interpersonal skills, ability to manage multiple projects, proficiency in network planning tools, Bachelor's degree. That's a mix of requirements and qualifications. We could split: Requirements: experience items (first 6?). Qualifications: education. Skills: tools proficiency, vendor equipment, IP routing, network automation, international carrier markets. Let's extract: From "Who You Are": - Proven experience (typically 5+ years) in network planning for large-scale telecommunications or cloud/content networks. - Demonstrated experience with wavelength (DWDM/coherent optics) and dark fiber-based network solutions. - Extensive experience in performing network capacity forecasting, management, and optimization. - Solid understanding of network architecture principles, including redundancy, diversity, and resilience. - Experience working directly with telecommunications vendors for capacity procurement and solution review. - Strong analytical and problem-solving skills, with the ability to interpret complex technical information and make data-driven decisions. - Excellent communication and interpersonal skills, with the ability to effectively collaborate with technical and non-technical stakeholders. - Ability to manage multiple projects simultaneously and prioritize tasks in a fast-paced environment. - Proficiency in network planning tools and software (e.g., GIS systems, FiberLocator, capacity management platforms) is highly desirable. - Bachelor's degree in Electrical Engineering, Telecommunications, Computer Science, or a related field. Equivalent practical experience will also be considered. Then "Preferred Experience with specific vendor equipment (e.g., Ciena, Nokia, Infinera, Cisco)." - Knowledge of IP routing and switching principles. - Familiarity with network automation concepts. - Experience working with international carrier markets (EMEA and/or APAC) and the fiber/subsea landscape relevant to CoreWeave's global backbone expansion. Thus we can assign: Requirements: first 8 items (up to ability to manage multiple projects). Qualifications: Bachelor's degree item. Skills: proficiency in network planning tools (though it's "highly desirable" maybe skill), plus preferred vendor equipment