Project Scheduler
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Include only sections with real content. The posting includes "About The Role" (which is like About the role). Then "Primary Responsibilities" (Responsibilities). Then "Experience" (maybe Requirements? Actually Experience is part of qualifications). Then "Education". Then "Knowledge & Skills". Then "Travel". Then "About WEG Electric Corp." (company description). Then "We offer a pleasant work environment, competitive compensation, and a full benefits package." (Benefits). Also "To Apply:" etc which we need to drop (application instructions). Also EEO etc drop. Also "While the start date has not yet been determined..." is metadata; we can fold into short p or drop. Also "Preferred location: Atlanta-Metro, GA..." location info; we can include maybe in About the role? Could be part of role description. We'll include as a short p.
We need to preserve all substantive information, not invent. No placeholder sections like Pay or Schedule unless present. There's no explicit pay or schedule details. Travel is mentioned but not schedule. So we should not create Pay or Schedule sections. Benefits: we have "We offer a pleasant work environment, competitive compensation, and a full benefits package." That's benefits content. So we can create Benefits section with that sentence.
Qualifications: maybe combine Experience and Education as Qualifications? The instruction says use headings like Qualifications, Skills, etc. We have Experience, Education, Knowledge & Skills. Could map Experience+Education to Qualifications, Knowledge & Skills to Skills. But we need to preserve all info; we can create Qualifications section containing Experience and Education subpoints? However we must not invent headings not in list? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning we can use those headings. It doesn't forbid other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings where appropriate. So we should map content to those headings. Let's decide:
- About the role: use the "About The Role" paragraph.
- Responsibilities: use "Primary Responsibilities" content (the bullet-like paragraphs). We'll need to convert to - for any list of duties/requirements/benefits. The responsibilities are in paragraphs with sentences; we can treat each sentence as a list item? The instruction: "Use
- for any list of duties/requirements/benefits". The responsibilities are a list of duties; we can make each duty a
- . We'll need to parse the responsibilities section into items.
Responsibilities text includes multiple paragraphs each starting with a bold heading? Actually the text:
"Primary Responsibilities
Project Scheduling & Planning
Develop and maintain integrated project schedules covering engineering, procurement, manufacturing, logistics, construction, commissioning, customer acceptance, and project closeout activities.Create schedule baselines, work breakdown structures (WBS), activity logic, milestones, calendars, and responsibility assignments.Incorporate contractual milestones, customer commitments, vendor activities, long-lead items, manufacturing requirements, and project interfaces into project schedules.Identify critical path activities, schedule constraints, float erosion, and potential impacts to key project milestones.Support project change management activities and ensure approved schedule changes are properly reflected in project plans.
Schedule Analysis & Reporting
Maintain project schedules through regular updates, forecasting, and progress measurement activities.Prepare look-ahead schedules, schedule narratives, variance analyses, and critical path assessments.Provide Project Managers with schedule performance insights, emerging risks, and recommended mitigation strategies.Analyze schedule delays, identify root causes, and support recovery planning efforts.Support project reviews, customer meetings, management updates, and monthly project reporting requirements.
Project Controls & Stakeholder Coordination
Support project controls activities, including forecasting, progress measurement, risk management, reporting, and change management.Coordinate with Project Controllers and project teams to provide schedule information supporting financial forecasting, milestone billing, and project reporting.Participate in project kickoffs, progress reviews, vendor meetings, factory coordination meetings, and customer discussions.Maintain schedule documentation, reports, narratives, and supporting records within approved project management systems.
Proposal Support & Continuous Improvement
Develop preliminary schedules and execution plans supporting EPC bids, proposals, and project pursuits.Review schedules for resource conflicts, sequencing concerns, long-lead risks, and execution constraints.Support development of scheduling standards, templates, and project planning tools.Identify opportunities to improve scheduling accuracy, forecasting, reporting, and project execution performance.Leverage AI-enabled tools and technologies where appropriate to improve scheduling efficiency, reporting, and project decision-making."
We can split each bold heading as a group, but we can just make each sentence as
- . However we need to preserve all info; we could keep the headings as plain text inside
- or separate . Probably okay to keep headings as part of
- text.
Simplify: create
with each duty as - containing the sentences.
Similarly for Requirements: we have Experience, Education, Knowledge & Skills. Could combine Experience and Education into Requirements? Actually Requirements could be experience and education. Qualifications could be certifications? But we have "Planning & Scheduling Professional (PSP), Project Management Professional (PMP), Primavera P6 certification, or equivalent training preferred." That's under Experience section? Actually it's under Experience bullet list: "Planning & Scheduling Professional (PSP), Project Management Professional (PMP), Primavera P6 certification, or equivalent training preferred." That's a qualification.
We could map:
- Requirements: Experience (5+ years etc) and Education.
- Qualifications: Certifications/preferred training.
- Skills: Knowledge & Skills section.
But the instruction says we can use those headings; we need to include a section only when posting has real specific content. So we can include Requirements, Qualifications, Skills, Benefits.
Let's extract:
Experience:
- 5+ years of experience in project scheduling, project controls, construction planning, engineering planning, manufacturing planning, or a related discipline.
- Experience developing and maintaining schedules for EPC, industrial, infrastructure, manufacturing, ETO, or large capital projects.
- Demonstrated experience performing schedule analysis, forecasting, variance reporting, and recovery planning.
- Experience working with engineering organizations, vendors, manufacturers, subcontractors, and field execution teams preferred.
- Planning & Scheduling Professional (PSP), Project Management Professional (PMP), Primavera P6 certification, or equivalent training preferred.
Education:
- Bachelor's degree in Engineering, Construction Management, Project Management, or a related discipline preferred.
- Equivalent combinations of education, certifications, and directly related experience will be considered.
Knowledge & Skills:
- Technical Expertise: Advanced proficiency with Primavera P6 and strong working knowledge of project scheduling and project controls principles.
- Proficiency with Microsoft Project and Microsoft Office applications, particularly Excel, Word, and PowerPoint.
- Knowledge of Critical Path Method (CPM) scheduling, forecasting, progress measurement, float analysis, schedule risk assessment, and recovery planning.
- Experience with Autodesk Construction Cloud, Autodesk Forma, Procore, or similar project management platforms preferred.
- Understanding of engineering, procurement, manufacturing, construction, commissioning, and project closeout activities.
- Leadership & Communication: Collaborates effectively with project managers, engineers, manufacturing teams, vendors, contractors, and customers.
- Communicates schedule risks, impacts, assumptions, and recommendations clearly to stakeholders at all levels.
- Influences project decisions through data-driven analysis and effective reporting.
- Strategic Thinking: Proactively identifies schedule risks and recommends mitigation strategies before project milestones are impacted.
- Balances multiple projects and competing priorities in a dynamic environment.
- Continuously seeks opportunities to improve scheduling processes, forecasting accuracy, and cross-functional project execution.
Travel: "Travel may be required based on project requirements, customer needs, and business priorities. Travel is expected to be occasional and determined on a project-by-project basis." This could be placed maybe under Responsibilities? But we have no Travel heading in allowed list; we could incorporate into Responsibilities as a duty? Or we could create a Schedule section? Not appropriate. Probably we can include Travel as a short p under About the role or Responsibilities? The instruction says we can fold minor metadata into a short
or drop it. Travel is not minor metadata? It's a condition. Could be placed as a short p after Responsibilities. But we must not create a Schedule section unless posting actually states them. Travel is not schedule. So we can add a
about travel after Responsibilities.
Benefits: "We offer a pleasant work environment, competitive compensation, and a full benefits package."
Also there is a line about "While the start date has not yet been determined, we're interested in speaking with project scheduling professionals who may be exploring future opportunities due to project completion, contract expiration, relocation, or long-term career planning. Preferred location: Atlanta-Metro, GA, with a strong preference for candidates within commuting distance of our Duluth, GA headquarters." This is metadata; we can fold into a short p maybe under About the role.
Also "About WEG Electric Corp." description is company info; we could include as a short p maybe under About the role? Or we could drop? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company description is not boilerplate; it's substantive info about employer. Should we keep? Likely yes, as it's part of posting. We can include as a short p maybe under About the role or separate section? There's no heading for company info; we could just include as a
after About the role.
We must not repeat the job title as a heading. The job title is "Project Scheduler". Not used.
Now produce HTML fragment:
About the role
Serve as the Project Scheduler responsible for developing, maintaining, and analyzing integrated project schedules for complex engineered-to-order (ETO), systems, and EPC projects. Supporting projects from order handoff through closeout, you will work closely with Project Managers, engineering teams, manufacturing facilities, vendors, subcontractors, and customers to establish schedule baselines, monitor progress, identify schedule risks, and support successful project execution. This role plays a key part in project forecasting and delivery by providing schedule visibility, critical path analysis, risk identification, and recovery planning across the full project lifecycle. The Project Scheduler serves as a trusted partner to project teams, helping drive informed decisions through accurate planning, reporting, and schedule performance analysis. When project workload permits, the Project Scheduler will also support proposal development, schedule standardization initiatives, and continuous improvement efforts across the Project Management organization. While the start date has not yet been determined, we're interested in speaking with project scheduling professionals who may be exploring future opportunities due to project completion, contract expiration, relocation, or long-term career planning. Preferred location: Atlanta-Metro, GA, with a strong preference for candidates within commuting distance of our Duluth, GA headquarters.
WEG Electric Corp. is the largest industrial electric motor manufacturer in the Americas and one of the largest electric motor manufacturers in the world, producing more than 21 million units annually. Founded in 1961, WEG Electric Corp. operates mainly in the capital goods sector and has five main businesses: Motors, Energy, Automation, Coatings, and Transmission & Distribution, providing global solutions for electric motors, variable frequency drives, soft starters, controls, panels, transformers, and generators. The US corporate office is in Duluth, GA, with manufacturing units in Minnesota, Indiana, and Missouri, and over 30,000 employees worldwide. Visit our website to learn more: www.weg.net
Responsibilities
- Project Scheduling & Planning: Develop and
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings where appropriate. So we should map content to those headings. Let's decide:
- About the role: use the "About The Role" paragraph.
- Responsibilities: use "Primary Responsibilities" content (the bullet-like paragraphs). We'll need to convert to - for any list of duties/requirements/benefits. The responsibilities are in paragraphs with sentences; we can treat each sentence as a list item? The instruction: "Use
- for any list of duties/requirements/benefits". The responsibilities are a list of duties; we can make each duty a
- . We'll need to parse the responsibilities section into items.
Responsibilities text includes multiple paragraphs each starting with a bold heading? Actually the text:
"Primary Responsibilities
Project Scheduling & Planning
Develop and maintain integrated project schedules covering engineering, procurement, manufacturing, logistics, construction, commissioning, customer acceptance, and project closeout activities.Create schedule baselines, work breakdown structures (WBS), activity logic, milestones, calendars, and responsibility assignments.Incorporate contractual milestones, customer commitments, vendor activities, long-lead items, manufacturing requirements, and project interfaces into project schedules.Identify critical path activities, schedule constraints, float erosion, and potential impacts to key project milestones.Support project change management activities and ensure approved schedule changes are properly reflected in project plans.
Schedule Analysis & Reporting
Maintain project schedules through regular updates, forecasting, and progress measurement activities.Prepare look-ahead schedules, schedule narratives, variance analyses, and critical path assessments.Provide Project Managers with schedule performance insights, emerging risks, and recommended mitigation strategies.Analyze schedule delays, identify root causes, and support recovery planning efforts.Support project reviews, customer meetings, management updates, and monthly project reporting requirements.
Project Controls & Stakeholder Coordination
Support project controls activities, including forecasting, progress measurement, risk management, reporting, and change management.Coordinate with Project Controllers and project teams to provide schedule information supporting financial forecasting, milestone billing, and project reporting.Participate in project kickoffs, progress reviews, vendor meetings, factory coordination meetings, and customer discussions.Maintain schedule documentation, reports, narratives, and supporting records within approved project management systems.
Proposal Support & Continuous Improvement
Develop preliminary schedules and execution plans supporting EPC bids, proposals, and project pursuits.Review schedules for resource conflicts, sequencing concerns, long-lead risks, and execution constraints.Support development of scheduling standards, templates, and project planning tools.Identify opportunities to improve scheduling accuracy, forecasting, reporting, and project execution performance.Leverage AI-enabled tools and technologies where appropriate to improve scheduling efficiency, reporting, and project decision-making."
We can split each bold heading as a group, but we can just make each sentence as
- . However we need to preserve all info; we could keep the headings as plain text inside
- or separate . Probably okay to keep headings as part of
- text.
Simplify: create
with each duty as - containing the sentences.
Similarly for Requirements: we have Experience, Education, Knowledge & Skills. Could combine Experience and Education into Requirements? Actually Requirements could be experience and education. Qualifications could be certifications? But we have "Planning & Scheduling Professional (PSP), Project Management Professional (PMP), Primavera P6 certification, or equivalent training preferred." That's under Experience section? Actually it's under Experience bullet list: "Planning & Scheduling Professional (PSP), Project Management Professional (PMP), Primavera P6 certification, or equivalent training preferred." That's a qualification.
We could map:
- Requirements: Experience (5+ years etc) and Education.
- Qualifications: Certifications/preferred training.
- Skills: Knowledge & Skills section.
But the instruction says we can use those headings; we need to include a section only when posting has real specific content. So we can include Requirements, Qualifications, Skills, Benefits.
Let's extract:
Experience:
- 5+ years of experience in project scheduling, project controls, construction planning, engineering planning, manufacturing planning, or a related discipline.
- Experience developing and maintaining schedules for EPC, industrial, infrastructure, manufacturing, ETO, or large capital projects.
- Demonstrated experience performing schedule analysis, forecasting, variance reporting, and recovery planning.
- Experience working with engineering organizations, vendors, manufacturers, subcontractors, and field execution teams preferred.
- Planning & Scheduling Professional (PSP), Project Management Professional (PMP), Primavera P6 certification, or equivalent training preferred.
Education:
- Bachelor's degree in Engineering, Construction Management, Project Management, or a related discipline preferred.
- Equivalent combinations of education, certifications, and directly related experience will be considered.
Knowledge & Skills:
- Technical Expertise: Advanced proficiency with Primavera P6 and strong working knowledge of project scheduling and project controls principles.
- Proficiency with Microsoft Project and Microsoft Office applications, particularly Excel, Word, and PowerPoint.
- Knowledge of Critical Path Method (CPM) scheduling, forecasting, progress measurement, float analysis, schedule risk assessment, and recovery planning.
- Experience with Autodesk Construction Cloud, Autodesk Forma, Procore, or similar project management platforms preferred.
- Understanding of engineering, procurement, manufacturing, construction, commissioning, and project closeout activities.
- Leadership & Communication: Collaborates effectively with project managers, engineers, manufacturing teams, vendors, contractors, and customers.
- Communicates schedule risks, impacts, assumptions, and recommendations clearly to stakeholders at all levels.
- Influences project decisions through data-driven analysis and effective reporting.
- Strategic Thinking: Proactively identifies schedule risks and recommends mitigation strategies before project milestones are impacted.
- Balances multiple projects and competing priorities in a dynamic environment.
- Continuously seeks opportunities to improve scheduling processes, forecasting accuracy, and cross-functional project execution.
Travel: "Travel may be required based on project requirements, customer needs, and business priorities. Travel is expected to be occasional and determined on a project-by-project basis." This could be placed maybe under Responsibilities? But we have no Travel heading in allowed list; we could incorporate into Responsibilities as a duty? Or we could create a Schedule section? Not appropriate. Probably we can include Travel as a short p under About the role or Responsibilities? The instruction says we can fold minor metadata into a short
or drop it. Travel is not minor metadata? It's a condition. Could be placed as a short p after Responsibilities. But we must not create a Schedule section unless posting actually states them. Travel is not schedule. So we can add a
about travel after Responsibilities.
Benefits: "We offer a pleasant work environment, competitive compensation, and a full benefits package."
Also there is a line about "While the start date has not yet been determined, we're interested in speaking with project scheduling professionals who may be exploring future opportunities due to project completion, contract expiration, relocation, or long-term career planning. Preferred location: Atlanta-Metro, GA, with a strong preference for candidates within commuting distance of our Duluth, GA headquarters." This is metadata; we can fold into a short p maybe under About the role.
Also "About WEG Electric Corp." description is company info; we could include as a short p maybe under About the role? Or we could drop? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company description is not boilerplate; it's substantive info about employer. Should we keep? Likely yes, as it's part of posting. We can include as a short p maybe under About the role or separate section? There's no heading for company info; we could just include as a
after About the role.
We must not repeat the job title as a heading. The job title is "Project Scheduler". Not used.
Now produce HTML fragment:
About the role
Serve as the Project Scheduler responsible for developing, maintaining, and analyzing integrated project schedules for complex engineered-to-order (ETO), systems, and EPC projects. Supporting projects from order handoff through closeout, you will work closely with Project Managers, engineering teams, manufacturing facilities, vendors, subcontractors, and customers to establish schedule baselines, monitor progress, identify schedule risks, and support successful project execution. This role plays a key part in project forecasting and delivery by providing schedule visibility, critical path analysis, risk identification, and recovery planning across the full project lifecycle. The Project Scheduler serves as a trusted partner to project teams, helping drive informed decisions through accurate planning, reporting, and schedule performance analysis. When project workload permits, the Project Scheduler will also support proposal development, schedule standardization initiatives, and continuous improvement efforts across the Project Management organization. While the start date has not yet been determined, we're interested in speaking with project scheduling professionals who may be exploring future opportunities due to project completion, contract expiration, relocation, or long-term career planning. Preferred location: Atlanta-Metro, GA, with a strong preference for candidates within commuting distance of our Duluth, GA headquarters.
WEG Electric Corp. is the largest industrial electric motor manufacturer in the Americas and one of the largest electric motor manufacturers in the world, producing more than 21 million units annually. Founded in 1961, WEG Electric Corp. operates mainly in the capital goods sector and has five main businesses: Motors, Energy, Automation, Coatings, and Transmission & Distribution, providing global solutions for electric motors, variable frequency drives, soft starters, controls, panels, transformers, and generators. The US corporate office is in Duluth, GA, with manufacturing units in Minnesota, Indiana, and Missouri, and over 30,000 employees worldwide. Visit our website to learn more: www.weg.net
Responsibilities
- Project Scheduling & Planning: Develop and
- for any list of duties/requirements/benefits". The responsibilities are a list of duties; we can make each duty a
- . We'll need to parse the responsibilities section into items. Responsibilities text includes multiple paragraphs each starting with a bold heading? Actually the text: "Primary Responsibilities Project Scheduling & Planning Develop and maintain integrated project schedules covering engineering, procurement, manufacturing, logistics, construction, commissioning, customer acceptance, and project closeout activities.Create schedule baselines, work breakdown structures (WBS), activity logic, milestones, calendars, and responsibility assignments.Incorporate contractual milestones, customer commitments, vendor activities, long-lead items, manufacturing requirements, and project interfaces into project schedules.Identify critical path activities, schedule constraints, float erosion, and potential impacts to key project milestones.Support project change management activities and ensure approved schedule changes are properly reflected in project plans. Schedule Analysis & Reporting Maintain project schedules through regular updates, forecasting, and progress measurement activities.Prepare look-ahead schedules, schedule narratives, variance analyses, and critical path assessments.Provide Project Managers with schedule performance insights, emerging risks, and recommended mitigation strategies.Analyze schedule delays, identify root causes, and support recovery planning efforts.Support project reviews, customer meetings, management updates, and monthly project reporting requirements. Project Controls & Stakeholder Coordination Support project controls activities, including forecasting, progress measurement, risk management, reporting, and change management.Coordinate with Project Controllers and project teams to provide schedule information supporting financial forecasting, milestone billing, and project reporting.Participate in project kickoffs, progress reviews, vendor meetings, factory coordination meetings, and customer discussions.Maintain schedule documentation, reports, narratives, and supporting records within approved project management systems. Proposal Support & Continuous Improvement Develop preliminary schedules and execution plans supporting EPC bids, proposals, and project pursuits.Review schedules for resource conflicts, sequencing concerns, long-lead risks, and execution constraints.Support development of scheduling standards, templates, and project planning tools.Identify opportunities to improve scheduling accuracy, forecasting, reporting, and project execution performance.Leverage AI-enabled tools and technologies where appropriate to improve scheduling efficiency, reporting, and project decision-making." We can split each bold heading as a group, but we can just make each sentence as
- . However we need to preserve all info; we could keep the headings as plain text inside
- or separate . Probably okay to keep headings as part of
- text. Simplify: create
- with each duty as
- containing the sentences.
Similarly for Requirements: we have Experience, Education, Knowledge & Skills. Could combine Experience and Education into Requirements? Actually Requirements could be experience and education. Qualifications could be certifications? But we have "Planning & Scheduling Professional (PSP), Project Management Professional (PMP), Primavera P6 certification, or equivalent training preferred." That's under Experience section? Actually it's under Experience bullet list: "Planning & Scheduling Professional (PSP), Project Management Professional (PMP), Primavera P6 certification, or equivalent training preferred." That's a qualification.
We could map:
- Requirements: Experience (5+ years etc) and Education.
- Qualifications: Certifications/preferred training.
- Skills: Knowledge & Skills section.
But the instruction says we can use those headings; we need to include a section only when posting has real specific content. So we can include Requirements, Qualifications, Skills, Benefits.
Let's extract:
Experience:
- 5+ years of experience in project scheduling, project controls, construction planning, engineering planning, manufacturing planning, or a related discipline.
- Experience developing and maintaining schedules for EPC, industrial, infrastructure, manufacturing, ETO, or large capital projects.
- Demonstrated experience performing schedule analysis, forecasting, variance reporting, and recovery planning.
- Experience working with engineering organizations, vendors, manufacturers, subcontractors, and field execution teams preferred.
- Planning & Scheduling Professional (PSP), Project Management Professional (PMP), Primavera P6 certification, or equivalent training preferred.
Education:
- Bachelor's degree in Engineering, Construction Management, Project Management, or a related discipline preferred.
- Equivalent combinations of education, certifications, and directly related experience will be considered.
Knowledge & Skills:
- Technical Expertise: Advanced proficiency with Primavera P6 and strong working knowledge of project scheduling and project controls principles.
- Proficiency with Microsoft Project and Microsoft Office applications, particularly Excel, Word, and PowerPoint.
- Knowledge of Critical Path Method (CPM) scheduling, forecasting, progress measurement, float analysis, schedule risk assessment, and recovery planning.
- Experience with Autodesk Construction Cloud, Autodesk Forma, Procore, or similar project management platforms preferred.
- Understanding of engineering, procurement, manufacturing, construction, commissioning, and project closeout activities.
- Leadership & Communication: Collaborates effectively with project managers, engineers, manufacturing teams, vendors, contractors, and customers.
- Communicates schedule risks, impacts, assumptions, and recommendations clearly to stakeholders at all levels.
- Influences project decisions through data-driven analysis and effective reporting.
- Strategic Thinking: Proactively identifies schedule risks and recommends mitigation strategies before project milestones are impacted.
- Balances multiple projects and competing priorities in a dynamic environment.
- Continuously seeks opportunities to improve scheduling processes, forecasting accuracy, and cross-functional project execution.
Travel: "Travel may be required based on project requirements, customer needs, and business priorities. Travel is expected to be occasional and determined on a project-by-project basis." This could be placed maybe under Responsibilities? But we have no Travel heading in allowed list; we could incorporate into Responsibilities as a duty? Or we could create a Schedule section? Not appropriate. Probably we can include Travel as a short p under About the role or Responsibilities? The instruction says we can fold minor metadata into a short
or drop it. Travel is not minor metadata? It's a condition. Could be placed as a short p after Responsibilities. But we must not create a Schedule section unless posting actually states them. Travel is not schedule. So we can add a
about travel after Responsibilities. Benefits: "We offer a pleasant work environment, competitive compensation, and a full benefits package." Also there is a line about "While the start date has not yet been determined, we're interested in speaking with project scheduling professionals who may be exploring future opportunities due to project completion, contract expiration, relocation, or long-term career planning. Preferred location: Atlanta-Metro, GA, with a strong preference for candidates within commuting distance of our Duluth, GA headquarters." This is metadata; we can fold into a short p maybe under About the role. Also "About WEG Electric Corp." description is company info; we could include as a short p maybe under About the role? Or we could drop? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company description is not boilerplate; it's substantive info about employer. Should we keep? Likely yes, as it's part of posting. We can include as a short p maybe under About the role or separate section? There's no heading for company info; we could just include as a
after About the role. We must not repeat the job title as a heading. The job title is "Project Scheduler". Not used. Now produce HTML fragment:
About the role
Serve as the Project Scheduler responsible for developing, maintaining, and analyzing integrated project schedules for complex engineered-to-order (ETO), systems, and EPC projects. Supporting projects from order handoff through closeout, you will work closely with Project Managers, engineering teams, manufacturing facilities, vendors, subcontractors, and customers to establish schedule baselines, monitor progress, identify schedule risks, and support successful project execution. This role plays a key part in project forecasting and delivery by providing schedule visibility, critical path analysis, risk identification, and recovery planning across the full project lifecycle. The Project Scheduler serves as a trusted partner to project teams, helping drive informed decisions through accurate planning, reporting, and schedule performance analysis. When project workload permits, the Project Scheduler will also support proposal development, schedule standardization initiatives, and continuous improvement efforts across the Project Management organization. While the start date has not yet been determined, we're interested in speaking with project scheduling professionals who may be exploring future opportunities due to project completion, contract expiration, relocation, or long-term career planning. Preferred location: Atlanta-Metro, GA, with a strong preference for candidates within commuting distance of our Duluth, GA headquarters.
WEG Electric Corp. is the largest industrial electric motor manufacturer in the Americas and one of the largest electric motor manufacturers in the world, producing more than 21 million units annually. Founded in 1961, WEG Electric Corp. operates mainly in the capital goods sector and has five main businesses: Motors, Energy, Automation, Coatings, and Transmission & Distribution, providing global solutions for electric motors, variable frequency drives, soft starters, controls, panels, transformers, and generators. The US corporate office is in Duluth, GA, with manufacturing units in Minnesota, Indiana, and Missouri, and over 30,000 employees worldwide. Visit our website to learn more: www.weg.net
Responsibilities
- Project Scheduling & Planning: Develop and
- text. Simplify: create