Assistant Professor - School of Media Arts and Design
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. No Job ID etc. Remove boilerplate. Preserve all substantive info.
We need to parse posting: It includes many details: Opening date, Working Title, State Role Title N/A, Position Type, Position Status, FLSA, College/Division, Department, Pay Band N/A, Pay Rate: Commensurate with Experience, Is JMU only? No, grant-funded? No, Conflict of Interest? No, Beginning Review Date: 10/22/2026, About JMU Mission etc, General Information about SMAD, Duties And Responsibilities, Qualifications, Additional Posting Information (application instructions - we must remove application instructions), Conditions Of Employment (background check, E-Verify), EEO Statement, Reasonable Accommodation (remove). We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we must drop EEO Statement, Reasonable Accommodation, Conditions of Employment? Conditions of Employment includes background check and E-Verify - that's legal boilerplate; likely should be removed. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". So Conditions of Employment (background check, E-Verify) is legal boilerplate, remove. EEO Statement remove. Reasonable Accommodation remove. Also remove application instructions (cover letter, CV, references, dual career program). Also remove duplicated lines.
We need to keep substantive info: About JMU Mission, Vision, Who We Are, General Information about SMAD, Duties And Responsibilities, Qualifications. Also maybe Pay? Pay Rate: Commensurate with Experience - that's placeholder "Commencement with Experience" which is not specific; we should not create Pay section unless posting actually states them. It says "Pay Rate: Commensurate with Experience". That's not a specific number or range, it's vague. According to rule: 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. So we should not include Pay section. Similarly Schedule? Not given. Benefits? Not given. So we will not include those.
We need sections: About the role (maybe "About the role" corresponds to General Information about SMAD and JMU mission?). Could combine. Responsibilities (Duties And Responsibilities). Requirements (Qualifications). Possibly Skills? Not explicitly listed. Could embed skills within qualifications. But we need to follow rule: use headings only when posting has real specific content. We have content for About the role (JMU mission, SMAD description). Responsibilities (Duties And Responsibilities). Requirements (Qualifications). Could also have "About JMU" but we can put under About the role.
We must not repeat job title as heading. So no heading for "Assistant Professor - School of Media Arts and Design". Good.
We need to output only HTML fragment, no /, no markdown fences.
Thus produce something like:
About the role
... content ...
Responsibilities
- ... each duty ...
Requirements
- ... each qualification ...
or drop it. So we could include a short paragraph with opening date and review date maybe. But we need to decide if we keep it. It's substantive? It's a date. Could be included in a short
under About the role maybe. But we must not create headings for minor metadata. So we can include a paragraph with "Opening date: Sep 21 2026. Beginning review date: 10/22/2026." That's fine. Also "Working Title: Assistant Professor - School of Media Arts and Design" but we should not repeat job title as heading; we could include it in a paragraph maybe. But the instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid including it in a paragraph. However, it's somewhat redundant. Might be okay to include as part of metadata. But we could drop it to avoid duplication. The instruction says fold minor metadata into a short
or drop it. So we could include a short paragraph with the working title and maybe position type etc. But we already have position type in the posting: "Position Type: Instructional / Teaching Faculty". That's also metadata. Could include. But we need to preserve ALL substantive information; does that include metadata like position type, FLSA status, etc? Those are likely considered boilerplate? Not exactly; they are specifics about the position. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not say to remove metadata like position type, FLSA, pay band, etc. However, we should not create headings for them unless they have real specific content. We could include them in a short paragraph. But we also need to avoid creating sections like Pay/Schedule/Benefits unless posting actually states them. Pay Band: N/A, Pay Rate: Commensurate with Experience - those are not specific, so we should not create Pay section. But we could still mention them in a paragraph? The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It doesn't forbid mentioning them elsewhere. However, to be safe, we could include them in a short paragraph under About the role or as a separate metadata paragraph. But we must preserve ALL substantive information. If we drop Pay Band and Pay Rate, are we losing substantive info? They are not substantive (they are N/A or vague). Might be okay to drop. The instruction says preserve ALL substantive information; does not require preserving nonsubstantive placeholders. So we can drop N/A and "Commensurate with Experience". Similarly, we could drop Position Type? It's substantive: it's Instructional / Teaching Faculty. That's meaningful. FLSA Status: Exempt: Not Eligible for Overtime - also substantive. College/Division, Department - substantive. Beginning Review Date - substantive. Opening date - substantive. Thus we should include those details in a short paragraph. We need to avoid headings for minor metadata. So we can have a
that includes: "Position Type: Instructional / Teaching Faculty. FLSA Status: Exempt: Not Eligible for Overtime. College/Division: College of Arts and Letters. Department: School of Media Arts (100018). Opening date: Sep 21 2026. Beginning review date: 10/22/2026." We could also include Working Title but it's same as job title; maybe skip. Now we need to structure sections:
About the role
Combine JMU mission/vision/who we are, SMAD general info, plus metadata paragraph? Might be too long. Better to split: About the role could include JMU mission/vision/who we are and SMAD description. Then a separate
for metadata? But we said we prefer few substantive sections over many thin ones. Could combine metadata into About the role paragraph after the description. Thus About the role paragraph