Non-Student Hourly Music Director

We need to output HTML fragment with headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove Benefits link generic? The posting says "Benefits For information regarding our Benefits, click here." That's not specific benefit details, just a link. According to rule: never create Benefits section unless posting actually states them. It states "Benefits For information regarding our Benefits, click here." That's not specific benefit details; it's just a pointer. Likely we should not include Benefits section because no specific benefits listed. Similarly Pay: posting says Salary: $25.00. That's specific pay. So we can include Pay section with that. Schedule: posting says "Work Schedule Flexible preparation work with Saturday classes". That's specific schedule info. So include Schedule section. Requirements: Minimum Qualifications: Degree in Music Education with an emphasis on early childhood music education. Also Required License/Registration/Certifications: Degree in Music Education (duplicate). So we can include Requirements (or Qualifications). The spec says we can use headings like Requirements, Qualifications, Skills. We need to decide which sections to include based on content. We have About Us - Values Overview (but that's generic about UNT System). Might be considered "About the role"? Actually "About Us - Values Overview" is generic about the system, not role-specific. Could we include an "About the role" section? The posting includes "Department Summary" and "Position Overview". That's role-specific. So we could have an "About the role" section containing Department Summary and Position Overview. Also we have "Job Duties" which can be Responsibilities. Also "Knowledge, Skills And Abilities" and "Preferred Qualifications" can be Skills or Qualifications. Also "Physical Requirements", "Environmental Hazards", "Work Schedule", "Driving University Vehicle", "Security Sensitive", "Special Instructions". Some of those may be considered Requirements or other. But we need to avoid filler. We need to preserve all substantive information. So we need to extract all substantive info and place into appropriate sections. We must not include boilerplate like EEO statement, etc. Also remove "Special Instructions Applicants must submit a minimum of two professional references..." That's application instruction, should be removed. Also "Benefits For information regarding our Benefits, click here." is not specific, we should not include Benefits section. Also "Retirement Eligibility: Not Retirement Eligible" maybe could be included under Pay? Not exactly. Could be a detail but not under headings we have. Could we include a "Details" section? Not allowed headings besides those listed. So we might need to fold minor metadata into a short

or drop it. The 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 at top for things like Employee Classification, Campus, Division, Sub Division-Department, Department, Job Location, Salary, FTE, Retirement Eligibility, etc. But we already have Salary in Pay section, Work Schedule in Schedule section. The rest like Employee Classification, Campus, Division, Sub Division-Department, Department, Job Location, FTE, Retirement Eligibility could be folded into a short

. However we must preserve ALL substantive information. So we need to include those details somewhere. We can put them in a

after the heading maybe before sections. The instruction says we can fold minor metadata into a short

or drop it. So we can create a paragraph with those details. We must not repeat job title as heading. So no

for title. We need to output only HTML fragment, no /, no markdown. Thus structure:

Employee Classification: Non-Student Help - Hourly; Campus: University of North Texas; Division: UNT-Provost; Sub Division-Department: UNT-College of Music; Department: UNT-Music Education-134350; Job Location: Denton; FTE: 0.48; Retirement Eligibility: Not Retirement Eligible.

Then sections:

About the role

Department Summary: The Division on Music Education strives to prepare students for a career in music education. Position Overview: Leading the Early Childhood Music Program and supervising student hourly workers.

Responsibilities

• Prepare lessons
• Lead class
• Supervise student workers

Requirements

Minimum Qualifications: Degree in Music Education with an emphasis on early childhood music education.

Required License/Registration/Certifications: Degree in Music Education.

Skills

• Child development
• Early childhood music
• Ability to prepare lessons
• Lead groups of children
• Supervise students

Maybe also include Preferred Qualifications as part of Skills or Requirements? Could add a separate section "Preferred Qualifications". But we have limited headings; we could add another

Preferred Qualifications

if there is specific content. The posting says "Preferred Qualifications: Music Education with a specialization in Early Childhood Music". That's specific. So we should include that. Could be under Requirements or a separate section. Since we have headings for Requirements, Qualifications, Skills, we could use "Qualifications" for both minimum and preferred? But we already used Requirements for minimum qualifications. Could use "Qualifications" for preferred. However we need to avoid duplicate content. Let's think: We have Minimum Qualifications and Required License/Certifications (both degree). Preferred Qualifications: Music Education with a specialization in Early Childhood Music. That's similar to minimum but more specific. Could combine. But we need to preserve all info. So we could have a section "Qualifications" containing both minimum and preferred. But we already used Requirements for minimum. Maybe better to rename: Use "Requirements" for minimum qualifications and required certifications; use "Preferred Qualifications" for preferred. That's allowed as heading? The list of allowed headings includes "Qualifications". Not "Preferred Qualifications". But we could use "Qualifications" to cover both. However we need to not invent headings not in list? 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 exhaustive? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should stick to those headings. So we can use "Qualifications" to include both minimum and preferred. Or we could use "Requirements" for minimum and "Qualifications" for preferred. That seems reasonable. Thus:

Requirements

Minimum Qualifications: Degree in Music Education with an emphasis on early childhood music education.

Required License/Registration/Certifications: Degree in Music Education.

Qualifications

Preferred Qualifications: Music Education with a specialization in Early Childhood Music.

Skills

...

Then Pay:

Pay

Salary: $25.00 per hour.

Schedule:

Schedule

Work Schedule: Flexible preparation work with Saturday classes.

We might also include Physical Requirements and Environmental Hazards, Driving University Vehicle, Security Sensitive. Those could be placed under a section like "Working Conditions" but not in allowed headings. Could we include them under "Requirements"? Might be considered job requirements. Could add a subsection within Requirements? But we must use

• for any list of duties/requirements/benefits. So we could add a list under Requirements for physical requirements etc. However we already used Requirements for qualifications. Might be better to have a separate section "Working Conditions" but not allowed. Could we add them under "Responsibilities"? Not appropriate. Perhaps we can add a section "Details" but not allowed. The instruction says we can fold minor metadata into a short

  or drop it. Physical Requirements etc might be considered minor metadata? They are substantive but maybe we can include them in a short paragraph under a heading like "Requirements" as additional list items. Let's see: The posting includes Physical Requirements: Communicating with others to exchange information; Lifting and moving objects up to 20 pounds; Moving self in various positions to perform tasks in tight and confined spaces; Moving about to accomplish tasks or moving from one worksite to another; Repetitive motions that may include the wrists, hands and/or fingers. Environmental Hazards: No adverse environmental conditions expected. Driving University Vehicle: No. Security Sensitive: This is a Security Sensitive Position. These are job-related details. Could be included under a section like "Requirements" or "Qualifications". Since we already have Requirements and Qualifications headings, we could add a subsection "Physical Requirements" as a list under Requirements. But we need to follow rule: Use

  • for any list of duties/requirements/benefits. So we can add a list under Requirements for physical requirements etc. However we already used Requirements for qualifications; we could combine both qualification and physical requirements in same section but separate lists. That's okay. Alternatively we could create a section "Working Conditions" but not in allowed headings; risk of being considered invalid. Better to stick to allowed headings. Thus we can have:

    Requirements

    Minimum Qualifications: Degree in Music Education with an emphasis on early childhood music education.

    Required License/Registration/Certifications: Degree in Music Education.

    • Communicating with others to exchange information.
    • Lifting and moving objects up to 20 pounds.
    • Moving self in various positions to perform tasks in tight and confined spaces.
    • Moving about to accomplish tasks or moving from one worksite to another.
    • Repetitive motions that may include the wrists, hands and/or fingers.

    Environmental Hazards: No adverse environmental conditions expected.

    Driving University Vehicle: No.

    Security Sensitive: This is a Security Sensitive Position.

    But we need to avoid filler like "No adverse environmental conditions expected." That's substantive. It's okay. Now we also have "Benefits For information regarding our Benefits, click here." We decided not to include Benefits section because not specific. So we skip. Now we need to ensure we didn't include any boilerplate like EEO statement, etc. We removed. Now we need to output only HTML fragment. Let's construct. Start with a paragraph for metadata. Then sections in logical order: About the role, Responsibilities, Requirements, Skills, Pay, Schedule. We might also include Qualifications section for preferred qualifications. Let's add after Requirements. Thus order:

    Employee Classification: Non-Student Help - Hourly; Campus: University of North Texas; Division: UNT-Provost; Sub Division-Department: UNT-College of Music; Department: UNT-Music Education-134350; Job Location: Denton; FTE: 0.48; Retirement Eligibility: Not Retirement Eligible.

    About the role

    Department Summary: The Division on Music Education strives to prepare students for a career in music education. Position Overview: Leading the