Senior Project Planner Scheduler

We need to output HTML fragment with sections: Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes Company Overview (maybe not needed as heading? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. So we need to map content to these headings. The posting includes "Company Overview" (maybe treat as About the role? Actually "About the role" is typical but we have "Company Overview" and "Role Overview". Could combine into About the role? Probably we can create an "About the role" section containing the company overview and role overview. Then "Responsibilities" from Key Responsibilities. Then "Requirements" from Requirements bullet. Then maybe "Qualifications" could be same as Requirements? But we should not duplicate. The posting includes "Preferred experience..." etc. Could treat Requirements as the bullet list; Qualifications maybe not separate. Skills could be derived from requirements (proficiency in Oracle Primavera P6 etc). Benefits from "Why Should You Apply?" includes benefits. Pay and Schedule: not mentioned explicitly, so we should NOT include those sections. Also we should not include empty sections. Thus produce HTML with sections: About the role, Responsibilities, Requirements, Skills, Benefits. Possibly also Qualifications if we want to separate education vs experience? But we can combine. We must preserve all substantive information, not invent or summarize away detail. Must not omit details. So we need to include all details from company overview, role overview, responsibilities, requirements, benefits. Must not drop any detail. We need to format lists with

• . For prose use

  . For headings use

  . We must not include boilerplate like EEO, etc. Remove EEO lines. Also remove navigation, cookie, legal, etc. Also remove application instructions (none present). Also remove duplicated lines. We need to ensure we keep all substantive content: Let's extract. Company Overview paragraph: "At Mitsubishi Power, we're not just building better clean energy technologies; we're architecting a better future. Our team is boldly redefining power generation to accelerate the world's energy transition. We operate as one team, pushing toward our vision of the future. We value problem solvers, prioritize collaboration, and support each other in an inclusive culture built on accountability and authenticity by demonstrating our values: Safety, Family, Innovative, Inclusive, Accountable & Courageous. Together, we’re building the future we all aspire to - making net zero a reality." Role Overview paragraph: "The Senior Project Scheduler serves as a lead technical authority in project planning and scheduling, responsible for developing, integrating, analyzing, and optimizing complex project schedules across the full project lifecycle. This role drives scheduling strategy, risk identification, critical path management, delay analysis, and recovery planning to support successful project execution. The Senior Project Scheduler leads integration across internal functions and external stakeholders, including EPC contractors, Owner’s Engineers, and suppliers, while ensuring alignment with contractual milestones and providing independent schedule analysis and recommendations to project leadership. The role also supports Earned Value Management and mentors junior schedulers while establishing best practices across the project controls function." Key Responsibilities: a long list bullet points. We need to convert each line into

  . Ensure we keep all. Requirements: bullet list: "Bachelor's degree in Engineering, Construction Management, or a related field from an accredited four-year college or university, with six (6) to eight (8) years of related project planning and scheduling experience. In lieu of a bachelor’s degree, a minimum of ten (10) years of progressively responsible project planning and scheduling experience. Preferred experience planning and scheduling within an EPC environment supporting power generation, energy, or large-scale industrial projects. Experience in other industries may be considered when it demonstrates strong proficiency in critical path scheduling, schedule development, and project controls principles. Advanced proficiency in Oracle Primavera P6, including schedule development, baselining, resource loading, progress updates, and integration. Demonstrated experience with Critical Path Analysis, delay analysis, schedule risk assessment, recovery planning, and forensic schedule analysis. Experience integrating engineering, procurement, manufacturing, construction, commissioning, contractor, and supplier schedules. Knowledge of Earned Value Management, progress measurement, and schedule-cost integration. Ability to read, analyze, and interpret professional journals, technical procedures, business documentation, and governmental regulations. Ability to prepare reports, business correspondence, and procedures and present information effectively to managers, customers, and the public. Strong mathematical, analytical, and reasoning skills, including the ability to evaluate probabilities, percentages, ratios, proportions, and technical instructions. Knowledge of project management databases, spreadsheets, word processing software, electronic mail, graphics, technical diagrams, flow charts, and reporting tools. Ability to travel domestically and internationally up to 20% to 25%." Benefits: from "Why Should You Apply?" paragraph: "Excellent Benefits (Medical, Dental, Vision & 401K Matching). Excellent development programs and advancement opportunities. Tuition reimbursement and on-the-job training. Paid vacation, sick time, and holidays. Committed to quality products and services. Great working environment and culture. Employee Appreciation Programs and Event." We should not include EEO line. Now produce HTML. Structure:

  About the role

  Company overview paragraph + Role overview paragraph? Could combine into one

  with both paragraphs separated by a space or
  . Probably better to have two

  elements? The instruction: use

  for prose. Could have multiple

  . We'll put company overview in one

  , role overview in another

  . Then

  Responsibilities

  with each responsibility as
  • . Then

    Requirements

    with each requirement as
    • . However the requirements are sentences; we could break each sentence into
    • . That preserves detail. Then

      Skills

      maybe we could extract skills from requirements: Advanced proficiency in Oracle Primavera P6, etc. But we already have them in requirements; maybe we can still have Skills section summarizing? But we must not invent or summarize away detail; we could still list skills as separate items but they'd be duplicate. Better to omit Skills section if it would be duplicate. However the instruction says prefer a few substantive sections over many thin ones. We could combine Requirements and Skills into one section? But they ask to use headings for those categories if content exists. We have content for Skills (proficiency in Oracle Primavera P6, Critical Path Analysis, etc). We could create Skills section listing those specific skills, but that would be extracting from requirements, potentially summarizing but not inventing. It's okay to rephrase? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we extract skills from requirements, we are not losing detail if we also keep them in Requirements? Might be duplication but okay. However to avoid duplication, we could keep Requirements as is and not add Skills. But then we would not have a Skills section despite having skill details. The instruction: "Prefer a few substantive sections over many thin ones." It doesn't require us to create a Skills section if we already have them elsewhere. But the heading list is just examples; we only include sections when posting has real, specific content for it. The posting does have specific skill content (proficiency in Oracle Primavera P6, etc). So we could include a Skills section with those items. However we must ensure we don't lose any detail; if we put them only in Skills and not in Requirements, we would lose the degree/experience etc. So we need to keep both. Could keep Requirements section for education/experience, and Skills section for technical proficiencies. That seems reasonable. Thus parse requirements into two groups: education/experience (first two sentences) and preferred experience etc. Then technical skills etc. But to keep it simple, we could just have Requirements section covering all bullet points, and not have Skills section. But then we would not have a Skills section despite having skill-specific content; but the instruction doesn't mandate a Skills section if we already covered them. It says "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's examples, not required to use all. So we can omit Skills if we deem it's covered elsewhere. However the instruction also says "Prefer a few substantive sections over many thin ones." So having many thin sections is discouraged. So better to have fewer sections: About the role, Responsibilities, Requirements, Benefits. That's four sections. That seems good. Thus we will not include Skills section. Now ensure we don't include any boilerplate: Remove EEO lines, also remove "Why Should You Apply?" heading? We'll incorporate benefits under Benefits heading. Now produce HTML. We need to ensure we don't include any extra text outside HTML fragment. Let's craft. About the role: two

      elements. Responsibilities:

      with each bullet. We need to split the responsibilities list into items. Let's copy each line from the posting: - Lead development of Level 1 through Level 4 Oracle Primavera P6 schedules, ensuring proper logic, sequencing, coding, and alignment with the project execution strategy. - Develop and maintain fully integrated project schedules incorporating OEM equipment supply, internal and Owner’s Engineer activities, EPC construction schedules, and interface milestones across all parties. - Define and enforce scheduling standards, coding structures, and Work Breakdown Structure alignment across projects. - Own master schedule integrity by validating logic quality, realistic durations, dependencies, and appropriate constraints. - Perform advanced Critical Path Analysis and monitor near-critical paths, float erosion, and emerging schedule risks. - Develop data-driven mitigation strategies, recovery schedules, and what-if scenarios to address potential delays. - Lead schedule integration with EPC contractors and partners through alignment workshops, logic validation, interface management, and cross-schedule dependency mapping. - Provide monthly independent assessments of EPC schedule performance, credibility, progress, and forecasted completion dates. - Analyze and validate contractor schedules against contractual obligations and project milestones. - Perform detailed forensic schedule analysis, including Time Impact Analysis and window analysis. - Evaluate delays involving engineering, procurement, manufacturing, construction, and commissioning activities. - Support Project Management and Legal teams with schedule-based claims analysis, documentation, and technical findings. - Ensure schedules are resource-loaded and aligned with cost structures to support accurate Earned Value Management reporting. - Support development of rules of credit and progress measurement methodologies. - Validate schedule-driven progress against actual project performance. - Provide executive-level insights on milestone status, critical path changes, schedule risks, and recovery actions. - Develop clear, concise schedule reports for leadership, customers, and project stakeholders. - Present schedule analysis during customer meetings, monthly reviews, and executive briefings. - Serve as the primary scheduling interface with Project Management, Supply Chain, Engineering, Construction, EPC partners, and Commissioning teams. - Ensure alignment among schedule, cost, contractual milestones, and execution strategy. - Mentor and guide Project Schedulers and junior project controls team members. - Review baseline and update schedules prepared by others for compliance with scheduling standards and best practices. - Support continuous improvement of scheduling methodologies, templates, processes, and tools. - Travel to project sites as required to provide onsite scheduling support during construction, commissioning, and other critical project phases. - Comply with safety policies, protect confidential information, and maintain the highest standards of honesty and integrity. - Perform other duties as assigned. Now Requirements: list each sentence as
      • . Let's split: - Bachelor's degree in Engineering, Construction Management, or a related field from an accredited four-year college or university, with six (6) to eight (8) years of related project planning and scheduling experience. - In lieu of a bachelor’s degree, a minimum of ten (10) years of progressively responsible project planning and scheduling experience. - Preferred experience planning and scheduling within an EPC environment supporting power generation, energy, or large-scale industrial projects. - Experience in other industries may be considered when it demonstrates strong proficiency