Senior Strategic Sourcing Manager, Cloud & Strategic Partnerships

We need to output HTML fragment with sections: About the role? Actually the posting includes "Who We Are", "Who You Are", "What You'll Be Doing", "Experience You'll Need", "US Pay Range". Also maybe "Join Us in Securing and Accelerating the World's AI Transformation" is more marketing but could be considered part of description. However we must only include sections when posting has real specific content. We should not repeat job title as heading. We need headings: About the role? Not present. The sections we have: Who We Are (company description), Who You Are (role description), What You'll Be Doing (responsibilities), Experience You'll Need (requirements), US Pay Range (pay). Also maybe Benefits? Not given. Schedule? Not given. So we include those sections with appropriate headings: "About the Company" maybe? But instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use those as examples; we can use similar but likely they expect those headings. However we have content that maps: "Who We Are" could be About the role? Actually About the role is about the job, not company. But we have company description; maybe we can put under "About the role"? Might be okay. "Who You Are" could be Requirements/Qualifications. "What You'll Be Doing" is Responsibilities. "Experience You'll Need" is Requirements/Qualifications as well. Pay range is Pay. We must not invent sections like Benefits if not present. So we will have sections: About the role (company overview), Responsibilities, Requirements, Pay. We need to use

• for any list of duties/requirements/benefits. So we need to turn bullet points into lists. We must preserve all substantive information, not invent or summarize away detail. So we need to keep details like specific tasks, etc. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we must cut out the EEO sections, inclusion sections, Linkedin etc. Also remove "Join Us in Securing and Accelerating the World's AI Transformation" maybe considered marketing but could be kept? It's not boilerplate; it's a description of Rubrik's mission. Might be considered part of "Who We Are". But we already have Who We Are earlier. The later paragraph repeats similar mission. Might be duplicate; we can drop duplicates. We need to output only HTML fragment, no /, no markdown fences. Let's extract content: Who We Are Rubrik is one of the fastest-growing companies in Silicon Valley, revolutionizing data protection and management in the multi-cloud IT industry. Our mission is to unlock the power of data by organizing and protecting the world's business information, and we've built a forward-thinking, design-oriented brand that is changing how enterprises think about resilience. We don't wait for someone else to define the industry — we define it ourselves. Rubrik was the first platform to orchestrate data for hybrid and multi-cloud enterprises anytime, anywhere, blending future-proof architecture with consumer-grade simplicity. We're looking for people who produce extraordinary results, who are comfortable in ambiguity, and who are excited by hard problems. If you have a limitless drive and like to win, we want to talk to you. Who You Are As Rubrik's business increasingly runs on hyperscale cloud infrastructure, we're adding an individual contributor Senior Strategic Sourcing Manager to own the end-to-end, 360° relationship with our most strategic cloud and technology partners — including AWS, Google Cloud, and Microsoft — as well as other key strategic vendor relationships across the business. While strategic cloud and technology partnerships are the anchor of this position, you'll also flex into broader sourcing deals across the team's portfolio as priorities shift — negotiating agreements, running competitive sourcing events, and partnering cross-functionally wherever the business needs strong commercial leadership. You'll work closely with cross-functional partners including Engineering, IT, InfoSec, Legal, Finance, and Accounting. You're a self-starter who's comfortable operating with limited direction and full ownership of your domain — a pragmatic problem-solver who thrives in a fast-paced environment. You will report to the Head of Global Procurement and be accountable for savings, risk, and relationship health across your portfolio. What You'll Be Doing Strategic Cloud & Partner Relationship Management Own the 360° relationship with Rubrik's strategic cloud providers (AWS, Google Cloud, Microsoft) and other top-tier strategic vendors — spanning commercial negotiations, governance, payment, escalation management, and long-term partnership strategy.Serve as the primary sourcing point of contact for these accounts, coordinating quarterly and annual business reviews, scorecards, and joint roadmap discussions with internal stakeholders and partner account teams.Structure and negotiate complex, multi-year cloud and strategic partnership agreements, including committed-use discounts, credits, co-marketing terms, and other commercial levers that drive measurable value.Build a deep understanding of each strategic partner's roadmap, pricing constructs, and program offerings, and translate that knowledge into strategies that benefit Rubrik's cost position and technical roadmap. Broader Strategic Sourcing Support Beyond the strategic account portfolio, project-manage additional complex deals across Rubrik's technology sourcing categories — software, hardware, SaaS, cloud, and professional services — driving collaboration among all parties to reach favorable terms.Develop and drive category strategy and optimization opportunities across Engineering, InfoSec, and IT, as capacity and business priorities require.Prepare RFQs and RFPs, evaluate proposals, and administer competitive sourcing events for a range of deals as needed.Manage the commercial aspects of contracts and license agreements, ensuring obligations are met and renewals are tracked in a scalable way. Leadership & Cross-Functional Impact Act as a thought leader from a sourcing/procurement perspective, partnering with business stakeholders to develop new and creative strategies.Build strategic relationships with both external suppliers and internal business partners to drive results and influence decisions.Contribute to programs that assess and promote supplier performance and development, including goal-setting, business reviews, and formal scorecards.Establish and report on KPIs supporting the procurement team's goals, with particular visibility into strategic cloud spend and value delivered. Experience You'll Need 8+ years of experience in Indirect or Technology Sourcing, with a strong track record negotiating complex technology, SaaS, or cloud agreements in a fast-paced environment.Direct experience managing strategic relationships with major cloud or technology providers (e.g., AWS, Google Cloud, Microsoft) strongly preferred.Excellent negotiation skills and broad procurement category management experience (Software, Hardware, SaaS, Cloud, and Professional Services).Proven ability to manage a portfolio of both strategic, high-visibility accounts and a rotating set of tactical or ad hoc deals simultaneously.Excellent customer service skills and the ability to partner with key stakeholders and build relationships across multi-functional teams.Experience with supplier scorecards and supplier relationship management.Strong financial and analytical skills to identify cost savings opportunities and support business-case development.Self-starting, entrepreneurial, scrappy, and resourceful, with a strong work ethic and high integrity.Working knowledge of Coupa and NetSuite preferred.Experience in contract negotiation from a legal perspective (e.g., J.D.) a plus. US Pay Range $165,600—$248,400 USD We also have "The minimum and maximum base salaries for this role are posted below; additionally, the role is eligible for bonus potential, equity and benefits." That's pay info plus mention of bonus, equity, benefits. We should include that as part of Pay section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state bonus potential, equity and benefits. So we can include a Pay section that mentions salary range and also bonus, equity, benefits. But we should not create a Benefits section separately unless benefits are detailed. Since they only mention eligibility for bonus, equity and benefits (no detail), we could include that in Pay section. However we should not create a Benefits section with placeholder text. So we will include Pay section with salary range and note about bonus, equity, benefits. Now we need to format. We'll have:

  About the role

  Who We Are Rubrik is one of the fastest-growing companies in Silicon Valley, revolutionizing data protection and management in the multi-cloud IT industry. Our mission is to unlock the power of data by organizing and protecting the world's business information, and we've built a forward-thinking, design-oriented brand that is changing how enterprises think about resilience. We don't wait for someone else to define the industry — we define it ourselves. Rubrik was the first platform to orchestrate data for hybrid and multi-cloud enterprises anytime, anywhere, blending future-proof architecture with consumer-grade simplicity. We're looking for people who produce extraordinary results, who are comfortable in ambiguity, and who are excited by hard problems. If you have a limitless drive and like to win, we want to talk to you.

  But maybe we should separate Who We Are and Who You Are? However we only have About the role heading; we could include both Who We Are and Who You Are under About the role? Might be mixing. Better to have two sections: About the company (maybe not in list) but we could use About the role for Who You Are? Actually About the role usually describes the role, not company. Who You Are describes the role expectations. So we could put Who You Are under About the role. And Who We Are could be omitted or placed as a brief intro before sections? 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. It didn't forbid having a preamble paragraph before headings. So we could keep Who We Are as a leading

  before any headings. Then have headings for Responsibilities, Requirements, Pay. Thus:

  Who We Are Rubrik is one of the fastest-growing companies in Silicon Valley, revolutionizing data protection and management in the multi-cloud IT industry. Our mission is to unlock the power of data by organizing and protecting the world's business information, and we've built a forward-thinking, design-oriented brand that is changing how enterprises think about resilience. We don't wait for someone else to define the industry — we define it ourselves. Rubrik was the first platform to orchestrate data for hybrid and multi-cloud enterprises anytime, anywhere, blending future-proof architecture with consumer-grade simplicity. We're looking for people who produce extraordinary results, who are comfortable in ambiguity, and who are excited by hard problems. If you have a limitless drive and like to win, we want to talk to you.

  Then

  About the role

  with Who You Are content. Then

  Responsibilities

  with What You'll Be Doing content, broken into lists. Then

  Requirements

  with Experience You'll Need content, broken into lists. Then

  Pay

  with pay range and note about bonus, equity, benefits. We need to turn duties into
  • . The responsibilities section has multiple bullet-like sentences separated by periods. We need to extract each distinct duty. Let's parse What You'll Be Doing: Strategic Cloud & Partner Relationship Management - Own the 360° relationship with Rubrik's strategic cloud providers (AWS, Google Cloud, Microsoft) and other top-tier strategic vendors — spanning commercial negotiations, governance, payment, escalation management, and long-term partnership strategy. - Serve as the primary sourcing point of contact for these accounts, coordinating quarterly and annual business reviews, scorecards, and joint roadmap discussions with internal stakeholders and partner account teams. - Structure and negotiate complex, multi-year cloud and strategic partnership agreements, including committed-use discounts, credits, co-marketing terms, and other commercial levers that drive measurable value. - Build a deep understanding of each strategic partner's roadmap, pricing constructs