Senior Supply Chain Manager (Strategic Planning)

We need to output HTML fragment with sections: About the role (but note the page already shows job title, we shouldn't repeat job title as heading). The posting includes "About Nscale" (company description) then "About the Role". We need to include sections only when there is real specific content. We have "About the Role" content. Also "What You'll Do", "Who You Are", maybe "Benefits" (they mention benefits package). Also "Pay" (salary range). Also maybe "Schedule"? Not present. So we include sections: About the Role (maybe we can combine with "What You'll Do"? But they said use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly. We have "About the Role" description (the paragraph after About the Role heading). Then "What You'll Do" corresponds to Responsibilities. Then "Who You Are" corresponds to Requirements/Qualifications/Skills. Then benefits and pay. We need to avoid repeating job title as heading. We'll output:

About the Role

... (the paragraph about hiring Senior Supply Chain Manager ... )

Then Responsibilities:

Responsibilities

• ... each bullet from "What You'll Do" ...

Then Requirements/Qualifications/Skills: maybe combine into one section "Requirements" or separate? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose to have Requirements (or Qualifications) covering the "Who You Are" bullet points. We'll output:

Requirements

• ... each bullet from Who You Are ...

Then Benefits:

Benefits

... description of benefits ...

Pay:

Pay

Salary Range $100,000—$170,000 USD ... maybe also mention bonus, equity, commission.

We should not include Schedule (no info). Also we should not include metadata like Job ID. Remove boilerplate like privacy notice, unsolicited candidate submissions. Also remove "About Nscale" maybe? It's company description; not required as a heading per list but could be included as "About the Company"? Not in allowed headings. Probably we should omit it because not in list; but we could include as a paragraph without heading? The instruction: 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 those for section headings. It might be okay to include other headings but better to stick to those. The "About Nscale" is not required; we can drop it as it's not a specific section heading from list. However we need to preserve ALL substantive information; dropping company description loses info. But maybe it's considered boilerplate? It's substantive about the company. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep it. But we need to put it somewhere. Could be a

without heading, or we could use

About Nscale

though not in list but maybe acceptable. The instruction says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. implies those are examples, not exclusive. So we can use other headings as needed. Safer to include About Nscale as heading. Thus sections: About Nscale, About the Role, Responsibilities, Requirements, Benefits, Pay. We need to ensure we don't create empty sections. Now extract content. About Nscale paragraph: "Nscale is the GPU cloud engineered for AI. We provide cost-effective, high-performance infrastructure for AI start-ups and large enterprise customers. Nscale enables AI-focused companies to achieve superior results by reducing the complexity of AI development. Our GPU cloud bolsters technical capabilities and directly supports strategic business outcomes, including cost management, rapid innovation, and environmental responsibility. We thrive on a culture of relentless innovation, ownership, and accountability, where every team member takes pride in their work and drives it with excellence and urgency. As an Nscaler, you'll build trust through openness and transparency, where everyone is inspired to do their best work. If you join our team, you'll be contributing to building the technology that powers the future." About the Role paragraph: "We're hiring a Senior Supply Chain Manager to join our Strategic Planning team, where you'll bring hands-on supply chain expertise to the work of forecasting AI demand and capacity supply globally. This is an individual contributor role for someone who has spent their career deep in supply chain — procurement, supplier management, BOM-level planning, lead time and capacity dynamics — and wants to apply that expertise at the strategic level, rather than someone coming from a pure forecasting or planning background without supply chain depth. You'll sit within Strategic Planning but work in close partnership with Sales, Finance, and Product Engineering, ensuring that commercial pipeline signals, customer contracts, and AI cluster configurations are grounded in real supply chain constraints — component lead times, supplier capacity, and build feasibility — as they're translated into global demand plans." What You'll Do bullets (need to parse): - Early on, you'll get deep on how demand signals currently flow through the business — auditing existing forecast processes across GPU nodes, rack assemblies, networking fabric, and power and cooling equipment, and mapping how commercial pipeline, customer contracts, and AI cluster configurations translate (or fail to translate) into BOM-level demand signals. You'll bring your supply chain lens to this audit, identifying where forecasts break down against real-world procurement and supplier constraints, and you'll build working relationships with the Sales, Finance, and Product Engineering teams you'll partner with continuously. - From there, you'll contribute to and help maintain the global demand forecast — a rolling 18–24 month view across GPU nodes, racks, networking, and power/cooling — modeling demand volatility, ramp curves, and burst scenarios across customer segments. You'll ground these models in supplier lead times, component availability, and build capacity, working closely with supply chain and procurement to stress-test whether demand plans are actually executable. You'll help integrate revenue forecasts with infrastructure capacity planning, flag risks tied to lead times and GPU availability, and contribute analysis into monthly demand reviews. - Over time, you'll become a key supply-chain voice within Strategic Planning — feeding data-driven, supplier-informed input into capital planning processes, supporting GPU reservation and long-lead component strategy, and helping ensure deployment timing holds up against contractual and revenue commitments. You'll be measured on forecast accuracy, the quality of your supply chain input into planning decisions, responsiveness to demand shifts, and overall demand plan stability. We need to split into list items; each bullet could be a

. Could combine sentences but keep each bullet as separate

. We'll keep three

items. Who You Are bullets: - 6+ years of experience in supply chain management, procurement, or infrastructure/hardware supply chain — this is a supply chain role first, planning role second - Deep, hands-on knowledge of supply chain mechanics: supplier management, lead times, BOM structures, procurement cycles, and build/manufacturing constraints - Experience in high-growth technology, infrastructure-heavy, or hardware environments (AI, cloud, data center, or similar strongly preferred) - Strong understanding of infrastructure components including compute, networking, racks, and power systems, from a supply chain and sourcing perspective - Ability to translate real-world supply chain constraints into forecasting and planning inputs — you know what's actually buildable and deliverable, not just what's modeled - Solid analytical skills, comfortable working with demand models and scenario planning, even if forecasting isn't your primary background - Strong cross-functional collaboration skills; comfortable partnering with Finance, Sales, and Engineering without needing to manage them - Comfortable operating in ambiguity, contributing to planning frameworks being built from the ground up We'll make each a

. Benefits paragraph: "In addition to base salary, this role may be eligible for bonus, equity, and/or commission programs. Nscale may offer a competitive benefits package including medical, dental, vision, flexible paid time off, parental leave, and retirement plan participation." Pay paragraph: "The range below reflects the base salary for the position. Actual compensation may vary based on job-related factors such as skill set, experience, education, and location. In addition to base salary, this role may be eligible for bonus, equity, and/or commission programs. Nscale may offer a competitive benefits package including medical, dental, vision, flexible paid time off, parental leave, and retirement plan participation. Salary Range $100,000—$170,000 USD" But note benefits already mentioned; we might duplicate. Better to separate: Benefits section includes medical etc. Pay section includes salary range and mention of bonus/equity/commission. Thus Benefits: "Nscale may offer a competitive benefits package including medical, dental, vision, flexible paid time off, parental leave, and retirement plan participation." Pay: "The range below reflects the base salary for the position. Actual compensation may vary based on job-related factors such as skill set, experience, education, and location. In addition to base salary, this role may be eligible for bonus, equity, and/or commission programs. Salary Range $100,000—$170,000 USD" We should not repeat benefits in Pay. Now remove boilerplate: "For information on how Nscale handles candidate personal data, please see our Employee & Candidate Privacy Notice: Here." and "Nscale does not accept unsolicited candidate submissions from recruitment agencies." Also remove "About Nscale" maybe we keep. Now produce HTML fragment. We'll output:

About Nscale

...

About the Role

...

Responsibilities

• ...
...

Requirements

• ...
...

Benefits

...

Pay

...

Make sure no extra whitespace issues. Let's craft the exact strings. About Nscale paragraph: exactly as given. About the Role paragraph: exactly as given. Responsibilities items: Item1: "Early on, you'll get deep on how demand signals currently flow through the business — auditing existing forecast processes across GPU nodes, rack assemblies, networking fabric, and power and cooling equipment, and mapping how commercial pipeline, customer contracts, and AI cluster configurations translate (or fail to translate) into BOM-level demand signals. You'll bring your supply chain lens to this audit, identifying where forecasts break down against real-world procurement and supplier constraints, and you'll build working relationships with the Sales, Finance, and Product Engineering teams you'll partner with continuously." Item2: "From there, you'll contribute to and help maintain the global demand forecast — a rolling 18–24 month view across GPU nodes, racks, networking, and power/cooling — modeling demand volatility, ramp curves, and burst scenarios across customer segments. You'll ground these models in supplier lead times, component availability, and build capacity, working closely with supply chain and procurement to stress-test whether demand plans are actually executable. You'll help integrate revenue forecasts with infrastructure capacity planning, flag risks tied to lead times and GPU availability, and contribute analysis into monthly demand reviews." Item3: "Over time, you'll become a key supply-chain voice within Strategic Planning — feeding data-driven, supplier-informed input into capital planning processes, supporting GPU reservation and long-lead component strategy, and helping ensure deployment timing holds up against contractual and revenue commitments. You'll be measured on forecast accuracy, the quality of your supply chain input into planning decisions, responsiveness to demand shifts, and overall demand plan stability." Requirements items: 1.