Project Manager I/II

We need to output HTML fragment with sections: About the role? Actually the posting includes "About CORE" then "Job Summary", "Essential Duties And Responsibilities", "Minimum Qualifications Of Position", "Preferred Qualifications Of Position – Project Manager I", "Preferred Qualifications Of Position - Project Manager II", "Compensation Range for Project Manager I", "Compensation Range for Project Manager II", "Working Conditions And Physical Requirements", "Application Timeline", "CORE Offers a Comprehensive Benefits Package". We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. Use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. Do not repeat job title. Do not include Job ID etc. Remove boilerplate like EEO, application instructions, etc. Also remove duplicated lines. We need to preserve all substantive information. So we need to extract content and format. Let's parse: - About CORE: description of cooperative. Could be "About the role"? Actually "About CORE" is about company, not role. But we have "About the role" heading allowed. Could we use that for company description? The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings as appropriate. "About the role" could contain job summary and maybe about CORE? The job summary is about responsibilities. But we can put company description under "About the role"? Might be okay. However we also have "Job Summary" which is a prose description of role. That could go under "About the role". Or we could have separate sections: "About the role" for summary, "Responsibilities" for duties, "Requirements" for minimum qualifications, "Qualifications" for preferred qualifications, "Skills" maybe for technical skills, "Benefits" for benefits, "Pay" for compensation ranges, "Schedule" for work schedule (9/80). The posting includes "Working Conditions And Physical Requirements" which could be part of Requirements or maybe separate but not in allowed headings; we could incorporate into Requirements or maybe not create a separate heading if not allowed. Since only those headings allowed, we should map content accordingly. We must not create sections with filler. So we need to decide which sections to include based on content. Let's extract: Company description: "About CORE CORE Electric Cooperative is the largest member-owned electric distribution cooperative in Colorado dedicated to providing reliable, affordable, clean, and safe electric service to our communities. With a commitment to innovation and member satisfaction, we strive to meet the evolving needs of our members while maintaining the highest standards of service excellence." Job Summary: "Responsible to the System Improvement Manager for the project management, engineering and coordination of activities related to transmission, substation and distribution projects. Works in conjunction with the consulting engineer, CORE’s Engineering and Operations Departments, and contractors to schedule, inspect and oversee projects. In addition, reviews proposed contracts and construction documents, prepares as-built construction documents, and reviews contractor billings. Represents the interests of the Association in all aspects of work and ensures compliance with the latest contract standards and specifications." Essential Duties And Responsibilities: list of duties (multiple sentences). We'll turn into

  • . Minimum Qualifications Of Position: list of qualifications (bullet-like sentences). We'll turn into
    • . Preferred Qualifications Of Position – Project Manager I: includes Software & Systems Experience, Technical & Construction Knowledge etc. This is a list of preferred qualifications. Preferred Qualifications Of Position - Project Manager II: includes Minimum Requirements, Regulatory & Standards Knowledge, Software & Systems Experience, Broadband Funding & Grant Awareness, Technical & Construction Knowledge. Compensation Range for Project Manager I: "$92,900 - $123,800" Compensation Range for Project Manager II: "$103,200 - $137,500" Working Conditions And Physical Requirements: prose about physical demands. Application Timeline: "The application deadline for this job is estimated to be 10/8/2026. However, this timeline may be shortened or extended depending on business needs, the availability of qualified candidates, and whether the role is filled or not. We encourage qualified candidates to submit their application(s) expediently so as not to miss out on opportunities." This is application instruction; we should remove application instructions per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should drop the Application Timeline section. CORE Offers a Comprehensive Benefits Package: list of benefits. We also have "9/80 work schedule: every other Friday off!" which is a schedule benefit; could go under Benefits or Schedule. Since we have Schedule heading allowed, we could put schedule info there. But the benefits list includes that as first item. We could either put schedule under Benefits or Schedule. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine schedule into Benefits. But we have a Benefits heading allowed; we can include schedule as part of benefits list. However we also have a Schedule heading; we could create a Schedule section with just the 9/80 schedule. But that might be thin. Better to include schedule within Benefits. Thus sections we will output: - About the role: includes company description + job summary? Could combine. But we might separate: About the role (company description), Responsibilities (essential duties), Requirements (minimum qualifications), Qualifications (preferred qualifications for both I and II), Benefits (benefits list + schedule), Pay (compensation ranges). That seems reasonable. We must not repeat job title as heading. Not needed. We must not include Pay/Schedule/Benefits unless posting actually states them. We have Pay (compensation ranges) and Benefits (benefits). Schedule we have as part of benefits; we could still include Schedule heading if we want but it's thin. I'd avoid Schedule heading to keep few sections. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Now format:

      About the role

      CORE Electric Cooperative is the largest member-owned electric distribution cooperative in Colorado dedicated to providing reliable, affordable, clean, and safe electric service to our communities. With a commitment to innovation and member satisfaction, we strive to meet the evolving needs of our members while maintaining the highest standards of service excellence.

      Responsible to the System Improvement Manager for the project management, engineering and coordination of activities related to transmission, substation and distribution projects. Works in conjunction with the consulting engineer, CORE’s Engineering and Operations Departments, and contractors to schedule, inspect and oversee projects. In addition, reviews proposed contracts and construction documents, prepares as-built construction documents, and reviews contractor billings. Represents the interests of the Association in all aspects of work and ensures compliance with the latest contract standards and specifications.

      But we have two paragraphs; could combine into one? It's okay. Next Responsibilities:

      Responsibilities

      • Managing engineering and construction activities for substations, transmission lines, distribution lines, facility relocation and other projects.
      • Practicing cost control, monitoring expenditures, reviewing task orders, approving invoices and change orders, and providing monthly budget amendments for assigned projects.
      • Ensuring projects are closed in accordance with procedures in place with GIS, Finance, Purchasing and Operations.
      • Supporting permitting and land acquisition activities.
      • Building relationships with various entities, understanding and acknowledging changes to utility accommodation codes and advocating for CORE when changes are proposed to existing codes.
      • Preparing and overseeing contracts and managing schedules with independent contractors, consultants, surveyors, tree trimmers, reclamation firms, and other vendors.
      • Preparing bid documents, participating in pre-bid meetings, evaluating proposals and providing award recommendations for various engineering and construction contracts.
      • Participating in developing, maintaining and updating department procedures, project design criteria and RFP documents.
      • Mentoring other Project Managers and interns.
      Next Requirements (minimum qualifications):

      Requirements

      • Bachelor’s degree in engineering or construction management, business, information technology or related field. (Will consider candidates with equivalent work experience in place of formal educational requirements.)
      • Demonstrated ability to lead and influence others.
      • Strong presentation and facilitation skills.
      • Excellent verbal and written communication skills.
      • Ability to adapt to change and work with diverse cross‑functional teams.
      • Proficient with Microsoft Office: Excel, Word, Outlook, Projects, PowerPoint and with general office equipment.
      • Requires valid Colorado driver’s license with satisfactory driving record.
      • A Colorado Professional Engineer’s license or PMP Certification is preferred.
      Note: The parenthetical about equivalent work experience is part of the qualification; we keep it. Next Qualifications (preferred qualifications for both I and II). Could combine but need to avoid duplication. There's overlap: both have Software & Systems Experience, Technical & Construction Knowledge etc. We'll list combined unique items, but we must preserve all substantive information; we can list both sets but note duplication? Better to list both sections maybe separate subheadings? But we only have allowed headings; we could still have a single Qualifications section and include all preferred qualifications, noting that some apply to specific levels. We'll include bullet points, maybe with notes. Let's extract all preferred qualifications: From Project Manager I: - Software & Systems Experience in Alden One (Alden Systems). - Comfort with GIS platforms (ESRI/ArcGIS) for mapping poles and attachments. - Technical & Construction Knowledge: * Understands what joint use is and knows construction practices. * Can read and interpret field notes, staking sheets, and construction drawings. * Understands pole ownership, transfers, and abandonment processes (including detach/rearrangement notices - relevant to Lumen situations). * Knowledge of communications vs. power space on the pole and proper attachment standards. * Familiar with pole inspection, auditing, and inventory reconciliation practices. From Project Manager II: - Minimum Requirements - Project Manager II: Minimum 5 years of project management experience - Regulatory & Standards Knowledge: * Understands NESC codes for joint use (clearances, grades of construction, loading). * Familiarity with FCC pole attachment rules and the one-touch make-ready (OTMR) framework. * Awareness of state PUC/PSC regulations and how they affect attachment rights, timelines, and rates in our operating territory. * Understands make-ready engineering - cost estimation, timelines, and who pays for what. - Software & Systems Experience in Alden One (Alden Systems). - Comfort with GIS platforms (ESRI/ArcGIS) for mapping poles and attachments. - Broadband Funding & Grant Awareness: * Familiarity with BEAD (Broadband Equity, Access, and Deployment) - understands that BEAD-funded fiber projects generate a surge of new attachment applications and make-ready requests. * Awareness of how BEAD deployment timelines create pressure on make-ready engineering and permitting turnaround (grantees often have aggressive build schedules and deadlines). * Awareness of related programs and how they overlap - NTIA oversight of BEAD, plus adjacent funding like RDOF, ARPA, and state broadband office grants. - Technical & Construction Knowledge (same as above list). Thus we can combine. We'll produce a Qualifications section with bullets, possibly grouping. We'll avoid duplication: list each unique item once, but we need to preserve all info; if we omit duplication we might lose info that it's required for both levels? But the info is same; preserving once is fine. However we might lose the note that Minimum 5