Maintenance Associate
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule).
- Use - for lists,
for prose.
- Do NOT repeat job title as heading (not provided anyway).
- Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short
or drop.
- Preserve ALL substantive information; do NOT invent or summarize.
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
- Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD").
- Never create Pay/Schedule/Benefits sections unless posting actually states them.
- Prefer few substantive sections over many thin ones.
- Output ONLY HTML fragment — no /, no markdown code fences.
Now, parse the content:
The posting starts with "Company Description" but it's actually a mix of role description and company info. The first paragraph: "You are ... a multitasker with attention to detail, a skilled handyman that can handle a variety of tasks, and a professional who is committed to getting the job done right. As part of the facilities maintenance team you play a key role in maintaining the upkeep of campus buildings. You will report to the Facility Manager in Ashland, VA. The work schedule is Monday-Friday. The salary range for this position is between $19 and $22 per hour and can be higher depending on skills and experience."
That's about the role, schedule, pay. Then "We are ... focused on selling and supporting Anton Paar's range..." That's company description.
Then "Job Description" with bullet points: "Ensures buildings are maintained and presentable and in operational condition General upkeep including: Replacing light bulbs, patching and touching up paint as needed, inspecting and report stains or similar damager that cannot be repaired, handling maintenance tasks around the campus. Completing special tasks as assigned"
Then "Qualifications" with bullet points: "experience with facility maintenance or a background in related trades strongly preferred Strong attention to detail Excellent time management, organizational, and prioritizing skills Proficiency in using computer and email"
Then "Additional Information" with multiple paragraphs: about recruiting process, In Motion Program, benefits package, drug free workplace, pre-employment drug tests, equal opportunity, visa sponsorship, not accepting applications via agencies, apply via career site.
We need to remove boilerplate: "At Anton Paar, we truly value every application. Our recruiting team knows your time matters, so we promise to get back to you within 48 hours. Quick, transparent, and personal. Each application does get reviewed by a member of our corporate recruiting team. Just how hiring should be." That's application process boilerplate, remove.
"Life at Anton Paar is more than just work, with an employee-led In Motion Program organizing active social events during and outside working hours. We also offer unique and rewarding positions with competitive salaries, an award-winning benefits package, and opportunities for professional growth." This mentions benefits package, but not specifics. The rule: never create Benefits section unless posting actually states them. It says "award-winning benefits package" but no details. Should we include a Benefits section? The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It states "award-winning benefits package" but no specifics. Might be considered filler. However, it's a substantive mention of benefits. But the rule says "include a section ONLY when the posting has real, specific content for it". "Award-winning benefits package" is vague. Probably not specific enough. But we have Pay and Schedule explicitly stated: salary range $19-22/hr, schedule Monday-Friday. So we can create Pay and Schedule sections.
Also "We provide a drug free workplace and require pre-employment drug tests." That's a requirement/condition.
"Anton Paar USA, Inc. considers all qualified candidates for this position." EEO boilerplate, remove.
"This position is not eligible for current or future work authorization or visa sponsorship." That's a specific condition, keep.
"We do not accept applications via personnel service providers or recruitment agencies and ask all interested applicants to submit their documents directly via our career site." Application instructions, remove.
Now, structure sections:
Possible sections:
- About the role (or Company Description? The first paragraph describes the role and company). The rule suggests headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We have responsibilities (Job Description), qualifications (Qualifications), pay, schedule, and maybe a company overview.
But the first paragraph includes both role context and company info. Could split: "About the role" for the first paragraph (multitasker, handyman, report to Facility Manager, Ashland, VA). Then "Company overview" for the Anton Paar description. However, the rule says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't mention "Company overview". But we can use "About the company" or similar? The rule says "e.g." so we can use other headings if needed. But prefer standard ones.
Better: Use "About the role" for the first paragraph (since it describes the role). Then "Company description" for the company paragraph. But the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other headings, but we should keep to those if possible. However, the company description is substantive. Could include as a paragraph under "About the role"? But it's separate.
Alternatively, we can have "About the role" and "Company overview". But the rule says "Prefer a few substantive sections over many thin ones." So maybe combine company description into a single "About the role" section? But the company description is about the company, not the role. However, the first paragraph already includes company context? Actually the first paragraph is "You are ... a multitasker... As part of the facilities maintenance team... You will report to the Facility Manager in Ashland, VA. The work schedule is Monday-Friday. The salary range..." That's role-specific. Then "We are ... focused on selling and supporting Anton Paar's range..." That's company description.
We could create two sections: "About the role" and "Company overview". But the rule doesn't list "Company overview". However, it's common. I think it's okay to include a heading for company description if there's content. The rule 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 exhaustive. But to be safe, maybe we can put company description under "About the role" as a paragraph? But that would mix.
Let's see: The user wants clean, well-structured semantic HTML. I'll create sections as appropriate.
Plan sections:
1. About the role (includes first paragraph: multitasker, handyman, report to Facility Manager, location Ashland, VA)
2. Company overview (the Anton Paar description)
3. Responsibilities (from Job Description)
4. Qualifications (from Qualifications)
5. Pay (salary range)
6. Schedule (Monday-Friday)
7. Additional details (drug free workplace, pre-employment drug test, no visa sponsorship) - but maybe not a standard heading. Could be "Requirements" or "Conditions". The rule mentions "Requirements" as a heading. But we already have Qualifications. Could add "Employment conditions" or similar. However, the rule says never create a section unless real specific content. We have specific content: drug free workplace, pre-employment drug test, no visa sponsorship. That's substantive. Could put under "Additional information" but that heading not in list. Could use "Requirements" for these? But Qualifications already covers skills. Might create a "Conditions" section. But the rule says prefer few substantive sections. Maybe include these in a "Notes" section? But not in list.
Alternatively, we can include the drug test and visa sponsorship in a "Requirements" section? But the rule says "Requirements" is an example heading. Could use "Requirements" for both qualifications and conditions? But we already have Qualifications. The posting has "Qualifications" and "Additional Information". We can map "Qualifications" to "Qualifications" heading, and "Additional Information" to maybe "Benefits" (but benefits not detailed) and "Pay" and "Schedule" already separate. The remaining: drug free, drug test, no visa sponsorship. Could be under "Employment conditions" but not in list. Might just include as a paragraph under "Qualifications"? Not ideal.
Better: Create a "Conditions" section with heading "Conditions" (not in list but okay). However, the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use others. But to be safe, maybe we can use "Requirements" for the conditions? But "Requirements" might be confused with qualifications. The posting has "Qualifications" and "Additional Information". I'll create a section "Additional information" for the remaining substantive points (drug free, drug test, no visa sponsorship). But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It doesn't say we cannot create "Additional information". But we should avoid boilerplate. The additional information includes some boilerplate (recruiting process) which we remove. The remaining is specific.
Let's decide on sections:
- About the role
- Company overview (or "About the company")
- Responsibilities
- Qualifications
- Pay
- Schedule
- Employment conditions (or "Additional details")
But the rule says "Prefer a few substantive sections over many thin ones." So maybe combine Pay and Schedule into one "Compensation and schedule" section? But they are separate headings in examples. Could keep separate.
Also, the first paragraph includes schedule and pay. We'll extract those into separate sections.
Now, write HTML.
We'll output only the fragment.
Let's draft:
About the role
You are a multitasker with attention to detail, a skilled handyman that can handle a variety of tasks, and a professional who is committed to getting the job done right. As part of the facilities maintenance team you play a key role in maintaining the upkeep of campus buildings. You will report to the Facility Manager in Ashland, VA.
Company overview
Anton Paar is focused on selling and supporting high-precision measuring instruments for physical, chemical, mechanical, and structural properties. A highly diverse, dynamic, and financially sound company, we have grown every year since our start in 1986. Our exceptionally high investment in R&D fuels industry-leading solutions throughout a vast range of the industrial and academic landscape, impacting nearly every product you use in daily life. Anton Paar USA is a for-profit sales and service organization in the Anton Paar Group, privately owned by the charitable Santner Foundation with its headquarters in Graz, Austria.
Responsibilities
- Ensure buildings are maintained, presentable, and in
for prose. - Do NOT repeat job title as heading (not provided anyway). - Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short
or drop. - Preserve ALL substantive information; do NOT invent or summarize. - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. - Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). - Never create Pay/Schedule/Benefits sections unless posting actually states them. - Prefer few substantive sections over many thin ones. - Output ONLY HTML fragment — no /, no markdown code fences. Now, parse the content: The posting starts with "Company Description" but it's actually a mix of role description and company info. The first paragraph: "You are ... a multitasker with attention to detail, a skilled handyman that can handle a variety of tasks, and a professional who is committed to getting the job done right. As part of the facilities maintenance team you play a key role in maintaining the upkeep of campus buildings. You will report to the Facility Manager in Ashland, VA. The work schedule is Monday-Friday. The salary range for this position is between $19 and $22 per hour and can be higher depending on skills and experience." That's about the role, schedule, pay. Then "We are ... focused on selling and supporting Anton Paar's range..." That's company description. Then "Job Description" with bullet points: "Ensures buildings are maintained and presentable and in operational condition General upkeep including: Replacing light bulbs, patching and touching up paint as needed, inspecting and report stains or similar damager that cannot be repaired, handling maintenance tasks around the campus. Completing special tasks as assigned" Then "Qualifications" with bullet points: "experience with facility maintenance or a background in related trades strongly preferred Strong attention to detail Excellent time management, organizational, and prioritizing skills Proficiency in using computer and email" Then "Additional Information" with multiple paragraphs: about recruiting process, In Motion Program, benefits package, drug free workplace, pre-employment drug tests, equal opportunity, visa sponsorship, not accepting applications via agencies, apply via career site. We need to remove boilerplate: "At Anton Paar, we truly value every application. Our recruiting team knows your time matters, so we promise to get back to you within 48 hours. Quick, transparent, and personal. Each application does get reviewed by a member of our corporate recruiting team. Just how hiring should be." That's application process boilerplate, remove. "Life at Anton Paar is more than just work, with an employee-led In Motion Program organizing active social events during and outside working hours. We also offer unique and rewarding positions with competitive salaries, an award-winning benefits package, and opportunities for professional growth." This mentions benefits package, but not specifics. The rule: never create Benefits section unless posting actually states them. It says "award-winning benefits package" but no details. Should we include a Benefits section? The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It states "award-winning benefits package" but no specifics. Might be considered filler. However, it's a substantive mention of benefits. But the rule says "include a section ONLY when the posting has real, specific content for it". "Award-winning benefits package" is vague. Probably not specific enough. But we have Pay and Schedule explicitly stated: salary range $19-22/hr, schedule Monday-Friday. So we can create Pay and Schedule sections. Also "We provide a drug free workplace and require pre-employment drug tests." That's a requirement/condition. "Anton Paar USA, Inc. considers all qualified candidates for this position." EEO boilerplate, remove. "This position is not eligible for current or future work authorization or visa sponsorship." That's a specific condition, keep. "We do not accept applications via personnel service providers or recruitment agencies and ask all interested applicants to submit their documents directly via our career site." Application instructions, remove. Now, structure sections: Possible sections: - About the role (or Company Description? The first paragraph describes the role and company). The rule suggests headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We have responsibilities (Job Description), qualifications (Qualifications), pay, schedule, and maybe a company overview. But the first paragraph includes both role context and company info. Could split: "About the role" for the first paragraph (multitasker, handyman, report to Facility Manager, Ashland, VA). Then "Company overview" for the Anton Paar description. However, the rule says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't mention "Company overview". But we can use "About the company" or similar? The rule says "e.g." so we can use other headings if needed. But prefer standard ones.
Better: Use "About the role" for the first paragraph (since it describes the role). Then "Company description" for the company paragraph. But the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other headings, but we should keep to those if possible. However, the company description is substantive. Could include as a paragraph under "About the role"? But it's separate.
Alternatively, we can have "About the role" and "Company overview". But the rule says "Prefer a few substantive sections over many thin ones." So maybe combine company description into a single "About the role" section? But the company description is about the company, not the role. However, the first paragraph already includes company context? Actually the first paragraph is "You are ... a multitasker... As part of the facilities maintenance team... You will report to the Facility Manager in Ashland, VA. The work schedule is Monday-Friday. The salary range..." That's role-specific. Then "We are ... focused on selling and supporting Anton Paar's range..." That's company description.
We could create two sections: "About the role" and "Company overview". But the rule doesn't list "Company overview". However, it's common. I think it's okay to include a heading for company description if there's content. The rule 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 exhaustive. But to be safe, maybe we can put company description under "About the role" as a paragraph? But that would mix.
Let's see: The user wants clean, well-structured semantic HTML. I'll create sections as appropriate.
Plan sections:
1. About the role (includes first paragraph: multitasker, handyman, report to Facility Manager, location Ashland, VA)
2. Company overview (the Anton Paar description)
3. Responsibilities (from Job Description)
4. Qualifications (from Qualifications)
5. Pay (salary range)
6. Schedule (Monday-Friday)
7. Additional details (drug free workplace, pre-employment drug test, no visa sponsorship) - but maybe not a standard heading. Could be "Requirements" or "Conditions". The rule mentions "Requirements" as a heading. But we already have Qualifications. Could add "Employment conditions" or similar. However, the rule says never create a section unless real specific content. We have specific content: drug free workplace, pre-employment drug test, no visa sponsorship. That's substantive. Could put under "Additional information" but that heading not in list. Could use "Requirements" for these? But Qualifications already covers skills. Might create a "Conditions" section. But the rule says prefer few substantive sections. Maybe include these in a "Notes" section? But not in list.
Alternatively, we can include the drug test and visa sponsorship in a "Requirements" section? But the rule says "Requirements" is an example heading. Could use "Requirements" for both qualifications and conditions? But we already have Qualifications. The posting has "Qualifications" and "Additional Information". We can map "Qualifications" to "Qualifications" heading, and "Additional Information" to maybe "Benefits" (but benefits not detailed) and "Pay" and "Schedule" already separate. The remaining: drug free, drug test, no visa sponsorship. Could be under "Employment conditions" but not in list. Might just include as a paragraph under "Qualifications"? Not ideal.
Better: Create a "Conditions" section with heading "Conditions" (not in list but okay). However, the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use others. But to be safe, maybe we can use "Requirements" for the conditions? But "Requirements" might be confused with qualifications. The posting has "Qualifications" and "Additional Information". I'll create a section "Additional information" for the remaining substantive points (drug free, drug test, no visa sponsorship). But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It doesn't say we cannot create "Additional information". But we should avoid boilerplate. The additional information includes some boilerplate (recruiting process) which we remove. The remaining is specific.
Let's decide on sections:
- About the role
- Company overview (or "About the company")
- Responsibilities
- Qualifications
- Pay
- Schedule
- Employment conditions (or "Additional details")
But the rule says "Prefer a few substantive sections over many thin ones." So maybe combine Pay and Schedule into one "Compensation and schedule" section? But they are separate headings in examples. Could keep separate.
Also, the first paragraph includes schedule and pay. We'll extract those into separate sections.
Now, write HTML.
We'll output only the fragment.
Let's draft:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." implies those are examples, not exhaustive. But to be safe, maybe we can put company description under "About the role" as a paragraph? But that would mix.
Let's see: The user wants clean, well-structured semantic HTML. I'll create sections as appropriate.
Plan sections:
1. About the role (includes first paragraph: multitasker, handyman, report to Facility Manager, location Ashland, VA)
2. Company overview (the Anton Paar description)
3. Responsibilities (from Job Description)
4. Qualifications (from Qualifications)
5. Pay (salary range)
6. Schedule (Monday-Friday)
7. Additional details (drug free workplace, pre-employment drug test, no visa sponsorship) - but maybe not a standard heading. Could be "Requirements" or "Conditions". The rule mentions "Requirements" as a heading. But we already have Qualifications. Could add "Employment conditions" or similar. However, the rule says never create a section unless real specific content. We have specific content: drug free workplace, pre-employment drug test, no visa sponsorship. That's substantive. Could put under "Additional information" but that heading not in list. Could use "Requirements" for these? But Qualifications already covers skills. Might create a "Conditions" section. But the rule says prefer few substantive sections. Maybe include these in a "Notes" section? But not in list.
Alternatively, we can include the drug test and visa sponsorship in a "Requirements" section? But the rule says "Requirements" is an example heading. Could use "Requirements" for both qualifications and conditions? But we already have Qualifications. The posting has "Qualifications" and "Additional Information". We can map "Qualifications" to "Qualifications" heading, and "Additional Information" to maybe "Benefits" (but benefits not detailed) and "Pay" and "Schedule" already separate. The remaining: drug free, drug test, no visa sponsorship. Could be under "Employment conditions" but not in list. Might just include as a paragraph under "Qualifications"? Not ideal.
Better: Create a "Conditions" section with heading "Conditions" (not in list but okay). However, the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use others. But to be safe, maybe we can use "Requirements" for the conditions? But "Requirements" might be confused with qualifications. The posting has "Qualifications" and "Additional Information". I'll create a section "Additional information" for the remaining substantive points (drug free, drug test, no visa sponsorship). But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It doesn't say we cannot create "Additional information". But we should avoid boilerplate. The additional information includes some boilerplate (recruiting process) which we remove. The remaining is specific.
Let's decide on sections:
- About the role
- Company overview (or "About the company")
- Responsibilities
- Qualifications
- Pay
- Schedule
- Employment conditions (or "Additional details")
But the rule says "Prefer a few substantive sections over many thin ones." So maybe combine Pay and Schedule into one "Compensation and schedule" section? But they are separate headings in examples. Could keep separate.
Also, the first paragraph includes schedule and pay. We'll extract those into separate sections.
Now, write HTML.
We'll output only the fragment.
Let's draft:
About the role
About the role
You are a multitasker with attention to detail, a skilled handyman that can handle a variety of tasks, and a professional who is committed to getting the job done right. As part of the facilities maintenance team you play a key role in maintaining the upkeep of campus buildings. You will report to the Facility Manager in Ashland, VA.
Company overview
Anton Paar is focused on selling and supporting high-precision measuring instruments for physical, chemical, mechanical, and structural properties. A highly diverse, dynamic, and financially sound company, we have grown every year since our start in 1986. Our exceptionally high investment in R&D fuels industry-leading solutions throughout a vast range of the industrial and academic landscape, impacting nearly every product you use in daily life. Anton Paar USA is a for-profit sales and service organization in the Anton Paar Group, privately owned by the charitable Santner Foundation with its headquarters in Graz, Austria.
Responsibilities
- Ensure buildings are maintained, presentable, and in