Dance Accompanist III (Hourly)

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate, navigation, etc. Keep all substantive info. Let's parse the posting. Job Title: Dance Accompanist III (Hourly) – not to be repeated as heading. Job Description Summary: Provides support to a departmental office or program. Job Description Description of Duties and Tasks: list of duties. Knowledge: list. Skills: list. Technology Skills: list. Physical Requirements: description. Safety: description. Pay Rate: $58.30/Hour Up to 19 hours per week. Number Of Openings: 1 Job Posting Close Date: October 2, 2026 Also there is info about closing times, domicile requirement, etc. Those are boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The domicile requirement maybe considered legal? It's a policy statement; maybe we should drop it as boilerplate? It's not EEO but it's a requirement. However the instruction says remove legal boilerplate. The domicile requirement is a policy (AR 4.0300.01). Likely considered legal boilerplate, remove. Also "If you are a current Austin Community College employee, please click this link to apply through your Workday account." That's application instruction, remove. Also the mission statement paragraphs about ACC: that's about the institution, maybe considered boilerplate? It's descriptive but not specific to the role. Might be considered boilerplate? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The mission statement is generic about the college, not specific to the job. Could be considered boilerplate but it's not navigation/legal/EEO. Might be considered fluff but still substantive? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It doesn't say to remove generic mission statements. However they said "Prefer a few substantive sections over many thin ones." The mission statement is not specific to the role; maybe we can drop it as it's not directly about the job. But we need to preserve ALL substantive information; if we drop it, we might be losing info about the college's mission that could be relevant. However typical job postings include such generic description; but the instruction didn't explicitly forbid it. I'd keep it maybe under "About the role" or "About the college". But we have to use headings only for sections with real specific content. Could create an "About the role" section that includes the summary and maybe the mission? The summary is "Provides support to a departmental office or program." That's substantive. Better to structure:

About the role

Provides support to a departmental office or program.

Responsibilities

• Assists faculty by preparing and playing live music for dance classes
• Researches and sources arrangements suitable for accompanying dance
• May make arrangements for and perform in departmental productions
• May assist faculty in instructing dancers in musical concepts

Knowledge

• Office procedures and practices
• Customer service techniques

Skills

• Maintaining confidentiality of work-related information and materials
• Establishing and maintaining effective working relationships
• Maintaining an established work schedule
• Effectively using interpersonal and communication skills
• Effectively using organizational and planning skills
• Entering data, maintaining files, and performing other clerical duties
• Effective customer-orientation when working with a multicultural population

Technology Skills

• Use a variety of spreadsheet, word processing, database, and presentation software
• May also use social media, work with desktop publishing, and update webpages

Physical Requirements

Work is routinely performed in a standard office or similar environment. Subject to standing, walking, sitting, bending, reaching, kneeling, pushing, and pulling. Occasional lifting of objects up to 10 pounds.

Safety

Work safely and follow safety rules. Report unsafe working conditions and behavior. Take reasonable and prudent actions to prevent others from engaging in unsafe practices.

Pay

$58.30/Hour. Up to 19 hours per week.

Schedule

Up to 19 hours per week (already mentioned). Could combine with Pay? But schedule is separate; we have schedule info: Up to 19 hours per week. Could put under Schedule. We also have Number Of Openings: 1 and Job Posting Close Date: October 2, 2026. Those could be placed under a short

maybe under a heading like "Job Details" but we only have allowed headings list; we could put them under a generic

without heading? The instruction: Use

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. those). Probably we should stick to those headings only. For metadata like openings and close date, we could include them in a

under maybe "About the role" or just after the summary. But better to add a short paragraph after the summary: "Number of openings: 1. Position closes October 2, 2026." That's substantive. We should not include Benefits section because not mentioned. We should not include Requirements/Qualifications unless present; we have Knowledge and Skills but not explicit Requirements/Qualifications. Could combine Knowledge as Requirements? But better to follow given headings: we have Knowledge separate; we could treat Knowledge as Requirements? The instruction list includes Requirements, Qualifications. We have Knowledge and Skills; we could map Knowledge to Requirements, Skills to Skills. But we already have Skills section; we could rename Knowledge to Requirements. However the instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings but suggests using those. It's safer to map Knowledge to Requirements, and Skills to Skills. But we already have Skills list; we could keep Skills as Skills, and move Knowledge to Requirements. However the posting explicitly labels "Knowledge" and "Skills". To preserve all info, we should keep both headings as they appear? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings like Knowledge, Technology Skills, Physical Requirements, Safety. But they gave examples; maybe we should stick to those examples only. However the instruction also says "Prefer a few substantive sections over many thin ones." Having many thin sections like Knowledge, Technology Skills, Physical Requirements, Safety may be many thin ones. Could combine some. We could combine Knowledge and Skills into a single Skills section? But they are distinct. However we could keep them as separate sections but using headings "Knowledge" and "Skills" which are not in the examples but maybe acceptable. The instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." implies those are examples, not exclusive. So we can use other headings as needed. So we can keep Knowledge, Technology Skills, Physical Requirements, Safety as headings. Thus final HTML fragment will include:

About the role

Provides support to a departmental office or program. Number of openings: 1. Position closes October 2, 2026.

Responsibilities

...

Knowledge

...

Skills

...

Technology Skills

...

Physical Requirements

...

Safety

...

Pay

$58.30/Hour. Up to 19 hours per week.

Schedule

Up to 19 hours per week.

But note schedule duplicates pay info; we could keep schedule as "Up to 19 hours per week." Pay already mentions that. Could combine but okay. We must not repeat job title as heading. Good. We must not put Job ID/requisition numbers as headings; none. We must remove boilerplate: we removed domicile, employee link, mission statement paragraphs, Clery Act details, disclaimer, etc. Also removed "Job Posting Closing Times: Job postings are removed from advertising at 12:00 A.M. on the closing date e.g., at midnight on the day before the closing date." That's boilerplate. Also removed "Austin Community College employees are required to maintain a domicile in the State of Texas while working for the college and throughout the duration of employment. – AR 4.0300.01". Removed. Also removed "If you are a current Austin Community College employee, please click this link to apply through your Workday account." Also removed the mission statement paragraphs about ACC. Also removed Clery Act details and disclaimer. Also removed "As required by the US Department of Education..." etc. Also removed "Disclaimer ..." etc. Now ensure we preserve all substantive info: duties, knowledge, skills, technology skills, physical requirements, safety, pay, schedule, number of openings, close date, summary. Check we didn't miss any duty: list includes: - Assists faculty by preparing and playing live music for dance classes - Researches and sources arrangements suitable for accompanying dance - May make arrangements for and perform in departmental productions - May assist faculty in instructing dancers in musical concepts Yes. Knowledge list: - Office procedures and practices. - Customer service techniques. Skills list (the long list): - Maintaining confidentiality of work-related information and materials. - Establishing and maintaining effective working relationships. - Maintaining an established work schedule. - Effectively using interpersonal and communication skills. - Effectively using organizational and planning skills. - Entering data, maintaining files, and performing other clerical duties. - Effective customer-orientation when working with a multicultural population. Technology Skills: - Use a variety of spreadsheet, word processing, database, and presentation software. - May also use social media, work with desktop publishing, and update webpages. Physical Requirements: - Work is routinely performed in a standard office or similar environment. - Subject to standing, walking, sitting, bending, reaching, kneeling, pushing, and pulling. - Occasional lifting of objects up to 10 pounds. Safety: - Work safely and follow safety rules. - Report unsafe working conditions and behavior. - Take reasonable and prudent actions to prevent others from engaging in unsafe practices. Pay Rate: $58.30/Hour Up to 19 hours per week. Number Of Openings: 1 Job Posting Close Date: October 2, 2026 We included number of openings and close date in About the role paragraph. Now ensure we didn't include any filler like "commensurate with experience". Not present. Now output only HTML fragment. Let's craft. We need to open and close tags appropriately. We'll output: