Data Center Category Manager, Data Center Sourcing & Procurement
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to parse the posting: It's a job description for Procurement Category Manager at Amazon (AWS). Contains description, responsibilities, qualifications, etc. No explicit pay, schedule, benefits mentioned. There's mention of "Why AWS?" and "Inclusive Team Culture", "Mentorship & Career Growth", "Work/Life Balance". Those could be considered Benefits? But they are more about culture. The instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can include sections like About the role (maybe a summary), Responsibilities, Requirements/Qualifications, Skills, Benefits (if specific benefits mentioned). The posting mentions "Why AWS?" and "Inclusive Team Culture", "Mentorship & Career Growth", "Work/Life Balance". Those are benefits/culture. Could be considered Benefits section. However they are not explicit benefits like health insurance, but they are still benefits. The instruction says "Prefer a few substantive sections over many thin ones." So maybe combine culture/benefits into a Benefits section.
We need to avoid repeating job title as heading. Also no Job ID.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information, not invent or summarize away detail. So we need to include the content but can format as lists.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. There's none obvious except maybe "#DCPD_Delivery" at end (maybe a tag). Should drop that.
We need to output only HTML fragment.
Let's extract sections:
- About the role: Could be the introductory paragraph: "Amazon is seeking a motivated and data-driven procurement category manager to support the Americas data center construction space. The candidate should have strong supply chain and procurement skills, analytical and financial acumen, communication capabilities and a hands-on passion to dive-deep into processes used in our data center operations network. Additionally, candidate must have proven skills in managing large-scale supply chain and procurement improvement projects."
That's about role.
- Responsibilities: The bullet-like sentences after "As a Procurement Category Manager, you will..." includes: create and implement sourcing strategies within construction services space and collaborate with internal business partners and suppliers to drive efficiencies, reduce risks, and costs for Amazon. develop mechanisms and metrics to hold suppliers accountable for performance and delivery. drive results through methods that include competitive bidding, negotiating, and analyzing data and market trends for your category. The ideal candidate thinks long term, drives multiple initiatives, communicates appropriately and influences customers and suppliers at all levels. You will be collaborative, but also work with significant autonomy. To be successful in this role you will be highly analytical; think strategically and globally; exhibit curiosity and learning drive; have a sense of urgency to meet customer timelines, succeed in a fast-paced environment; and have a high level of customer focus and business judgement. It will be critical to embrace and model Amazon’s Leadership Principles and have an entrepreneurial spirit.
Also "A Successful Candidate Will Demonstrate ..." list of items.
But those are more qualifications/requirements.
We also have "A day in the life": each day you will interact with different teams responsible for all aspects of the data centers. You will prioritize your activities to support data center capacity availability and safety focusing on the actions that are most impactful. You will have the opportunity to work on projects locally and globally.
That could be responsibilities or day-to-day.
- About The Team: description of AWS Infrastructure Services.
- About AWS Diverse Experiences: encouragement to apply.
- Why AWS? description.
- Inclusive Team Culture.
- Mentorship & Career Growth.
- Work/Life Balance.
We need to decide sections.
Probably sections: About the role, Responsibilities, Requirements, Skills, Benefits (culture/benefits), About the team (maybe not needed as separate heading? Could be "About the team").
But the instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings if content exists.
We have content for About the role (intro). Responsibilities (the duties). Requirements/Qualifications (the list of proven experience etc). Skills (maybe the analytical, financial, communication etc). Benefits (the culture, mentorship, work-life balance). Pay and Schedule not present, so omit.
We need to avoid duplication: The "A Successful Candidate Will Demonstrate" list includes many items that could be requirements/qualifications. Also earlier "The candidate should have strong supply chain and procurement skills..." etc.
We need to preserve all substantive information; we can combine similar points but not lose detail. However we must not invent or summarize away detail. Summarizing may be okay if we keep the detail? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That suggests we should not omit details; we need to keep them. But we can rephrase? Probably we should keep the original sentences but format as list items.
Thus we need to extract each distinct statement and put as
- .
Let's parse:
Intro paragraph (About the role):
- Amazon is seeking a motivated and data-driven procurement category manager to support the Americas data center construction space.
- The candidate should have strong supply chain and procurement skills, analytical and financial acumen, communication capabilities and a hands-on passion to dive-deep into processes used in our data center operations network.
- Additionally, candidate must have proven skills in managing large-scale supply chain and procurement improvement projects.
That's three bullet points.
Responsibilities (As a Procurement Category Manager, you will ...):
- Create and implement sourcing strategies within construction services space and collaborate with internal business partners and suppliers to drive efficiencies, reduce risks, and costs for Amazon.
- Develop mechanisms and metrics to hold suppliers accountable for performance and delivery.
- Drive results through methods that include competitive bidding, negotiating, and analyzing data and market trends for your category.
- The ideal candidate thinks long term, drives multiple initiatives, communicates appropriately and influences customers and suppliers at all levels.
- You will be collaborative, but also work with significant autonomy.
- To be successful in this role you will be highly analytical; think strategically and globally; exhibit curiosity and learning drive; have a sense of urgency to meet customer timelines, succeed in a fast-paced environment; and have a high level of customer focus and business judgement.
- It will be critical to embrace and model Amazon’s Leadership Principles and have an entrepreneurial spirit.
Also "A day in the life":
- Each day you will interact with different teams responsible for all aspects of the data centers.
- You will prioritize your activities to support data center capacity availability and safety focusing on the actions that are most impactful.
- You will have the opportunity to work on projects locally and globally.
These could also be responsibilities.
Requirements/Qualifications (A Successful Candidate Will Demonstrate):
- Proven experience driving large-scale process improvements resulting in measurable value
- High attention to detail including proven ability to manage multiple, competing priorities simultaneously
- Ability to think strategically and execute methodically
- Demonstrated ability to influence teams to adopt change utilizing smart technologies
- Ability to work in a fast-paced environment where ambiguity exists and continuous innovation is desired
- Committed to learning and expanding professional and technical knowledge
- Demonstrated analytical, financial and quantitative skills and ability to use hard data and metrics to back up assumptions and develop business cases
- Willingness to roll up your sleeves and do whatever is necessary; general manager / owner mentality
- Demonstrated ability to dive deep in understanding the product, our business, and the competitive landscape
- Ability to see ahead comprehensively and devise a strong plan of action, and ensure execution happens on time, every time
- Ability to get things done and produce conclusive, measurable results within time commitments
- Strong data analysis and analytical skills
Note some duplicates: strong data analysis and analytical skills appears twice? Actually "Strong data analysis and analytical skills" at end duplicates earlier "Demonstrated analytical, financial and quantitative skills". We'll keep both as separate items? Might be duplicate but we should preserve; maybe we can keep both but note duplication. The instruction says remove duplicated lines. So we should remove duplicate lines. The duplicate is "Strong data analysis and analytical skills" vs "Demonstrated analytical, financial and quantitative skills". Not exact duplicate but similar. We'll keep both as they are not identical.
Also "Ability to think strategically and execute methodically" maybe similar to "think strategically and globally". Not duplicate.
We'll keep list.
Skills: Could be extracted from earlier: strong supply chain and procurement skills, analytical and financial acumen, communication capabilities, hands-on passion to dive-deep into processes, proven skills in managing large-scale supply chain and procurement improvement projects, ability to think long term, drive multiple initiatives, communicate appropriately, influence customers and suppliers, collaborative, work with autonomy, highly analytical, think strategically and globally, exhibit curiosity and learning drive, sense of urgency, fast-paced environment, high level of customer focus and business judgement, embrace Leadership Principles, entrepreneurial spirit.
But many of these overlap with responsibilities/qualifications. To avoid too many sections, we could combine Skills into Requirements or Responsibilities. However instruction says prefer few substantive sections over many thin ones. So maybe we have About the role, Responsibilities, Requirements, Benefits. Skills could be part of Requirements.
But we need to follow heading list: they gave examples but not mandatory to use all. We can choose which sections to include based on content.
Thus we can have:
About the role
- ...
Responsibilities
- ...
Requirements
- ...
Benefits
- ...
We need to include Benefits content: from "Why AWS?", "Inclusive Team Culture", "Mentorship & Career Growth", "Work/Life Balance". Also maybe "AWS values diverse experiences." That's also a benefit.
Let's extract those:
- Why AWS?: Amazon Web Services (AWS) is the world’s most comprehensive and broadly adopted cloud platform. We pioneered cloud computing and never stopped innovating — that’s why customers from the most successful startups to Global 500 companies trust our robust suite of products and services to power their businesses.
- Inclusive Team Culture: AWS values curiosity and connection. Our employee-led and company-sponsored affinity groups promote inclusion and empower our people to take pride in what makes us unique. Our inclusion events foster stronger, more collaborative teams. Our continual innovation is fueled by the bold ideas, fresh perspectives, and passionate voices our teams bring to everything we do.
- Mentorship & Career Growth: We’re continuously raising our performance bar as we strive to become Earth’s Best Employer. That’s why you’ll find endless knowledge-sharing, mentorship and other career-advancing resources here to help you develop into a better-rounded professional.
- Work/Life Balance: We value work-life harmony. Achieving success at work should never come at the expense of sacrifices at home, which is why we strive for flexibility as part of our working culture. When we feel supported in the workplace and at home, there’s nothing we can’t achieve.
- AWS values diverse experiences: Even if you do not meet all of the preferred qualifications and skills listed in the job description, we encourage candidates to apply. If your career is just starting, hasn’t followed a traditional path, or includes alternative experiences, don’t let it stop you from applying.
We can turn each paragraph into a - .
Now we need to ensure we don't include boilerplate like "#DCPD_Delivery". Remove that.
Now produce HTML fragment.
We must not include or . Just the fragment.
Let's craft.
Check for any duplicated lines: In Responsibilities we have "think strategically and globally" and also "Ability to think strategically and
for prose. We need to preserve all substantive information, not invent or summarize away detail. So we need to include the content but can format as lists. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. There's none obvious except maybe "#DCPD_Delivery" at end (maybe a tag). Should drop that. We need to output only HTML fragment. Let's extract sections: - About the role: Could be the introductory paragraph: "Amazon is seeking a motivated and data-driven procurement category manager to support the Americas data center construction space. The candidate should have strong supply chain and procurement skills, analytical and financial acumen, communication capabilities and a hands-on passion to dive-deep into processes used in our data center operations network. Additionally, candidate must have proven skills in managing large-scale supply chain and procurement improvement projects." That's about role. - Responsibilities: The bullet-like sentences after "As a Procurement Category Manager, you will..." includes: create and implement sourcing strategies within construction services space and collaborate with internal business partners and suppliers to drive efficiencies, reduce risks, and costs for Amazon. develop mechanisms and metrics to hold suppliers accountable for performance and delivery. drive results through methods that include competitive bidding, negotiating, and analyzing data and market trends for your category. The ideal candidate thinks long term, drives multiple initiatives, communicates appropriately and influences customers and suppliers at all levels. You will be collaborative, but also work with significant autonomy. To be successful in this role you will be highly analytical; think strategically and globally; exhibit curiosity and learning drive; have a sense of urgency to meet customer timelines, succeed in a fast-paced environment; and have a high level of customer focus and business judgement. It will be critical to embrace and model Amazon’s Leadership Principles and have an entrepreneurial spirit. Also "A Successful Candidate Will Demonstrate ..." list of items. But those are more qualifications/requirements. We also have "A day in the life": each day you will interact with different teams responsible for all aspects of the data centers. You will prioritize your activities to support data center capacity availability and safety focusing on the actions that are most impactful. You will have the opportunity to work on projects locally and globally. That could be responsibilities or day-to-day. - About The Team: description of AWS Infrastructure Services. - About AWS Diverse Experiences: encouragement to apply. - Why AWS? description. - Inclusive Team Culture. - Mentorship & Career Growth. - Work/Life Balance. We need to decide sections. Probably sections: About the role, Responsibilities, Requirements, Skills, Benefits (culture/benefits), About the team (maybe not needed as separate heading? Could be "About the team"). But the instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings if content exists. We have content for About the role (intro). Responsibilities (the duties). Requirements/Qualifications (the list of proven experience etc). Skills (maybe the analytical, financial, communication etc). Benefits (the culture, mentorship, work-life balance). Pay and Schedule not present, so omit. We need to avoid duplication: The "A Successful Candidate Will Demonstrate" list includes many items that could be requirements/qualifications. Also earlier "The candidate should have strong supply chain and procurement skills..." etc. We need to preserve all substantive information; we can combine similar points but not lose detail. However we must not invent or summarize away detail. Summarizing may be okay if we keep the detail? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That suggests we should not omit details; we need to keep them. But we can rephrase? Probably we should keep the original sentences but format as list items. Thus we need to extract each distinct statement and put as
About the role
- ...
Responsibilities
- ...
Requirements
- ...
Benefits
- ...