Procurement Specialist

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay, Schedule. Use

for each heading. Use

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

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". So we need to extract content. Let's parse the posting. Overview: description of role. Could be "About the role". We'll put that in

  About the role

  with

  containing overview text. Responsibilities: there is a "Responsibilities" heading with bullet points. We'll output

  Responsibilities

  then
  • each bullet. Qualifications: there is "Qualifications" with Minimum Qualifications and Preferred Qualifications. We'll output

    Qualifications

    then maybe separate sub-sections? But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use Qualifications for both minimum and preferred. Could also use Requirements for minimum? But we have Qualifications heading allowed. We'll put both minimum and preferred under Qualifications, maybe separate
    for each. Skills: maybe we can extract skills from qualifications? But we have no explicit skills section. Could combine skills within Qualifications. But we could create a Skills heading if there is explicit skill list. The posting mentions "Experience using AI tools", "Experience reviewing and redlining commercial agreements", etc. Those are more qualifications/experience. Could treat them as Skills. However we should only create sections if there is real specific content. There is content for skills (like "Experience with SaaS licensing models", "Proficiency with Notion, SharePoint, and Microsoft 365"). Might be better to put under Qualifications. The instruction: "Prefer a few substantive sections over many thin ones." So we likely combine into Qualifications. Benefits: there is a Benefits section with list. We'll output

    Benefits

    then
    • each benefit. Pay: there is pay range and bonus. We'll output

      Pay

      with

      containing base pay range and discretionary bonus. Schedule: there is mention of remote-first working conditions, generous time off, wellness days, etc. Also "Travel Required Up to 10%". That could be schedule? There's no explicit schedule like full-time, part-time, hours. Could infer schedule is full-time remote-first. But we should not create Schedule unless posting actually states them. It does mention remote-first working conditions, generous time off, wellness days. That's more about benefits/work arrangement. Could treat as Schedule? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state remote-first working conditions, generous time off, wellness days. That's about schedule/time off. So we can create Schedule section with that info. But we also have travel required up to 10% - could be part of Schedule. Thus we will have sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. We must not include Requirements heading if we don't have separate content; we can skip. Now we need to extract precise content, preserving all substantive information, not inventing or summarizing away detail. Let's extract About the role: The overview paragraph(s) before Responsibilities. From text: "Rithum™ is the world’s most trusted commerce network, accelerating how brands, suppliers, and retailers work together to deliver seamless e-commerce experiences. We provide an unmatched platform for brands and retailers, enabling them to accelerate growth, optimize operations across channels, scale product offerings and enhance margins. Today, more than 40,000 companies trust Rithum to grow their business across hundreds of channels, representing over $50 billion in annual GMV. Using our commerce, marketing, and delivery solutions, our customers create optimized consumer shopping journeys from beginning to end. Overview As a Procurement Specialist, you own procurement from intake through executed contract, keeping requests moving while protecting spend, timelines, and our risk posture. You partner closely with Legal, Security, Privacy, IT, and Finance to land the right deals on the right terms, and you run sourcing events that produce real savings rather than simply processing paperwork. This is a hands-on, high-visibility role on a small team: in your first 90 days you ramp on Zip, the intake process, and the active vendor portfolio and begin running your own sourcing events and renewals; by six months you own a defined category of spend and have removed at least one real source of friction from the process; and within a year stakeholders come to you because procurement moves faster with you in it, with measurable savings and cycle time improvement to show for it. At Rithum, all team members are expected to leverage AI to work smarter, accelerate decision-making, automate repeatable work, and improve outcomes. You are encouraged to continuously identify opportunities to apply AI, data, and scalable processes to enhance productivity, drive innovation, and deliver greater value for our clients, partners, and teams while maintaining appropriate judgment, quality, security, and compliance." We need to preserve all that. We'll put in

      . Now Responsibilities: there is a heading "Responsibilities" then subheadings: Procurement Operations, Sourcing and Negotiation, AI-Enabled Delivery, Stakeholder Enablement. Each with bullet-like sentences. We'll extract each bullet as

    • . We need to preserve all detail. Let's list them: Under Procurement Operations: - Own the procurement lifecycle end to end, from intake triage and sourcing through purchase orders, vendor onboarding, and invoice matching, keeping requests moving so business teams are never blocked waiting on procurement. - Improve how procurement runs in Zip and adjacent systems by removing steps that create delay, building in the controls that keep data clean as volume grows, and reporting on pipeline, cycle time, and realized savings. Under Sourcing and Negotiation: - Run sourcing events from scoping through award, including vendor evaluations, RFx execution, and renewals, and own the recommendation you bring forward. - Build the business case behind award and renewal decisions using total cost of ownership, license and tier rightsizing, vendor consolidation, and market benchmarking, and quantify the savings you deliver. - Lead commercial negotiations on assigned agreements and partner with Legal, Security, and Privacy to land terms that protect Rithum without slowing the business down. Under AI-Enabled Delivery: - Use AI as the starting point for recurring procurement work, including contract summarization, first-pass redlines, spend and proposal analysis, market research, and stakeholder communications, and verify every output against the source before it informs a decision or leaves your hands. - Share the AI approaches that work with your teammates, so the whole function gets faster, not just you. Under Stakeholder Enablement: - Enable the rest of the business through training, playbooks, and clear guidance on when and how to engage procurement. - Tailor how you present procurement requirements, cost analysis, and trade-offs to different audiences, from engineers and vendors to finance leaders. We'll put each as
    • . Now Qualifications: Minimum Qualifications and Preferred Qualifications. Minimum Qualifications list (each bullet): - 2 or more years of experience in procurement, sourcing, or contract operations, ideally supporting SaaS and software spend - Hands-on experience with an intake-to-procure or procurement workflow platform such as Zip, Coupa, Ariba, or similar - Experience reviewing and redlining commercial agreements and working alongside Legal to close open terms - Experience running sourcing events or renewals through to an award or signature decision - Experience presenting sourcing recommendations, cost analysis, and commercial trade-offs to finance, technical, and vendor audiences - Experience managing a concurrent pipeline of procurement requests at varying stages, with documented tracking in a procurement or workflow system - Experience using AI tools (e.g., ChatGPT, Microsoft Copilot, Claude) to improve productivity through research, communication, analysis, documentation, automation, workflow optimization, and decision-making. - Demonstrated practice of verifying AI output against the source document or system of record before it informs a decision or is shared Preferred Qualifications: - 3 or more years of procurement experience, including running sourcing events end to end - Bachelor's degree in business, supply chain, finance, or a related field preferred - CPSM, CIPS, or a similar certification - Experience with SaaS licensing models, usage-based pricing, and using renewal timing as leverage - Familiarity with vendor risk, security, and privacy review processes - Experience building or automating procurement workflows, including with AI - Proficiency with Notion, SharePoint, and Microsoft 365 - Prior experience in a remote-first, fast-moving technology company We'll put these as
    • under Qualifications. Possibly separate Minimum and Preferred with headings? But we only allowed headings list; we could add

      but not allowed. Better to just list all qualifications; maybe we can separate with

      indicating Minimum and Preferred. But we must not invent headings not allowed. We can include a

      before the list: "

      Minimum Qualifications:

      " then

      . Then another

      for Preferred Qualifications. That's acceptable as prose. Now Benefits: list from text: "Benefits Medical, dental and vision benefits: Affordable health care plans and company HSA contributions, starting on Day 1A 6% 401(k) matchCompetitive time off package with 20 days of Paid Time Off, 9 Company-Paid holidays, 2 paid floating holidays, 7 paid sick days, 2 Wellness days, and 1 Paid Volunteer Day; at 3 years of service PTO increases to 22 days, and at 5 years it increases to 25 days12 weeks primary caregiver leave & 4 weeks secondary caregiver leaveAccident, critical illness, and hospital indemnity insurancePet insuranceLegal assistance and identity theft insurance plansLife insurance 2x salaryAccess to the Calm app and the Employee Assistance Program$65/month Remote work stipend for internetCulture and team-building activitiesTuition assistanceCareer development opportunitiesCharitable contribution match up to $250 per year" We need to split into sensible items. The text is jammed; we need to parse. Let's extract each benefit: - Medical, dental and vision benefits: Affordable health care plans and company HSA contributions, starting on Day 1 - 6% 401(k) match - Competitive time off package with 20 days of Paid Time Off, 9 Company-Paid holidays, 2 paid floating holidays, 7 paid sick days, 2 Wellness days, and 1 Paid Volunteer Day; at 3 years of service PTO increases to 22 days, and at 5 years it increases to 25 days - 12 weeks primary caregiver leave & 4 weeks secondary caregiver leave - Accident, critical illness, and hospital indemnity insurance - Pet insurance - Legal assistance and identity theft insurance plans - Life insurance 2x salary - Access to the Calm app and the Employee Assistance Program - $65/month Remote work stipend for internet - Culture and team-building activities - Tuition assistance - Career development opportunities - Charitable contribution match up to $250 per year We'll put each as

      • . Now Pay: text: "We believe in transparency and fairness in our compensation practices. For this position, the expected base pay range is: $60,000-$85,000 per year. This range represents the base pay for the role across all U.S. locations and is determined based on market data, internal equity,