Night General Cleaner (Full-Time)
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists
- Use
for prose
- Do NOT repeat job title as heading (page already shows it)
- Do NOT put Job ID/requisition numbers as headings
- Preserve ALL substantive information
- Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions)
- Include section ONLY when posting has real specific content for it
- Never emit heading followed by filler/placeholder text
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Output ONLY HTML fragment, no html/body, no markdown code fences
Now, map content to sections:
1. "Who We Are" -> Could be "About the company" or similar. But the allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Who We Are" is about the company, not the role. The rules say use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." so maybe other headings allowed? But prefer those. However, "Who We Are" is company description. Could be "About the company" but not in list. Might fold into a short
under "About the role"? But "What You'll Be Doing" is role overview. Let's see.
The posting has:
- Who We Are (company description)
- What You'll Be Doing (role overview)
- Night Cleaner Responsibilities (list)
- Night Cleaner Requirements (list)
- Schedule: Monday - Friday, 5:00PM-1:30AM
No Pay, Benefits, Qualifications separate from Requirements, Skills separate.
We need to decide sections. The rules: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those exact headings. "About the role" could encompass "What You'll Be Doing". "Responsibilities" for the responsibilities list. "Requirements" for requirements list. "Schedule" for the schedule.
"Who We Are" is company info. Could be included as a short paragraph before sections? But the output should be HTML fragment with sections. The rules say "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid company description. But the example headings don't include "About the company". However, we can include a section "About the company" if we want? The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. But also "Prefer a few substantive sections over many thin ones." So maybe we can include "About the company" as a section? But the company description is substantive. However, the user might expect only those headings. Let's see typical job posting reformatting: often they have "About the Company" or "Company Overview". But the instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It might be that we should only use those headings. But "About the role" is not "About the company". The posting has "What You'll Be Doing" which is about the role. So we can have "About the role" heading with the "What You'll Be Doing" prose. Then "Responsibilities" with the list. Then "Requirements" with the list. Then "Schedule" with the schedule.
What about "Who We Are"? Could be a short paragraph before sections? But the output is only HTML fragment, we can include a
before any heading? The rules don't forbid prose outside sections. But they say "Output ONLY the HTML fragment". It could be a series of sections. I think we can include a
for company description, then sections. However, the instruction: "Reformat a job posting into clean, well-structured semantic HTML." Usually they'd want sections. I'll include a section "About the company" with
? But the example headings don't include it. 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. But to be safe, maybe we can fold "Who We Are" into a short
before the first heading? But then it's not a section. The rules: "include a section ONLY when the posting has real, specific content for it". The company description is real content. But the heading "About the company" is not in the example list. However, the example list is not exhaustive. I think it's okay to add "About the company" as a heading. But the instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This could be interpreted as "use these headings". But "About the role" is there, not "About the company". The posting has "What You'll Be Doing" which is about the role. So we can have "About the role" heading with that content. The "Who We Are" is separate. Could be a short intro paragraph. I'll include it as a
before the first heading. That seems acceptable.
Now, the EEO/diversity/ADA/PWFA/E-Verify boilerplate should be removed. The schedule is at the end: "Monday - Friday, 5:00PM-1:30AM". That's a schedule, so we can create a "Schedule" section.
The requirements list includes "High school diploma, GED, or suitable equivalent." and "Authorized to work in the U.S. – We Use E-Verify". The E-Verify is metadata, we can fold into a short
or drop. The rule: "fold minor metadata into a short
or drop it." So we can include a sentence in Requirements or a separate note. But better to keep in Requirements list as a bullet? It's a requirement. But "Authorized to work in the U.S." is a requirement. The "We Use E-Verify" is metadata. We can keep "Authorized to work in the U.S." as a bullet, and maybe add a note about E-Verify in a paragraph after the list? But the rule says fold minor metadata into a short
or drop it. I'll include "Authorized to work in the U.S. (E-Verify used)." as a bullet.
Now, the responsibilities list: there are many bullets. We'll put them in
- .
The requirements list: also bullets.
The "What You'll Be Doing" is prose: "We are looking for a reliable and professional night cleaner to keep our facilities clean. You will be responsible for maintaining a clean facility by completing a variety of cleaning tasks to keep the buildings looking perfect. You will be tasked with keeping facilities clean in the evenings, potentially locking doors, and arming alarms. To work well in this role, you should have some cleaning experience and basic knowledge of various cleaning products." That's a paragraph.
The "Who We Are" is prose: "CSI International Inc, founded in 1989, provides integrated building services to clients in real estate, property management, pharmaceuticals, telecommunications, higher education, manufacturing, and insurance. Throughout CSI International Inc.’s constant growth and evolution, our primary goal – exceeding our clients’ expectations – has remained unchanged. Because of this, we enjoy an incomparable reputation for cost-effective solutions with responsive services with uncompromising quality." That's a paragraph.
Now, structure:
Option 1:
Company description...
About the role
What you'll be doing...
Responsibilities
- ...
Requirements
- ...
Schedule
Monday - Friday, 5:00PM-1:30AM
But the rule: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use exactly those headings. "About the role" is good. "Responsibilities" good. "Requirements" good. "Schedule" good.
We have no Qualifications, Skills, Benefits, Pay sections, so omit.
Now, the company description: where to put? Could be a
before "About the role". That's fine.
But the instruction: "Do NOT repeat the job title as a heading (the page already shows it)". The job title is "Night Cleaner". We are not using that as heading.
Now, ensure we preserve ALL substantive information. The responsibilities list includes "Other responsibilities as assigned by your supervisor." Keep that.
Requirements list includes "Ability to manage your time efficiently." etc. Keep all.
Now, the schedule: "Monday - Friday, 5:00PM-1:30AM". That's a single line. Use
for prose.
Now, remove duplicated lines? There's no duplication.
Remove application instructions? There's none.
Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The EEO paragraph is boilerplate, remove. The ADA/PWFA paragraph is boilerplate, remove. The contact for accommodation is application instruction? It's about reasonable accommodation request. That's part of EEO boilerplate, remove.
The "CSI International, Inc. is committed to fostering..." etc. Remove.
The "Consistent with the Americans with Disabilities Act..." etc. Remove.
The "If reasonable accommodation is needed, please contact the Recruitment Team at 813-425-1985." Remove.
Now, the "Authorized to work in the U.S. – We Use E-Verify" is a requirement but also metadata. Keep the requirement, maybe phrase as "Authorized to work in the U.S. (E-Verify used)."
Now, write HTML.
Let's craft:
CSI International Inc, founded in 1989, provides integrated building services to clients in real estate, property management, pharmaceuticals, telecommunications, higher education, manufacturing, and insurance. Throughout CSI International Inc.’s constant growth and evolution, our primary goal – exceeding our clients’ expectations – has remained unchanged. Because of this, we enjoy an incomparable reputation for cost-effective solutions with responsive services with uncompromising quality.
About the role
We are looking for a reliable and professional night cleaner to keep our facilities clean. You will be responsible for maintaining a clean facility by completing
for prose - Do NOT repeat job title as heading (page already shows it) - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) - Include section ONLY when posting has real specific content for it - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Output ONLY HTML fragment, no html/body, no markdown code fences Now, map content to sections: 1. "Who We Are" -> Could be "About the company" or similar. But the allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Who We Are" is about the company, not the role. The rules say use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." so maybe other headings allowed? But prefer those. However, "Who We Are" is company description. Could be "About the company" but not in list. Might fold into a short
under "About the role"? But "What You'll Be Doing" is role overview. Let's see. The posting has: - Who We Are (company description) - What You'll Be Doing (role overview) - Night Cleaner Responsibilities (list) - Night Cleaner Requirements (list) - Schedule: Monday - Friday, 5:00PM-1:30AM No Pay, Benefits, Qualifications separate from Requirements, Skills separate. We need to decide sections. The rules: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those exact headings. "About the role" could encompass "What You'll Be Doing". "Responsibilities" for the responsibilities list. "Requirements" for requirements list. "Schedule" for the schedule.
"Who We Are" is company info. Could be included as a short paragraph before sections? But the output should be HTML fragment with sections. The rules say "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid company description. But the example headings don't include "About the company". However, we can include a section "About the company" if we want? The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. But also "Prefer a few substantive sections over many thin ones." So maybe we can include "About the company" as a section? But the company description is substantive. However, the user might expect only those headings. Let's see typical job posting reformatting: often they have "About the Company" or "Company Overview". But the instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It might be that we should only use those headings. But "About the role" is not "About the company". The posting has "What You'll Be Doing" which is about the role. So we can have "About the role" heading with the "What You'll Be Doing" prose. Then "Responsibilities" with the list. Then "Requirements" with the list. Then "Schedule" with the schedule.
What about "Who We Are"? Could be a short paragraph before sections? But the output is only HTML fragment, we can include a
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It might be that we should only use those headings. But "About the role" is not "About the company". The posting has "What You'll Be Doing" which is about the role. So we can have "About the role" heading with the "What You'll Be Doing" prose. Then "Responsibilities" with the list. Then "Requirements" with the list. Then "Schedule" with the schedule. What about "Who We Are"? Could be a short paragraph before sections? But the output is only HTML fragment, we can include a
before any heading? The rules don't forbid prose outside sections. But they say "Output ONLY the HTML fragment". It could be a series of sections. I think we can include a
for company description, then sections. However, the instruction: "Reformat a job posting into clean, well-structured semantic HTML." Usually they'd want sections. I'll include a section "About the company" with
? But the example headings don't include it. 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. But to be safe, maybe we can fold "Who We Are" into a short
before the first heading? But then it's not a section. The rules: "include a section ONLY when the posting has real, specific content for it". The company description is real content. But the heading "About the company" is not in the example list. However, the example list is not exhaustive. I think it's okay to add "About the company" as a heading. But the instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This could be interpreted as "use these headings". But "About the role" is there, not "About the company". The posting has "What You'll Be Doing" which is about the role. So we can have "About the role" heading with that content. The "Who We Are" is separate. Could be a short intro paragraph. I'll include it as a
before the first heading. That seems acceptable. Now, the EEO/diversity/ADA/PWFA/E-Verify boilerplate should be removed. The schedule is at the end: "Monday - Friday, 5:00PM-1:30AM". That's a schedule, so we can create a "Schedule" section. The requirements list includes "High school diploma, GED, or suitable equivalent." and "Authorized to work in the U.S. – We Use E-Verify". The E-Verify is metadata, we can fold into a short
or drop. The rule: "fold minor metadata into a short
or drop it." So we can include a sentence in Requirements or a separate note. But better to keep in Requirements list as a bullet? It's a requirement. But "Authorized to work in the U.S." is a requirement. The "We Use E-Verify" is metadata. We can keep "Authorized to work in the U.S." as a bullet, and maybe add a note about E-Verify in a paragraph after the list? But the rule says fold minor metadata into a short
or drop it. I'll include "Authorized to work in the U.S. (E-Verify used)." as a bullet. Now, the responsibilities list: there are many bullets. We'll put them in
- .
The requirements list: also bullets.
The "What You'll Be Doing" is prose: "We are looking for a reliable and professional night cleaner to keep our facilities clean. You will be responsible for maintaining a clean facility by completing a variety of cleaning tasks to keep the buildings looking perfect. You will be tasked with keeping facilities clean in the evenings, potentially locking doors, and arming alarms. To work well in this role, you should have some cleaning experience and basic knowledge of various cleaning products." That's a paragraph.
The "Who We Are" is prose: "CSI International Inc, founded in 1989, provides integrated building services to clients in real estate, property management, pharmaceuticals, telecommunications, higher education, manufacturing, and insurance. Throughout CSI International Inc.’s constant growth and evolution, our primary goal – exceeding our clients’ expectations – has remained unchanged. Because of this, we enjoy an incomparable reputation for cost-effective solutions with responsive services with uncompromising quality." That's a paragraph.
Now, structure:
Option 1:
Company description...
About the role
What you'll be doing...
Responsibilities
- ...
Requirements
- ...
Schedule
Monday - Friday, 5:00PM-1:30AM
But the rule: "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use exactly those headings. "About the role" is good. "Responsibilities" good. "Requirements" good. "Schedule" good. We have no Qualifications, Skills, Benefits, Pay sections, so omit. Now, the company description: where to put? Could be a
before "About the role". That's fine. But the instruction: "Do NOT repeat the job title as a heading (the page already shows it)". The job title is "Night Cleaner". We are not using that as heading. Now, ensure we preserve ALL substantive information. The responsibilities list includes "Other responsibilities as assigned by your supervisor." Keep that. Requirements list includes "Ability to manage your time efficiently." etc. Keep all. Now, the schedule: "Monday - Friday, 5:00PM-1:30AM". That's a single line. Use
for prose. Now, remove duplicated lines? There's no duplication. Remove application instructions? There's none. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The EEO paragraph is boilerplate, remove. The ADA/PWFA paragraph is boilerplate, remove. The contact for accommodation is application instruction? It's about reasonable accommodation request. That's part of EEO boilerplate, remove. The "CSI International, Inc. is committed to fostering..." etc. Remove. The "Consistent with the Americans with Disabilities Act..." etc. Remove. The "If reasonable accommodation is needed, please contact the Recruitment Team at 813-425-1985." Remove. Now, the "Authorized to work in the U.S. – We Use E-Verify" is a requirement but also metadata. Keep the requirement, maybe phrase as "Authorized to work in the U.S. (E-Verify used)." Now, write HTML. Let's craft:
CSI International Inc, founded in 1989, provides integrated building services to clients in real estate, property management, pharmaceuticals, telecommunications, higher education, manufacturing, and insurance. Throughout CSI International Inc.’s constant growth and evolution, our primary goal – exceeding our clients’ expectations – has remained unchanged. Because of this, we enjoy an incomparable reputation for cost-effective solutions with responsive services with uncompromising quality.
About the role
We are looking for a reliable and professional night cleaner to keep our facilities clean. You will be responsible for maintaining a clean facility by completing