Project Manager Water Mitigation

We need to output HTML fragment with sections: About the role (maybe heading "About The Role" but we should use

for section headings). The posting includes "About The Role" heading, "What You'll Do", "What You Bring", "Compensation & Benefits", "Who We Are". Also "Benefits" line at top? Actually the posting starts with "Benefits 401(k)401(k) matchingDental insuranceOpportunity for advancementPaid time offTraining & development". That seems like a garbled benefits list. Then later "Compensation & Benefits" includes bullet points: Consistent overtime opportunities, Company vehicle / equipment provided for job use, Paid IICRC training and certification support, Clear advancement path within a growing, multi-territory company that promotes from within. Also there is a compensation line: "Compensation: $19.00 - $23.00 per hour". So we need a Pay section if posting actually states them. Yes, compensation is stated. So we should include a Pay section with that info. Benefits: The posting includes benefits list: 401(k) matching, Dental insurance, Opportunity for advancement, Paid time off, Training & development. Also "Company vehicle / equipment provided for job use", "Paid IICRC training and certification support", "Clear advancement path". Those are benefits. So we should include a Benefits section with those items. Schedule: Not explicitly stated besides "Availability for overtime, evenings, and weekends as emergencies require". That's schedule info. Could be considered schedule. The rule: include Schedule section only if posting actually states them. It does mention overtime availability, evenings, weekends. So we can include Schedule. We must not repeat job title as heading. The title is "Project Manager – Water Mitigation SERVPRO Team Landers | Salt Lake City, UT". We should not put that as heading. We must not include Job ID/requisition numbers. We must remove boilerplate: EEO, equal opportunity, application instructions, navigation, cookie, legal, etc. Also remove duplicated lines. We need to preserve all substantive information. We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have: - About the role: The paragraph under "About The Role". That's substantive. - Responsibilities: Could be "What You'll Do" list. - Requirements/Qualifications/Skills: Could combine "What You Bring" which includes required experience, preferred experience, skills, certifications, tools, driver's license, physical ability, availability. We could split into Requirements (required) and Qualifications (preferred) and Skills (maybe). But rule: prefer few substantive sections over many thin ones. So maybe combine into a single "Requirements" section that includes both required and preferred? But we need to follow headings list: we can use any of those headings if we have content. We could have "Requirements" and "Skills". But we need to avoid thin sections. Better: Use "Responsibilities" for What You'll Do. Use "Requirements" for What You Bring (including required experience, preferred, skills, certifications, etc.). Use "Benefits" for benefits list. Use "Pay" for compensation. Use "Schedule" for availability for overtime, evenings, weekends. We also have "Who We Are" description about company. Could be included as "About the company" but not in headings list. Could we include as a section? Not in allowed headings list. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add other headings. We could incorporate "Who Are" into About the role or maybe omit? The rule: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that info somewhere. Could we put it under About the role? The About the role heading is for description of the role; but "Who We Are" is about company. Could we add a section like "About the company"? Not allowed. However we could incorporate it into the About the role section as extra paragraph? Might be okay as it's still substantive and not violating heading list. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, not exclusive? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. But we could still add other headings if needed? The instruction says "use

for section headings (e.g. ...)". It doesn't forbid other headings, but suggests using those for typical sections. Safer to stick to those headings and fit all info within them. We can put company description under About the role as a paragraph after role description. Thus sections: -

About the role

: includes the paragraph about role and maybe company description. -

Responsibilities

: list of What You'll Do. -

Requirements

: list of What You Bring (including required, preferred, skills, certifications, tools, driver's license, physical ability, availability for overtime etc). But we also need schedule separate? Could include availability in Requirements but we also need Schedule section. Might be better to separate schedule. Thus: -

Requirements

: required experience, preferred experience, certifications, tools, driver's license, physical ability. -

Schedule

: availability for overtime, evenings, weekends as emergencies require. -

Benefits

: list of benefits. -

Pay

: compensation range. We must not include empty sections. Now we need to extract the exact content. Let's parse the posting: Benefits line at top: "Benefits 401(k)401(k) matchingDental insuranceOpportunity for advancementPaid time offTraining & development". This seems garbled: likely they intended "Benefits: 401(k) matching, Dental insurance, Opportunity for advancement, Paid time off, Training & development". We'll treat as list. Then job title line: "Project Manager – Water Mitigation SERVPRO Team Landers | Salt Lake City, UT Full-Time | Overtime Available". We'll not use as heading. Then "About The Role" paragraph: "SERVPRO Team Landers is looking for an experienced Mitigation Project Manager to join our Salt Lake City team. When a home or business floods, our crews are the first ones through the door — and our PMs are the ones who make sure every job is set up right, dried to standard, documented cleanly, and closed out on time. This is a hands-on leadership role. You'll run crews in the field, own the drying process from first moisture reading to final dry standard, and keep your job files airtight. If you've worked water mitigation before, know your way around a dry book, and have led a crew through a busy loss season, we want to talk to you." Then "What You'll Do" bullet list (looks like sentences separated by line breaks). We'll convert to

• . List: - Lead and direct mitigation crews on water damage jobs — setting daily priorities, assigning tasks, and keeping work moving safely and efficiently - Perform initial inspections, moisture mapping, and job scoping - Set up drying plans and place equipment (air movers, dehumidifiers, air scrubbers) per IICRC S500 standards - Complete daily monitoring visits — take and record moisture, temperature, and humidity readings and adjust equipment as needed - Build and maintain complete dry books / drying logs, photo documentation, and job notes so every file is audit-ready - Communicate clearly and professionally with property owners, adjusters, and internal teams throughout the life of the job - Oversee demo, containment, and equipment pickup; verify dry standard is met before closing out - Train and coach technicians in the field, holding the crew to our quality and safety standards - Participate in the on-call rotation for emergency response Then "What You Bring" bullet list: - Prior water mitigation experience (required) - Experience building and maintaining dry books and drying documentation (strongly preferred) - Experience with daily monitoring and adjusting drying systems (strongly preferred) - Experience running crews and leading technicians in the field (strongly preferred) - Strong leadership, communication, and organizational skills — you take ownership and follow through - IICRC WRT certification a plus (ASD, AMRT a bonus) — or willingness to obtain - Familiarity with CompanyCam, Matterport, Xactimate, or similar tools a plus - Valid driver's license and a clean driving record (required) - Ability to lift 50+ lbs, work in crawlspaces and attics, and handle physically demanding conditions - Availability for overtime, evenings, and weekends as emergencies require Then "Compensation & Benefits" paragraph: "Consistent overtime opportunities Company vehicle / equipment provided for job use Paid IICRC training and certification support Clear advancement path within a growing, multi-territory company that promotes from within" Also there is a line: "Compensation: $19.00 - $23.00 per hour" Then "Who We Are" paragraph: "SERVPRO Team Landers is a fast-growing restoration company operating across Oregon, Washington, Utah, and California. We're built on a simple standard: take care of people on the worst day they've had, and do it right the first time." Then "Our Core Values" list: "Relentlessly Focus on Winning Consistently Exceed Expectations Act with Urgency Solve the Problem Continuously Improve Our DNA: Hungry, Humble, Smart." Then a paragraph: "If that sounds like you, we'd like to meet you." Then "Ready to Apply?" etc (application instructions) - we must remove. Then equal opportunity boilerplate - remove. Then more fluff about making difference, etc - maybe considered boilerplate? It's somewhat generic but still about company mission. Might be considered substantive? It's somewhat promotional but still about company. However it's likely considered boilerplate? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The fluff about making difference may not be boilerplate but could be considered promotional. However it's not EEO or legal. It's about mission. Might be considered substantive? It's not directly about role, responsibilities, requirements, benefits, pay, schedule. Could be considered "Who We Are" which we already captured partially. The rest may be redundant. We'll keep the "Who We Are" paragraph and maybe core values? Core values could be considered substantive about company culture. But not in allowed headings. Could we include under About the role? Might be okay to add as extra paragraph. We need to preserve ALL substantive information. So we should keep the core values and mission statements if they are substantive. However they might be considered boilerplate? The instruction only mentions specific boilerplate types: cookie/navigation/legal/EEO/equal-opportunity/scam-warning. So core values are not those. So we should keep them. Thus we need to incorporate "Who We Are", "Our Core Values", and maybe the mission statement paragraphs into About the role section. Let's extract: Who We Are: "SERVPRO Team Landers is a fast-growing restoration company operating across Oregon, Washington, Utah, and California. We're built on a simple standard: take care of people on the worst day they've had, and do it right the first time." Our Core Values: "Relentlessly Focus on Winning Consistently Exceed Expectations Act with Urgency Solve the Problem Continuously Improve Our DNA: Hungry, Humble, Smart." Then: "If that