Fields Operations Manager

We need to output HTML fragment with sections: About the role? The posting includes "Why High-Performing Managers Choose Blanton's", "Real Pay for Real Ownership", "Career Growth", "Leadership Environment", "Values That Mean Something", "The Role", "What You'll Do", "How You Win In This Role", "What You Bring", "What It Feels Like To Work Here", "Your Path Starts Here — And It Starts Fast". Also location: Fayetteville, NC & Raleigh, NC at top. Should we include location as a paragraph? Probably yes as part of About the role? The instruction: 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. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to decide which sections to include. The posting includes Pay (salary range $75K-95K base + performance-based bonus). Benefits: Medical, Company-paid dental, Vision, Life insurance (with family options), 401(k) with company match, Immediate holiday eligibility. Also maybe "Full Benefits". So we can include Benefits and Pay sections. Responsibilities: "What You'll Do" list. Also "How You Win In This Role" maybe as performance metrics? Could be part of Responsibilities or separate? But we can combine into Responsibilities. Requirements: "What You Bring" includes Must-Haves and Nice-to-Haves. Could be Requirements and Qualifications. Skills: maybe not separate. About the role: The initial paragraphs about field leadership, why choose Blanton's, etc. Could be About the role. We need to avoid filler headings. Ensure each heading has substantive content. We'll produce sections: About the role, Responsibilities, Requirements, Benefits, Pay. We must not include Schedule (not mentioned). Also not include Qualifications separate if we combine with Requirements. We need to use

  for each section heading. Inside sections, use

  for prose,

  • for lists. We must preserve all substantive information: location, etc. Let's extract content. Location: "Fayetteville, NC & Raleigh, NC". Could be a short paragraph at top before sections? Probably as part of About the role? Could be a

    with location. Now About the role: The initial paragraph(s) before "Why High-Performing Managers Choose Blanton's". Actually the posting starts with location line then "Tired of Being Everywhere and Owning Nothing? You already know field leadership is more than checking in on jobs...". That's about the role and company. Then "Why High-Performing Managers Choose Blanton's" is a heading but we should not repeat headings; we can incorporate that content into About the role or maybe a separate section "Why Choose Blanton's"? But instruction says use headings like About the role, Responsibilities, etc. It didn't forbid other headings but says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those standard headings; but we could also add other headings if needed? It says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings for sections; but we could also use other headings if they fit? The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but it gives examples. Safer to stick to those headings. So we need to map content to those headings. Thus we need sections: About the role, Responsibilities, Requirements, Benefits, Pay. Possibly also Qualifications? But we can combine Requirements and Qualifications into one? The instruction says we can use those headings; we can choose which to include. Prefer few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements (including must-haves and nice-to-haves), Benefits, Pay. Now we need to ensure we don't include filler like "commensurate with experience". Not present. Now extract content for each. About the role: Should include the introductory motivational text, why high-performing managers choose Blanton's, leadership environment, values, etc. Also maybe "The Role" paragraph. Let's gather. From posting: - "Tired of Being Everywhere and Owning Nothing? You already know field leadership is more than checking in on jobs. It's the difference between techs who just show up and A-players who own the outcome. It's where customer experience is won or lost, call by call. It's where the standard you accept becomes the standard you get. But too many companies treat field leadership like a scheduling function instead of a performance-building one. At Blanton's Air, Plumbing & Electric, Field Operations Manager is a leadership seat. You don't just check boxes. You build A-players. You own the standard. You drive the numbers every single day." - "Why High-Performing Managers Choose Blanton's Real Pay for Real Ownership $75,000-95,000 base salary + performance-based bonus tied to operational KPIs. Full Benefits Medical Company-paid dental Vision Life insurance (with family options) 401(k) with company match Immediate holiday eligibility Career Growth 75+ years strong and scaling toward a $74M operation with 265 A-players. Leadership Environment Clear expectations. Real accountability. Authority to fix what's broken. Values That Mean Something Always Do the Right Thing Always Growing Can Do Be Kind Deliver WOW" - "The Role As the Field Operations Manager, you own the performance of your team of field technicians. Your responsibility is simple: deliver an exceptional customer experience and hit performance targets on every job, every day — while developing your team into A-players and championing the Blanton's standard in the field." We can combine all that into About the role. Now Responsibilities: "What You'll Do" list. List items: - Lead, coach, and hold your team accountable to Blanton's performance standards - Serve as a service systems expert, ensuring the team consistently follows Blanton's proven field process - Serve as the subject matter expert on Blanton's Service System for field resources - Develop technicians into top ("A" player) performers through hands-on coaching - Complete ride-alongs each day, following Blanton's process — Bloom scorecard, curbside feedback forms, job reviews, huddle report - Schedule and complete 1-on-1s weekly (or bi-weekly with approval) - Facilitate team meetings using the L10 (Level 10) framework - Champion the Blanton's brand in the field and in the community - Own and continuously improve field operating processes - Partner with dispatch to ensure the right tech is on the right call, every time - Resolve escalations and eliminate breakdowns in communication Also "How You Win In This Role" list: - Revenue and truck goals met - Gross profit goal met - 5-Star review target attained - WOW membership sales target attained - Replacement and upgrade sales goal met - Right-the-first-time work on every job - Core values personified by you and your team These could be considered performance metrics; could be part of Responsibilities or separate. Since we want few sections, we could include them under Responsibilities as additional bullet points (maybe separate sublist). But we need to preserve all substantive info. We'll include them as part of Responsibilities. Now Requirements: "What You Bring" Must-Haves and Nice-to-Haves. Must-Haves: - HIENTS (typo? maybe "HIENTS" is garbled; but we must preserve as is? It says "HIENTS Demonstrated leadership ability Proven experience in home services Excellent customer service orientation". Likely a formatting error; but we must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the text exactly as appears? The line: "Must-Haves HIENTS Demonstrated leadership ability Proven experience in home services Excellent customer service orientation". Probably "HIENTS" is a mistake but we keep it. We'll keep as is. - Nice-to-Haves: - Proven experience in field operations / trade management (HVAC, plumbing, or electrical) - Experience using ServiceTitan, or a related field service management software - Advanced trade certifications (HVAC, plumbing, or electrical) Also maybe "What It Feels Like To Work Here" and "Your Path Starts Here — And It Starts Fast" could be part of About the role or separate but we can incorporate into About the role to avoid many sections. Now Benefits: list: - Medical - Company-paid dental - Vision - Life insurance (with family options) - 401(k) with company match - Immediate holiday eligibility Also "Full Benefits" heading. Now Pay: "$75,000-95,000 base salary + performance-based bonus tied to operational KPIs." Also maybe mention "Real Pay for Real Ownership". We'll include that. Now we need to output HTML fragment. Structure:

    About the role

    ... (including location maybe)

    Responsibilities

    • ...
    ...

    Requirements

    Must-Haves: ...

    • Nice-to-Haves items
    maybe. But we need to use
    • for any list of duties/requirements/benefits. For Requirements we have Must-Haves (maybe a paragraph) and Nice-to-Haves list. Could also make Must-Haves as list. Better: Use
      • for Must-Haves and Nice-to-Haves combined? But we need to differentiate. Could have two lists: one for Must-Haves, one for Nice-to-Haves, each preceded by a

        heading? But headings inside section not allowed? We could just have a

        with "Must-Haves:" then list. But instruction: Use

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

          for prose. So we can have a

          for prose, then a

          • for list. Thus for Requirements:

            Must-Haves: HIENTS Demonstrated leadership ability Proven experience in home services Excellent customer service orientation

            then
            • Nice-to-Haves items
            . However Nice-to-Haves is also a list; we could treat as list with a preceding

            Nice-to-Haves:

            . Now Benefits:
            • ...
            Pay:

            $75,000-95,000 base salary + performance-based bonus tied to operational KPIs.

            Now ensure we don't repeat job title as