Senior Sirion CLM Administrator

The user wants me to reformat a job posting into clean, well-structured semantic HTML. I need to follow specific rules: 1. Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) 2. Use

• for lists of duties/requirements/benefits 3. Use

  for prose 4. Do NOT repeat the job title as a heading 5. Do NOT put Job ID/requisition numbers as headings 6. Preserve ALL substantive information 7. Remove boilerplate (cookie/navigation/legal/EEO/scam-warning, duplicated lines, application instructions) 8. Include a section ONLY when the posting has real, specific content for it 9. Never emit a heading followed by filler/placeholder text 10. Never create Pay/Schedule/Benefits sections unless the posting actually states them 11. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting content: The posting has: - "About Us" / "Who We Are" / "What We Do" - company background - "Job Description Summary" - role summary - "Responsibilities" / "Job Description" - detailed responsibilities - "Qualifications" - required qualifications - "Preferred Qualifications" - preferred qualifications - "Working Conditions" - hybrid work environment - "Compensation" - salary range and bonus info - "What We Offer" - benefits package - "Inclusion & Diversity" - diversity info - "Giving Back" - foundation info - "Transamerica's Parent Company Aegon" - parent company info I need to structure this into appropriate sections. The rules say to use specific heading names: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Let me map: - "Job Description Summary" → "About the role" - "Responsibilities" / "Job Description" → "Responsibilities" - "Qualifications" → "Requirements" (or "Qualifications"? The rules mention both "Requirements" and "Qualifications" as possible headings. I'll use "Qualifications" for the required ones and maybe "Preferred Qualifications" as a subsection or separate heading? The rules say use

  for section headings like "Qualifications". I think I should have "Qualifications" for required and maybe "Preferred Qualifications" as a separate h3 or include under Qualifications. But the rules list "Qualifications" as a heading option. I'll use "Qualifications" for required and "Preferred Qualifications" as another h3.) - "Working Conditions" → "Schedule" (since it mentions hybrid work environment) - "Compensation" → "Pay" - "What We Offer" → "Benefits" - The rest (Inclusion & Diversity, Giving Back, Parent Company) are company boilerplate that should be removed per rules: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". The Inclusion & Diversity and Giving Back and Parent Company are company marketing, not specific to the job. The rules say "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Also "Preserve ALL substantive information". The benefits are substantive. The company background (About Us, Who We Are, What We Do) is also boilerplate? The rules say "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." The company background is not job-specific. I think we should drop the company background sections (About Us, Who We Are, What We Do) as they are generic company info, not specific to this role. The job description summary is specific to the role. The responsibilities, qualifications, working conditions, compensation, benefits are job-specific. The inclusion & diversity, giving back, parent company are company-wide boilerplate. Also there's a disclaimer about scam warnings - that's boilerplate to remove. Now, the "What We Offer" section includes "Compensation Benefits" and "Health and Work/Life Balance Benefits" with lists. That's the benefits section. The "Compensation" section has salary range and bonus info - that's Pay. "Working Conditions" says "Hybrid work environment" - that's Schedule. Now, I need to output HTML fragment with h3 headings and ul/li for lists, p for prose. Let me structure:

  About the role

  Serve as the primary functional owner of our Contract Lifecycle Management (CLM) platform and related procurement technologies. Serves as a critical bridge between business stakeholders, sourcing teams, legal, risk, TPRM, technology, suppliers, and platform providers. Drive operational excellence, lead contract intake and governance processes, manage vendor relationships, support technology enhancements, and ensure the stability and optimization of procurement systems. Act as the primary point of contact for CLM strategy, platform administration, business requirements, escalations, quarterly business reviews (QBRs), and continuous improvement initiatives.

  Responsibilities

  • Serve as the primary administrator and business owner of the Contract Lifecycle Management (CLM) platform.
  • Escalation point for platform issues and operational disruptions.
  • Manage platform configuration, workflows, templates, clause libraries, user access, and governance controls.
  • Lead system enhancements, upgrades, releases, testing, deployment, and ongoing platform optimization.
  • Partner with Procurement, Legal, Compliance, Risk, TPRM, IT, and business stakeholders to improve contracting processes and user experience.
  • Act as the primary point of contact for contract intake, routing, approvals, escalations, and stakeholder support.
  • Ensure contracts follow established governance requirements based on risk, supplier type, spend thresholds, and business needs.
  • Manage system integrations and data flow between CLM, procurement, and related technology platforms.
  • Gather business and technical requirements and lead testing efforts for integrations, enhancements, releases and defect remediation.
  • Develop reporting and dashboards; analyze contract cycle times, intake volumes, bottlenecks, supplier activity, and operational performance.
  • Lead issue resolution, incident management, root cause analysis, and continuous improvement initiatives while recommending new platform capabilities and enhancements.

  Qualifications

  • Bachelor's degree in Business, Procurement, Supply Chain, Information Systems, Finance, or related field or equivalent combination of education, training, certifications, and relevant work experience
  • 5+ years of experience in Procurement, Sourcing, Procurement Operations, Contract Management, or Supply Chain
  • Strong knowledge of contract lifecycle processes and procurement operations
  • Hands-on CLM administration experience
  • Experience supporting contingent workforce, statement of work (SOW), and supplier engagement processes
  • Experience gathering business requirements and translating them into system solutions
  • Strong experience managing system integrations and cross-functional technology initiatives
  • Demonstrated experience leading vendor management and governance activities
  • Experience supporting system incidents, escalations, and production issue resolution
  • Advanced stakeholder management and communication skills

  Preferred Qualifications

  • Sirion Labs CLM expertise
  • Power BI and reporting expertise
  • Knowledge of supplier management, third-party risk, and contract compliance programs
  • Experience supporting procurement transformation initiatives
  • PMP, CPSM, CPSP, Certified Procurement Professional, or similar certification
  • Experience with CRM tools: Icertis Contract Intelligence, Inconclad, Agiloft, Conga

  Schedule

  Hybrid work environment

  Pay

  The salary for this position generally ranges between $94,000.00 - $124,000.00 annually. Please note that the salary range is a good faith estimate for this position and actual starting pay is determined by several factors including qualifications, experience, geography, work location designation (in-office, hybrid, remote) and operational needs. Salary may vary above and below the stated amounts, as permitted by applicable law. Additionally, this position is typically eligible for an Annual Bonus based on the Company Bonus Plan/Individual Performance and is at the Company's discretion.

  Benefits

  For eligible employees, we offer a comprehensive benefits package designed to support both the personal and financial well-being of our employees.

  Compensation Benefits

  • Competitive Pay
  • Bonus for Eligible Employees
  • Benefits Package
  • Pension Plan
  • 401k Match
  • Employee Stock Purchase Plan
  • Tuition Reimbursement
  • Disability Insurance
  • Medical Insurance
  • Dental Insurance
  • Vision Insurance
  • Employee Discounts
  • Career Training & Development Opportunities

  Health and Work/Life Balance Benefits

  • Paid Time Off starting at 160 hours annually for employees in their first year of service.
  • Ten (10) paid holidays per year (typically mirroring the New York Stock Exchange (NYSE) holidays).
  • Be Well Company holistic wellness program, which includes Wellness Coaching and Reward Dollars
  • Parental Leave – fifteen (15) days of paid parental leave per calendar year to eligible employees with at least one year of service at the time of birth, placement of an adopted child, or placement of a foster care child.
  • Adoption Assistance
  • Employee Assistance Program
  • Back-Up Care Program
  • PTO for Volunteer Hours
  • Employee Matching Gifts Program
  • Employee Resource Groups
  • Inclusion and Diversity Programs
  • Employee Recognition Program
  • Referral Bonus Programs
  Note: The rules say use

  for section headings. Should I use h4 for subsections? The rules don't forbid h4, but they say "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say not to use h4 for subsections. However, to keep it simple, maybe I should keep all as h3? But "Compensation Benefits" and "Health and Work/Life Balance Benefits" are subsections of Benefits. I could make them h3 as well, but that would create many h3 headings. The rules say "Prefer a few substantive sections over many thin ones." But these are substantive lists. I think using h4 is fine, but the output should be HTML fragment. The rules don't explicitly forbid h4. However, the example headings are all h3. I'll use h3 for main sections and maybe h4 for subsections, but to be safe, I'll make them h3 as well? But then we'd have many h3 headings. The rules say "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you cannot have other h3 headings. But "Compensation Benefits" and "Health and Work/Life Balance Benefits" are not in the example list