Landscape - Seasonal

We need to output HTML fragment with sections for headings where there is real content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. From posting: - Position Title: Landscape - Seasonal (but we should not repeat job title as heading). So we can maybe include a short paragraph with position info? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a

with position info like "Position Title: Landscape - Seasonal, Requisition Number H00214P, Hourly/Work Study, Campus Location: Weber State University - Ogden, UT". But we need to preserve all substantive information. However we must remove boilerplate like EEO, navigation, legal, etc. The first paragraph about WSU's Commitment to Equal Opportunity is boilerplate EEO; we should remove it. Also "Notes to Applicant" includes application instructions; we should remove application instructions. Also "Posting Detail Information" includes dates etc; we might keep some metadata? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a short paragraph with position info (title, requisition, category, location). Also maybe include schedule info: "Hours per week: 40 hours a week (seasonal position)" and "Alternate work schedule 6am-3:30pm". That is schedule info, so we can create a Schedule section with

Schedule

and then

• ... maybe just a

  because it's not a list? The rule: Use

  • for any list of duties/requirements/benefits, and

    for prose. So schedule can be prose

    . Pay: we have Pay Grade Salary Hourly Pay Rate $13.00. So we can create Pay section with

    Pay

    and

    Hourly Pay Rate: $13.00

    . Benefits: none mentioned. So we should not create Benefits section. Responsibilities: we have "Experience with weeding, mulching, planting, pruning, trash removal, and other duties are necessary to be a successful member of the Landscape Department." Also "This is a 40 hour a week seasonal position The Landscape Department is responsible for all WSU landscaping." Could treat responsibilities as list: weeding, mulching, planting, pruning, trash removal, other duties. So we can create Responsibilities section with
    • Weeding
    etc. Also maybe include "The Landscape Department is responsible for all WSU landscaping." as a prose

    before list? But we can incorporate as list item. Requirements: "Required Qualifications Experience with weeding, mulching, planting, pruning, and trash removal. Basic Computer Skills." That's similar to responsibilities but it's required qualifications. Could be Requirements section. Preferred Qualifications: "High school diploma or equivalent. A valid Utah Driver License." That's qualifications. Skills: maybe "Basic Computer Skills." Could be Skills section. But we need to avoid duplication. Let's think: We have Required Qualifications (experience with weeding, mulching, planting, pruning, trash removal; basic computer skills). Preferred Qualifications (high school diploma or equivalent; valid Utah driver license). We could combine into Requirements section with subpoints? But instruction: Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have separate headings for Requirements, Qualifications, Skills. We need to decide what goes where. We could map: - About the role: maybe a brief description: "This is a 40 hour a week seasonal position. The Landscape Department is responsible for all WSU landscaping." That's about the role. - Responsibilities: list of duties: weeding, mulching, planting, pruning, trash removal, other duties. - Requirements: maybe "Experience with weeding, mulching, planting, pruning, and trash removal. Basic Computer Skills." (these are required qualifications). Could also include "High school diploma or equivalent. A valid Utah Driver License." as preferred qualifications but maybe put under Qualifications. - Qualifications: maybe "High school diploma or equivalent. A valid Utah Driver License." - Skills: maybe "Basic Computer Skills." (though that could be under Requirements). But we can still include. We must not create sections with filler like "commensurate with experience". We have actual content for each. Pay: we have hourly pay rate $13.00. Schedule: we have "Alternate work schedule 6am-3:30pm 40 hours a week (seasonal position)". So schedule section. We should not include Benefits as none. We should not include Job ID etc as headings; we can put them in a short

    at top maybe. We must remove boilerplate: EEO commitment, notes to applicant (application instructions), posting detail information (dates, open until filled, quick link). Also remove "Background Check? No". That's maybe minor metadata; we could fold into a short p? But it's not heading. Could include in a short paragraph under "About the role"? Might be considered metadata. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. So we can include a short paragraph with position title, requisition number, category, location, maybe background check? But background check is a yes/no; we could include. Let's craft:

    Position Title: Landscape - Seasonal
    Requisition Number: H00214P
    Position Category: Hourly/Work Study
    Campus Location: Weber State University - Ogden, UT
    Background Check: No

    But we should avoid using ? Not prohibited. The instruction only about headings and lists. Using is fine. Could also just plain text. Now sections:

    About the role

    This is a 40 hour a week seasonal position. The Landscape Department is responsible for all WSU landscaping.

    Responsibilities

    • Weeding
    • Mulching
    • Planting
    • Pruning
    • Trash removal
    • Other duties as needed

    Requirements

    Experience with weeding, mulching, planting, pruning, and trash removal. Basic computer skills.

    Qualifications

    • High school diploma or equivalent
    • Valid Utah driver license

    Skills

    Basic computer skills

    Pay

    Hourly pay rate: $13.00

    Schedule

    Alternate work schedule: 6am‑3:30pm, 40 hours per week (seasonal position)

    We have duplicated basic computer skills in Requirements and Skills; maybe we should avoid duplication. Could move basic computer skills to Skills only, and Requirements just experience. But Required Qualifications includes both experience and basic computer skills. We could keep Requirements as experience only, and Skills as basic computer skills. Let's adjust: Requirements: Experience with weeding, mulching, planting, pruning, and trash removal. Skills: Basic computer skills. Qualifications: High school diploma or equivalent; Valid Utah driver license. That avoids duplication. Now check if any other content: "Experience with weeding, mulching, planting, pruning, trash removal, and other duties are necessary to be a successful member of the Landscape Department." That's responsibilities. Already captured. Now ensure we didn't miss any substantive info: "This is a 40 hour a week seasonal position" included in About the role. "The Landscape Department is responsible for all WSU landscaping." included. "Alternate work schedule 6am-3:30pm 40 hours a week (seasonal position)" captured in Schedule. "Pay Grade Salary Hourly Pay Rate $13.00" captured. "Background Check? No" we included in metadata paragraph. "Job Open Date 03/12/2026 Review Date 03/14/2026 Job Close Date 10/12/2026 Open Until Filled Quick Link for Direct Access to Posting https://jobs.weber.edu/postings/4190" - we removed as per instruction (application instructions, posting detail). Should we keep any of that? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The dates and quick link are part of posting detail; not explicitly prohibited but likely considered metadata; but we could fold minor metadata into a short p or drop it. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. So we could include a short paragraph with those dates maybe. However they said "minor metadata". The dates could be considered minor metadata. But we already have a short paragraph for position info; we could add the dates there. However the instruction also says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The dates are not exactly those; they are posting detail. Might be okay to keep them as minor metadata in a short p. But we need to be careful not to create a heading for them. We'll just add them to the metadata paragraph. Let's create metadata paragraph:

    Position Title: Landscape - Seasonal
    Requisition Number: H00214P
    Position Category: Hourly/Work Study
    Campus Location: Weber State University - Ogden, UT
    Background Check: No
    Open Date: 03/12/2026
    Review Date: 03/14/2026
    Close Date: 10/12/2026

    That seems okay. Now ensure we didn't include any boilerplate like "We strive to create a culture where everyone feels valued and appreciated." That's EEO; removed. Now output only HTML fragment. Let's craft final HTML:

    Position Title: Landscape - Seasonal
    Requisition Number: H00214P
    Position Category: Hourly/Work Study
    Campus Location: Weber State University - Ogden, UT
    Background Check: No
    Open Date: 03/12/2026
    Review Date: 03/14/2026
    Close Date: 10/12/2026

    About the role

    This is a 40 hour a week seasonal position. The Landscape Department is responsible for all WSU landscaping.

    Responsibilities

    • Weeding
    • Mulching
    • Planting
    • Pruning
    • Trash removal
    • Other duties as needed