Strategic Sourcing Leader, Professional Services
OpenAI · San Francisco, CA · 3 wk ago
On-siteOTHR$266k–$295k/yrFull-time
We need to output HTML fragment with sections for headings where content exists. Must not repeat job title. Use for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the posting.
The posting includes:
- About The Team (some description)
- About The Role (description)
- In This Role, You Will (list of duties)
- You Might Thrive In This Role If You Have (list of qualifications/requirements)
- About OpenAI (company description)
- Compensation Range: $266K - $295K
Also location: based in San Francisco, CA. Hybrid work model: three days in office per week, relocation assistance.
We need to include sections only when real specific content.
We should not include boilerplate like EEO, equal opportunity, scam warning, etc. Remove those.
We need to decide which sections to output: maybe About the role (could combine About The Team and About The Role? The instruction: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content.
We have:
- About the role: could be the description of role (About The Role paragraph). Could also include About The Team? Probably not needed as heading; but we could include as part of About the role? The instruction says do NOT repeat the job title as a heading. It doesn't forbid other headings like About the team. But they gave list of suggested headings; we can use those if we have content. We have content for About the role (the paragraph). We have Responsibilities (the "In This Role, You Will" list). We have Requirements/Qualifications/Skills (the "You Might Thrive In This Role If You Have" list). Could split into Requirements and Qualifications and Skills? The list includes experience, leadership, negotiation, understanding models, etc. Could treat as Requirements (or Qualifications). We could make one section for Requirements (or Qualifications). Since they said prefer few substantive sections over many thin ones, we could combine Requirements and Qualifications into one section maybe "Requirements". Or we could have "Qualifications". Let's decide: Use "Requirements" for the list of experience/skills. Could also add "Skills" but maybe not needed.
We have Pay: compensation range given. So we need a Pay section with that.
We have Schedule: hybrid work model (three days in office per week) and location San Francisco, CA, relocation assistance. That's schedule info. So we can have Schedule section.
We have Benefits: not explicitly mentioned besides relocation assistance (maybe considered benefit). Could include relocation assistance under Benefits? But they said only include section if posting has real specific content. Relocation assistance is a benefit. Could create Benefits section with relocation assistance. However we already have Schedule covering hybrid work and location; relocation assistance could be under Benefits. Let's include Benefits section with relocation assistance.
We also have About OpenAI description; could be under About the role? Not exactly. Could be a separate section like "About OpenAI". But not in the list. The instruction says use headings 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. ...). It doesn't say we cannot have other headings, but suggests we should use those for sections. However we could still include a heading like "About OpenAI" but it's not in the list; maybe it's okay but they gave examples. Safer to follow the instruction: only use those headings. Then we need to embed About OpenAI somewhere else, maybe as a paragraph under About the role? But that would misrepresent. However we could treat About OpenAI as part of "About the role" (the role is at OpenAI). Could combine.
Alternatively, we could create a section "About OpenAI" but risk violating instruction. I'd rather follow instruction strictly: only use those headings. So we need to fit all substantive content under those headings.
We have:
- About the role: could include description of role (About The Role) and maybe also About The Team? But we can include a brief paragraph about team under About the role? Might be okay.
- Responsibilities: the bullet list of duties.
- Requirements: the list of qualifications/experience.
- Skills: maybe we could split some skill-based items (like financial judgement, AI usage, inclusive team environment) into Skills. But we can also put all under Requirements.
- Benefits: relocation assistance.
- Pay: compensation range.
- Schedule: hybrid work model, location.
We need to ensure we don't create sections with filler like "commensurate with experience". Not present.
We must not include boilerplate like EEO etc. Remove those lines.
Now craft HTML.
Structure:
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the posting.
The posting includes:
- About The Team (some description)
- About The Role (description)
- In This Role, You Will (list of duties)
- You Might Thrive In This Role If You Have (list of qualifications/requirements)
- About OpenAI (company description)
- Compensation Range: $266K - $295K
Also location: based in San Francisco, CA. Hybrid work model: three days in office per week, relocation assistance.
We need to include sections only when real specific content.
We should not include boilerplate like EEO, equal opportunity, scam warning, etc. Remove those.
We need to decide which sections to output: maybe About the role (could combine About The Team and About The Role? The instruction: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content.
We have:
- About the role: could be the description of role (About The Role paragraph). Could also include About The Team? Probably not needed as heading; but we could include as part of About the role? The instruction says do NOT repeat the job title as a heading. It doesn't forbid other headings like About the team. But they gave list of suggested headings; we can use those if we have content. We have content for About the role (the paragraph). We have Responsibilities (the "In This Role, You Will" list). We have Requirements/Qualifications/Skills (the "You Might Thrive In This Role If You Have" list). Could split into Requirements and Qualifications and Skills? The list includes experience, leadership, negotiation, understanding models, etc. Could treat as Requirements (or Qualifications). We could make one section for Requirements (or Qualifications). Since they said prefer few substantive sections over many thin ones, we could combine Requirements and Qualifications into one section maybe "Requirements". Or we could have "Qualifications". Let's decide: Use "Requirements" for the list of experience/skills. Could also add "Skills" but maybe not needed.
We have Pay: compensation range given. So we need a Pay section with that.
We have Schedule: hybrid work model (three days in office per week) and location San Francisco, CA, relocation assistance. That's schedule info. So we can have Schedule section.
We have Benefits: not explicitly mentioned besides relocation assistance (maybe considered benefit). Could include relocation assistance under Benefits? But they said only include section if posting has real specific content. Relocation assistance is a benefit. Could create Benefits section with relocation assistance. However we already have Schedule covering hybrid work and location; relocation assistance could be under Benefits. Let's include Benefits section with relocation assistance.
We also have About OpenAI description; could be under About the role? Not exactly. Could be a separate section like "About OpenAI". But not in the list. The instruction says use headings 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. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should limit to those headings. So we should not add About OpenAI as a heading; maybe we can incorporate that into About the role paragraph? But it's about the company, not role. However we could omit it as it's not required? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the About OpenAI description somewhere. If we cannot add a heading not in list, we could put it in a
without a heading? The instruction says use
for section headings (e.g. ...). It doesn't say we cannot have other headings, but suggests we should use those for sections. However we could still include a heading like "About OpenAI" but it's not in the list; maybe it's okay but they gave examples. Safer to follow the instruction: only use those headings. Then we need to embed About OpenAI somewhere else, maybe as a paragraph under About the role? But that would misrepresent. However we could treat About OpenAI as part of "About the role" (the role is at OpenAI). Could combine.
Alternatively, we could create a section "About OpenAI" but risk violating instruction. I'd rather follow instruction strictly: only use those headings. So we need to fit all substantive content under those headings.
We have:
- About the role: could include description of role (About The Role) and maybe also About The Team? But we can include a brief paragraph about team under About the role? Might be okay.
- Responsibilities: the bullet list of duties.
- Requirements: the list of qualifications/experience.
- Skills: maybe we could split some skill-based items (like financial judgement, AI usage, inclusive team environment) into Skills. But we can also put all under Requirements.
- Benefits: relocation assistance.
- Pay: compensation range.
- Schedule: hybrid work model, location.
We need to ensure we don't create sections with filler like "commensurate with experience". Not present.
We must not include boilerplate like EEO etc. Remove those lines.
Now craft HTML.
Structure:
About the role
... combine About The Team and About The Role paragraphs ...
Responsibilities
- ... ...
Requirements
- ... ...
Benefits
- Relocation assistance for new employees.
Pay
Compensation range: $266K - $295K.
Schedule
Based in San Francisco, CA. Hybrid work model: three days in the office per week.
We need to ensure we preserve all substantive information from the posting. Let's extract the About The Team paragraph: "OpenAI Finance helps ensure the organisation is positioned for long-term success as we pursue our mission. The Strategic Sourcing & Procurement team helps OpenAI scale responsibly and at speed by choosing the right external partners, structuring strong commercial agreements and building resilient supplier relationships. We partner with teams across the company to turn rapidly evolving needs into practical, economically sound solutions. Professional Services provides specialist expertise and capacity across OpenAI, spanning consulting and advisory, finance and accounting, legal, people-related services and managed services. Our sourcing team helps business leaders define the outcomes they need, select capable partners and establish clear commercial and delivery accountability." That's a lot. About The Role paragraph: "We are seeking a Strategic Sourcing Leader to lead and develop the Professional Services sourcing team and set direction across its portfolio. This is a people-management role with accountability for team performance, commercial quality, stakeholder experience and sustained business outcomes. You will translate business priorities into category strategies, achievable delivery plans and clear decision authority, while developing the judgement and independence of experienced sourcing professionals. You will oversee a broad portfolio, from strategic advisory relationships and enterprise programmes to a high volume of statements of work and renewals. You will remain hands-on in selected complex negotiations and critical decisions, while enabling the team to own and deliver its work. Working with senior leaders across Finance, Accounting, Legal, People, Extended Workforce and the business, you will create clarity from incomplete information, resolve competing priorities and adapt the team's approach as OpenAI grows. This role is based in San Francisco, CA. We use a hybrid work model of three days in the office per week and offer relocation assistance to new employees." Note: location and hybrid and relocation also appear here; but we will move those to Benefits/Schedule sections to avoid duplication. However we must preserve all info; we can keep them in the About the role paragraph but then also list them elsewhere? That would duplicate. Better to extract location/hybrid/relocation from that paragraph and not duplicate. But we need to preserve all substantive info; we can keep them in the Schedule/Benefits sections and remove from About the role paragraph to avoid duplication. However the instruction says preserve ALL substantive information; does not forbid rephrasing or moving content as long as not lost. So we can extract those details and place them in appropriate sections, and adjust the About the role paragraph to omit those specifics (or keep them but then we would have duplication). Safer to remove them from About the role paragraph and place them in Benefits/Schedule. Thus About the role paragraph will be the combination of About The Team and About The Role without location/hybrid/relocation sentences. Let's craft About the role paragraph: "OpenAI Finance helps ensure the organisation is positioned for long-term success as we pursue our mission. The Strategic Sourcing & Procurement team helps OpenAI scale responsibly and at speed by choosing the right external partners, structuring strong commercial agreements and building resilient supplier relationships. We partner with teams across the company to turn rapidly evolving needs into practical, economically sound solutions. Professional Services provides specialist expertise and capacity across OpenAI, spanning consulting and advisory, finance and accounting, legal, people-related services and managed services. Our sourcing team helps business leaders define the outcomes they need, select capable partners and establish clear commercial and delivery accountability. We are seeking a Strategic Sourcing Leader to lead and develop the Professional Services sourcing team and set direction across its portfolio. This is a people-management role with accountability for team performance, commercial quality, stakeholder experience and sustained business outcomes. You will translate business priorities into category strategies, achievable delivery plans and clear decision authority, while developing the judgement and independence of experienced sourcing professionals. You will oversee a broad portfolio, from strategic advisory relationships and enterprise programmes to a high volume of statements of work and renewals. You will remain hands-on in selected complex negotiations and critical decisions, while enabling the team to own and deliver its work. Working with senior leaders across Finance, Accounting, Legal, People, Extended Workforce and the business, you will create clarity from incomplete information, resolve competing priorities and adapt the team's approach as OpenAI grows." Now Responsibilities: the list starting with "In This Role, You Will Lead and develop the team: ..." etc. Need to break into bullet points. Let's extract each bullet: - Lead and develop the team: set clear objectives and expectations, delegate with appropriate decision boundaries, provide regular feedback, review performance and address persistent gaps. - Build development and coverage plans that strengthen capability and reduce reliance on individual experts. - Set the Professional Services portfolio strategy and roadmap, connecting business objectives, demand, spend, supplier markets and risk. - Guide category plans and decisions on where to compete, consolidate, retain specialist partners or change the service delivery model. - Manage the team's pipeline and capacity across strategic negotiations, supplier governance and recurring SOWs. - Allocate work by capability, complexity and risk; make resource constraints and dependencies visible; and agree priorities and recovery plans before commitments become unachievable. - Personally lead selected critical negotiations and set standards for commercial quality across the team. - Review strategy and assumptions early, using credible alternatives and comparable economics to shape scope, resource mix, pricing, deliverables, acceptance criteria, change controls, audit rights and exit protections. - Build proportionate intake, tiering, preferred-partner models, playbooks and review pathways with Procurement Operations, Contract Management, Enablement and control functions. - Agree decision rights and usable handovers so repeatable work moves efficiently and material exceptions receive the right attention. - Strengthen supplier relationships and accountability through segmentation, competition, performance reviews and improvement plans. - Agree post-signature owners with the business and use service evidence, concentration risk, renewal exposure and transition options to guide supplier decisions. - Assess supplier productivity proposals for their effect on staffing, fees, quality and delivery risk. - Partner with Finance and Accounting on spend visibility, demand scenarios, forecasting, approval discipline and invoice-to-contract alignment. - Test fee models,