Construction Field Manager

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title. No Job ID etc. Remove boilerplate like EEO etc. We need to preserve all substantive info. Let's parse the posting: First line: "Supporting Delmarva, Ohio as needed" maybe location? Not a heading. Then "What makes us great: At the heart of our Company is a dedication to delivering energy that drives progress. We put people first, work to keep them safe and build trusting relationships." This is about company culture; could be "About the role"? Actually "What makes us great" is about company. Could be "About the role"? Usually "About the role" describes the job. But we have "What You’ll Be Working On…" which is responsibilities. So we can have sections: About the role (maybe the first paragraph about company dedication?), Responsibilities (the bullet list after "What You’ll Be Working On…"), Requirements (maybe "Who You Are..."), Qualifications (maybe overlapping), Skills (maybe specific skills), Benefits (the "Benefits/what’s in it for you?"), Pay (not mentioned), Schedule (not mentioned). So we should not create Pay or Schedule sections because not present. We need to decide which headings to use: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. Possibly also "Work Environment" but not required. We must not create sections with filler text. So we need to ensure each heading has substantive content. Let's extract content: About the role: Could be the introductory paragraph: "Supporting Delmarva, Ohio as needed What makes us great: At the heart of our Company is a dedication to delivering energy that drives progress. We put people first, work to keep them safe and build trusting relationships." That's about company mission. Could be considered About the role? Might be okay. But maybe better: "About the role" could be a brief summary: The job is about managing construction inspection etc. However we have a separate Responsibilities section that details duties. So About the role could be a short overview: maybe the first sentence "Supporting Delmarva, Ohio as needed" plus the "What makes us great" paragraph. That's substantive. Responsibilities: All bullet points after "What You’ll Be Working On…" up to before "Who You Are...". That's a long list. We'll put each as

inside

. Requirements: Could be the "Who You Are..." paragraph that lists education, experience, etc. That includes: High School Diploma plus Associate's Degree in Construction management, Engineering, or equivalent combination; five to ten years related work experience; proficiency in standard business software; conscientious work ethic; supervisor with effective communication and active listening skills, creative and passionate team player and problem solver; ability to prioritize and adapt; high degree oral/written communication; valid Driver’s License; extensive experience (5 years minimum preferred) in system operations, inspection, and construction practices; preferably certified in welding inspection and pipeline tapping/stopple; advanced knowledge of pipeline system operations; advanced knowledge of design codes and specifications (49 CFR Part 192, ASME, API, etc.); advanced design of pipeline facilities (mains, service, valves sites, M&R Stations, etc.). That's requirements/qualifications. We could split into Requirements (education, experience, basic) and Qualifications (certifications, knowledge). But we can also combine. The instruction: prefer a few substantive sections over many thin ones. So maybe we have Requirements (covering education, experience, basic skills) and Qualifications (certifications, advanced knowledge). Skills could be separate: proficiency in Microsoft Suite, communication skills, etc. But we already have many. Let's think: The posting includes "Who You Are..." which is a mix of requirements and qualifications. Could treat that as Requirements. Then we could have a Skills section for specific technical skills: welding inspection certification, pipeline tapping/stopple, design codes, etc. But those are also qualifications. Given the instruction to prefer few substantive sections, maybe we just have: About the role, Responsibilities, Requirements (which includes education, experience, skills, certifications, knowledge), Benefits. That's four sections. We must not include Pay or Schedule. Now we need to format. We need to wrap each section:

About the role

then

...

for prose. For lists,
• ...
. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting. Let's extract the exact text for About the role: "Supporting Delmarva, Ohio as needed What makes us great: At the heart of our Company is a dedication to delivering energy that drives progress. We put people first, work to keep them safe and build trusting relationships." There is a missing space between "needed" and "What". We'll keep as is but maybe add a space for readability? The instruction: preserve ALL substantive information; do not invent or summarize away detail. Adding a space is not inventing content, just formatting. Probably okay. We'll keep the text as given but we can add a space for readability; it's not changing meaning. Safer to keep exactly: "Supporting Delmarva, Ohio as needed What makes us great: At the heart of our Company is a dedication to delivering energy that drives progress. We put people first, work to keep them safe and build trusting relationships." Now Responsibilities: list all items after "What You’ll Be Working On…" up to before "Who You Are...". Let's copy them exactly as sentences (they are already sentences). We'll need to ensure we capture each bullet. The text: Managing construction inspection and ensuring that facilities are installed and documented according to applicable standards. Scheduling and managing company and contractor personnel on site. Ensuring cost effective use of company and contractor personnel on “Time and Material” and “Not to Exceed” jobs. Representing Chesapeake Utilities with governmental representatives and managing compliance with construction permits. Managing public relations on and near construction sites. Meeting construction deadlines. Approving change orders and payment to vendors based on spending authority. Ensuring safety and environmental compliance on construction site. Ensuring that CUC, State, and Federal safety requirements are maintained. Ensuring that all Capital Projects and Pipeline facilities are installed to Chesapeake Utilities and DOT specification. Assisting in cost estimates for construction projects and providing information to project manager for project budgeting, forecasting, and scheduling. Providing project timeline estimates. Determining least cost alternatives for projects. Procuring material off of material lists. Conducting frequent job update meetings and supply status reports. Analyzing and organizing pipeline data and records. Completing and filing essential documentation. Generating prints or drawings for construction projects as required. Generating and filing as-built drawings. Directing CAD operator in the development of as built and final construction drawings. Reviewing proposed State/Utility construction plans and accurately determining the company’s pipeline involvement. Assisting in training for Operator Qualification Program. Evaluating and qualifying company personnel in accordance with company OQ Program within areas of expertise. Coordinating repairs or preventative maintenance to pipeline facilities. Assisting in implementation of Pipeline Integrity Plan. Performing other duties as required. We need to keep the quotes around “Time and Material” and “Not to Exceed”. Use proper quotes? We'll keep as is. Now Requirements: "Who You Are..." paragraph. Let's extract: You hold a High School Diploma plus Associate's Degree in Construction management, Engineering, or equivalent combination of education, knowledge and experience. You have five to ten years of related work experience. You are proficient in the use of standard business software (Microsoft Suite). You possess conscientious work ethic. You are a supervisor with effective communication and active listening skills, a creative and passionate team player and problem solver. You have the ability to prioritize and adapt in order to compete projects and requirements. (Note: likely "complete projects". We'll keep as given.) You have a high degree of oral and written communication skills. You possess a valid Driver’s License. You have extensive experience (5 years minimum preferred) in system operations, inspection, and construction practices. You are preferably certified in welding inspection and pipeline tapping/stopple. You have advanced knowledge of pipeline system operations. You have advanced knowledge of design codes and specifications (49 CFR Part 192, ASME, API, etc.). You have advanced design of pipeline facilities (mains, service, valves sites, M&R Stations, etc.). We need to keep each as separate sentences; we can put them in
• or

  . Since it's a list of requirements, we can use

  • . The instruction: Use
    • for any list of duties/requirements/benefits. So we should use list for requirements. Thus we will have

      Requirements

      • ... each item.
      Now Benefits: The section "Benefits/what’s in it for you?" includes bullet-like sentences but not bullet list. It's a paragraph with multiple items separated by commas and line breaks? Let's copy: Competitive base salaryFantastic opportunities for career growthCooperative, supportive and empowered team atmosphereAnnual bonus and salary increase opportunitiesMonthly recognition eventsEndless wellness initiatives and community eventsRobust and customizable benefit packages-choose what works best with your life. Options include generous 401k, medical, dental and life insurance, tuition reimbursement, compensated volunteer hours and MORE!Paid time off, holidays and a separate bank of sick time! We need to preserve all substantive information. There's missing spaces between some phrases (e.g., "salaryFantastic", "growthCooperative", "eventsRobust", "life.Options", "hours and MORE!Paid"). We should keep as is? The instruction: preserve ALL substantive information; do not invent or summarize away detail. Adding spaces could be considered inventing? It's just formatting; but we might inadvertently change meaning if we add spaces where none were originally. However the original likely had missing spaces due to OCR. But we must not invent. Safer to keep the exact string as given, but we can break into list items for readability? That would be inventing structure (list) but not adding content. The instruction says use
      • for any list of duties/requirements/benefits. So we should turn the benefits into a list. However we need to ensure we don't lose any content. We can split by the phrases that are separated by missing spaces? That's ambiguous. Better to keep as a single

        preserving the exact text, even if it's run-on. That would satisfy preserving all info. But the instruction says use

        • for any list of benefits. However if we keep as paragraph, we are not following that rule. The rule: "Use
          • for any list of duties/requirements/benefits, and

            for prose." So if the benefits are presented as a list (even if not bullet), we should convert to list. The original text seems to be a list of benefits but missing spaces and punctuation. We can infer separate items: Competitive base salary, Fantastic opportunities for career growth, Cooperative, supportive and empowered team atmosphere, Annual bonus and salary increase opportunities, Monthly recognition events, Endless wellness initiatives and community events, Robust and customizable benefit packages-choose what works best with your life. Options include generous 401k, medical, dental and life insurance, tuition reimbursement, compensated volunteer hours and MORE!, Paid time off, holidays and a separate bank of sick time! We can split by detecting capital letters after lowercase? That's messy. Safer to keep as a single paragraph but note that it's not a list. However the instruction may be strict; but we must not invent content. Splitting into list items could be considered inventing structure but not content. I think it's acceptable to treat as list because the content is clearly a list of benefits. The missing spaces are likely OCR errors;