Junior Scheduler

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Us", "About This Role", "About Summit Line Construction", "Position Summary", "Key Responsibilities", "Required Qualifications", "Preferred Qualifications", "What You'll Get", "Work Environment". Also maybe "About Us" is not needed as heading? 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. We need to decide which sections to include. The posting includes: About Us (company description), About This Role (maybe redundant), About Summit Line Construction (company details), Position Summary, Key Responsibilities, Required Qualifications, Preferred Qualifications, What You'll Get (benefits), Work Environment. Also there is EEO boilerplate which we must remove. We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can also use other headings? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples, but we can use other headings if needed? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect we use those headings where appropriate. However we have content like "About Us", "About Summit Line Construction", "Position Summary". Those could be considered "About the role" or "About the company". Might be okay to use "About the role" for position summary and responsibilities? But we need to preserve all substantive info. Could combine. Better approach: Use headings: About the role (covers Position Summary and maybe About This Role), Responsibilities (Key Responsibilities), Requirements (Required Qualifications), Qualifications (Preferred Qualifications), Benefits (What You'll Get), Work Environment (maybe as its own heading? Not in list but could be considered "Schedule"? Not exactly. Work Environment includes travel, location. Could be part of "About the role" or separate "Work Environment". Since not in examples, maybe we should avoid creating a heading not in list? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use

  for section headings (e.g ...)". Likely they want us to use those headings where applicable, but we can also add others if needed? The phrase "e.g." suggests examples, not exhaustive. So we can use other headings like "Work Environment". However they also say "Prefer a few substantive sections over many thin ones." So we might combine. We need to output only HTML fragment, no /, no markdown. We need to use

  • for any list of duties/requirements/benefits. So for responsibilities, qualifications, benefits we need lists. We need to preserve all substantive info, not invent or summarize away detail. So we need to keep details like specific tasks, specific qualifications, etc. We must remove boilerplate like EEO. Let's extract substantive content: About Us: "Summit Line Construction, a subsidiary of Quanta Services, Inc. (NYSE: PWR), is one of North America's premier utility construction companies. Headquartered in Heber City, Utah, we offer powerline and substation construction and maintenance services in a variety of utility markets. Like many Quanta operating companies, Summit Line continues to experience significant growth. As our national operations expand, we seek motivated individuals to join the team!" About This Role: repeats some of About Summit Line Construction? Actually "About This Role About Summit Line Construction Summit Line Construction is a high-voltage electrical utility contractor and Quanta Services company headquartered in Heber City, Utah. The company self-performs transmission line, distribution, substation, and renewable energy construction across the Western U.S., delivering projects that range from routine system upgrades to large-scale greenfield builds. As part of the Quanta Services family, Summit Line operates with the backing of the largest specialty contractor network in North America while maintaining the field-focused culture of a regional contractor that has earned its reputation one structure at a time. Building today what powers tomorrow." Position Summary: "This role supports project controls and scheduling operations across active transmission, distribution, substation, and renewable energy construction projects throughout the Western United States. Working under the direction of the Project Controls Manager and/or an assigned Senior Scheduler, and in coordination with project managers and field leadership, the Junior Scheduler assists in building, maintaining, and analyzing CPM schedules that reflect real field conditions and contractual obligations. The work is detail-intensive, deadline-driven, and directly tied to project performance — candidates should expect to be challenged and developed quickly." Key Responsibilities: bullet list under "What You'll Do" with subheadings: Schedule Development & Maintenance, Schedule Monitoring & Reporting, Collaboration & Field Coordination, Document Control & Data Integrity. Each has multiple bullet points. Required Qualifications: list with items: 1 to 3 years experience..., Bachelor's degree..., Basic working knowledge..., Foundational working knowledge..., Proficiency..., Demonstrated ability..., Strong attention..., Effective written..., Ability to travel... Preferred Qualifications: list items. What You'll Get: bullet list: Medical, dental, and vision insurance; 401(k) retirement plan with company match; Paid vacation and company holidays; Employer-paid life and disability insurance; Direct exposure to large-scale transmission, substation, and renewable energy projects across the Western United States; Mentorship from experienced project controls professionals within the Quanta Services network. Work Environment: description: primarily office-based at headquarters in Heber City, Utah, with hybrid flexibility; field visits and extended project site assignments; travel up to 100%; project sites across Western U.S.; ability to move between office and active construction sites essential. We need to output HTML with

    headings and

    paragraphs and

    • for lists. We need to decide sections. Perhaps:

      About the Role

      (contains About Us, About This Role, Position Summary combined into prose)

      Responsibilities

      (list)

      Requirements

      (Required Qualifications as list)

      Preferred Qualifications

      (list) maybe as "Qualifications"? But we already have Requirements. Could combine Required and Preferred into one Qualifications section with subheadings? But instruction says prefer few substantive sections over many thin ones. Could have Requirements (required) and Preferred Qualifications as separate? Might be thin. Could combine into one "Qualifications" section with two sublists? But we need to use
      • for any list. Could have a

        intro then two

        lists with headings? But headings inside section maybe

        ? Not allowed? Only

        for section headings. Could use for subheadings inside

        . But better to keep separate sections: Requirements and Preferred Qualifications. Benefits:

        Benefits> list. Work Environment: maybe

        Work Environment> paragraph. We must not include Pay or Schedule sections because not specified. We must not include filler like "commensurate with experience". Not present. Now we need to ensure we preserve all substantive info. Let's craft. We'll need to convert bullet points into

        . Ensure we keep the exact wording. Let's extract each bullet. From Key Responsibilities: Schedule Development & Maintenance - Assist in the development of project baseline schedules using Critical Path Method (CPM) logic, incorporating engineering, procurement, permitting, and construction sequences specific to transmission and distribution work - Maintain and update project schedules on a weekly and monthly basis, reflecting actual progress, revised sequencing, and current look-ahead windows - Build activity logic in Primavera P6, linking predecessors and successors to accurately model field workflows such as structure spotting, excavation, concrete pours, framing, stringing, sagging, and energization milestones - Support the development of resource-loaded schedules that align crew deployment plans with project milestones and budgeted labor hours - Perform all scheduling work in accordance with Summit Line Project Controls procedures, CPM Technical Standards & Requirements, contractual scheduling specifications, and approved project-specific requirements Schedule Monitoring & Reporting - Compare actual progress against baseline and generate variance reports that identify activities with negative float or slippage risk - Prepare and distribute two-week look-ahead schedules in coordination with field superintendents and project managers - Produce schedule narrative reports for internal project reviews, owner submittals, and monthly progress reporting packages - Track key project milestones, contractual completion dates, and owner-imposed interim deadlines, flagging conflicts or risks to the project controls team Collaboration & Field Coordination - Work directly with project managers, construction managers, and field superintendents to gather accurate progress data and incorporate field realities into schedule updates - Participate in project schedule review meetings, owner progress meetings, and internal project controls calls - Coordinate with procurement and materials management teams to incorporate equipment and material lead times — including conductor, transformers, transmission structures, and switchgear — into schedule logic - Support the preparation of delay analyses, time impact analyses (TIAs), and schedule recovery plans under the direction of the Project Controls Manager or assigned Senior Scheduler Document Control & Data Integrity - Maintain organized schedule files, revision histories, and update logs in accordance with company and client document control requirements - Assist in the setup and maintenance of project controls templates and schedule standards across active projects - Support project closeout by preparing final as-built schedules and documenting schedule performance metrics Required Qualifications: - 1 to 3 years of experience in construction project controls, scheduling, or a comparable support role - Bachelor's degree in Construction Management, Civil Engineering, Project Management, or a related field — OR equivalent demonstrated experience in a construction project controls or scheduling support role - Basic working knowledge of CPM scheduling methodology and schedule logic concepts - Foundational working knowledge of Primavera P6, or demonstrated ability to successfully complete Summit Line Primavera P6 training - Proficiency in Microsoft Office Suite, particularly Excel; ability to work with large data sets and perform basic schedule analysis - Demonstrated ability to read and interpret construction drawings, specifications, and contract documents - Strong attention to detail with the ability to manage multiple concurrent deadlines without loss of accuracy - Effective written and verbal communication skills; must be able to work productively with field personnel, project managers, and clients - Ability to travel to project sites across the Western U.S. as required — up to 100% travel for certain project assignments Preferred Qualifications: - Hands-on experience building or updating construction schedules in Primavera P6 - Prior internship or work experience with an electrical utility contractor, heavy civil contractor, or specialty subcontractor - Familiarity with transmission or distribution construction scopes, including structure installation, conductor stringing, or substation construction sequences - Exposure to earned value management (EVM) principles or project cost controls - Experience preparing schedule submittals or time impact analyses in a contractor environment