Front Desk - Sprinker Recreation Center - Temporary

The user wants me to reformat a job posting into clean semantic HTML. Let me analyze the content and structure it according to the rules. First, I need to identify the sections: - About the role / Summary (the "Why It's a Great Opportunity" and "Why It's a Great Department" sections) - Responsibilities (Core Daily Responsibilities) - Requirements / Qualifications (Minimum Qualifications, Preferred Qualifications) - Additional info: background check, application process, etc. but these are boilerplate/instructions to remove Rules: - Use

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 - Do NOT put Job ID/requisition numbers as headings - Fold minor metadata into short

  or drop - 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 - 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, let's parse the content: The posting starts with "Description This position is in-officeSome of these opportunities may be up to 40 hours per week for up to 5 months of employment, while others may provide part-time coverage for less than 70 hours per monthShifts vary between 6:45 am and 10 pm, Monday to Sunday, and during the holidaysThese temporary positions are not eligible for County benefits" This is metadata about schedule, hours, benefits eligibility. It's substantive: it describes the nature of the position (temporary, in-office, hours, shifts, no benefits). This could go under a "Schedule" or "About the role" section. Since there's no explicit "Schedule" heading in the posting, but it does state schedule details, I could include a Schedule section. However, the rule says never create Schedule section unless posting actually states them. It does state shifts and hours. But also says "These temporary positions are not eligible for County benefits" - that's benefits info. Could create a Benefits section? But it says not eligible for County benefits. That's specific. However, the rule says never create Benefits section unless posting actually states them. It does state benefits (not eligible). But is that considered "stating benefits"? It's stating lack of benefits. Might be worth including as a note in About the role. Better to fold into a short

  in About the role. Next: "Summary Why It's a Great Opportunity: We are looking for a self-motivated and team player Front Desk staff to join our team at Sprinker Recreation Center. You will provide a high level of customer service to the public in an energetic and fast-paced environment. Why It's a Great Department Pierce County Parks and Recreation manages more than 5,200 acres of parks, trails, and open space, ranging from community hubs to natural areas. We deliver diverse recreation programs and maintain the infrastructure that supports both active play and quiet connection with nature. Our department is made up of four divisions: Park and Recreation Operations, Business Operations, Volunteer and Resource Development, and Park Stewardship and Infrastructure Delivery, working together to serve one of the most dynamic and fast-growing regions in Washington. Guided by our mission to create livable communities, we provide opportunities for people to connect with nature, learn about sustainability, live healthy lives, and experience inclusive, thriving public spaces. Joining Pierce County Parks means being part of a forward-thinking team that values collaboration, innovation, and community impact, where your work truly makes a difference every day. Learn more about the Pierce County Parks and Recreation Department" This is descriptive prose about the role and department. Good for "About the role" section. Next: "Core Daily Responsibilities Greeting customers and providing assistance via email, phone, and in personAssisting with program registrationsPark Shelter and Field RentalsOperate point of sale system and accurately process paymentsMulti-line phonesAiding in the security of the facilityWork with little or no supervision in a self-motivated manner" This is a list of responsibilities. Should be

  • under Responsibilities heading. Next: "Minimum Qualifications Minimum 18 years of ageHigh School diploma or GEDAbility to work flexible hours, including evenings and weekends" List of minimum qualifications. Next: "Preferred Qualifications Previous cash handling experience is highly desiredCustomer service-related workKnowledge of Microsoft products" List of preferred qualifications. Next: "As a condition of employment, the applicant will need to authorize and complete a background check. Information received from the background check is reviewed case-by-case and will not necessarily remove an applicant from consideration." This is a condition, could be part of Requirements or a separate note. Might fold into Requirements section as a paragraph. Next: "Supplemental Information How To Apply Complete and submit a detailed online Pierce County Employment Application by selecting “APPLY” above or visiting www.piercecountywa.gov/jobs .If you have questions about this opportunity, email the Recruitment Team at PCHRRecruit@piercecountywa.gov and include the job number and title.Individuals who need accommodation in the application or interview process may contact Human Resources at (253) 798-7480 at least two days prior to the need.Applicants must be legally authorized to work in the United States without the need for visa sponsorship." This is application instructions, boilerplate. Remove. Next: "Our Recruitment Practices This is a competitive and meritorious selection process. Pierce County applications are reviewed by human hiring staff in accordance with the qualifications listed for the position. Pierce County understands applicants may use AI tools when preparing application materials. We recognize these tools can make the process easier; however, we ask that everything you submit genuinely reflects your own experience, skills, knowledge, and writing style. During the interview process, you may be asked to demonstrate your skills, including writing and subject knowledge, and to speak to your experience in your own voice. Applicants should be prepared to respond to interview questions without relying on AI-generated responses or reading prepared answers from a screen. Any misrepresentation may result in disqualification or separation. Applicants whose qualifications most closely align with the County’s needs will be eligible for further consideration. Notification of application status typically occurs within two to three weeks after the closing date. Some applicants may receive short notice to participate in additional selection steps, which may include assessments, phone screens, or interviews. Upon offer, compensation is based on a range of job-related factors, including the requirements of the role, your skills and experience, and internal pay equity." This is recruitment practices, compensation mention but no specific pay range. It says "compensation is based on a range of job-related factors..." but no actual pay numbers. This is boilerplate. Remove. Next: "Our Welcoming Workplace Commitment Pierce County is committed to fostering a Welcoming Workplace where employees are supported, respected, and able to thrive. We believe a strong public workforce is representative of the community it serves and that fair and just access to opportunity strengthens public service. Guided by the County Executive’s Forward Together mission, Pierce County works to build communities that are safe, welcoming, and connected. This same commitment shapes how we recruit, develop, and retain our employees. County employees make a direct and visible impact in the lives of residents every day, and we invite you to join us in helping keep Pierce County a place people are proud to call home. We are unable to sponsor or take over sponsorship of an employment visa at this time." EEO/welcoming workplace boilerplate. Remove. Thus, the substantive sections are: 1. About the role (including summary, department description, and the initial description about hours/shifts/benefits) 2. Responsibilities 3. Requirements (Minimum Qualifications) 4. Preferred Qualifications (could be under Requirements or separate Qualifications section) The rules mention headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I should use those exact headings where appropriate. I'll create: -

    About the role

    with prose paragraphs covering the summary, department description, and the initial description (in-office, hours, shifts, temporary, no benefits). -

    Responsibilities

    with
    • for each duty. -

      Requirements

      with
      • for minimum qualifications, and maybe a paragraph for background check. -

        Qualifications

        for preferred qualifications? Or combine with Requirements? The rules list both Requirements and Qualifications as possible headings. Since there are both minimum and preferred, I could have Requirements for minimum, and Qualifications for preferred. But the rule says "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I can use both. Alternatively, I could have a single "Requirements" section with two sublists: Minimum and Preferred. But the rule says use

        for section headings. It doesn't forbid subheadings, but we should keep it simple. I'll do two sections: Requirements (minimum) and Qualifications (preferred). However, "Qualifications" might be ambiguous. The posting says "Minimum Qualifications" and "Preferred Qualifications". I'll use "Requirements" for minimum, and "Preferred qualifications" as a subsection? But the rule says only

        for headings. Could do

        Requirements

        then a paragraph "Minimum qualifications:" then list, then "Preferred qualifications:" then list. That's fine. But the rule says "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say we must use all, only those that have content. I think having two sections: Requirements and Qualifications is okay. However, "Qualifications" might be considered same as Requirements. I'll combine into one Requirements section with two lists. Let's see: The posting has "Minimum Qualifications" and "Preferred Qualifications". I'll create a "Requirements" heading, then a paragraph "Minimum qualifications:" then

        for those, then a paragraph "Preferred qualifications:" then
        for those. That's clean. Also, the background check condition: I'll add a paragraph after the lists. Now, the initial description: "This position is in-office Some of these opportunities may be up to 40 hours per week for up to 5 months of employment, while others may provide part-time coverage for less than 70 hours per month Shifts vary between 6:45 am and 10 pm, Monday to Sunday, and during the holidays These temporary positions are not eligible for County benefits" This is specific info about schedule, duration, benefits. Could be a "Schedule" section? The rule says never create Schedule section unless posting actually states them. It does state shifts and hours. But also says "temporary positions not eligible for County benefits". That's benefits. Could create a "Schedule" section with the hours/shifts/duration, and a "Benefits" section with "not eligible for County benefits". However, the rule says never create Benefits section unless posting actually states them. It does state benefits (ineligibility). But is that considered stating benefits? It's stating lack of benefits. Might be better to include in About the role as a paragraph. I'll include in About the role as a paragraph summarizing the nature of the position. Now, let's write the HTML. Structure:

        About the role

        This position is in-office. Some opportunities may be up to 40 hours per week for up to 5 months of employment