Supply Chain Manager, GPCS AMER
About the role
...
- Responsibilities: list of duties: bullet points after "Key job responsibilities". We'll extract each line. List: - Coordinate with launch teams, operations, and Category to align assigned suppliers, item selection, and delivery requirements with site needs, launch schedules, and volume demands - Assist in developing and implementing ordering strategies that account for diverse site configurations (e.g., co-located vs. standalone), optimizing plans while operating within site constraints - Drive integration projects and change management initiatives in alignment with senior management, coordinating between partners and internal stakeholders - Monitor procurement plans and escalate risks or gaps to leadership as network growth, new site launches, and operational requirements evolve - Identify and recommend opportunities to drive cost savings, process efficiencies, and standardization across the non-inventory supply chain - Manage all administrative tasks required to establish new sites and enable ordering, including system setup, catalog configuration, and supplier alignment - Conduct weekly cycle count management to maintain inventory accuracy and identify discrepancies - Resolve procurement-related tickets and escalations in a timely manner, supporting intake process establishment across sites We'll put- each.
- About The Team: could be part of About the role? But we have separate "About The Team" paragraph. Could be part of About the role or separate section? The instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So "About The Team" maybe considered part of About the role? But we could include as part of About the role content. However we have already an About the role section; we could incorporate team description there. But we must not invent sections. We could keep About the role as description of role and maybe add team info there. Or we could treat "About The Team" as part of About the role. I'd merge.
- Basic Qualifications: list of qualifications. That's Requirements? The instruction says Requirements heading. So we can put Basic Qualifications under Requirements.
- Preferred Qualifications: could be Qualifications or Skills? There's also Skills heading. We have Preferred Qualifications list includes many items: experience using data analysis, planning, performance metrics, process improvement, collaborating with cross-functional teams, programming/scripting, ERP tools, multi-site operations, developing ordering strategies, communication skills, etc. We could split into Qualifications (maybe Preferred Qualifications) and Skills (technical skills). But we need to decide.
We have headings: Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have Basic Qualifications (mandatory) -> Requirements.
Preferred Qualifications -> Qualifications (maybe). Skills could be derived from Preferred Qualifications that are skill-based: programming/scripting, ERP tools, data analysis, communication. But we could also put all Preferred Qualifications under Qualifications and leave Skills empty (omit). Better to have a Skills section if we have specific skill items. Let's extract skill-like items:
- Experience using data analysis to drive business decisions
- Experience with planning, performance metrics, and process improvement
- Experience collaborating with cross-functional teams including Marketing, Product Management, Customer Service, Operations, Legal, Finance, and Senior Leadership
- Experience with programming/scripting (Batch, VB, PowerShell, Java, C#, Chef, Perl, Ruby and/or PHP), or experience in SQL Server/MySQL and experience that includes strong analytical skills, attention to detail, and effective communication abilities
- Experience in written and verbal communication skills to communicate with technical and non-technical audiences, including senior leadership
- Knowledge of ERP and procurement tools, including Oracle, Coupa and Ariba
- Experience supporting multi-site operations or network-level procurement
- Experience developing ordering strategies
These could be considered Qualifications. Skills maybe: programming/scripting, SQL, ERP tools, data analysis, communication. But we can just put them under Qualifications and omit Skills if no distinct skill list. However instruction: Prefer a few substantive sections over many thin ones. So maybe combine Requirements and Qualifications into one? But headings are prescribed; we can include both if they have content.
We also have Benefits: description includes "Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location. Amazon also offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave. Learn more about our benefits at https://amazon.jobs/en/benefits."
We have Pay: "The base salary range for this position is listed below. Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location." Also there is a location salary range: "USA, AZ, Tempe - 64,200.00 - 96,200.00 USD annually". So we have Pay info.
Schedule: Not mentioned. No schedule info. So we should not include Schedule section.
We also need to include maybe a short paragraph for metadata like location? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we could include location and salary range in a short
maybe under Pay? Or we could have a separate short paragraph before sections? Probably include location and salary as part of Pay section. Thus sections: - About the role (combining role description and team description) - Responsibilities - Requirements (Basic Qualifications) - Qualifications (Preferred Qualifications) - Benefits - Pay (including salary range and sign-on/RSU) We'll omit Skills if no distinct content; but we could create Skills from preferred qualifications that are skill-based. However to avoid thin sections, maybe we omit Skills. Check if any content for Skills: we could extract "Experience with programming/scripting (Batch, VB, PowerShell, Java, C#, Chef, Perl, Ruby and/or PHP), or experience in SQL Server/MySQL and experience that includes strong analytical skills, attention to detail, and effective communication abilities" and "Experience in written and verbal communication skills". That's skill-like. But we already have Qualifications covering those. If we make Skills separate, we'd have to split content; risk of thin sections. Better to keep Qualifications. Thus output:
About the role
Global Procurement Central Services (GPCS) is seeking a Non-Inventory Supply Chain Manager to support the non-inventory procurement strategy for emerging and growing business lines within Amazon's operational network. This role will assist in designing and building procurement processes, drive strategic projects and change initiatives in collaboration with multiple stakeholders, and execute day-to-day procurement operations that ensure site readiness and operational continuity. The initial focus will include supporting emerging programs such as Prime Air, with the scope expanding as new business lines grow. Successful candidates are natural self-starters who thrive in ambiguous, fast-changing environments. This role requires someone who is highly adaptable — capable of quickly adjusting strategies and implementation plans in response to dynamic business needs and varying site conditions. The ideal candidate excels at managing multiple stakeholder relationships, driving consistent standards across diverse partners, and balancing technical requirements with operational constraints. Global Procurement Central Services (GPCS) is a centralized corporate team that provides non-inventory procurement support across Amazon's operational network. GPCS manages the end-to-end supply chain of forecasting, purchasing, delivery, escalation management, and financial reconciliation. This role within GPCS will support the operational readiness of Amazon's emerging and growing business lines, including programs such as Prime Air, ensuring sites have the non-inventory supplies and consumables needed to operate effectively. This is a critical role in building scalable procurement processes that support network growth and expansion.
Responsibilities
- Coordinate with launch teams, operations, and Category to align assigned suppliers, item selection, and delivery requirements with site needs, launch schedules, and volume demands
- Assist in developing and implementing ordering strategies that account for diverse site configurations (e.g., co-located vs. standalone), optimizing plans while operating within site constraints
- Drive integration projects and change management initiatives in alignment with senior management, coordinating between partners and internal stakeholders
- Monitor procurement plans and escalate risks or gaps to leadership as network growth, new site launches, and operational requirements evolve
- Identify and recommend opportunities to drive cost savings, process efficiencies, and standardization across the non-inventory supply chain
- Manage all administrative tasks required to establish new sites and enable ordering, including system setup, catalog configuration, and supplier alignment
- Conduct weekly cycle count management to maintain inventory accuracy and identify discrepancies
- Resolve procurement-related tickets and escalations in a timely manner, supporting intake process establishment across sites
Requirements
- Bachelor's degree or equivalent qualification in supply chain management, engineering, business management or other relevant field
- Experience with data analysis and basic Excel skills
- Experience managing multiple projects and priorities across teams in a fast-paced, deadline-driven environment
- 1+ years of Purchasing, Inventory Management & Supply Chain experience
Qualifications
- Experience using data analysis to drive business decisions
- Experience with planning, performance metrics, and process improvement
- Experience collaborating with cross-functional teams including Marketing, Product Management, Customer Service, Operations, Legal, Finance, and Senior Leadership
- Experience with programming/scripting (Batch, VB, PowerShell, Java, C#, Chef, Perl, Ruby and/or PHP), or experience in SQL Server/MySQL and experience that includes strong analytical skills, attention to detail, and effective communication abilities
- Experience in written and verbal communication skills to communicate with technical and non-technical audiences, including senior leadership
- Knowledge of ERP and procurement tools, including Oracle, Coupa and Ariba
- Experience supporting multi-site operations or network-level procurement
- Experience developing ordering strategies
Benefits
Your Amazon package will include sign-on payments and restricted stock units (RSUs). Amazon also offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave. Learn more about our benefits at https://amazon.jobs/en/benefits