Full-Time Overnight Lead Cleaner (Thu-Mon, 11PM-6AM)
` for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule).
- Use `- ` for lists of duties/requirements/benefits.
- Use `
` for prose.
- Do NOT repeat job title as heading (already shown).
- Do NOT put Job ID / requisition numbers as headings - fold minor metadata into short `
` or drop it.
- Preserve ALL substantive information; do NOT invent or summarize away detail.
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
- IMPORTANT: Include a section ONLY when the posting has real, specific content for it — 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.
- Prefer a few substantive sections over many thin ones.
- Output ONLY the HTML fragment — no `/`, no markdown code fences.
2. **Analyze the Job Posting Text:**
Let me parse the input text carefully. It's a job posting for "ParkX Porter". I need to extract relevant sections and structure them.
Input text structure (roughly):
- Job Overview: "The ParkX Porter is responsible for maintaining cleanliness..."
- Key Responsibilities: bullet points (list of duties)
- Qualifications: bullet points (list of requirements)
- Benefits: section with text about compensation, benefits, etc.
- Virginia Compensation Range: "$19 USD - $19 USD"
I need to map these to the requested headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
Let's identify content for each:
- **About the role / Job Overview**: The first paragraph "The ParkX Porter is responsible for maintaining cleanliness in the common areas at assigned sites. Duties include general upkeep such as pressure washing, window cleaning, trash removal, and routine cleaning tasks. Porter also support event setup and cleanup when necessary and respond to cleanliness concerns as they arise. The position requires reliability, attention to detail, and the ability to work professionally and courteously with property staff, tenants, and visitors." This can go under "About the role" or similar. The rules say: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading (the page already shows it). So I shouldn't create a heading just for "ParkX Porter". I'll use "About the role" for the overview prose.
- **Responsibilities**: The "Key Responsibilities" section has many bullet points. I'll use `- ` for each. I need to preserve all substantive information, not summarize away detail. So I'll list each responsibility as a separate `
- `, but maybe group them? The rules say: Use
- for any list of duties/requirements/benefits. I'll make one `
` with all responsibility `- `s.
- **Requirements vs Qualifications**: The posting has "Qualifications" section and also mentions requirements throughout. The requested headings include "Requirements" and "Qualifications". I need to decide how to split. Looking at the text: "Qualifications" section lists: High School Diploma or Equivalent, Valid driver's license without major violations, Flexibility to work after hours and weekends for events, Outgoing personality..., Strong problem-solving, time management and communication skills, Must be highly credible and trustworthy..., Must hold oneself and others accountable..., Must have a positive, can-do attitude..., Must want to continuously learn and develop..., Exceptional oral communication, active listening, and organizational skills, Ability to establish strong working relationships..., Ability to multitask and prioritize tasks with strong attention to detail in a fast-paced environment, Self-directed and able to work independently, with minimal supervision.
There's also "Physical Demands & Work Environment" section which lists physical demands. That could be part of Requirements or Qualifications, or I could create a separate "Requirements" section that includes qualifications, physical demands, etc. The requested headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I need to map the content appropriately.
Let's re-read the rules: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It lists examples, not mandates that all must be present. "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text..." So I should only include sections that have real content. I need to check each:
- About the role: Yes, has content.
- Responsibilities: Yes, Key Responsibilities section.
- Requirements: The posting has qualifications and physical demands. I can combine or split. I'll likely make a "Requirements" section that includes qualifications, physical demands, and maybe skills. Or I can have separate "Qualifications" and "Skills" if there's distinct content. Looking at the text, "Qualifications" is a distinct section. "Physical Demands & Work Environment" is another. "Skills" might be covered in qualifications or responsibilities. The requested heading "Skills" could map to the skills listed in Qualifications. I'll see.
- Qualifications: Yes, explicit section.
- Skills: The qualifications list includes skills like problem-solving, communication, etc. I could either merge into Qualifications or make a separate Skills section. Since the rules say prefer a few substantive sections over many thin ones, I might combine skills into Qualifications, or make a brief Skills section if there's notable content beyond Qualifications. Let's examine: The Qualifications section already lists skills implicitly. I'll probably put what's clearly skills-relevant under Qualifications, or create a Skills section if there's extra. But the rules say don't create sections unless posting actually states them. "Qualifications" is explicitly stated. "Skills" as a heading might be redundant. I'll check if there's a separate "Skills" section - no. I'll likely omit "Skills" or fold into Qualifications. But the user listed "Skills" as an example heading. I need to decide based on content. The posting has "Strong problem-solving, time management and communication skills" etc. I can create a "Skills" section with those, but it might thin things out. I'll see later.
- Benefits: Yes, has "Benefits Compensation: Benefit Package: Medical, Dental, Vision, 401K Match, Life Insurance Career Development Opportunities for Advancement within our expanding portfolio Annual Professional Development Funds to fuel your growth Employee Perks (to name a few): Free Parking and EV charging Parental Leave Program Enjoy a Friendly Work Environment that values collaboration Note benefits vary depending on the function of your role". Also "The wage range listed for this position reflects..." and "Virginia Compensation Range: $19 USD - $19 USD". The rules: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Benefits section is stated. Pay range is stated ("Virginia Compensation Range: $19 USD - $19 USD"). Schedule? The posting mentions "Flexibility to work after hours and weekends for events", "Available for weekend and after-hours work, particularly during events or peak periods." But no explicit "Schedule" section with standard hours. I'll be careful: "Schedule" heading should only appear if there's real content. I can maybe fold schedule-related info into Benefits or a short paragraph, but the rule says never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits is clearly stated. Pay range is stated. Schedule? The posting mentions weekend/after-hours work, but no formal schedule description. I'll likely include Pay as a section (since it has specific range), Benefits as a section, and maybe not Schedule unless I can add meaningful content without filler. The rule: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". So if I can't fill Schedule meaningfully, I omit it.
- Pay: The posting has "Virginia Compensation Range: $19 USD - $19 USD" and discusses compensation factors. I can create a "Pay" section with that range, but must be careful not to add filler. The range is specific: "$19 USD - $19 USD". That's a single value essentially. I'll include it.
- Schedule: Not explicitly a section. I'll omit or fold into Benefits/Pay if needed, but better to omit since no clear schedule details.
Now, let's outline the HTML structure based on what I'll include:
Headings I'll use (only where content exists):
- About the role
(job overview prose)
- Responsibilities
(Key Responsibilities list)
- Qualifications
(Qualifications list)
- Benefits
(Benefits package, perks, compensation notes)
- Pay
(Virginia Compensation Range)
I won't include "Requirements" as a separate heading if I fold everything into Qualifications, or I could make a "Requirements" section that includes physical demands and qualifications. But the rules say "include a section ONLY when the posting has real, specific content for it". The posting has a "Qualifications" section and a "Physical Demands & Work Environment" section. I could combine them into one "Qualifications" section, or create "Requirements" and "Qualifications" separately. Let's see the requested headings: "Requirements, Qualifications, Skills". I think I'll make "Qualifications" contain the qualifications list, and maybe add a "Requirements" section that includes physical demands and other requirements. But that might duplicate. Let's re-read carefully: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." These are examples of valid headings. I don't have to use all. I'll use only those that have distinct, non-filler content.
Let's decide on final sections:
1. About the role - the job overview paragraph.
2. Responsibilities - the Key Responsibilities list.
3. Qualifications - the Qualifications list (including skills mentioned there).
4. Benefits - the Benefits section including perks, compensation notes, but I need to separate Pay? The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." Benefits is stated. Pay is stated separately as "Virginia Compensation Range". I could either make a Pay section or fold into Benefits. Since Pay has specific range, I'll make a separate "Pay" section. But I must ensure no filler. The range is "$19 USD - $19 USD". I'll put that in a
or as part of Pay section.
5. Pay - the compensation range.
What about "Skills"? The qualifications list includes skills. I could either include them in Qualifications or make a Skills section. Since Qualifications already lists them, and making a separate Skills section might be redundant/thin, I'll fold skills into Qualifications or just note they're part of qualifications. The rule: "Prefer a few substantive sections over many thin ones." So I'll likely have: About
` for prose. - Do NOT repeat job title as heading (already shown). - Do NOT put Job ID / requisition numbers as headings - fold minor metadata into short `
` or drop it. - Preserve ALL substantive information; do NOT invent or summarize away detail. - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. - IMPORTANT: Include a section ONLY when the posting has real, specific content for it — 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. - Prefer a few substantive sections over many thin ones. - Output ONLY the HTML fragment — no `/`, no markdown code fences. 2. **Analyze the Job Posting Text:** Let me parse the input text carefully. It's a job posting for "ParkX Porter". I need to extract relevant sections and structure them. Input text structure (roughly): - Job Overview: "The ParkX Porter is responsible for maintaining cleanliness..." - Key Responsibilities: bullet points (list of duties) - Qualifications: bullet points (list of requirements) - Benefits: section with text about compensation, benefits, etc. - Virginia Compensation Range: "$19 USD - $19 USD" I need to map these to the requested headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Let's identify content for each: - **About the role / Job Overview**: The first paragraph "The ParkX Porter is responsible for maintaining cleanliness in the common areas at assigned sites. Duties include general upkeep such as pressure washing, window cleaning, trash removal, and routine cleaning tasks. Porter also support event setup and cleanup when necessary and respond to cleanliness concerns as they arise. The position requires reliability, attention to detail, and the ability to work professionally and courteously with property staff, tenants, and visitors." This can go under "About the role" or similar. The rules say: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading (the page already shows it). So I shouldn't create a heading just for "ParkX Porter". I'll use "About the role" for the overview prose.
- **Responsibilities**: The "Key Responsibilities" section has many bullet points. I'll use `- ` for each. I need to preserve all substantive information, not summarize away detail. So I'll list each responsibility as a separate `
- `, but maybe group them? The rules say: Use
- for any list of duties/requirements/benefits. I'll make one `
` with all responsibility `- `s.
- **Requirements vs Qualifications**: The posting has "Qualifications" section and also mentions requirements throughout. The requested headings include "Requirements" and "Qualifications". I need to decide how to split. Looking at the text: "Qualifications" section lists: High School Diploma or Equivalent, Valid driver's license without major violations, Flexibility to work after hours and weekends for events, Outgoing personality..., Strong problem-solving, time management and communication skills, Must be highly credible and trustworthy..., Must hold oneself and others accountable..., Must have a positive, can-do attitude..., Must want to continuously learn and develop..., Exceptional oral communication, active listening, and organizational skills, Ability to establish strong working relationships..., Ability to multitask and prioritize tasks with strong attention to detail in a fast-paced environment, Self-directed and able to work independently, with minimal supervision.
There's also "Physical Demands & Work Environment" section which lists physical demands. That could be part of Requirements or Qualifications, or I could create a separate "Requirements" section that includes qualifications, physical demands, etc. The requested headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I need to map the content appropriately.
Let's re-read the rules: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It lists examples, not mandates that all must be present. "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text..." So I should only include sections that have real content. I need to check each:
- About the role: Yes, has content.
- Responsibilities: Yes, Key Responsibilities section.
- Requirements: The posting has qualifications and physical demands. I can combine or split. I'll likely make a "Requirements" section that includes qualifications, physical demands, and maybe skills. Or I can have separate "Qualifications" and "Skills" if there's distinct content. Looking at the text, "Qualifications" is a distinct section. "Physical Demands & Work Environment" is another. "Skills" might be covered in qualifications or responsibilities. The requested heading "Skills" could map to the skills listed in Qualifications. I'll see.
- Qualifications: Yes, explicit section.
- Skills: The qualifications list includes skills like problem-solving, communication, etc. I could either merge into Qualifications or make a separate Skills section. Since the rules say prefer a few substantive sections over many thin ones, I might combine skills into Qualifications, or make a brief Skills section if there's notable content beyond Qualifications. Let's examine: The Qualifications section already lists skills implicitly. I'll probably put what's clearly skills-relevant under Qualifications, or create a Skills section if there's extra. But the rules say don't create sections unless posting actually states them. "Qualifications" is explicitly stated. "Skills" as a heading might be redundant. I'll check if there's a separate "Skills" section - no. I'll likely omit "Skills" or fold into Qualifications. But the user listed "Skills" as an example heading. I need to decide based on content. The posting has "Strong problem-solving, time management and communication skills" etc. I can create a "Skills" section with those, but it might thin things out. I'll see later.
- Benefits: Yes, has "Benefits Compensation: Benefit Package: Medical, Dental, Vision, 401K Match, Life Insurance Career Development Opportunities for Advancement within our expanding portfolio Annual Professional Development Funds to fuel your growth Employee Perks (to name a few): Free Parking and EV charging Parental Leave Program Enjoy a Friendly Work Environment that values collaboration Note benefits vary depending on the function of your role". Also "The wage range listed for this position reflects..." and "Virginia Compensation Range: $19 USD - $19 USD". The rules: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Benefits section is stated. Pay range is stated ("Virginia Compensation Range: $19 USD - $19 USD"). Schedule? The posting mentions "Flexibility to work after hours and weekends for events", "Available for weekend and after-hours work, particularly during events or peak periods." But no explicit "Schedule" section with standard hours. I'll be careful: "Schedule" heading should only appear if there's real content. I can maybe fold schedule-related info into Benefits or a short paragraph, but the rule says never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits is clearly stated. Pay range is stated. Schedule? The posting mentions weekend/after-hours work, but no formal schedule description. I'll likely include Pay as a section (since it has specific range), Benefits as a section, and maybe not Schedule unless I can add meaningful content without filler. The rule: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". So if I can't fill Schedule meaningfully, I omit it.
- Pay: The posting has "Virginia Compensation Range: $19 USD - $19 USD" and discusses compensation factors. I can create a "Pay" section with that range, but must be careful not to add filler. The range is specific: "$19 USD - $19 USD". That's a single value essentially. I'll include it.
- Schedule: Not explicitly a section. I'll omit or fold into Benefits/Pay if needed, but better to omit since no clear schedule details.
Now, let's outline the HTML structure based on what I'll include:
Headings I'll use (only where content exists):
- About the role
(job overview prose)
- Responsibilities
(Key Responsibilities list)
- Qualifications
(Qualifications list)
- Benefits
(Benefits package, perks, compensation notes)
- Pay
(Virginia Compensation Range)
I won't include "Requirements" as a separate heading if I fold everything into Qualifications, or I could make a "Requirements" section that includes physical demands and qualifications. But the rules say "include a section ONLY when the posting has real, specific content for it". The posting has a "Qualifications" section and a "Physical Demands & Work Environment" section. I could combine them into one "Qualifications" section, or create "Requirements" and "Qualifications" separately. Let's see the requested headings: "Requirements, Qualifications, Skills". I think I'll make "Qualifications" contain the qualifications list, and maybe add a "Requirements" section that includes physical demands and other requirements. But that might duplicate. Let's re-read carefully: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." These are examples of valid headings. I don't have to use all. I'll use only those that have distinct, non-filler content.
Let's decide on final sections:
1. About the role - the job overview paragraph.
2. Responsibilities - the Key Responsibilities list.
3. Qualifications - the Qualifications list (including skills mentioned there).
4. Benefits - the Benefits section including perks, compensation notes, but I need to separate Pay? The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." Benefits is stated. Pay is stated separately as "Virginia Compensation Range". I could either make a Pay section or fold into Benefits. Since Pay has specific range, I'll make a separate "Pay" section. But I must ensure no filler. The range is "$19 USD - $19 USD". I'll put that in a
or as part of Pay section.
5. Pay - the compensation range.
What about "Skills"? The qualifications list includes skills. I could either include them in Qualifications or make a Skills section. Since Qualifications already lists them, and making a separate Skills section might be redundant/thin, I'll fold skills into Qualifications or just note they're part of qualifications. The rule: "Prefer a few substantive sections over many thin ones." So I'll likely have: About
- for any list of duties/requirements/benefits. I'll make one `
- ` with all responsibility `
- `s.
- **Requirements vs Qualifications**: The posting has "Qualifications" section and also mentions requirements throughout. The requested headings include "Requirements" and "Qualifications". I need to decide how to split. Looking at the text: "Qualifications" section lists: High School Diploma or Equivalent, Valid driver's license without major violations, Flexibility to work after hours and weekends for events, Outgoing personality..., Strong problem-solving, time management and communication skills, Must be highly credible and trustworthy..., Must hold oneself and others accountable..., Must have a positive, can-do attitude..., Must want to continuously learn and develop..., Exceptional oral communication, active listening, and organizational skills, Ability to establish strong working relationships..., Ability to multitask and prioritize tasks with strong attention to detail in a fast-paced environment, Self-directed and able to work independently, with minimal supervision.
There's also "Physical Demands & Work Environment" section which lists physical demands. That could be part of Requirements or Qualifications, or I could create a separate "Requirements" section that includes qualifications, physical demands, etc. The requested headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I need to map the content appropriately.
Let's re-read the rules: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It lists examples, not mandates that all must be present. "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text..." So I should only include sections that have real content. I need to check each: - About the role: Yes, has content. - Responsibilities: Yes, Key Responsibilities section. - Requirements: The posting has qualifications and physical demands. I can combine or split. I'll likely make a "Requirements" section that includes qualifications, physical demands, and maybe skills. Or I can have separate "Qualifications" and "Skills" if there's distinct content. Looking at the text, "Qualifications" is a distinct section. "Physical Demands & Work Environment" is another. "Skills" might be covered in qualifications or responsibilities. The requested heading "Skills" could map to the skills listed in Qualifications. I'll see. - Qualifications: Yes, explicit section. - Skills: The qualifications list includes skills like problem-solving, communication, etc. I could either merge into Qualifications or make a separate Skills section. Since the rules say prefer a few substantive sections over many thin ones, I might combine skills into Qualifications, or make a brief Skills section if there's notable content beyond Qualifications. Let's examine: The Qualifications section already lists skills implicitly. I'll probably put what's clearly skills-relevant under Qualifications, or create a Skills section if there's extra. But the rules say don't create sections unless posting actually states them. "Qualifications" is explicitly stated. "Skills" as a heading might be redundant. I'll check if there's a separate "Skills" section - no. I'll likely omit "Skills" or fold into Qualifications. But the user listed "Skills" as an example heading. I need to decide based on content. The posting has "Strong problem-solving, time management and communication skills" etc. I can create a "Skills" section with those, but it might thin things out. I'll see later. - Benefits: Yes, has "Benefits Compensation: Benefit Package: Medical, Dental, Vision, 401K Match, Life Insurance Career Development Opportunities for Advancement within our expanding portfolio Annual Professional Development Funds to fuel your growth Employee Perks (to name a few): Free Parking and EV charging Parental Leave Program Enjoy a Friendly Work Environment that values collaboration Note benefits vary depending on the function of your role". Also "The wage range listed for this position reflects..." and "Virginia Compensation Range: $19 USD - $19 USD". The rules: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Benefits section is stated. Pay range is stated ("Virginia Compensation Range: $19 USD - $19 USD"). Schedule? The posting mentions "Flexibility to work after hours and weekends for events", "Available for weekend and after-hours work, particularly during events or peak periods." But no explicit "Schedule" section with standard hours. I'll be careful: "Schedule" heading should only appear if there's real content. I can maybe fold schedule-related info into Benefits or a short paragraph, but the rule says never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits is clearly stated. Pay range is stated. Schedule? The posting mentions weekend/after-hours work, but no formal schedule description. I'll likely include Pay as a section (since it has specific range), Benefits as a section, and maybe not Schedule unless I can add meaningful content without filler. The rule: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". So if I can't fill Schedule meaningfully, I omit it. - Pay: The posting has "Virginia Compensation Range: $19 USD - $19 USD" and discusses compensation factors. I can create a "Pay" section with that range, but must be careful not to add filler. The range is specific: "$19 USD - $19 USD". That's a single value essentially. I'll include it. - Schedule: Not explicitly a section. I'll omit or fold into Benefits/Pay if needed, but better to omit since no clear schedule details. Now, let's outline the HTML structure based on what I'll include: Headings I'll use (only where content exists): -
About the role
(job overview prose) -Responsibilities
(Key Responsibilities list) -Qualifications
(Qualifications list) -Benefits
(Benefits package, perks, compensation notes) -Pay
(Virginia Compensation Range) I won't include "Requirements" as a separate heading if I fold everything into Qualifications, or I could make a "Requirements" section that includes physical demands and qualifications. But the rules say "include a section ONLY when the posting has real, specific content for it". The posting has a "Qualifications" section and a "Physical Demands & Work Environment" section. I could combine them into one "Qualifications" section, or create "Requirements" and "Qualifications" separately. Let's see the requested headings: "Requirements, Qualifications, Skills". I think I'll make "Qualifications" contain the qualifications list, and maybe add a "Requirements" section that includes physical demands and other requirements. But that might duplicate. Let's re-read carefully: "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." These are examples of valid headings. I don't have to use all. I'll use only those that have distinct, non-filler content. Let's decide on final sections: 1. About the role - the job overview paragraph. 2. Responsibilities - the Key Responsibilities list. 3. Qualifications - the Qualifications list (including skills mentioned there). 4. Benefits - the Benefits section including perks, compensation notes, but I need to separate Pay? The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." Benefits is stated. Pay is stated separately as "Virginia Compensation Range". I could either make a Pay section or fold into Benefits. Since Pay has specific range, I'll make a separate "Pay" section. But I must ensure no filler. The range is "$19 USD - $19 USD". I'll put that in a
or as part of Pay section. 5. Pay - the compensation range. What about "Skills"? The qualifications list includes skills. I could either include them in Qualifications or make a Skills section. Since Qualifications already lists them, and making a separate Skills section might be redundant/thin, I'll fold skills into Qualifications or just note they're part of qualifications. The rule: "Prefer a few substantive sections over many thin ones." So I'll likely have: About
- `s.
- **Requirements vs Qualifications**: The posting has "Qualifications" section and also mentions requirements throughout. The requested headings include "Requirements" and "Qualifications". I need to decide how to split. Looking at the text: "Qualifications" section lists: High School Diploma or Equivalent, Valid driver's license without major violations, Flexibility to work after hours and weekends for events, Outgoing personality..., Strong problem-solving, time management and communication skills, Must be highly credible and trustworthy..., Must hold oneself and others accountable..., Must have a positive, can-do attitude..., Must want to continuously learn and develop..., Exceptional oral communication, active listening, and organizational skills, Ability to establish strong working relationships..., Ability to multitask and prioritize tasks with strong attention to detail in a fast-paced environment, Self-directed and able to work independently, with minimal supervision.
There's also "Physical Demands & Work Environment" section which lists physical demands. That could be part of Requirements or Qualifications, or I could create a separate "Requirements" section that includes qualifications, physical demands, etc. The requested headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I need to map the content appropriately.
Let's re-read the rules: "use