Materials Manager, Manufacturing Facilities
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the posting.
The posting includes:
- About Fluidstack (company description)
- How We Operate (principles)
- The Supply Chain Team (description of team)
- Examples of key problems the team is working on (list)
- Role Scope (description)
- What We're Looking For (list of qualifications)
- Bonus: Manufacturing launches... (list)
- Compensation Range: $199K - $262K
Also there is EEO statement, application instructions, etc. We need to remove boilerplate: EEO, application instructions, etc.
We need to decide sections: Possibly "About the role" (maybe combine company description and How We Operate?), "Responsibilities" (Role Scope?), "Requirements" (What We're Looking For?), "Qualifications" maybe same as requirements? The instructions say we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content.
We have:
- About the role: Could include company description and How We Operate? Or maybe "About Fluidstack" is about company, not role. But we could put under "About the role" a summary of role context: The Supply Chain Team description, examples of key problems, Role Scope. Might be better to separate: "About the role" could be the role scope and team description. "Responsibilities" could be the examples of key problems (list). "Requirements" could be What We're Looking For (list). "Skills" maybe not separate. "Pay" we have compensation range. "Benefits" not mentioned. "Schedule" not mentioned.
Thus we will have sections: About the role, Responsibilities, Requirements, Pay.
We must not include empty sections.
We need to use
for each section heading.
Inside sections, we need to use
for prose,
- for lists.
We must preserve all substantive information, not invent or summarize away detail. So we need to include the text exactly (or close) but we can format.
We must remove boilerplate: EEO, application instructions, etc. Also remove duplicated lines.
Let's extract substantive content:
From "About Fluidstack":
"We exist to make humanity more free. For most of human history, you farmed or you starved. Technology gave people more time for the things they wanted to do, instead of things they had to do. Powerful AI will be the biggest lever for human choice we've ever built - but only if models are aligned with what humanity actually wants. There are groups building AI who don't share these goals. Whoever deploys frontier compute infrastructure fastest will decide whether AI expands human freedom or shrinks it. We're singularly focused on delivering 10 to 100s of GWs of compute faster than anyone else, rethinking every layer of the stack. We acquire power, design and build data centers, and operate them - with teams spanning hardware and software. Speed and scale are our key differentiators. Come be a part of building civilization-scale infrastructure for AI. We hire people who care deeply about this problem space. If that is you, please apply!"
That's substantive.
"How We Operate":
"Be a barrel. Full autonomy. Own things end to end, take on scope without being asked, no permission required to operate outside your core role.Insane urgency. We drive everything forward as fast as possible.Reason from first principles. Challenge every assumption. Zero analogy thinking, no egos, the best idea wins.Love of the game. The frontier of AI is the most interesting problem of our time. We put in long hours at high intensity to push the frontier forward.Build something that actually matters. If you're going to spend your time, spend it on something that matters to the world."
That's also substantive.
"The Supply Chain Team":
"The Supply Chain Team Examples of key problems the team is working on Supply tens of gigawatts of compute, the largest build out of compute in history. Qualify and dual-source across every critical equipment category, with lead-time and capacity thresholds tied directly to the forward build pipeline.Make supply chain the reason we build faster than anyone. Our modular build redefines speed in this industry, and it lives or dies on supply chain. Keep procurement permanently off the critical path so schedule compression stays our advantage, not our constraint.Build the most accurate supply chain prediction modelling that exists. Use the frontier of AI to forecast lead times, demand, and disruption with a precision the industry has never had, and turn that foresight into a structural edge."
That seems like a paragraph with list items but not bullet. We can treat as list.
"Role Scope":
"Own global sourcing for manufacturing facilities: the equipment, fit-out, and services that stand up and run our factories.Negotiate supplier agreements across capital equipment, MRO, and facility services with lead times tied to the production ramp.Qualify and dual-source critical categories so no single supplier can stall the factory.Drive total cost, not just price: freight, spares, uptime, and terms."
That's a list of responsibilities.
"What We're Looking For":
"The below is a starting point. We always make space for exceptional people, so if you don't fit this role exactly, tell us where you would.You've sourced capital equipment or industrial categories at scale and closed the deals yourself.You've built supplier redundancy that got tested and held.You negotiate from a should-cost model, not a quote comparison.You've managed suppliers through a factory launch or major ramp.Your contracts anticipate the failure modes: delays, quality, and support.Bonus: Manufacturing launches. Equipment categories such as weld, CNC, and material handling. International supply bases. ERP procurement."
That's a list of qualifications/requirements.
"Compensation Range: $199K - $262K"
We need to include Pay section.
We must not include EEO statement, application instructions, etc.
We need to avoid duplication: The "Supply Chain Team" paragraph includes "Examples of key problems the team is working on" then list. We can treat that as Responsibilities.
We need to preserve all substantive information: So we need to include the company description and How We Operate maybe under About the role? Or we could have a separate section "About Fluidstack"? But headings limited to given list. We could put under "About the role" a combination of company description and How We Operate and maybe team description. But we need to ensure we don't lose any info.
Better: Use "About the role" for company description and How We Operate (since it's about the role context). Then "Responsibilities" for Role Scope and maybe examples of key problems. Then "Requirements" for What We're Looking For (including bonus). Then "Pay" for compensation.
We must not create Benefits or Schedule sections.
Now format.
We need to use
About the role
then content.
Inside About the role: we have two paragraphs: About Fluidstack and How We Operate. Could combine into one with both? But better to separate into two
elements.
We must not add extra headings.
Now Responsibilities: we need to list the examples of key problems and role scope. Could combine into a
with items.
Let's extract items:
From "Examples of key problems the team is working on":
- Supply tens of gigawatts of compute, the largest build out of compute in history.
- Qualify and dual-source across every critical equipment category, with lead-time and capacity thresholds tied directly to the forward build pipeline.
- Make supply chain the reason we build faster than anyone. Our modular build redefines speed in this industry, and it lives or dies on supply chain.
- Keep procurement permanently off the critical path so schedule compression stays our advantage, not our constraint.
- Build the most accurate supply chain prediction modelling that exists. Use the frontier of AI to forecast lead times, demand, and disruption with a precision the industry has never had, and turn that foresight into a structural edge.
From Role Scope:
- Own global sourcing for manufacturing facilities: the equipment, fit-out, and services that stand up and run our factories.
- Negotiate supplier agreements across capital equipment, MRO, and facility services with lead times tied to the production ramp.
- Qualify and dual-source critical categories so no single supplier can stall the factory.
- Drive total cost, not just price: freight, spares, uptime, and terms.
We could combine all into one list under Responsibilities.
Now Requirements: from What We're Looking For:
- You've sourced capital equipment or industrial categories at scale and closed the deals yourself.
- You've built supplier redundancy that got tested and held.
- You negotiate from a should-cost model, not a quote comparison.
- You've managed suppliers through a factory launch or major ramp.
- Your contracts anticipate the failure modes: delays, quality, and support.
- Bonus: Manufacturing launches.
- Equipment categories such as weld, CNC, and material handling.
- International supply bases.
- ERP procurement.
We need to preserve the "Bonus: Manufacturing launches." as an item? It's a heading for bonus items. Could treat as separate item: "Bonus: Manufacturing launches." Then sub-items? But we can't nest lists? We could just include as separate items: "Bonus: Manufacturing launches." then "Equipment categories such as weld, CNC, and material handling." etc. That's fine.
Now Pay: Pay
Compensation Range: $199K - $262K
We must not include any other sections.
Now ensure we didn't include any boilerplate: We removed EEO, application instructions, etc.
Check for duplicated lines: None.
Now output HTML fragment.
We need to ensure we don't include any markdown fences.
Let's craft:
About the role
We exist to make humanity more free. For most of human history, you farmed or you starved. Technology gave people more time for the things they wanted to do, instead of things they had to do. Powerful AI will be the biggest lever for human choice we've ever built - but only if models are aligned with what humanity actually wants. There are groups building AI who don't share these goals. Whoever deploys frontier compute infrastructure fastest will decide whether AI expands human freedom or shrinks it. We're singularly focused on delivering 10 to 100s of GWs of compute faster than anyone else, rethinking every layer of the stack. We acquire power, design and build data centers, and operate them - with teams spanning hardware and software. Speed and scale are our key differentiators. Come be a part of building civilization-scale infrastructure for AI. We hire people who care deeply about this problem space. If that is you, please apply!
Be a barrel. Full autonomy. Own things end to end, take on
for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. The posting includes: - About Fluidstack (company description) - How We Operate (principles) - The Supply Chain Team (description of team) - Examples of key problems the team is working on (list) - Role Scope (description) - What We're Looking For (list of qualifications) - Bonus: Manufacturing launches... (list) - Compensation Range: $199K - $262K Also there is EEO statement, application instructions, etc. We need to remove boilerplate: EEO, application instructions, etc. We need to decide sections: Possibly "About the role" (maybe combine company description and How We Operate?), "Responsibilities" (Role Scope?), "Requirements" (What We're Looking For?), "Qualifications" maybe same as requirements? The instructions say we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. We have: - About the role: Could include company description and How We Operate? Or maybe "About Fluidstack" is about company, not role. But we could put under "About the role" a summary of role context: The Supply Chain Team description, examples of key problems, Role Scope. Might be better to separate: "About the role" could be the role scope and team description. "Responsibilities" could be the examples of key problems (list). "Requirements" could be What We're Looking For (list). "Skills" maybe not separate. "Pay" we have compensation range. "Benefits" not mentioned. "Schedule" not mentioned. Thus we will have sections: About the role, Responsibilities, Requirements, Pay. We must not include empty sections. We need to use
for each section heading. Inside sections, we need to use
for prose,
- for lists.
We must preserve all substantive information, not invent or summarize away detail. So we need to include the text exactly (or close) but we can format.
We must remove boilerplate: EEO, application instructions, etc. Also remove duplicated lines.
Let's extract substantive content:
From "About Fluidstack":
"We exist to make humanity more free. For most of human history, you farmed or you starved. Technology gave people more time for the things they wanted to do, instead of things they had to do. Powerful AI will be the biggest lever for human choice we've ever built - but only if models are aligned with what humanity actually wants. There are groups building AI who don't share these goals. Whoever deploys frontier compute infrastructure fastest will decide whether AI expands human freedom or shrinks it. We're singularly focused on delivering 10 to 100s of GWs of compute faster than anyone else, rethinking every layer of the stack. We acquire power, design and build data centers, and operate them - with teams spanning hardware and software. Speed and scale are our key differentiators. Come be a part of building civilization-scale infrastructure for AI. We hire people who care deeply about this problem space. If that is you, please apply!"
That's substantive.
"How We Operate":
"Be a barrel. Full autonomy. Own things end to end, take on scope without being asked, no permission required to operate outside your core role.Insane urgency. We drive everything forward as fast as possible.Reason from first principles. Challenge every assumption. Zero analogy thinking, no egos, the best idea wins.Love of the game. The frontier of AI is the most interesting problem of our time. We put in long hours at high intensity to push the frontier forward.Build something that actually matters. If you're going to spend your time, spend it on something that matters to the world."
That's also substantive.
"The Supply Chain Team":
"The Supply Chain Team Examples of key problems the team is working on Supply tens of gigawatts of compute, the largest build out of compute in history. Qualify and dual-source across every critical equipment category, with lead-time and capacity thresholds tied directly to the forward build pipeline.Make supply chain the reason we build faster than anyone. Our modular build redefines speed in this industry, and it lives or dies on supply chain. Keep procurement permanently off the critical path so schedule compression stays our advantage, not our constraint.Build the most accurate supply chain prediction modelling that exists. Use the frontier of AI to forecast lead times, demand, and disruption with a precision the industry has never had, and turn that foresight into a structural edge."
That seems like a paragraph with list items but not bullet. We can treat as list.
"Role Scope":
"Own global sourcing for manufacturing facilities: the equipment, fit-out, and services that stand up and run our factories.Negotiate supplier agreements across capital equipment, MRO, and facility services with lead times tied to the production ramp.Qualify and dual-source critical categories so no single supplier can stall the factory.Drive total cost, not just price: freight, spares, uptime, and terms."
That's a list of responsibilities.
"What We're Looking For":
"The below is a starting point. We always make space for exceptional people, so if you don't fit this role exactly, tell us where you would.You've sourced capital equipment or industrial categories at scale and closed the deals yourself.You've built supplier redundancy that got tested and held.You negotiate from a should-cost model, not a quote comparison.You've managed suppliers through a factory launch or major ramp.Your contracts anticipate the failure modes: delays, quality, and support.Bonus: Manufacturing launches. Equipment categories such as weld, CNC, and material handling. International supply bases. ERP procurement."
That's a list of qualifications/requirements.
"Compensation Range: $199K - $262K"
We need to include Pay section.
We must not include EEO statement, application instructions, etc.
We need to avoid duplication: The "Supply Chain Team" paragraph includes "Examples of key problems the team is working on" then list. We can treat that as Responsibilities.
We need to preserve all substantive information: So we need to include the company description and How We Operate maybe under About the role? Or we could have a separate section "About Fluidstack"? But headings limited to given list. We could put under "About the role" a combination of company description and How We Operate and maybe team description. But we need to ensure we don't lose any info.
Better: Use "About the role" for company description and How We Operate (since it's about the role context). Then "Responsibilities" for Role Scope and maybe examples of key problems. Then "Requirements" for What We're Looking For (including bonus). Then "Pay" for compensation.
We must not create Benefits or Schedule sections.
Now format.
We need to use
About the role
then content. Inside About the role: we have two paragraphs: About Fluidstack and How We Operate. Could combine into onewith both? But better to separate into two
elements. We must not add extra headings. Now Responsibilities: we need to list the examples of key problems and role scope. Could combine into a
- with items.
Let's extract items:
From "Examples of key problems the team is working on":
- Supply tens of gigawatts of compute, the largest build out of compute in history.
- Qualify and dual-source across every critical equipment category, with lead-time and capacity thresholds tied directly to the forward build pipeline.
- Make supply chain the reason we build faster than anyone. Our modular build redefines speed in this industry, and it lives or dies on supply chain.
- Keep procurement permanently off the critical path so schedule compression stays our advantage, not our constraint.
- Build the most accurate supply chain prediction modelling that exists. Use the frontier of AI to forecast lead times, demand, and disruption with a precision the industry has never had, and turn that foresight into a structural edge.
From Role Scope:
- Own global sourcing for manufacturing facilities: the equipment, fit-out, and services that stand up and run our factories.
- Negotiate supplier agreements across capital equipment, MRO, and facility services with lead times tied to the production ramp.
- Qualify and dual-source critical categories so no single supplier can stall the factory.
- Drive total cost, not just price: freight, spares, uptime, and terms.
We could combine all into one list under Responsibilities.
Now Requirements: from What We're Looking For:
- You've sourced capital equipment or industrial categories at scale and closed the deals yourself.
- You've built supplier redundancy that got tested and held.
- You negotiate from a should-cost model, not a quote comparison.
- You've managed suppliers through a factory launch or major ramp.
- Your contracts anticipate the failure modes: delays, quality, and support.
- Bonus: Manufacturing launches.
- Equipment categories such as weld, CNC, and material handling.
- International supply bases.
- ERP procurement.
We need to preserve the "Bonus: Manufacturing launches." as an item? It's a heading for bonus items. Could treat as separate item: "Bonus: Manufacturing launches." Then sub-items? But we can't nest lists? We could just include as separate items: "Bonus: Manufacturing launches." then "Equipment categories such as weld, CNC, and material handling." etc. That's fine.
Now Pay:
Pay
Compensation Range: $199K - $262K
We must not include any other sections. Now ensure we didn't include any boilerplate: We removed EEO, application instructions, etc. Check for duplicated lines: None. Now output HTML fragment. We need to ensure we don't include any markdown fences. Let's craft:About the role
We exist to make humanity more free. For most of human history, you farmed or you starved. Technology gave people more time for the things they wanted to do, instead of things they had to do. Powerful AI will be the biggest lever for human choice we've ever built - but only if models are aligned with what humanity actually wants. There are groups building AI who don't share these goals. Whoever deploys frontier compute infrastructure fastest will decide whether AI expands human freedom or shrinks it. We're singularly focused on delivering 10 to 100s of GWs of compute faster than anyone else, rethinking every layer of the stack. We acquire power, design and build data centers, and operate them - with teams spanning hardware and software. Speed and scale are our key differentiators. Come be a part of building civilization-scale infrastructure for AI. We hire people who care deeply about this problem space. If that is you, please apply!
Be a barrel. Full autonomy. Own things end to end, take on