Senior Compliance Manager

We need to output HTML fragment with sections: About the role? Actually the description includes "ABOUT US", "Overview", "Position Objectives", "Requirements", "Work Condition/Physical Demands", "Travel Requirements", "BENEFITS/COMPENSATION", "SALARY RANGE". Also "Education And Preferred Training Requirements" is part of Requirements? Actually after Requirements heading there is "POSITION REQUIREMENTS:" then list, then "Education And Preferred Training Requirements". We need to follow rules: use

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

• for any list of duties/requirements/benefits, and

  for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include. The posting includes: About Us (company description), Overview (mission, role description), Position Objectives (duties), Requirements (POSITION REQUIREMENTS, Education And Preferred Training Requirements), Work Condition/Physical Demands, Travel Requirements, Benefits/Compensation, Salary Range. We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use "About the role" for overview/mission description? Actually "About the role" could be the overview of role. "Responsibilities" for Position Objectives. "Requirements" for POSITION REQUIREMENTS and Education And Preferred Training Requirements. "Qualifications" maybe for certifications? But we can combine. "Skills" maybe for abilities listed. "Benefits" for benefits. "Pay" for salary range. "Schedule" maybe not present (no schedule details). Travel requirements could be part of Schedule? But schedule heading only if posting actually states schedule; travel is not schedule. Could omit schedule. We must not create sections with filler. So we include sections where we have content. We need to output only HTML fragment, no /. Use

  headings,

  for prose,

  • for lists. We need to preserve all substantive information. Let's extract content. First, "ABOUT US" paragraph: "Cerapedics is a global, commercial-stage orthopedics company that is dedicated to redefining the path to bone repair by healing bones faster and at higher rates, so all patients can get back to living their fullest lives. Bone grafts, including Cerapedics’ products, are used in over four million annual spine, orthopedics, trauma, and interventional procedures worldwide. Cerapedics has two drug-device products approved by the FDA powered by Cerapedics’ proprietary P-15 Osteogenic Cell Binding Peptide: PearlMatrix™ Bone Graft for all major lumbar interbody surgical approaches and i-FACTOR® Bone Graft for single-level anterior cervical discectomy and fusion (ACDF) in the cervical spine. Cerapedics is headquartered in Westminster, Colorado." We could put that under "About the role"? Actually "About the role" is about the role, not company. But we could treat "About the role" as overview of role and company? The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid using About the role for company overview? Probably better to put company description under "About the role" as it's about the role context. Or we could omit About the role and instead put company description in a

    before any heading? But we need to use headings for sections; we can have a leading

    before first heading? The instruction: "use

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

    • for any list of duties/requirements/benefits, and

      for prose." It doesn't forbid having prose outside headings. But we likely should structure with headings. We could have:

      About the role

      Cerapedics is a global, commercial-stage orthopedics company ... Westminster, Colorado.

      Overview: Healing lives through bone repair – this mission is what inspires us every day. If that is inspiring to you as well, consider joining us as a Senior Compliance Manager in our Westminster office. This is an onsite position. In this role, you will contribute to our mission through collaborating with internal clients at all levels of management. As a Senior Compliance Manager working on the Legal team, you will be empowered through meaningful work and career development to manage all aspects of the Compliance function's reporting requirements relating to the Federal Physician Payments Sunshine Act, and international, state and municipal transparency laws. A typical day will include- providing counseling on healthcare compliance issues; working closely with the Compliance Officer on strategic compliance matters; providing support on the general compliance needs of the company; and collaborating with key stakeholders to develop, review and/or deliver compliant training materials for internal and external audiences.

      That seems good. Then Responsibilities: Position Objectives bullet list? Actually Position Objectives is a paragraph with multiple sentences each starting with a verb. Could treat as list. We'll convert to
      • . Extract Position Objectives sentences: - Oversee and collaborate across internal teams and external partners to manage State and Federal Transparency reporting obligations, including review, remediation, and accurate aggregate spend reporting—under the Federal Sunshine Act and applicable international, state and municipal laws, ensuring data integrity across multiple systems and vendors. - Work closely with the Compliance Officer and General Counsel to develop and maintain an aggregate spend assumptions and interpretations document and remain current with aggregate spend related laws and regulations, for timely implementation of updates to this document. - Work with the Compliance Officer to monitor, audit, and investigate to ensure that any allegation or identified violation of company policy related to aggregate spend is properly investigated, remediation taken, and monitor controls established to prevent future instances. - Develop and implement effective training and communication initiatives related to aggregate spend and state reporting for senior management, employees, customers and third-party vendors. - Coordinate, conduct, and report corrective action planning on compliance trainings, education, auditing, and monitoring, including periodic field rides, trade show attendance, and company sponsored HCP educational events. - Conduct and support the management of compliance investigations and enforcement in collaboration with the Legal Department. - Support Compliance review, approval, and processing of Healthcare Professional engagements and contracting to ensure compliance with applicable laws. - Development and publish quarterly Compliance metrics. - Provide training on a wide range of issues related to compliance, including policies and guidelines applicable to labeling and promotional content, reimbursement, and interactions with healthcare providers. Note: "Development and publish quarterly Compliance metrics." maybe should be "Develop and publish". We'll keep as is. We'll put under

        Responsibilities

        with
        • each. Then Requirements: We have POSITION REQUIREMENTS list and Education And Preferred Training Requirements list. POSITION REQUIREMENTS: - Bachelors Degree required - Minimum 8 years of healthcare industry compliance experience required, preferably in a global pharmaceutical or medical device company - Sunshine Act and transparency reporting experience required - U.S. Healthcare Compliance Certification a plus Education And Preferred Training Requirements: - Strong knowledge of OIG seven elements, False Claims Act, Anti-kickback Statute, and anti-bribery considerations - Experience working with Commercial and Medical Affairs functions - Experience managing compliance and ethics investigations - Strong understanding of compliance processes and activities common to the medical device industry - Strong understanding of healthcare compliance and enforcement environment - Ability to develop strong trusting and productive relationships within and across the business areas to seek alignment on objectives and achieve results - Ability to work independently and prioritize in a rapid growth environment, with a sense of urgency - Excellent written and oral communication skills - High level of integrity with good ethical core values - Excellent time management and organizational skills - Strong attention to detail, organizational, analytical and people skills - Strong problem-solving skills to effectively envision, develop, and implement new strategies to address business issues and management requests We could combine both under Requirements heading, or separate into Requirements and Qualifications. Since we have both, we could use Requirements for the POSITION REQUIREMENTS and Qualifications for the Education And Preferred Training Requirements. Or we could put all under Requirements and note that Qualifications is not needed. The instruction says prefer a few substantive sections over many thin ones. So maybe combine all into Requirements. But we also have Skills section maybe for abilities like communication, problem solving etc. However those are already in the Education And Preferred Training Requirements. Could treat them as Skills. We could do:

          Requirements

          POSITION REQUIREMENTS:

          • ...

          Education And Preferred Training Requirements:

          • ...
          But that duplicates headings? Might be okay. Alternatively, we could have

          Requirements

          for the POSITION REQUIREMENTS, and

          Qualifications

          for the Education And Preferred Training Requirements. That yields two sections, both substantive. We also have Skills maybe not needed. We also have Benefits and Pay. Benefits: "BENEFITS/COMPENSATION (including, But Not Limited To) Medical and dental insurance, group life insurance, 401k matching, long term disability, potential target bonus, paid time off." We can list as
          • . Pay: "SALARY RANGE: $146,000.00 - $211,000.00 Base Salary: Annually Target Annual Bonus: Up to 20%". Also later "Compensation details: 146000-211000 Yearly Salary". We'll include Pay section. Schedule: Not present; we should not create Schedule section. Work Condition/Physical Demands and Travel Requirements: Could be placed under a section like "Working Conditions" but not in allowed headings. Since we only allowed those specific headings, we might need to omit or fold into other sections? The instruction: "use

            for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, not exclusive? It says "use

            for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings only. So we should not create other headings like Work Condition/Physical Demands. We could fold that content into a

            under Requirements or maybe under a generic

            without heading? But they said "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid having prose without heading. But better to keep headings only from list. We could put Work Condition/Physical Demands and Travel Requirements under a

            after Requirements maybe as part of "Requirements" or "Qualifications"? Not ideal. Alternatively, we could treat them as part of "Skills"? Not really. Maybe we can create a section "Working Conditions" but