Temporary Contract Specialist

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 Summary (which is about the role). It includes Minimum Requirements (Education, Experience). Preferred Requirements (skills). Job Duties (responsibilities). Systems & Tools (maybe part of responsibilities). Reporting & Analytics (responsibilities). Other Responsibilities (maybe part of responsibilities). Physical Requirements (maybe not needed). Benefits: there is a "Full Time Benefits:" list and "Part Time Benefits:" list. So we have benefits content. Pay: not mentioned. Schedule: not mentioned (though mentions in-office, not remote, maybe schedule not given). So we should not include Pay or Schedule sections. We need headings:

About the role

,

Responsibilities

,

Requirements

,

Qualifications

,

Skills

,

Benefits

. Possibly combine Requirements and Qualifications? The instructions: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have separate Requirements and Qualifications sections. Requirements likely includes minimum requirements (education, experience, work authorization, background check). Qualifications could be preferred requirements? Or maybe Qualifications includes education details? We'll interpret: Requirements = minimum requirements (education, experience, work auth, background check). Qualifications = preferred requirements (exceptional organizational skills etc). Skills = maybe specific skills like CLM systems, Excel, SAP, etc. But we can also put skills under Qualifications. However we need to avoid thin sections. Let's see content: Summary: about the role. Minimum Requirements: Combination of Education and Experience will be considered. Must be authorized to work in the US as defined by the Immigration Act of 1986. Must pass a Criminal Background Check. Education: Bachelor’s Degree Education Details: Bachelor’s degree in Business Administration, Supply Chain, Finance, Legal Studies, or a related field OR equivalent combination of education and relevant work experience. Years of Experience: Three (3) years of experience in procurement, contracting, sourcing, administrative operations, or a related business support role involving structured workflows and approvals. This is an in-office position based in Las Vegas, NV, and not eligible for remote work Preferred Requirements: list of skills/attributes. Job Duties: many bullet-like paragraphs. Systems & Tools: details. Reporting & Analytics: details. Other Responsibilities: generic. Physical Requirements: maybe not needed. Benefits: Full Time Benefits list and Part Time Benefits list. Thus we can create sections: About the role: use the Summary paragraph(s). Could combine the summary paragraphs into a

. Responsibilities: combine Job Duties, Systems & Tools, Reporting & Analytics, Other Responsibilities (maybe). Could be a

• list. Requirements: Minimum Requirements (education, experience, work auth, background check, location). Could be a
  . Qualifications: Preferred Requirements (list of skills/attributes). Could be a
  . Skills: maybe specific technical skills: CLM systems, Microsoft Office, SAP, SAP Ariba, Adobe Sign, Power BI, Tableau, Jira, etc. Could be a
  . Benefits: list of benefits (full-time and part-time). Could combine into
  . We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate: EEO, legal, scam warning, AI tools, etc. Also remove Physical Requirements? It's not boilerplate but maybe not needed; but we could include if we want but it's not one of the headings list; we could omit as not requested. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". Physical Requirements is specific content but not one of the standard headings; we could either omit or include under a different heading like "Other". Since not in list, better to omit. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from the sections we include. That means we need to include all the details from Minimum Requirements, Preferred Requirements, Job Duties, Systems & Tools, Reporting & Analytics, Other Responsibilities, Benefits. If we omit Physical Requirements, we lose that substantive info. But maybe we can include it under a heading like "Other" but not in list; but 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)." The e.g. suggests those are examples; we could still use other headings but they'd be non-standard. Safer to stick to those headings and incorporate Physical Requirements into maybe Responsibilities or Other? But it's not really responsibility. Could add a

  Physical Requirements

  but not in list; risk. I'd rather include it as a

  Physical Requirements

  because it's substantive and the instruction didn't forbid other headings, just gave examples. However the instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections; but not strictly prohibited to add others. However to be safe, we could incorporate Physical Requirements into a

  Other

  but not in list. Might be considered filler? Better to include as its own heading; it's substantive. But the instruction also says: "Prefer a few substantive sections over many thin ones." Physical Requirements is a thin section but still substantive. Could merge into Responsibilities? Not appropriate. Could add a

  Physical Requirements

  and keep. We'll decide to include Physical Requirements as its own heading. Now Benefits: we have both full-time and part-time lists. We'll combine into a single
  with items. We must not include boilerplate like EEO, legal, scam warning, AI tools, etc. Also remove "Full Time Benefits:" and "Part Time Benefits:" headings inside the content; we just list items. We need to preserve all substantive info: For benefits list: Full Time Benefits: Profit Sharing, Medical/Dental/Vision/Life/Disability Insurance, Medical Travel Reimbursement, Legal, Identity and Pet Insurance, 401K with an employer match, Employee Stock Purchase Plan, Employee Assistance Program, Tuition Reimbursement, Flight Benefits, Paid vacation, holidays, and sick time. Part Time Benefits: Profit Sharing, Medical Travel Reimbursement, Legal, Identity and Pet Insurance, 401K with an employer match, Employee Stock Purchase Plan, Employee Assistance Program, Tuition Reimbursement, Flight Benefits, Sick time. We'll combine duplicates? Should we keep both? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. If we combine and remove duplicates, we might be summarizing away detail (i.e., omitting that part-time lacks certain benefits). Better to keep both lists separate maybe under subheadings? But we only have Benefits section. Could do two
  with headings inside? Could use

  to indicate Full-Time Benefits and Part-Time Benefits then lists. That preserves detail. Thus Benefits section:

  Benefits

  then

  Full‑Time Benefits:

  ...

  Part‑Time Benefits:

  ...
  Now Responsibilities: we need to capture all duties from Job Duties, Systems & Tools, Reporting & Analytics, Other Responsibilities. We'll create a
  with each duty as
  • . Must preserve detail; we can break into multiple items. Let's extract: Job Duties (bullet-like paragraphs): - Support Procurement Managers in the execution of sourcing events, including Request for Information (RFI), Request for Proposal (RFP), and competitive bid processes - Coordinate sourcing timelines, intake requests, and milestone tracking to ensure projects progress efficiently and meet internal deadlines - Assist in spend analysis, supplier comparisons, and preparation of sourcing decision documentation - Facilitate end-to-end procurement approval workflows, ensuring required reviews and approvals (Procurement, Legal, Finance, Leadership) are obtained in the proper sequence - Track approvals, follow up with stakeholders, and ensure no sourcing or contracting activity proceeds without appropriate authorization - Maintain standardized process documentation and approval templates to promote consistency and audit readiness - Coordinate contract routing for review, signature, and execution in partnership with Legal, Finance, Leadership, and Procurement - Ensure all contracts, amendments, and supporting sourcing documentation are accurately entered and maintained in the designated contract management system - Maintain organized records of executed agreements, approvals, and sourcing artifacts in accordance with retention and compliance requirements - Ensure sourcing and procurement activities comply with corporate procurement policies, ethics standards, and regulatory requirements - Support documentation related to supplier due diligence, conflicts of interest, and required compliance attestations - Serve as a point of coordination between Procurement Managers and internal stakeholders - Coordinate communications with suppliers related to sourcing approvals, documentation requests, and administrative requirements - Support resolution of administrative or process-related supplier issues Systems & Tools: - Utilizes Microsoft Office applications (Excel, Word, PowerPoint, Outlook, Teams/SharePoint) to develop and maintain trackers, reports, dashboards, and standardized templates; ensures effective communication management and document control - Supports the SAP (ERP) purchase requisition and purchase order lifecycle, including vendor master coordination (as applicable); monitors goods receipt and invoice status visibility; and prepares basic reports in alignment with company controls - Creates and manages sourcing events (RFI/RFP) in SAP Ariba (Sourcing, Buying & Invoicing, Contracts, as applicable), supports supplier collaboration, routes approval workflows and contract workspaces, and coordinates supplier onboarding and required document collection - Routes agreements for review and signature using contract lifecycle management and electronic signature tools (e.g., Ariba, Adobe Sign); maintains executed agreements and tracks contract renewal and expiration dates - Supports KPI tracking using reporting and analytics tools (e.g., Power BI, Tableau), including monitoring cycle times, workload, and compliance metrics; prepares leadership ready summaries and reports - Manages work intake using ticketing systems (e.g., Jira), including logging and prioritizing requests and documenting status updates and approval decisions Reporting & Analytics: - Develop and maintain procurement reports and dashboards related to sourcing activity, approval cycle times, contract status, and compliance metrics - Track key process performance indicators (e.g., sourcing cycle time, approval turnaround, contract execution timelines) - Prepare summary materials and reports for Procurement leadership reviews and planning meetings Other Responsibilities: - Provide general administrative and analytical support to the Procurement organization as needed - Perform other duties as assigned to support Procurement Strategies and organizational objectives We'll combine all into a
    . Now Requirements (minimum): - Combination of Education and Experience will be considered. - Must be authorized to work in the US as defined by the Immigration Act of 1986. - Must pass a Criminal Background Check. - Education: Bachelor’s Degree - Education Details: Bachelor’s degree in Business Administration, Supply Chain, Finance, Legal Studies, or a related field OR equivalent combination of education and relevant work experience. - Years of Experience: Three (3) years of experience in procurement, contracting, sourcing, administrative operations, or a related business support role involving structured workflows and approvals. - This is an in-office position based in Las Vegas, NV, and not eligible for remote work We'll put each as