Jobs · Management · Oklahoma

Maintenance Tech - PM Shift

Milo's Tea Company, Inc. · Tulsa, OK · 2 days ago
ManagementFull-time
The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and structure it according to the rules. First, I need to identify the sections: 1. Company Overview - but this seems like general company info, not specific to the role. The rules say to use h3 for section headings like "About the role", "Responsibilities", etc. The company overview might be "About the company" but the rules don't list that as a standard heading. However, the posting has "Company Overview" and "Why You Will Love Life at Milo's" and "Benefits" and "Being a Culture Champion at Milo's" and "Equal Employment Opportunity Statement" and "Position Summary" and "Ownership" (which seems like responsibilities) and "Qualifications" and "Physical Demands" and "Skills". The rules: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use
  • for any list of duties/requirements/benefits, and

    for prose. 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. 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. We have Benefits section with a list. That should be included. The EEO statement is boilerplate, should be removed. The "Being a Culture Champion at Milo's" seems like company culture/values, maybe part of "About the company" or "Why join us". The "Position Summary" and "Ownership" (which lists duties) are responsibilities. "Qualifications" is requirements. "Physical Demands" is a section. "Skills" is a list. We need to decide which sections to include. The rules say include a section ONLY when the posting has real, specific content for it. So we should include: - About the role (maybe combine Position Summary and Ownership? But Ownership is a list of duties. Could be "Responsibilities".) - Responsibilities (from Ownership) - Qualifications (from Qualifications) - Physical Demands (from Physical Demands) - Skills (from Skills) - Benefits (from Benefits) Also "Why You Will Love Life at Milo's" is a paragraph, could be part of "About the company" or "Why join us". But the rules don't have a standard heading for that. Could use "About the company" but not listed. The example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use "About the role" for Position Summary, "Responsibilities" for Ownership, "Qualifications" for Qualifications, "Physical Demands" for Physical Demands, "Skills" for Skills, "Benefits" for Benefits. We should not include EEO statement. Also "Being a Culture Champion at Milo's" is a list of behaviors, maybe part of "About the company" or "Culture". But the rules say prefer a few substantive sections over many thin ones. Could include as "Culture" or "Values". However, the rules don't list "Culture" as a standard heading. But we can use h3 for any section heading? The rules say "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. But we should stick to those if possible. However, "Physical Demands" is not in the list but is a common job posting section. The rules say "include a section ONLY when the posting has real, specific content for it". So we can include Physical Demands. Similarly, "Why You Will Love Life at Milo's" is a paragraph, could be part of "About the role" or a separate "Why join us". But to keep it simple, maybe include as a paragraph under "About the role" or separate "About the company". However, the company overview is also there. The posting starts with "Company Overview" and "Why You Will Love Life at Milo's". That's company-level info. The job posting is for a maintenance position. The user wants to reformat the job posting. Usually job postings have "About the company" and "About the role". But the rules say do NOT repeat the job title as a heading. The page already shows it. So we can have "About the company" and "About the role". But the rules don't explicitly forbid "About the company". They say use h3 for section headings (e.g. ...). So we can use other headings. But the instruction: "Prefer a few substantive sections over many thin ones." So maybe combine company overview and why you'll love life into one "About the company" section. Then "About the role" for position summary. Then "Responsibilities" for ownership. Then "Qualifications". Then "Physical Demands". Then "Skills". Then "Benefits". Let's structure:

    About the company

    Company overview paragraph...

    Why you'll love life at Milo's paragraph...

    About the role

    Position summary paragraph...

    Responsibilities

    • ... each bullet from Ownership ...

    Qualifications

    Qualifications paragraph (education/experience)...

    Physical Demands

    Physical demands paragraph...

    Skills

    • Process Driven
    • Teamwork
    • ... etc.

    Benefits

    • Competitive salary
    • 100% employer-paid medical premiums for associates and families
    • ... etc.
    We must remove EEO statement and "Being a Culture Champion at Milo's" maybe incorporate into About the company? The "Being a Culture Champion at Milo's" is a list of behaviors. Could be part of "Culture" but we can include as a list under "About the company" or separate "Culture". But to keep sections few, maybe include as a list under "About the company". However, the rules say use ul li for any list of duties/requirements/benefits. This is a list of cultural expectations. Could be included. But the user said "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The EEO statement is boilerplate. "Being a Culture Champion at Milo's" is not boilerplate; it's specific to the company culture. But it's not a standard job posting section. However, it's substantive content. I'll include it as a subsection under "About the company" maybe as a list. Let's parse the content: Company Overview: multiple paragraphs. I'll combine into one or two paragraphs. Why You Will Love Life at Milo's: one paragraph. Benefits: list. Being a Culture Champion at Milo's: list of 6 items. Equal Employment Opportunity Statement: remove. Position Summary: one paragraph. Ownership: list of 14 bullet points (each line starting with "Perform", "Follow", etc.) Actually the text shows each as separate lines. They are duties. Qualifications: one paragraph. Physical Demands: two paragraphs. Skills: list of 7 skills. Now, we need to output ONLY the HTML fragment, no html/body, no markdown code fences. Let's write the HTML. We'll use h3 for each section. Use p for prose, ul li for lists. We must preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include all bullet points exactly. Let's craft. First, About the company: include Company Overview and Why You Will Love Life at Milo's and Being a Culture Champion at Milo's. But Being a Culture Champion is a list. Could be separate section "Culture" but we can include as a list under About the company. I'll do:

    About the company

    Milo’s Tea Company is one of the fastest-growing beverage companies in the United States. Our culture and operations are built on the belief that we can make a difference in the world. That is why we put People First and strive to continually reduce our environmental impact on the planet. We leverage our world-class operations and decades-long distribution partnerships to grow the footprint of our core products and create new, innovative beverage products. We are the #1 and fastest-growing brand in the Refrigerated Tea Category in the nation.

    Our core mission: People and Planet First — doing good is good for business. We are committed to unlocking the personal genius of every associate and have a strong focus on growth and learning. Our company is women-led and strongly committed to Diversity, Inclusion, and Belonging. We pledge 1% of profits annually to charitable giving. We are Platinum Certified in Zero Waste Manufacturing: recycling, reducing, and reusing 95% of waste at all facilities.

    You will collaborate with a group of passionate and high-performing people, where everyone feels empowered to do their best work and feels good about the work they are doing.

    Being a Culture Champion at Milo’s

    • Wear the HAT (Hungry-Agile-Together)
    • Work effectively with others
    • Help our TEAm achieve safety, quality, and production goals
    • Interact positively, be self-aware, avoid negative commentary
    • Commit to outstanding attendance
    • Conduct yourself respectfully with all Milo's TEAm members
    But the rules say use h3 for section headings. Using h4 might be okay but they said use h3 for section headings. Could make "Being a Culture Champion at Milo’s" an h3? That would be another section. But we want few sections. Could keep as h3? The example headings include "About the role", "Responsibilities", etc. Not "Culture". But we can use h3 for any section heading. The rule: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings. But to be safe, maybe incorporate the culture champion list as part of the About the company prose? But it's a list, better as ul. Could make a subsection with h3 "Culture". But that adds a section. The rules say prefer a few substantive sections over many thin ones. The culture champion list is 6 items, substantive. Could include as a separate section "Culture". But then we have many sections. Let's see: About the company, About the role, Responsibilities, Qualifications, Physical Demands, Skills, Benefits. That's 7 sections. Adding Culture makes 8. Might be okay. But the user said "Prefer a few substantive sections over many thin ones." So maybe combine Culture into About the company as a list without a heading? But the list needs a heading? Could just put the list after the paragraph with a bold label? But the rule says use h3 for section headings. Not required for sub-lists. However, the list is a distinct set of items. I think it's fine to include as a list under About the company without a subheading, but

Similar jobs