Jobs · Supply Chain

Senior Technical Sourcing Manager, Server & Storage Platforms

IREN · United States · 1 mo ago
RemoteRemoteSupply Chain$200k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: About IREN (company description) maybe "About the role"? Actually there is a "About IREN" paragraph, then "The Role" description. We can treat that as About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content accordingly. We have: - About IREN: description of company building infrastructure. Could be "About the role"? Actually "About the role" is about the role itself, not company. But we have "The Role" paragraph describing the role. That could be "About the role". We'll put that under

About the role

. - Responsibilities: The bullet list under "Job Requirements" actually looks like responsibilities (own the end-to-end sourcing relationship...). Then there is a separate "Job Responsibilities" heading but it's actually a list of qualifications? Wait the posting: after "Job Requirements" there is a list of responsibilities (own the end-to-end sourcing...). Then after that there is "Job Responsibilities" heading but then it lists qualifications/experience (12+ years...). That seems swapped. We need to preserve content as is. So we have two blocks: first block after "The Role" is a list of responsibilities (own the end-to-end sourcing...). Then later there is a block labeled "Job Responsibilities" that actually contains qualifications/experience. We need to decide which to map to Responsibilities section and which to Requirements/Qualifications/Skills. Given typical job posting: Responsibilities are duties; Requirements are qualifications/experience; Skills maybe separate. The posting has: - After "The Role": a paragraph describing role, then a list starting with "Own the end-to-end sourcing relationship..." etc. That's clearly responsibilities. - Then after that list, there is a heading "Job Responsibilities" but the content under it is: "12+ years of experience in technical sourcing..." etc. That's actually requirements/qualifications. Thus we need to interpret correctly: The first list = Responsibilities. The second block = Requirements (or Qualifications). We'll treat the second block as Requirements (maybe also Qualifications). We can split: Requirements could be experience, education; Qualifications could be preferred experience etc. But we can combine. We also have Benefits section: detailed benefits listed. Pay: Salary range: "Compensation The expected base salary for this role starts at $200,000-250,000k USD." Also later "Salary 250000 - 250000 USD (yearly)" seems duplicate. We'll include Pay section with the base salary range. Schedule: Not mentioned. So omit Schedule. Skills: Not explicitly listed; maybe we can infer from responsibilities but we should not invent. So omit Skills if no explicit content. Qualifications: Could be the education requirement: Bachelor's degree... plus preferred experience. We'll put that under Qualifications. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We need to use

for each heading. Use
  • for any list of duties/requirements/benefits. Use

    for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip the EEO statement at end, the "We value diverse perspectives..." etc. Also the "IE US Operations Inc., the employing entity..." etc. Also the "By applying..." etc. Also the "Salary 250000 - 250000 USD (yearly)" maybe duplicate but we can keep as part of Pay? It's duplicate but we can keep but maybe it's considered duplicated lines; we should remove duplicated lines. The base salary range already given; the duplicate line is same numbers but maybe we can keep one. We'll keep the earlier description. We need to ensure we don't include the "Job ID / requisition numbers" none present. Now craft HTML. First, About the role: combine the "About IREN" paragraph and "The Role" paragraph? Actually About the role should describe the role, not company. But we have both. We could put company description under About the role? Might be okay. But we could also treat About IREN as a separate section? Not in allowed headings. So we incorporate it into About the role as prose. Thus:

    About the role

    IREN is building the infrastructure behind the next era of AI. We design, build, and operate massive-scale data centers, and we’re racing to deploy some of the largest fleets of GPU and CPU compute on the planet. This isn’t incremental growth — it’s a full-throttle sprint to power the frontier of AI and high-performance computing. Our Technical Sourcing team sits at the center of that mission, securing the compute, services, and partnerships that let IREN move faster than anyone else in the industry.

    IREN is looking for a Technical Sourcing Manager, Server & Storage Platforms to take full ownership of our most critical OEM and ODM relationships. This is not a support role — you’ll be the commercial and operational owner of multimillion-dollar partnerships, driving the negotiations, pricing strategy, and supply commitments that determine how fast IREN can build. If you love the adrenaline of a supply-constrained market, thrive on high-stakes negotiation, and want to see your work show up as racks going live in a live data center within weeks of your decisions — this is the seat for you. You’ll operate with real autonomy, direct executive visibility, and the mandate to shape how IREN sources Server & Storage Platforms at hyperscale.

    Now Responsibilities: list from first block. We need to capture each bullet as
  • . The block: Own the end-to-end sourcing relationship with rack integration ODM partners: commercial negotiations, pricing, quoting, contracting, and account governance. Manage ODM partners’ rack integration build process, ensuring quality, schedule, and specification are met at every step. Own sourcing and vendor management for installation services, including Professional Services for Installation, Deployment & Verification (IDV) of AI infrastructure racks. Negotiate pricing, master purchase agreements, statements of work, service agreements, and SLAs that keep ODM and installation services vendors accountable to IREN’s speed and quality bar. Partner closely with Engineering, Operations, Deployment, and Program Management to align ODM rack integration and installation vendor capacity with delivery and go-live timelines — no excuses, no slippage. Own ODM and vendor performance end-to-end: run competitive bids, drive cost and reliability improvements, and raise the bar across the rack integration and installation services portfolio. Track ODM partners’ roadmaps and manufacturing/integration capacity to keep sourcing strategy ahead of upcoming platform transitions. Build and run the spares/repair strategy, including inventory planning and RMA turnaround, to keep fleets running at full capacity. Build and maintain demand forecasts with capacity planning and finance to inform purchase order timing and volume commitments. Keep contract documentation, vendor scorecards, and reporting sharp and ready for leadership at any moment. We'll put each as
  • . Now Requirements: The second block under "Job Responsibilities" heading (but actually requirements). Content: 12+ years of experience in technical sourcing, procurement, or vendor/services management, ideally within data center deployment or field services. Proven experience managing rack integration ODM or contract manufacturer relationships, and/or managing installation services such as deployment, commissioning, or verification. Strong contract negotiation skills and a track record managing multiple concurrent, high-stakes ODM and services vendor relationships. Excellent cross-functional collaboration skills — you move fluidly between engineering, operations, and finance. Bachelor’s degree in Supply Chain, Business, Engineering, or related field (or equivalent experience). Preferred Experience managing rack integration ODMs or Professional Services/installation vendors in support of large-scale AI/GPU compute deployments. Familiarity with data center commissioning timelines and how rack delivery integrates with installation, deployment, and verification schedules. We could split: Requirements = the first five items (experience, proven experience, strong contract negotiation, excellent cross-functional, Bachelor's). Qualifications = Preferred Experience and Familiarity (maybe also preferred). But we can also put all under Requirements and leave Qualifications empty (omit). However we need to include Qualifications section only if there is real specific content. We have preferred experience and familiarity; those could be qualifications. So we can make Qualifications section with those two items. Thus:

    Requirements

    • 12+ years of experience in technical sourcing, procurement, or vendor/services management, ideally within data center deployment or field services.
    • Proven experience managing rack integration ODM or contract manufacturer relationships, and/or managing installation services such as deployment, commissioning, or verification.
    • Strong contract negotiation skills and a track record managing multiple concurrent, high-stakes ODM and services vendor relationships.
    • Excellent cross-functional collaboration skills — you move fluidly between engineering, operations, and finance.
    • Bachelor’s degree in Supply Chain, Business, Engineering, or related field (or equivalent experience).

    Qualifications

    • Preferred Experience managing rack integration ODMs or Professional Services/installation vendors in support of large-scale AI/GPU compute deployments.
    • Familiarity with data center commissioning timelines and how rack delivery integrates with installation, deployment, and verification schedules.
    Now Benefits: list from Benefits section. We need to capture all bullet points under Health & Wellness, Retirement & Financial Wealth, Time Off & Leave Programs, Growth & Development, Community & Culture. We'll combine into a single list under Benefits? The instruction: use
    • for any list of duties/requirements/benefits. So we can make a single list with all benefits items. Let's extract: Health & Wellness: - 100% company paid health insurance premiums (medical, dental, and vision) for employees, 75% company paid coverage for dependents - Company-paid short-term and long-term disability insurance - Voluntary life, critical illness, and accident coverage available - Health Savings Accounts (HSA) – when combined with the High Deductible Health Plan - Employee Assistance Program and wellness resources Retirement & Financial Wealth: - 401(k) retirement plan with company match - Access to financial planning and legal services Time Off & Leave Programs: - Paid Time Off (PTO) and paid holidays Growth & Development: - Internal skills training and advancement pathways - Professional development to support certifications, continuing education, or role related training Community & Culture: - Company events and team-building activities We'll include each as
    • . Now Pay: we have compensation description. Content: "Compensation The expected base salary for this role starts at $200,000-250,000k USD.Actual compensation will be determined based on factors such as experience, qualifications, and market data for the region.Total Compensation package may be inclusive of annual incentive bonus, equity (long-term incentive).Relocation or Living-out-allowance / per diem (as appliable and based on successful candidate circumstances)" We need to preserve all substantive information. We'll put into

      . We should maybe separate sentences for readability but keep as is. Now we must not include duplicated lines like the Salary line at end. We'll omit that. Now ensure we don't include any boilerplate like EEO etc. Remove the paragraph starting "We value diverse perspectives..." and the IE US Operations Inc. statement, the E-Verify, etc. Now produce

Similar jobs