Jobs · Project Management · California

PM Special Projects Housekeeping

Marriott International · Dana Point, CA · 1 mo ago
On-siteProject Management$29.9/hrPart-time
We need to output HTML fragment with sections: h3 headings for sections present. We must not repeat job title. We need to include sections only if posting has real specific content. Let's parse the posting. We have: Additional Information (metadata) - Job Number, Job Category, Location, Schedule, Located Remotely?, Position Type, Pay Range. We should fold minor metadata into a short

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 can include a

with maybe location, schedule, pay range? But we need to preserve ALL substantive information. The substantive info includes location, schedule, pay range, position type, etc. However they say we can fold minor metadata into a short

or drop it. Likely we should include a short paragraph summarizing metadata: location, schedule, pay range, position type. But we must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting does state Pay Range: $29.90-$29.90 per hour (so a specific pay). It also states Schedule: Part Time. So we could include a Pay section and Schedule section? The instruction: "Prefer a few substantive sections over many thin ones." Also: "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." Since posting does state Pay Range and Schedule, we could create those sections. However they also say "Prefer a few substantive sections over many thin ones." Might be better to combine Pay and Schedule into a single "Details" section? But they gave examples of section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could use Pay and Schedule sections if we have content. We also have Position Summary (a paragraph). Then a list of duties/responsibilities (many bullet-like sentences). Then "PREFERRED QUALIFICATION" with sub-bullets: Education, Related Work Experience, Supervisory Experience, License or Certification. Then there is a lot of boilerplate about EEO etc which we should remove. Also there is a paragraph about Marriott International etc which is likely boilerplate but contains some substantive content about Gold Standards etc. Might be considered fluff but it's part of the posting describing culture. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The Marriott paragraph about culture might be considered boilerplate? It's not EEO but it's generic corporate fluff. Might be considered boilerplate? Not sure. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. It doesn't say remove all corporate fluff. However we should preserve ALL substantive information; do NOT invent or summarize away detail. The Marriott paragraph is substantive? It's more marketing. Might be considered not essential but still part of posting. However we might keep it as part of "About the role" or similar. But we need to decide. We have a "POSITION SUMMARY" paragraph: "Respond promptly to requests from guests and other departments...." Actually that's a list of duties. Wait the POSITION SUMMARY seems to be a long paragraph that includes many duties. Then after that there is "PREFERRED QUALIFICATION" list. Thus we could structure:

About the role

... (maybe the POSITION SUMMARY paragraph? Actually the POSITION SUMMARY is a paragraph describing duties; but we also have a list of duties later. Might be redundant. The POSITION SUMMARY is essentially a summary of responsibilities. We could treat that as About the role. Then

Responsibilities

with
  • each duty from the list after POSITION SUMMARY? Actually the POSITION SUMMARY already includes many duties; but we can still list them. Better: Use POSITION SUMMARY as About the role (a paragraph). Then Responsibilities as a list of the detailed duties (the bullet-like sentences after POSITION SUMMARY). Then Requirements/Qualifications: we have PREFERRED QUALIFICATION list (Education, etc). Could treat as Requirements. We also have Pay Range and Schedule. Could create

    Pay

    $29.90 per hour

    and

    Schedule

    Part Time

    . Or combine. We also have Location: could be in a metadata paragraph. We must not repeat job title. No headings for Job ID etc. We must output only HTML fragment. Let's extract details: Location: 1 Ritz Carlton Dr, Dana Point, California, United States, 92629 Schedule: Part Time Located Remotely?: N (No) Position Type: Non-Management Pay Range: $29.90-$29.90 per hour (so $29.90 per hour) Now the POSITION SUMMARY text: "Respond promptly to requests from guests and other departments. Fill cart with supplies and transport cart to assigned area. Enter guest rooms following procedures for gaining access and ensuring vacancy before entering. Replace guest amenities and supplies in rooms. Replace dirty linens and terry with clean items. Make beds and fold terry. Clean bathrooms. Remove trash, dirty linen, and room service items. Check that all appliances are present in the room and in working order. Straighten desk items, furniture, and appliances. Dust, polish, and remove marks from walls and furnishings. Vacuum carpets and performs floor care duties (e.g., in guest rooms and hallway). Follow all company and safety and security policies and procedures; report any maintenance problems, safety hazards, accidents, or injuries; complete safety training and certifications; properly store flammable materials. Ensure uniform and personal appearance are clean and professional; maintain confidentiality of proprietary information. Welcome and acknowledge all guests according to company standards; anticipate and address guests’ service needs; assist individuals with disabilities; thank guests with genuine appreciation. Speak with others using clear and professional language. Support team to reach common goals. Ensure adherence to quality expectations and standards. Move, lift, carry, and place objects weighing less than or equal to 25 pounds without assistance and in excess of 25 pounds with assistance. Ability to push and pull a loaded housekeeping cart and other work-related equipment over sloping and uneven surfaces. Reach overhead and below the knees, including bending, twisting, pulling, and stooping. Stand, sit, kneel, or walk for an extended period across an entire work shift. Grasp, turn, and manipulate objects of varying size and weight, requiring fine motor skills and hand-eye coordination. Perform other reasonable job duties as requested by Supervisors." That is a long sentence with many duties separated by periods. We could split into list items each sentence. Then PREFERRED QUALIFICATION: Education: No high school diploma or G.E.D. equivalent. Related Work Experience: No related work experience. Supervisory Experience: No supervisory experience. License or Certification: None Thus requirements: basically none required. We could still list them. Now the Marriott fluff paragraph: Starting "At Marriott International, we are dedicated to being an equal opportunity employer..." This is EEO boilerplate; we should remove it. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. So we should cut that paragraph. Also the subsequent paragraph about "At more than 100 award-winning properties worldwide..." is also corporate fluff but not EEO. Might be considered boilerplate? It's not explicitly listed to remove, but it's generic marketing. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. This paragraph is substantive? It's more about company culture. Might be considered not essential but still part of posting. However it's likely considered boilerplate as well. Safer to remove it? The instruction only explicitly mentions cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not say to remove generic corporate fluff. So we should keep it? But it's not substantive to the role; it's more about the company. However the instruction says "Prefer a few substantive sections over many thin ones." If we include that fluff, we might create a thin section. Better to omit it as it's not directly about the role. But we risk violating "Preserve ALL substantive information". Is that fluff substantive? It's not about the job duties or requirements; it's about company values. Might be considered not substantive for the job posting. I'd lean to remove it, as it's not essential to the role and could be considered boilerplate. However it's not EEO. The safe approach: keep it as a short paragraph under "About the role" maybe. But we already have About the role from POSITION SUMMARY. Adding more may be redundant. Given the instruction to prefer few substantive sections, I'd keep About the role (POSITION SUMMARY) and Responsibilities (list). Then Requirements (preferred qualification). Then Pay and Schedule maybe as separate sections or combined. Let's decide to include Pay and Schedule sections. Now we need to output HTML fragment only. Structure:

    Location: 1 Ritz Carlton Dr, Dana Point, CA 92629. Position Type: Non‑Management. Schedule: Part Time. Pay: $29.90 per hour.

    Then

    About the role

    [POSITION SUMMARY text]

    Then

    Responsibilities

    • ... each sentence as li
    Then

    Requirements

    • Education: No high school diploma or G.E.D. equivalent.
    • Related Work Experience: No related work experience.
    • Supervisory Experience: No supervisory experience.
    • License or Certification: None
    Optionally

    Pay

    $29.90 per hour

    and

    Schedule

    Part Time

    . But we already included pay and schedule in metadata paragraph; maybe we shouldn't duplicate. Better to keep metadata paragraph and not create separate Pay/Schedule sections to avoid thin sections. The instruction says prefer few substantive sections over many thin ones. So we can omit separate Pay/Schedule sections and just include them in metadata paragraph. Thus final sections: About the role, Responsibilities, Requirements. We need to ensure we don't repeat job title. No headings for Job ID etc. Now we need to split POSITION SUMMARY into a paragraph (maybe keep as is). It's long but okay. Now responsibilities list: we need to extract each duty sentence from after POSITION SUMMARY? Actually the POSITION SUMMARY already contains all those duties. If we make About the role as that paragraph, then Responsibilities could be a list of the same duties but that would duplicate. Better to treat About the role as a brief summary (maybe first sentence?) but we don't have a separate summary. The POSITION SUMMARY is essentially a list of duties. So we could make About the role as a short paragraph summarizing the role (maybe we can write a brief summary ourselves? But we cannot invent or summarize away detail. We must preserve ALL substantive information; we cannot invent or summarize away detail. Summarizing would be summarizing away detail, which is not allowed. So we cannot create a summary that omits details. We must keep all details. So we need to keep the full list of duties somewhere. We could keep them as a list under Responsibilities, and not have an About the role section (or have a very short About the role that just says "Housekeeping & Laundry Associate" but that's repeating job title? Not allowed). Better

Similar jobs

PM Housekeeping

Marcus Hotels & ResortsPittsburgh, PA· 2 days ago
Managementapply on hotels.marcuscareers.com