Project Procurement Lead
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to decide what goes where.
About the role: The introductory paragraph(s) before "We offer:" maybe include the first paragraph up to "Push it Forward — apply today." That's prose.
Responsibilities: The list under "Tasks and Qualifications: This is What You will do in The Role:" includes many bullet-like sentences. We'll turn each sentence into
- .
Requirements: Could be the "What We Are Looking For:" list includes degree, certifications, years experience, etc. That's qualifications. Could split into Requirements (maybe experience) and Qualifications (education/certifications). But we can combine? The instruction: prefer a few substantive sections over many thin ones. But we need to include sections only when posting has real specific content. We have content for each.
We could have:
- About the role (intro)
- Responsibilities (list)
- Qualifications (education, certifications, experience)
- Skills (technical skills)
- Benefits (list)
- Pay (range)
- Schedule (travel/hybrid)
We might omit Requirements if we put experience under Qualifications.
Let's extract details.
Intro paragraph:
"Dematic is seeking a Procurement Projects Lead to join our successful team. This prominent role requires working closely with Procurement Regional Category Leads, Project Management, Engineering, Solutions Development, Finance, A/P, Quality, and others. The goal is to develop, communicate, and implement outstanding strategies for projects that achieve timely completion, reduce risk, support revenue growth, and increase savings. This opportunity is ideal for an experienced Procurement professional to manage significant spending for key customers while helping us grow. At Dematic and KION, our talent is key to creating the magic of supply chain solutions. As part of a global community of communities, you’ll help orchestrate intelligent logistics that power the future of commerce. Here, you can push your career forward in an environment built on collaboration, growth, and real-world impact. Push it Forward — apply today."
We'll put that in
.
Benefits list: "Career Development", "Competitive Compensation and Benefits", "Pay Transparency", "Global Opportunities". Also maybe "Learn More Here: link" but that's a link; we could include as but not required. Probably just list items.
Pay: base pay range $76,500- $112,000 annually. Also note final compensation determined by factors.
Schedule: Travel required to Company and Project sites up to 25% of time as well as a hybrid of remote/in-office working time.
Now responsibilities list: Let's extract each sentence after "Tasks and Qualifications: This is What You will do in The Role:" until "What We Are Looking For:" starts.
The text:
"Act as the Single Point of Contact (SPOC) for the Project team to the Procurement organization.
Support Project Success and BU Goals by contributing to a Safe project. Deliver on schedule and budget. Monitor and control supply risks. Ensure compliance, optimize efficiency, and maintain quality.
Review and approve the Resale scope, budget, and schedule for assigned Projects.
At Project Handover, ensure the full baseline is understood and begin development of Procurement Plan to actively manage throughout the Project lifecycle.
Attend weekly project and risk management meetings to fully understand project scope, procured content with ‘as-is’ risks, and installation schedules with critical achievements.
Lead weekly project meetings to review Procurement Plan, Tracker, and Command Center data.
Collaborate with sourcing Category teams to identify qualified sources of Resale equipment to develop the Project sourcing plan.
Prepare Resale project requirements content sheet for Category teams to fill in the project sourcing plan.
Communicate supplier lead-times to establish equipment “just in time” order dates to ensure equipment is ordered with sufficient time to enable timely supplier deliveries to project schedule.
Guide the Delivery Assurance and Tactical Procurement team on project-specific expediting, ensuring supplier delivery dates are met, and synchronizing SAP delivery dates with the project timeline.
Participate in Gate review meetings and show Project Procurement preparedness. Notify the team of any Procurement-related concerns.
Conduct supplier gate reviews (based on content/risk) with key/critical suppliers per checklist.
Track negotiated resale savings (net of increases) to determine Procurement savings – this includes comparing “as-sold” Resale content budget compared to resale purchase actuals. Work with Project Finance for alignment.
Perform as the main Procurement liaison between Project Management and Engineering for project-related activity.
In the post-project assessments, lead a Procurement Lessons Learned meeting with the Project Team and devise proactive responses to supplier-related challenges for future projects.
Align with Business Unit Program Management project support structure, as well as large customer accounts.
Travel required to Company and Project sites up to 25% of time as well as a hybrid of remote/in-office working time."
Note: The last sentence about travel appears also in schedule; but it's also in responsibilities. Might duplicate. We'll keep it in responsibilities as part of duties, but also schedule section maybe separate. However we should avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that sentence somewhere. It appears both in responsibilities and schedule. We could keep it in responsibilities and also in schedule? That would duplicate. Better to keep it only once, maybe under Schedule, as it's schedule info. But responsibilities also include travel as part of duties. The posting includes travel under responsibilities list; we could keep it there and not duplicate in schedule. However schedule section would then be empty (no content). We need schedule section only if posting has real specific content for it. The posting does have travel/hybrid info; we can put that under Schedule. But then we would be removing it from responsibilities, losing that detail. However the responsibilities list includes that sentence; we could keep it there and also have schedule section referencing same info? That would be duplication. The instruction says preserve ALL substantive information; duplication is not prohibited but might be redundant. It didn't forbid duplication. It said do NOT invent or summarize away detail. Duplication preserves detail, not summarizing away. So we could keep it in both places. That's okay.
But we might prefer to keep travel under Schedule and keep responsibilities without that sentence. However then we lose that sentence from responsibilities; but we could argue it's still preserved under Schedule. The instruction: preserve ALL substantive information; does not require it to be in a specific place. So as long as it's present somewhere, it's fine. So we can move travel to Schedule and remove from responsibilities to avoid duplication. That seems reasonable.
Thus responsibilities list will exclude the travel sentence.
Now qualifications: "What We Are Looking For:" list:
- Bachelor's degree or equivalent experience in business, engineering, or a related field.
- Certified Professional Supply Management (CPSM) preferred and/or Project Management Professional (PMP) preferred.
- 5-8 years of relevant project-based Procurement experience.
- Strong communication and presentation skills.
- Operates with minimal business direction.
- Demonstrated knowledge and experience in procurement processes and driving business results through influence and leadership.
- Strong capabilities in Microsoft Office (Word, Excel, PowerPoint).
- Preferred experience in SAP and MS Teams.
- Embodies KION Group Values of Integrity, Collaboration, Courage, and Excellence.
We could split into Qualifications (education, certifications, experience) and Skills (communication, Microsoft Office, SAP, MS Teams, etc.). But we also have "Strong communication and presentation skills." that's a skill. "Operates with minimal business direction." maybe a competency. "Demonstrated knowledge and experience in procurement processes and driving business results through influence and leadership." maybe a qualification.
We could have:
- Qualifications: Bachelor's degree or equivalent experience; CPSM/PMP preferred; 5-8 years relevant project-based Procurement experience.
- Skills: Strong communication and presentation skills; Operates with minimal business direction; Demonstrated knowledge and experience in procurement processes and driving business results through influence and leadership; Strong capabilities in Microsoft Office (Word, Excel, PowerPoint); Preferred experience in SAP and MS Teams; Embodies KION Group Values of Integrity, Collaboration, Courage, and Excellence.
But the instruction: Prefer a few substantive sections over many thin ones. So maybe combine Qualifications and Skills into one section "Requirements" or "Qualifications". However we have separate headings list: Requirements, Qualifications, Skills. We could use only Qualifications and Skills if they have content. But we could also combine into Qualifications (including education, experience, skills). But we need to follow the allowed headings; we can omit sections if not needed. So we could have only Qualifications section containing all the bullet points. That would be fewer sections.
But we also have Benefits, Pay, Schedule sections.
Thus final sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule.
We need to ensure we don't create empty sections.
Now format:
About the role
...intro...
Responsibilities
- ... each duty ...
Qual
for prose. We need to decide what goes where. About the role: The introductory paragraph(s) before "We offer:" maybe include the first paragraph up to "Push it Forward — apply today." That's prose. Responsibilities: The list under "Tasks and Qualifications: This is What You will do in The Role:" includes many bullet-like sentences. We'll turn each sentence into
. Benefits list: "Career Development", "Competitive Compensation and Benefits", "Pay Transparency", "Global Opportunities". Also maybe "Learn More Here: link" but that's a link; we could include as but not required. Probably just list items. Pay: base pay range $76,500- $112,000 annually. Also note final compensation determined by factors. Schedule: Travel required to Company and Project sites up to 25% of time as well as a hybrid of remote/in-office working time. Now responsibilities list: Let's extract each sentence after "Tasks and Qualifications: This is What You will do in The Role:" until "What We Are Looking For:" starts. The text: "Act as the Single Point of Contact (SPOC) for the Project team to the Procurement organization. Support Project Success and BU Goals by contributing to a Safe project. Deliver on schedule and budget. Monitor and control supply risks. Ensure compliance, optimize efficiency, and maintain quality. Review and approve the Resale scope, budget, and schedule for assigned Projects. At Project Handover, ensure the full baseline is understood and begin development of Procurement Plan to actively manage throughout the Project lifecycle. Attend weekly project and risk management meetings to fully understand project scope, procured content with ‘as-is’ risks, and installation schedules with critical achievements. Lead weekly project meetings to review Procurement Plan, Tracker, and Command Center data. Collaborate with sourcing Category teams to identify qualified sources of Resale equipment to develop the Project sourcing plan. Prepare Resale project requirements content sheet for Category teams to fill in the project sourcing plan. Communicate supplier lead-times to establish equipment “just in time” order dates to ensure equipment is ordered with sufficient time to enable timely supplier deliveries to project schedule. Guide the Delivery Assurance and Tactical Procurement team on project-specific expediting, ensuring supplier delivery dates are met, and synchronizing SAP delivery dates with the project timeline. Participate in Gate review meetings and show Project Procurement preparedness. Notify the team of any Procurement-related concerns. Conduct supplier gate reviews (based on content/risk) with key/critical suppliers per checklist. Track negotiated resale savings (net of increases) to determine Procurement savings – this includes comparing “as-sold” Resale content budget compared to resale purchase actuals. Work with Project Finance for alignment. Perform as the main Procurement liaison between Project Management and Engineering for project-related activity. In the post-project assessments, lead a Procurement Lessons Learned meeting with the Project Team and devise proactive responses to supplier-related challenges for future projects. Align with Business Unit Program Management project support structure, as well as large customer accounts. Travel required to Company and Project sites up to 25% of time as well as a hybrid of remote/in-office working time." Note: The last sentence about travel appears also in schedule; but it's also in responsibilities. Might duplicate. We'll keep it in responsibilities as part of duties, but also schedule section maybe separate. However we should avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that sentence somewhere. It appears both in responsibilities and schedule. We could keep it in responsibilities and also in schedule? That would duplicate. Better to keep it only once, maybe under Schedule, as it's schedule info. But responsibilities also include travel as part of duties. The posting includes travel under responsibilities list; we could keep it there and not duplicate in schedule. However schedule section would then be empty (no content). We need schedule section only if posting has real specific content for it. The posting does have travel/hybrid info; we can put that under Schedule. But then we would be removing it from responsibilities, losing that detail. However the responsibilities list includes that sentence; we could keep it there and also have schedule section referencing same info? That would be duplication. The instruction says preserve ALL substantive information; duplication is not prohibited but might be redundant. It didn't forbid duplication. It said do NOT invent or summarize away detail. Duplication preserves detail, not summarizing away. So we could keep it in both places. That's okay. But we might prefer to keep travel under Schedule and keep responsibilities without that sentence. However then we lose that sentence from responsibilities; but we could argue it's still preserved under Schedule. The instruction: preserve ALL substantive information; does not require it to be in a specific place. So as long as it's present somewhere, it's fine. So we can move travel to Schedule and remove from responsibilities to avoid duplication. That seems reasonable. Thus responsibilities list will exclude the travel sentence. Now qualifications: "What We Are Looking For:" list: - Bachelor's degree or equivalent experience in business, engineering, or a related field. - Certified Professional Supply Management (CPSM) preferred and/or Project Management Professional (PMP) preferred. - 5-8 years of relevant project-based Procurement experience. - Strong communication and presentation skills. - Operates with minimal business direction. - Demonstrated knowledge and experience in procurement processes and driving business results through influence and leadership. - Strong capabilities in Microsoft Office (Word, Excel, PowerPoint). - Preferred experience in SAP and MS Teams. - Embodies KION Group Values of Integrity, Collaboration, Courage, and Excellence. We could split into Qualifications (education, certifications, experience) and Skills (communication, Microsoft Office, SAP, MS Teams, etc.). But we also have "Strong communication and presentation skills." that's a skill. "Operates with minimal business direction." maybe a competency. "Demonstrated knowledge and experience in procurement processes and driving business results through influence and leadership." maybe a qualification. We could have: - Qualifications: Bachelor's degree or equivalent experience; CPSM/PMP preferred; 5-8 years relevant project-based Procurement experience. - Skills: Strong communication and presentation skills; Operates with minimal business direction; Demonstrated knowledge and experience in procurement processes and driving business results through influence and leadership; Strong capabilities in Microsoft Office (Word, Excel, PowerPoint); Preferred experience in SAP and MS Teams; Embodies KION Group Values of Integrity, Collaboration, Courage, and Excellence. But the instruction: Prefer a few substantive sections over many thin ones. So maybe combine Qualifications and Skills into one section "Requirements" or "Qualifications". However we have separate headings list: Requirements, Qualifications, Skills. We could use only Qualifications and Skills if they have content. But we could also combine into Qualifications (including education, experience, skills). But we need to follow the allowed headings; we can omit sections if not needed. So we could have only Qualifications section containing all the bullet points. That would be fewer sections. But we also have Benefits, Pay, Schedule sections. Thus final sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. We need to ensure we don't create empty sections. Now format:
About the role
...intro...
Responsibilities
- ... each duty ...