Manager, Retail
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists,
for prose
- Do NOT repeat job title as heading (page already shows it)
- 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
- Include a section ONLY when posting has real, specific content for it — 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 a few substantive sections over many thin ones
- Output ONLY HTML fragment — no /, no markdown code fences
Now, let's map the content to appropriate sections:
The job title is "OKANA Candy Co. Manager" - I should not repeat this as heading.
The posting has:
- Summary/About the role: "What you will have an opportunity to do" paragraph
- Qualifications: list of minimum qualifications
- Performance Standards: list of standards (Customer Service, People Management, Quality, Financial, Managing the Business)
- Essential Functions: list of duties
- Physical Requirements: detailed list
- Use of Senses: detailed list
- Mental Requirements: detailed list
- Environmental Setting: detailed list
- Compensation: mentions "Compensation $ $" and then a paragraph about actual compensation packages based on factors
I need to decide which sections to include. The rules say use standard headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But also "include a section ONLY when the posting has real, specific content for it".
The posting has:
- Summary/About the role: yes, substantive paragraph
- Qualifications: yes, specific list
- Responsibilities: could combine Performance Standards and Essential Functions? Or separate? Performance Standards are more like expectations, Essential Functions are duties. Might combine under "Responsibilities" or have separate "Performance Standards" and "Essential Functions". The rules mention "Responsibilities" as a heading example. I think I'll create "Responsibilities" for Essential Functions, and maybe "Performance Standards" as a separate section since it's detailed.
- Physical Requirements, Use of Senses, Mental Requirements, Environmental Setting: these are very detailed and specific. They could be under "Requirements" or separate sections. The rules mention "Requirements" as a heading example. But these are very specific physical/mental/environmental requirements. I could create a "Physical Requirements" section, "Mental Requirements" section, etc. However, the rules say "Prefer a few substantive sections over many thin ones." But these are quite substantive with many items. I think I'll include them as separate sections because they are detailed and specific to this job.
- Compensation: the posting says "Compensation $ $" and then a paragraph. That's a Pay section. The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state compensation, albeit vaguely. But it does have a paragraph about compensation packages. I'll include a "Pay" section with that paragraph.
- Benefits: not mentioned specifically, so no Benefits section.
- Schedule: mentioned "Flexible schedule availability, including evenings, weekends, and holidays." That's in Qualifications. Could be a Schedule section but it's brief. Might fold into Qualifications or a separate Schedule section. The rules say never create Schedule unless posting actually states them. It does state schedule availability. I could include a "Schedule" section with that info.
- The "What are we looking for?" heading appears but then just "Compensation $ $". That seems like a placeholder. I'll ignore that heading.
- The EEO statement is boilerplate, remove.
- The job ID "#BMC-Okana" is minor metadata, fold into a short
or drop. I'll drop it.
- The company and property overviews are background, not job-specific. The rules say "Preserve ALL substantive information". But they are not about the role per se. However, they provide context. The rules don't explicitly say to remove company description, but they say "Reformat a job posting into clean, well-structured semantic HTML." The job posting includes that info. I think I should include it as an "About the Company" or "About the Property" section? The rules mention "About the role" as a heading example. Not "About the Company". But the posting has "About Our Property". I could include that as a section. However, the rules say "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." It doesn't forbid company description. But the example headings are job-specific: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Company description might be considered boilerplate? But it's part of the posting. I'll include it as a "About the Company" section? But the rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says "e.g.", so other headings are allowed. However, "Prefer a few substantive sections over many thin ones." The company description is substantive. I'll include it as "About the Company" and "About the Property" maybe combined.
But the user might expect only job-specific sections. Let's see the instruction: "Reformat a job posting into clean, well-structured semantic HTML." The entire posting is provided. I should include all substantive content. The company and property descriptions are part of the posting. I'll include them.
Now, structure:
1. About the Company (Pyramid Global Hospitality)
2. About the Property (OKANA Resort)
3. About the Role (Summary)
4. Qualifications
5. Performance Standards
6. Responsibilities (Essential Functions)
7. Physical Requirements
8. Use of Senses
9. Mental Requirements
10. Environmental Setting
11. Pay (Compensation)
12. Schedule (if separate)
But that's many sections. The rules say "Prefer a few substantive sections over many thin ones." However, each of these sections has substantial content (lists of many items). They are not thin. So it's okay.
I'll use for each section heading.
For lists, use - . For prose, use
.
Now, let's write the HTML.
First, About the Company: there are multiple paragraphs. I'll put them in
tags.
About the Property: multiple paragraphs.
About the Role: the summary paragraph.
Qualifications: list of bullet points.
Performance Standards: each standard with description. Could be a list of items with bold labels? The original has bold labels like "Customer Service:" then description. I'll preserve that as list items with the label and description.
Essential Functions: list of duties.
Physical Requirements: list of items with descriptions.
Use of Senses: list.
Mental Requirements: list.
Environmental Setting: list.
Pay: paragraph.
Schedule: maybe include the schedule availability from qualifications? But it's already in qualifications. Could create a separate Schedule section with that one line. But the rules say never create Schedule unless posting actually states them. It does state "Flexible schedule availability, including evenings, weekends, and holidays." That's a schedule requirement. I'll include a Schedule section with that.
But note: the qualifications list includes that as a bullet. If I create a Schedule section, I might duplicate. Better to keep it in Qualifications and not create a separate Schedule section unless there's more detail. The posting doesn't have a separate schedule section. So I'll not create a Schedule section.
Similarly, Benefits not mentioned.
Now, the "What are we looking for?" heading with "Compensation $ $" - that seems like a placeholder. The compensation paragraph follows. I'll use that paragraph for Pay section.
Now, let's write the HTML fragment.
I'll start with the company description.
Note: The posting has "Pyramid Global Hospitality is a leading hospitality management company..." and then "About Our Property Welcome to OKANA Resort..." I'll make two sections.
But the rules say "Do NOT repeat the job title as a heading". The job title is "OKANA Candy Co. Manager". I won't include that.
Now, code:
About the Company
Pyramid Global Hospitality is a leading hospitality management company with a portfolio of more than 200 hotels and resorts and over 18,000 associates across the United States, Caribbean, and Europe. Our platform includes Benchmark Resorts & Hotels, a collection of distinctive independent properties; Axiom Hospitality, our European hotel management company; and PYRAMIDWORKS, which provides integrated workplace and facilities services. With corporate offices in Boston, The Woodlands, Texas, and London, Pyramid combines global scale with a hands-on approach focused on exceptional service, operational excellence, and long-term partnerships.
At Pyramid, our people are at the heart of everything we do. We are committed to creating an environment where associates are respected, supported, and empowered to grow their careers. Team members have the opportunity to collaborate directly with experienced leaders, take on meaningful stretch assignments, and gain exposure to a diverse portfolio of properties, brands, and markets. Whether you are beginning your hospitality career or bringing years of experience, you'll find opportunities to learn, develop, and make an impact.
Our commitment to associates, guests, owners, and the communities we serve has helped make Pyramid and our properties among the most recognized in hospitality. From being named among the best places to work by respected publications such as USA Today, The Boston Globe, and The Houston Chronicle to earning top travel accolades from Travel + Leisure, Condé Nast Traveler, Forbes Travel Guide, and U.S. News & World Report, these recognitions reflect the culture, service excellence, and commitment to people that define the Pyramid experience.
About the Property
Welcome to OKANA Resort and Indoor WaterPark. Located along the picturesque Oklahoma River in the vibrant Horizons District, near downtown Oklahoma City, OKANA Resort & Indoor Water Park offers exceptional career opportunities. Conveniently situated with a dynamic indoor waterpark, over 400 well-appointed guest rooms and suites, including premium riverfront accommodations, a range of dining options, and extensive meeting and event spaces spanning 30,000 square feet, OKANA provides a unique setting for a rewarding career journey.
Shape your career
for prose - Do NOT repeat job title as heading (page already shows it) - 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 - Include a section ONLY when posting has real, specific content for it — 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 a few substantive sections over many thin ones - Output ONLY HTML fragment — no /, no markdown code fences Now, let's map the content to appropriate sections: The job title is "OKANA Candy Co. Manager" - I should not repeat this as heading. The posting has: - Summary/About the role: "What you will have an opportunity to do" paragraph - Qualifications: list of minimum qualifications - Performance Standards: list of standards (Customer Service, People Management, Quality, Financial, Managing the Business) - Essential Functions: list of duties - Physical Requirements: detailed list - Use of Senses: detailed list - Mental Requirements: detailed list - Environmental Setting: detailed list - Compensation: mentions "Compensation $ $" and then a paragraph about actual compensation packages based on factors I need to decide which sections to include. The rules say use standard headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But also "include a section ONLY when the posting has real, specific content for it". The posting has: - Summary/About the role: yes, substantive paragraph - Qualifications: yes, specific list - Responsibilities: could combine Performance Standards and Essential Functions? Or separate? Performance Standards are more like expectations, Essential Functions are duties. Might combine under "Responsibilities" or have separate "Performance Standards" and "Essential Functions". The rules mention "Responsibilities" as a heading example. I think I'll create "Responsibilities" for Essential Functions, and maybe "Performance Standards" as a separate section since it's detailed. - Physical Requirements, Use of Senses, Mental Requirements, Environmental Setting: these are very detailed and specific. They could be under "Requirements" or separate sections. The rules mention "Requirements" as a heading example. But these are very specific physical/mental/environmental requirements. I could create a "Physical Requirements" section, "Mental Requirements" section, etc. However, the rules say "Prefer a few substantive sections over many thin ones." But these are quite substantive with many items. I think I'll include them as separate sections because they are detailed and specific to this job. - Compensation: the posting says "Compensation $ $" and then a paragraph. That's a Pay section. The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state compensation, albeit vaguely. But it does have a paragraph about compensation packages. I'll include a "Pay" section with that paragraph. - Benefits: not mentioned specifically, so no Benefits section. - Schedule: mentioned "Flexible schedule availability, including evenings, weekends, and holidays." That's in Qualifications. Could be a Schedule section but it's brief. Might fold into Qualifications or a separate Schedule section. The rules say never create Schedule unless posting actually states them. It does state schedule availability. I could include a "Schedule" section with that info. - The "What are we looking for?" heading appears but then just "Compensation $ $". That seems like a placeholder. I'll ignore that heading. - The EEO statement is boilerplate, remove. - The job ID "#BMC-Okana" is minor metadata, fold into a short
or drop. I'll drop it. - The company and property overviews are background, not job-specific. The rules say "Preserve ALL substantive information". But they are not about the role per se. However, they provide context. The rules don't explicitly say to remove company description, but they say "Reformat a job posting into clean, well-structured semantic HTML." The job posting includes that info. I think I should include it as an "About the Company" or "About the Property" section? The rules mention "About the role" as a heading example. Not "About the Company". But the posting has "About Our Property". I could include that as a section. However, the rules say "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." It doesn't forbid company description. But the example headings are job-specific: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Company description might be considered boilerplate? But it's part of the posting. I'll include it as a "About the Company" section? But the rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says "e.g.", so other headings are allowed. However, "Prefer a few substantive sections over many thin ones." The company description is substantive. I'll include it as "About the Company" and "About the Property" maybe combined.
But the user might expect only job-specific sections. Let's see the instruction: "Reformat a job posting into clean, well-structured semantic HTML." The entire posting is provided. I should include all substantive content. The company and property descriptions are part of the posting. I'll include them.
Now, structure:
1. About the Company (Pyramid Global Hospitality)
2. About the Property (OKANA Resort)
3. About the Role (Summary)
4. Qualifications
5. Performance Standards
6. Responsibilities (Essential Functions)
7. Physical Requirements
8. Use of Senses
9. Mental Requirements
10. Environmental Setting
11. Pay (Compensation)
12. Schedule (if separate)
But that's many sections. The rules say "Prefer a few substantive sections over many thin ones." However, each of these sections has substantial content (lists of many items). They are not thin. So it's okay.
I'll use for each section heading.
For lists, use - . For prose, use
.
Now, let's write the HTML.
First, About the Company: there are multiple paragraphs. I'll put them in
tags.
About the Property: multiple paragraphs.
About the Role: the summary paragraph.
Qualifications: list of bullet points.
Performance Standards: each standard with description. Could be a list of items with bold labels? The original has bold labels like "Customer Service:" then description. I'll preserve that as list items with the label and description.
Essential Functions: list of duties.
Physical Requirements: list of items with descriptions.
Use of Senses: list.
Mental Requirements: list.
Environmental Setting: list.
Pay: paragraph.
Schedule: maybe include the schedule availability from qualifications? But it's already in qualifications. Could create a separate Schedule section with that one line. But the rules say never create Schedule unless posting actually states them. It does state "Flexible schedule availability, including evenings, weekends, and holidays." That's a schedule requirement. I'll include a Schedule section with that.
But note: the qualifications list includes that as a bullet. If I create a Schedule section, I might duplicate. Better to keep it in Qualifications and not create a separate Schedule section unless there's more detail. The posting doesn't have a separate schedule section. So I'll not create a Schedule section.
Similarly, Benefits not mentioned.
Now, the "What are we looking for?" heading with "Compensation $ $" - that seems like a placeholder. The compensation paragraph follows. I'll use that paragraph for Pay section.
Now, let's write the HTML fragment.
I'll start with the company description.
Note: The posting has "Pyramid Global Hospitality is a leading hospitality management company..." and then "About Our Property Welcome to OKANA Resort..." I'll make two sections.
But the rules say "Do NOT repeat the job title as a heading". The job title is "OKANA Candy Co. Manager". I won't include that.
Now, code:
About the Company
Pyramid Global Hospitality is a leading hospitality management company with a portfolio of more than 200 hotels and resorts and over 18,000 associates across the United States, Caribbean, and Europe. Our platform includes Benchmark Resorts & Hotels, a collection of distinctive independent properties; Axiom Hospitality, our European hotel management company; and PYRAMIDWORKS, which provides integrated workplace and facilities services. With corporate offices in Boston, The Woodlands, Texas, and London, Pyramid combines global scale with a hands-on approach focused on exceptional service, operational excellence, and long-term partnerships.
At Pyramid, our people are at the heart of everything we do. We are committed to creating an environment where associates are respected, supported, and empowered to grow their careers. Team members have the opportunity to collaborate directly with experienced leaders, take on meaningful stretch assignments, and gain exposure to a diverse portfolio of properties, brands, and markets. Whether you are beginning your hospitality career or bringing years of experience, you'll find opportunities to learn, develop, and make an impact.
Our commitment to associates, guests, owners, and the communities we serve has helped make Pyramid and our properties among the most recognized in hospitality. From being named among the best places to work by respected publications such as USA Today, The Boston Globe, and The Houston Chronicle to earning top travel accolades from Travel + Leisure, Condé Nast Traveler, Forbes Travel Guide, and U.S. News & World Report, these recognitions reflect the culture, service excellence, and commitment to people that define the Pyramid experience.
About the Property
Welcome to OKANA Resort and Indoor WaterPark. Located along the picturesque Oklahoma River in the vibrant Horizons District, near downtown Oklahoma City, OKANA Resort & Indoor Water Park offers exceptional career opportunities. Conveniently situated with a dynamic indoor waterpark, over 400 well-appointed guest rooms and suites, including premium riverfront accommodations, a range of dining options, and extensive meeting and event spaces spanning 30,000 square feet, OKANA provides a unique setting for a rewarding career journey.
Shape your career
- . For prose, use
. Now, let's write the HTML. First, About the Company: there are multiple paragraphs. I'll put them in
tags. About the Property: multiple paragraphs. About the Role: the summary paragraph. Qualifications: list of bullet points. Performance Standards: each standard with description. Could be a list of items with bold labels? The original has bold labels like "Customer Service:" then description. I'll preserve that as list items with the label and description. Essential Functions: list of duties. Physical Requirements: list of items with descriptions. Use of Senses: list. Mental Requirements: list. Environmental Setting: list. Pay: paragraph. Schedule: maybe include the schedule availability from qualifications? But it's already in qualifications. Could create a separate Schedule section with that one line. But the rules say never create Schedule unless posting actually states them. It does state "Flexible schedule availability, including evenings, weekends, and holidays." That's a schedule requirement. I'll include a Schedule section with that. But note: the qualifications list includes that as a bullet. If I create a Schedule section, I might duplicate. Better to keep it in Qualifications and not create a separate Schedule section unless there's more detail. The posting doesn't have a separate schedule section. So I'll not create a Schedule section. Similarly, Benefits not mentioned. Now, the "What are we looking for?" heading with "Compensation $ $" - that seems like a placeholder. The compensation paragraph follows. I'll use that paragraph for Pay section. Now, let's write the HTML fragment. I'll start with the company description. Note: The posting has "Pyramid Global Hospitality is a leading hospitality management company..." and then "About Our Property Welcome to OKANA Resort..." I'll make two sections. But the rules say "Do NOT repeat the job title as a heading". The job title is "OKANA Candy Co. Manager". I won't include that. Now, code:
About the Company
Pyramid Global Hospitality is a leading hospitality management company with a portfolio of more than 200 hotels and resorts and over 18,000 associates across the United States, Caribbean, and Europe. Our platform includes Benchmark Resorts & Hotels, a collection of distinctive independent properties; Axiom Hospitality, our European hotel management company; and PYRAMIDWORKS, which provides integrated workplace and facilities services. With corporate offices in Boston, The Woodlands, Texas, and London, Pyramid combines global scale with a hands-on approach focused on exceptional service, operational excellence, and long-term partnerships.
At Pyramid, our people are at the heart of everything we do. We are committed to creating an environment where associates are respected, supported, and empowered to grow their careers. Team members have the opportunity to collaborate directly with experienced leaders, take on meaningful stretch assignments, and gain exposure to a diverse portfolio of properties, brands, and markets. Whether you are beginning your hospitality career or bringing years of experience, you'll find opportunities to learn, develop, and make an impact.
Our commitment to associates, guests, owners, and the communities we serve has helped make Pyramid and our properties among the most recognized in hospitality. From being named among the best places to work by respected publications such as USA Today, The Boston Globe, and The Houston Chronicle to earning top travel accolades from Travel + Leisure, Condé Nast Traveler, Forbes Travel Guide, and U.S. News & World Report, these recognitions reflect the culture, service excellence, and commitment to people that define the Pyramid experience.
About the Property
Welcome to OKANA Resort and Indoor WaterPark. Located along the picturesque Oklahoma River in the vibrant Horizons District, near downtown Oklahoma City, OKANA Resort & Indoor Water Park offers exceptional career opportunities. Conveniently situated with a dynamic indoor waterpark, over 400 well-appointed guest rooms and suites, including premium riverfront accommodations, a range of dining options, and extensive meeting and event spaces spanning 30,000 square feet, OKANA provides a unique setting for a rewarding career journey.
Shape your career