Chief Compliance Officer (CCO)
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings based on content. We have "Department Summary" and "Position Overview". Could map to "About the role". Also "Minimum Qualifications" -> Requirements/Qualifications. "Knowledge, Skills And Abilities" -> Skills. "Preferred Qualifications" maybe also Qualifications. "Job Duties" -> Responsibilities. "Physical Requirements" maybe not needed? It's not a standard heading; but we could include under Requirements? However instruction: only include sections when posting has real specific content. Physical Requirements is present but not one of the listed headings; we could either omit or maybe include as a
under something else? The instruction says use those headings for section headings; but we can also have other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but likely they expect only those. We could incorporate Physical Requirements into Requirements or Skills? Probably better to include a section "Requirements" that includes minimum qualifications and physical requirements. But we must not invent content; we can include physical requirements as a
under Requirements. We have Salary: Commensurate with experience - that's vague; instruction: 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. Salary is stated as "Commencement with experience" which is placeholder; so we should NOT create a Pay section because it's just placeholder. Similarly Work Schedule Hours Vary - placeholder; do not create Schedule section. Benefits: "For information regarding our Benefits, click here." That's not specific; it's a link placeholder; we should not create Benefits section because no actual benefits listed. So we omit Benefits, Pay, Schedule. Thus we will have sections: About the role (maybe using Department Summary + Position Overview), Responsibilities (Job Duties), Requirements (Minimum Qualifications + Physical Requirements), Qualifications (maybe combine Minimum and Preferred? But we already used Requirements for qualifications; maybe we split: Requirements = Minimum Qualifications, Qualifications = Preferred Qualifications? But instruction says use headings like Requirements, Qualifications. We can have both. Let's assign: - About the role: Department Summary + Position Overview. - Responsibilities: Job Duties. - Requirements: Minimum Qualifications. - Qualifications: Preferred Qualifications. - Skills: Knowledge, Skills And Abilities. We must not repeat job title as heading. Good. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from those sections. We must strip boilerplate: EEO, navigation, legal, etc. Also remove "Special Instructions" maybe? It's about references; that's substantive? It's part of application instructions; we should remove application instructions per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So "Special Instructions Applicants must submit a minimum of two professional references..." is application instruction; remove. Also "Retirement Eligibility: ORP Eligible" maybe metadata; could be folded into short
or drop. It's minor metadata; we can include in a short
maybe under About the role? But instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a short paragraph with Employee Classification, Campus, Division, SubDivision-Department, Department, Job Location, FTE, Retirement Eligibility. But we must not repeat job title. We can include that as a
after the heading? Probably better to include a short paragraph under About the role or at top. Since we have About the role section, we can include that metadata there as a
. We must not include "About Us - Values Overview" as heading; we can incorporate that paragraph into About the role. Let's extract substantive content: About Us - Values Overview: paragraph about UNT System. Department Summary: paragraph about System Administration Compliance & Ethics Program. Position Overview: paragraph about CCO responsibilities. Minimum Qualifications: bullet? It's a sentence: "Bachelor's degree in law, business, finance, accounting, or related field; ten years of experience in compliance, risk management, audit, or legal roles, preferably in a large and complex organization; and Professional certification in compliance, such as Certified Compliance and Ethics Professional (CCEP), Certified Regulatory Compliance Manager (CRCM), or Certified Risk and Compliance Management Professional (CRCMP) or ability to obtain within one year of hire; or any equivalent combination of education, experience or training." Knowledge, Skills And Abilities: list of items separated by periods. We'll need to put each as
- .
Preferred Qualifications: list of items each starting with "Experience developing..." etc. We'll put as
- . Job Duties: list of duties each starting with a verb; we will put as
- . Physical Requirements: "Communicating with others to exchange information." and "Environmental Hazards No adverse environmental conditions expected." We'll put as
- maybe under Requirements? But we already have Requirements for minimum qualifications; we could add a subsection? But we can just include as
under Requirements? Better to add as
- under Requirements? However Requirements heading is for qualifications; but we can still include physical requirements as a
after the list. Since it's not a list, we can just put as
. We must not include "Work Schedule Hours Vary" etc. We must not include "Benefits For information regarding our Benefits, click here." (remove). We must not include EEO statement. Now construct HTML. We'll start with maybe a
for metadata: Employee Classification: Chief Compliance Officer (CCO) Campus: University of North Texas - Dallas Division: DAL-Office of the President SubDivision-Department: DAL-Office of the President Department: DAL-Compliance Office-500500 Job Location: Dallas FTE: 1.000000 Retirement Eligibility: ORP Eligible But we should not repeat job title; but Employee Classification repeats title; maybe we can drop that line. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include metadata but not as heading. It's okay to include Employee Classification? It's basically same as title; but we can keep it as metadata. Might be okay. We'll create a
with the metadata lines separated by commas or semicolons. Then sections:
About the role
UNT System overview paragraph + Department Summary + Position Overview combined? We need to preserve all substantive information; we can combine them into one or multiple
. Probably better to have multiple
under the section. We'll put:
[UNT System overview]
[Department Summary]
[Position Overview]
ThenResponsibilities
- ... ...
Requirements
Minimum Qualifications: ...
Maybe also include Physical Requirements asafter. Then
Qualifications
- Preferred Qualifications items
Skills
- Knowledge, Skills And Abilities items