Scheduler II
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 parse the posting.
Content:
Intro: "At Haskell, you’re not just joining a company—you’re joining a nationally recognized Top Workplace where diverse perspectives and inclusive thinking drive stronger outcomes. Whether you’re starting out, growing your expertise, or leading the way, you’ll find a culture grounded in trust, driven by excellence, and built to support your goals. Here, you’ll have the opportunity, flexibility, and sense of belonging to grow your career your way—while making a real impact."
That's about company culture; could be "About the role" or maybe "About Haskell". We'll use "About the role" as heading.
Next: "Scope of Position Functions as a scheduling system and process technical lead. Effectively manages and oversees planning and scheduling efforts with project and market teams. Compile, analyze, leverage, and communicate data pertaining to the development, progress, and changes of the project schedule. Leads training efforts regarding scheduling systems, processes, and utilization."
That's description of role; could be part of About the role or separate "Scope". But we can incorporate into About the role.
Then "Job Responsibilities" heading with bullet list of responsibilities.
Then "Education & Years Of Experience" heading with requirements.
Then "Qualifications" heading with bullet list.
Then "Foundational Competencies" heading with categories (Strategy, Delivery, Interpersonal). Might be considered "Skills" or "Competencies". Could be a section "Skills". The instruction says we can use Skills heading. So we can put that under Skills.
Then "Values" heading with list of values (Team, Excellence, Service, Trust). Could be part of culture but maybe we can include under "About the role" or separate "Values". But we need to avoid thin sections. Might combine Values into About the role or Skills? Probably better to have a separate "Values" section? But instruction says prefer a few substantive sections over many thin ones. Values list is substantive; could be its own section "Values". However they gave example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list Values but we can still use other headings? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, not exclusive. So we can add other headings if needed, but better to stick to those if possible. Values could be part of About the role or Skills. I'd incorporate Values into About the role paragraph.
Then "Environmental Factors And Physical Requirements" heading with details. That could be part of "Requirements" or maybe "Qualifications". Could be a separate section "Requirements". We'll treat that as Requirements.
Then "Haskell will make reasonable accommodations..." that's EEO boilerplate; remove.
Then "The job description will be reviewed periodically..." boilerplate; remove.
Then "Essential and marginal job functions are subject to modification." boilerplate; remove.
Then "Haskell is a Drug-Free Workplace, and an Equal Opportunity Employer..." boilerplate; remove.
Thus we need to output sections: About the role (including intro, scope, values), Responsibilities (list), Requirements (education/experience, environmental/physical), Qualifications (list), Skills (foundational competencies). Possibly also "Benefits", "Pay", "Schedule" not present, so omit.
We must not repeat job title. No metadata.
We need to preserve all substantive information. Let's extract.
Intro paragraph: At Haskell, you’re not just joining a company—you’re joining a nationally recognized Top Workplace where diverse perspectives and inclusive thinking drive stronger outcomes. Whether you’re starting out, growing your expertise, or leading the way, you’ll find a culture grounded in trust, driven by excellence, and built to support your goals. Here, you’ll have the opportunity, flexibility, and sense of belonging to grow your career your way—while making a real impact.
Scope of Position: Functions as a scheduling system and process technical lead. Effectively manages and oversees planning and scheduling efforts with project and market teams. Compile, analyze, leverage, and communicate data pertaining to the development, progress, and changes of the project schedule. Leads training efforts regarding scheduling systems, processes, and utilization.
We can combine these into About the role paragraph(s). Might be two paragraphs.
Responsibilities list: Let's extract each bullet from "Job Responsibilities" paragraph (it's a long sentence with many items separated by periods). We need to turn into - . The text:
"Demonstrate full competency in the system scheduling tools and scheduling best practices.
Manage scheduling and planning efforts including scheduling processes during the project and program development and execution.
Understands the impacts of all contractual and project requirements and can apply and communicate them to the project schedules and processes as necessary.
Leads and ensures schedule data integrity efforts in accordance with best practices and company standards.
Produce and distribute tailored schedule reporting to meet the project team’s needs that effectively communicate issues, status, health, and progress of the execution plan.
Manage the scheduling cycle to meet the needs of the project while following Haskell Policy, including but not limited to actualizing and updating, reports, narratives, time impact analysis, and fragnet schedules.
Lead communication efforts regarding the schedule to project teams, subcontract partners, clients, and internal leadership.
Apply full understanding of change impact management and able to support and guide project teams as changes arise.
Apply and effectively utilize resource and cost loading as necessary.
Support project teams by providing data for forecasting purposes.
Produce, analyze, and distill schedule data with full competency and understanding.
Engage proactively with risk management of schedule data being able to proactively report to the project teams.
Lead and develop training in scheduling best practices, processes, and tools.
Responsible for peer review of schedules for integrity, quality, and best practices as necessary.
Manages project scheduling teams or schedulers.
Travel, as necessary, to lead and support scheduling efforts
Participates in industry events and conferences.
Lead and support continual improvement of scheduling practices and processes
Other duties which may be assigned as needed.
Supervises others."
We need to ensure each is a list item.
Requirements: Education & Years Of Experience: "Four-year degree in engineering or construction management, eight years of scheduling or construction management experience, with a minimum of 4 years directly related to scheduling, or 10 plus years’ relevant experience in lieu of degree."
Also maybe include "Experience in a commercial contracting environment preferred." That's under Qualifications? Actually it's under Qualifications heading: "Experience in a commercial contracting environment preferred." So that's a qualification.
Also "Proficiency in Primavera scheduling software including cost/resource loading and analysis." etc.
Also "Solid analytic ability with excellent written and verbal communications skills required."
Also "Ability to organize and manage complex tasks, establish and meet schedules and maintain focus on goals."
Also "Proficiency in industry planning and scheduling practices and construction methods"
These are qualifications.
We also have "Foundational Competencies" with subcategories: Strategy - Planning for the Future: Developing talent, organizational alignment, strategic networking, and strategic thinking. Delivery - Achieving Results: Analytical thinking, problem solving and decision making, results driven, flexible thinking, managing resources, teamwork, and team leadership. Interpersonal - Building Relationships: Customer focus, influencing, negotiating, organizational knowledge, communication and presence, and diversity and inclusion.
We can treat these as Skills.
Environmental Factors And Physical Requirements: "While performing the duties of this job, team members may be required to visit alternate locations and therefore, must have ordinary ambulatory skills sufficient to do so. This position requires the ability to stand, walk, stoop, kneel, crouch, and manipulate (lift, carry, move) light to medium weights of 10-50 pounds. Requires good hand-eye coordination, arm, hand, and finger dexterity, including ability to grasp, and visual acuity to use a keyboard, operate equipment and read application/form information. The team member is frequently required to sit, reach with hands and arms, talk, and hear."
We'll put that under Requirements (maybe as a subsection). Could be its own section "Requirements". We'll include both education/experience and physical requirements under Requirements.
Now we need to output HTML fragment with
headings and
or
- .
We must not include any boilerplate.
Let's craft:
About the role
At Haskell, you’re not just joining a company—you’re joining a nationally recognized Top Workplace where diverse perspectives and inclusive thinking drive stronger outcomes. Whether you’re starting out, growing your expertise, or leading the way, you’ll find a culture grounded in trust, driven by excellence, and built to support your goals. Here, you’ll have the opportunity, flexibility, and sense of belonging to grow your career your way—while making a real impact.
Functions as a scheduling system and process technical lead. Effectively manages and oversees planning and scheduling efforts with project and market teams. Compiles, analyzes, leverages, and communicates data pertaining to the development, progress, and changes of the project schedule. Leads training efforts regarding scheduling systems, processes, and utilization.
Then Responsibilities:
Responsibilities
- Demonstrate full competency in the system scheduling tools and scheduling best practices.
- Manage scheduling and planning efforts including scheduling processes during the project and program development and execution.
- Understands the impacts of all contractual and project requirements and can apply and communicate them to the project schedules and processes as necessary.
- Leads and ensures schedule data integrity efforts in accordance with best practices and company standards.
- Produce and distribute tailored schedule reporting to meet the project team’s needs that effectively communicate issues, status, health, and progress of the execution plan.
- Manage the scheduling cycle to meet the needs of the project while following Haskell Policy, including but not limited to actualizing and updating, reports, narratives, time impact analysis, and fragnet schedules.
- Lead communication efforts regarding the schedule to project teams, subcontract partners, clients, and internal leadership.
- Apply full understanding of change impact management and able to support and guide project teams as changes arise.
- Apply and effectively utilize resource and cost loading as necessary.
- Support project teams by providing data for forecasting purposes.
- Produce, analyze, and distill schedule data with full competency and understanding.
- Engage proactively with risk management of schedule data being able to proactively report to the project teams.
- Lead and develop training in scheduling best practices, processes, and tools.
- Responsible for peer review of schedules for integrity, quality, and best practices as necessary.
- Manages project scheduling teams or schedulers.
- Travel, as necessary, to lead 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 parse the posting. Content: Intro: "At Haskell, you’re not just joining a company—you’re joining a nationally recognized Top Workplace where diverse perspectives and inclusive thinking drive stronger outcomes. Whether you’re starting out, growing your expertise, or leading the way, you’ll find a culture grounded in trust, driven by excellence, and built to support your goals. Here, you’ll have the opportunity, flexibility, and sense of belonging to grow your career your way—while making a real impact." That's about company culture; could be "About the role" or maybe "About Haskell". We'll use "About the role" as heading. Next: "Scope of Position Functions as a scheduling system and process technical lead. Effectively manages and oversees planning and scheduling efforts with project and market teams. Compile, analyze, leverage, and communicate data pertaining to the development, progress, and changes of the project schedule. Leads training efforts regarding scheduling systems, processes, and utilization." That's description of role; could be part of About the role or separate "Scope". But we can incorporate into About the role. Then "Job Responsibilities" heading with bullet list of responsibilities. Then "Education & Years Of Experience" heading with requirements. Then "Qualifications" heading with bullet list. Then "Foundational Competencies" heading with categories (Strategy, Delivery, Interpersonal). Might be considered "Skills" or "Competencies". Could be a section "Skills". The instruction says we can use Skills heading. So we can put that under Skills. Then "Values" heading with list of values (Team, Excellence, Service, Trust). Could be part of culture but maybe we can include under "About the role" or separate "Values". But we need to avoid thin sections. Might combine Values into About the role or Skills? Probably better to have a separate "Values" section? But instruction says prefer a few substantive sections over many thin ones. Values list is substantive; could be its own section "Values". However they gave example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list Values but we can still use other headings? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, not exclusive. So we can add other headings if needed, but better to stick to those if possible. Values could be part of About the role or Skills. I'd incorporate Values into About the role paragraph.
Then "Environmental Factors And Physical Requirements" heading with details. That could be part of "Requirements" or maybe "Qualifications". Could be a separate section "Requirements". We'll treat that as Requirements.
Then "Haskell will make reasonable accommodations..." that's EEO boilerplate; remove.
Then "The job description will be reviewed periodically..." boilerplate; remove.
Then "Essential and marginal job functions are subject to modification." boilerplate; remove.
Then "Haskell is a Drug-Free Workplace, and an Equal Opportunity Employer..." boilerplate; remove.
Thus we need to output sections: About the role (including intro, scope, values), Responsibilities (list), Requirements (education/experience, environmental/physical), Qualifications (list), Skills (foundational competencies). Possibly also "Benefits", "Pay", "Schedule" not present, so omit.
We must not repeat job title. No metadata.
We need to preserve all substantive information. Let's extract.
Intro paragraph: At Haskell, you’re not just joining a company—you’re joining a nationally recognized Top Workplace where diverse perspectives and inclusive thinking drive stronger outcomes. Whether you’re starting out, growing your expertise, or leading the way, you’ll find a culture grounded in trust, driven by excellence, and built to support your goals. Here, you’ll have the opportunity, flexibility, and sense of belonging to grow your career your way—while making a real impact.
Scope of Position: Functions as a scheduling system and process technical lead. Effectively manages and oversees planning and scheduling efforts with project and market teams. Compile, analyze, leverage, and communicate data pertaining to the development, progress, and changes of the project schedule. Leads training efforts regarding scheduling systems, processes, and utilization.
We can combine these into About the role paragraph(s). Might be two paragraphs.
Responsibilities list: Let's extract each bullet from "Job Responsibilities" paragraph (it's a long sentence with many items separated by periods). We need to turn into - . The text:
"Demonstrate full competency in the system scheduling tools and scheduling best practices.
Manage scheduling and planning efforts including scheduling processes during the project and program development and execution.
Understands the impacts of all contractual and project requirements and can apply and communicate them to the project schedules and processes as necessary.
Leads and ensures schedule data integrity efforts in accordance with best practices and company standards.
Produce and distribute tailored schedule reporting to meet the project team’s needs that effectively communicate issues, status, health, and progress of the execution plan.
Manage the scheduling cycle to meet the needs of the project while following Haskell Policy, including but not limited to actualizing and updating, reports, narratives, time impact analysis, and fragnet schedules.
Lead communication efforts regarding the schedule to project teams, subcontract partners, clients, and internal leadership.
Apply full understanding of change impact management and able to support and guide project teams as changes arise.
Apply and effectively utilize resource and cost loading as necessary.
Support project teams by providing data for forecasting purposes.
Produce, analyze, and distill schedule data with full competency and understanding.
Engage proactively with risk management of schedule data being able to proactively report to the project teams.
Lead and develop training in scheduling best practices, processes, and tools.
Responsible for peer review of schedules for integrity, quality, and best practices as necessary.
Manages project scheduling teams or schedulers.
Travel, as necessary, to lead and support scheduling efforts
Participates in industry events and conferences.
Lead and support continual improvement of scheduling practices and processes
Other duties which may be assigned as needed.
Supervises others."
We need to ensure each is a list item.
Requirements: Education & Years Of Experience: "Four-year degree in engineering or construction management, eight years of scheduling or construction management experience, with a minimum of 4 years directly related to scheduling, or 10 plus years’ relevant experience in lieu of degree."
Also maybe include "Experience in a commercial contracting environment preferred." That's under Qualifications? Actually it's under Qualifications heading: "Experience in a commercial contracting environment preferred." So that's a qualification.
Also "Proficiency in Primavera scheduling software including cost/resource loading and analysis." etc.
Also "Solid analytic ability with excellent written and verbal communications skills required."
Also "Ability to organize and manage complex tasks, establish and meet schedules and maintain focus on goals."
Also "Proficiency in industry planning and scheduling practices and construction methods"
These are qualifications.
We also have "Foundational Competencies" with subcategories: Strategy - Planning for the Future: Developing talent, organizational alignment, strategic networking, and strategic thinking. Delivery - Achieving Results: Analytical thinking, problem solving and decision making, results driven, flexible thinking, managing resources, teamwork, and team leadership. Interpersonal - Building Relationships: Customer focus, influencing, negotiating, organizational knowledge, communication and presence, and diversity and inclusion.
We can treat these as Skills.
Environmental Factors And Physical Requirements: "While performing the duties of this job, team members may be required to visit alternate locations and therefore, must have ordinary ambulatory skills sufficient to do so. This position requires the ability to stand, walk, stoop, kneel, crouch, and manipulate (lift, carry, move) light to medium weights of 10-50 pounds. Requires good hand-eye coordination, arm, hand, and finger dexterity, including ability to grasp, and visual acuity to use a keyboard, operate equipment and read application/form information. The team member is frequently required to sit, reach with hands and arms, talk, and hear."
We'll put that under Requirements (maybe as a subsection). Could be its own section "Requirements". We'll include both education/experience and physical requirements under Requirements.
Now we need to output HTML fragment with
headings and
or
- .
We must not include any boilerplate.
Let's craft:
About the role
At Haskell, you’re not just joining a company—you’re joining a nationally recognized Top Workplace where diverse perspectives and inclusive thinking drive stronger outcomes. Whether you’re starting out, growing your expertise, or leading the way, you’ll find a culture grounded in trust, driven by excellence, and built to support your goals. Here, you’ll have the opportunity, flexibility, and sense of belonging to grow your career your way—while making a real impact.
Functions as a scheduling system and process technical lead. Effectively manages and oversees planning and scheduling efforts with project and market teams. Compiles, analyzes, leverages, and communicates data pertaining to the development, progress, and changes of the project schedule. Leads training efforts regarding scheduling systems, processes, and utilization.
Then Responsibilities:
Responsibilities
- Demonstrate full competency in the system scheduling tools and scheduling best practices.
- Manage scheduling and planning efforts including scheduling processes during the project and program development and execution.
- Understands the impacts of all contractual and project requirements and can apply and communicate them to the project schedules and processes as necessary.
- Leads and ensures schedule data integrity efforts in accordance with best practices and company standards.
- Produce and distribute tailored schedule reporting to meet the project team’s needs that effectively communicate issues, status, health, and progress of the execution plan.
- Manage the scheduling cycle to meet the needs of the project while following Haskell Policy, including but not limited to actualizing and updating, reports, narratives, time impact analysis, and fragnet schedules.
- Lead communication efforts regarding the schedule to project teams, subcontract partners, clients, and internal leadership.
- Apply full understanding of change impact management and able to support and guide project teams as changes arise.
- Apply and effectively utilize resource and cost loading as necessary.
- Support project teams by providing data for forecasting purposes.
- Produce, analyze, and distill schedule data with full competency and understanding.
- Engage proactively with risk management of schedule data being able to proactively report to the project teams.
- Lead and develop training in scheduling best practices, processes, and tools.
- Responsible for peer review of schedules for integrity, quality, and best practices as necessary.
- Manages project scheduling teams or schedulers.
- Travel, as necessary, to lead and
headings and
or
- .
We must not include any boilerplate.
Let's craft:
About the role
At Haskell, you’re not just joining a company—you’re joining a nationally recognized Top Workplace where diverse perspectives and inclusive thinking drive stronger outcomes. Whether you’re starting out, growing your expertise, or leading the way, you’ll find a culture grounded in trust, driven by excellence, and built to support your goals. Here, you’ll have the opportunity, flexibility, and sense of belonging to grow your career your way—while making a real impact.
Functions as a scheduling system and process technical lead. Effectively manages and oversees planning and scheduling efforts with project and market teams. Compiles, analyzes, leverages, and communicates data pertaining to the development, progress, and changes of the project schedule. Leads training efforts regarding scheduling systems, processes, and utilization.
Then Responsibilities:Responsibilities
- Demonstrate full competency in the system scheduling tools and scheduling best practices.
- Manage scheduling and planning efforts including scheduling processes during the project and program development and execution.
- Understands the impacts of all contractual and project requirements and can apply and communicate them to the project schedules and processes as necessary.
- Leads and ensures schedule data integrity efforts in accordance with best practices and company standards.
- Produce and distribute tailored schedule reporting to meet the project team’s needs that effectively communicate issues, status, health, and progress of the execution plan.
- Manage the scheduling cycle to meet the needs of the project while following Haskell Policy, including but not limited to actualizing and updating, reports, narratives, time impact analysis, and fragnet schedules.
- Lead communication efforts regarding the schedule to project teams, subcontract partners, clients, and internal leadership.
- Apply full understanding of change impact management and able to support and guide project teams as changes arise.
- Apply and effectively utilize resource and cost loading as necessary.
- Support project teams by providing data for forecasting purposes.
- Produce, analyze, and distill schedule data with full competency and understanding.
- Engage proactively with risk management of schedule data being able to proactively report to the project teams.
- Lead and develop training in scheduling best practices, processes, and tools.
- Responsible for peer review of schedules for integrity, quality, and best practices as necessary.
- Manages project scheduling teams or schedulers.
- Travel, as necessary, to lead and