Senior Manager, FinOps - Private Cloud Capacity

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real content. The posting includes Company Description (maybe About the role?), Job Description (Responsibilities), Qualifications, Preferred Qualifications, Pay info, Benefits info, maybe Schedule not present. Also there is mention of background screening etc but that's boilerplate? It's part of job description but maybe we keep as part of responsibilities? It's a note about screening; we should keep substantive info: "NOTE: This position requires passing a ServiceNow background screening, USFedPASS..." That's a requirement? It's a condition. Could be part of Qualifications? But it's not a qualification; it's a requirement. We could include under Responsibilities? Probably better to include a short paragraph under Responsibilities or a separate section? There's no explicit heading for "Background check". We could embed in a

under Responsibilities or maybe under a "Requirements" section. Since we have a Qualifications section, we could put that note there as a requirement. But the instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." The background screening note is not minor metadata? It's a condition of employment; maybe we keep as a

under Qualifications or Responsibilities. I'd put it under Qualifications as a note. We need to preserve all substantive information, not invent or summarize away detail. So we need to include all bullet points from responsibilities etc. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We need headings

  for sections: we can decide which sections to include: About the role (maybe Company Description), Responsibilities (Job Description), Qualifications (including required qualifications), Preferred Qualifications (maybe under Skills? but we can have a separate section for Preferred Qualifications? The instruction says use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't list Preferred Qualifications separately; we could incorporate under Qualifications or Skills. Probably better to have Qualifications (required) and then maybe a separate "Preferred Qualifications" as a subsection? But we only allowed those headings; we could put preferred qualifications under Qualifications as a list with a note "Preferred". Or we could create a Skills section for preferred qualifications. However the instruction: "Prefer a few substantive sections over many thin ones." So we could combine required and preferred qualifications into one Qualifications section, with sub-lists? But we need to use

  • for any list. Could have two lists: one for Required Qualifications, one for Preferred Qualifications, each preceded by a

    describing. We also need Benefits and Pay sections if present. Pay: "For positions in this location, we offer a base pay of $165,500 - $289,600, plus equity (when applicable), variable/incentive compensation and benefits." Also note about OTE for sales positions not relevant. So we have Pay info. Benefits: "We also offer health plans, including flexible spending accounts, a 401(k) Plan with company match, ESPP, matching donations, a flexible time away plan and family leave programs." Also mention compensation based on geographic location etc. So we have Benefits. Schedule: not present, so omit. We also need to include Company Description maybe as About the role. The company description paragraph at start: "It all started when engineer Fred Luddy..." That's substantive. We'll put under

    About the role

    with

    . Responsibilities: The "What You Get To Do In This Role" section includes several bullet-like paragraphs. We need to turn each duty into list items. The text includes headings like "Data Center Migration & Exit Strategy", "Infrastructure Asset & Financial Planning", etc. Those are subheadings within responsibilities. We could treat each as a list item with maybe a or just plain text. Since we need

    • for any list of duties. We'll create a
      with each duty as
      • . Inside each
      • we can have the description text. We must preserve all substantive information; not invent or summarize away detail. So we need to include all details from each duty. Let's extract responsibilities sections: - Data Center Migration & Exit Strategy Lead end-to-end planning and execution for data center footprint reduction and migration initiatives. Develop site-by-site execution plans identifying: Rack decommission schedules Aisle and cage consolidation opportunities Space reclamation targets Facility exit milestones Partner with Capacity Engineering teams to: Consolidate workloads Optimize rack utilization Free up servers and racks for decommissioning Partner with Data Center Operations teams to: Execute hardware retirement programs Coordinate equipment removal Ensure operational readiness during migrations Create executive reporting for: Capacity recovery Space reclamation Financial benefits realization Risk mitigation Manage cross-functional governance reviews and executive business updates. - Infrastructure Asset & Financial Planning Drive financial analysis and accounting readiness for infrastructure retirement programs. Assess hardware assets scheduled for decommissioning including: Servers Storage systems Network equipment Data center infrastructure Analyze: Asset age Net book value Remaining depreciation schedules Write-off exposure Develop financial plans supporting: Asset retirement decisions Capital recovery strategies Accounting treatment recommendations Partner closely with Finance and Accounting teams to ensure compliance with corporate accounting policies. - Data Center Contract & Lease Optimization Evaluate colocation and facility contracts associated with migration programs. Identify: Early termination risks Contract obligations Opportunity costs and Exit penalties Develop business cases and executive recommendations for facility exits and consolidation opportunities. Quantify financial impact and long-term savings from data center footprint optimization. - Capacity Supply Chain Transformation Lead modernization and automation of the end-to-end infrastructure supply chain. Design and implement an integrated planning process spanning. Given the Demand forecast by the Demand Planners Capacity planning Procurement Manufacturing Logistics Installation Deployment readiness Build operational visibility into capacity lifecycle stages, including: Demand signal and CAPEX approved Purchase order creation Supplier manufacturing Logistics transit Data center receipt Rack-and-stack Workload-ready capacity Deliver executive dashboards and KPIs that provide visibility into capacity availability and supply chain bottlenecks. Partner with Engineering teams to improve forecasting accuracy and reduce deployment lead times. - AI-Driven Invoice & Receipt Automation Lead digital transformation initiatives to automate infrastructure financial operations. Partner with AI, Finance, Procurement, and Engineering teams to automate: Goods receipt processing Invoice validation Supplier invoice routing Matching and reconciliation workflows Establish operational controls and reporting to improve financial governance and visibility. We need to preserve all that. We'll create a
        with each top-level duty as
        • . Inside each
        • we can have

          for prose and nested

          for sublists? The instruction: "Use
          • for any list of duties/requirements/benefits, and

            for prose." It doesn't forbid nested lists. We'll do nested lists for sub-items. Now Qualifications: Required qualifications list: - Experience in leveraging or critically thinking about how to integrate AI into work processes, decision-making, or problem-solving. This may include using AI-powered tools, automating workflows, analyzing AI-driven insights, or exploring AI's potential impact on the function or industry. - 12 years of related experience with a Bachelor's degree in Engineering, Supply Chain, Finance, Computer Science, Business, or related field; or 8 years and a Master's degree; or a PhD with 5 years experience; or equivalent experience. - 10+ years of experience in one or more of the following: FinOps Cloud economics Capacity planning Data center operations Supply chain management Infrastructure finance - Experience managing large-scale infrastructure programs involving: Data center capacity Server lifecycle management Hardware procurement Capital expenditure planning - Strong understanding of: Asset depreciation Infrastructure accounting Financial planning and analysis Capital investment management - Experience driving cross-functional initiatives across Engineering, Finance, Procurement, and Operations organizations. Also note the background screening requirement: "NOTE: This position requires passing a ServiceNow background screening, USFedPASS (US Federal Personnel Authorization Screening Standards). This includes a credit check, criminal/misdemeanor check and taking a drug test. Any employment is contingent upon passing the screening. Due to Federal requirements, only US citizens, US naturalized citizens or US Permanent Residents, holding a green card, will be considered." This is a requirement; we can include as a

            under Qualifications. Preferred Qualifications list: - Experience operating hyperscale infrastructure environments. - Strong knowledge of private cloud or hybrid cloud capacity management. - Experience leading data center closures, consolidations, or migration programs. - Familiarity with AI/ML-driven business process automation. - Expertise with ERP, procurement, and financial systems. - Knowledge of supply chain analytics and predictive planning techniques. - MBA, Master's degree, or relevant certifications (FinOps, Supply Chain, PMP). We'll include these as a list under Qualifications maybe with a heading "Preferred Qualifications" but we only allowed headings list; we could treat as a subsection within Qualifications using a

            heading? But we must use

            for section headings only. Could we add another

            for "Preferred Qualifications"? The instruction says use

            for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use

            for section headings (e.g. ...)" implying those are examples; we could still use other headings but better to stick to those. However we could incorporate preferred qualifications under Qualifications as a separate list with a preceding

            "Preferred qualifications:" then

            . That satisfies. Now Benefits: list of benefits: health plans including flexible spending accounts, a 401(k) Plan with company match, ESPP, matching donations, a flexible time away plan and family leave programs. Also maybe mention equity, variable/incentive compensation already in Pay. We'll create Benefits
            . Pay: base pay range $165,500 - $289,600, plus equity (when applicable), variable/incentive compensation and benefits. Also note about OTE for sales positions not relevant. Also mention compensation based on geographic location etc. We'll include that as

            maybe. Now About the role: company description paragraph. We also need to include maybe a short paragraph about reporting line: "This role will report to the VP, Technology Business Management & FinOps". That's substantive; we could include under About the role or Responsibilities? Probably under About the role as part of description. Also note about location? Not given. Now we must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we need to cut out sections like "Additional Information Work Personas", "Equal Opportunity Employer", "Accommodations", "Export Control Regulations", "From Fortune..." etc. Also remove "NOTE: This position requires passing a ServiceNow background screening..." we kept as qualification. Now produce HTML fragment. Let's craft:

            About the role

            It all started when engineer Fred Luddy wrote code that automated a tedious task for his coworker, Phyllis. She cried tears of joy. That moment inspired Fred to build a company that