Manager, Procurement Management
for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. So we need to decide which sections to include.
We have:
- Company Description: about AbbVie. Could be "About the role"? Actually "About the role" is generic; but we could use "About AbbVie" maybe not in list. The list includes "About the role". The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples; we can use other headings? Probably we should stick to those headings where appropriate. But we can also use other headings if needed? 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 for sections. So we need to map content to those headings.
We have:
- About the role: could be Job Description summary.
- Responsibilities: list.
- Requirements: maybe Qualifications.
- Qualifications: maybe Education/Experience.
- Skills: maybe analytical, problem-solving, leadership.
- Benefits: from Additional Information: comprehensive package of benefits including paid time off, medical/dental/vision insurance and 401(k) to eligible employees. Also long-term incentive programs.
- Pay: compensation range described? The posting includes a note about compensation range but says "Applicable only to applicants applying to a position in any location with pay disclosure requirements under state or local law: The compensation range described below is the range of possible base pay compensation...". However they didn't actually give numbers. They just describe that there is a range but not provide actual numbers. So we should not create a Pay section unless posting actually states them. Since no actual numbers given, we should omit Pay section.
- Schedule: not mentioned.
- Requirements: maybe we can combine Qualifications and Requirements? The instruction: Use headings as appropriate. We could have "Qualifications" for education/experience, and "Skills" for analytical etc. "Requirements" maybe for experience managing teams etc. But we can decide.
We need to preserve all substantive information. Let's extract:
Company Description: AbbVie's mission... etc. Also follow social media links. That's substantive? It's company description; we could put under "About the role" maybe.
Job Description: The Manager, Procurement Management is responsible for managing the entire procurement process, from strategic sourcing to contracting, ensuring detailed execution aligned with category strategic vision. This role focuses on overseeing supplier selection and management, maintaining compliance with procurement policies, and executing tactical processes for supplier diversity and sustainability.
Responsibilities: list bullet points (the long sentences). We need to convert each sentence into
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings for sections. So we need to map content to those headings. We have: - About the role: could be Job Description summary. - Responsibilities: list. - Requirements: maybe Qualifications. - Qualifications: maybe Education/Experience. - Skills: maybe analytical, problem-solving, leadership. - Benefits: from Additional Information: comprehensive package of benefits including paid time off, medical/dental/vision insurance and 401(k) to eligible employees. Also long-term incentive programs. - Pay: compensation range described? The posting includes a note about compensation range but says "Applicable only to applicants applying to a position in any location with pay disclosure requirements under state or local law: The compensation range described below is the range of possible base pay compensation...". However they didn't actually give numbers. They just describe that there is a range but not provide actual numbers. So we should not create a Pay section unless posting actually states them. Since no actual numbers given, we should omit Pay section. - Schedule: not mentioned. - Requirements: maybe we can combine Qualifications and Requirements? The instruction: Use headings as appropriate. We could have "Qualifications" for education/experience, and "Skills" for analytical etc. "Requirements" maybe for experience managing teams etc. But we can decide. We need to preserve all substantive information. Let's extract: Company Description: AbbVie's mission... etc. Also follow social media links. That's substantive? It's company description; we could put under "About the role" maybe. Job Description: The Manager, Procurement Management is responsible for managing the entire procurement process, from strategic sourcing to contracting, ensuring detailed execution aligned with category strategic vision. This role focuses on overseeing supplier selection and management, maintaining compliance with procurement policies, and executing tactical processes for supplier diversity and sustainability. Responsibilities: list bullet points (the long sentences). We need to convert each sentence into
About the role
Company description paragraph + Job description paragraph.
Responsibilities
- ... ...
Qualifications
- Bachelors degree in Business Administration, Supply Chain Mgmt or related field.
- Minimum of 7 years of experience in procurement, supply chain, or related business or operations function.
- Previous experience managing teams and comprehensive understanding of procurement operations.
- Knowledge of the pharmaceutical industry is preferred.
Skills
- Strong analytical, problem-solving, and leadership skills.
Benefits
- Paid time off (vacation, holidays, sick)
- Medical, dental, and vision insurance
- 401(k) plan for eligible employees
- Eligibility to participate in long-term incentive programs
Requirements
- Key stakeholders: Business Leads, Business Partners, Category Leads/Managers, Procurement Leads
About the role
AbbVie's mission is to discover and deliver innovative medicines and solutions that solve serious health issues today and address the medical challenges of tomorrow. We strive to have a remarkable impact on people's lives across several key therapeutic areas including immunology, oncology and neuroscience - and products and services in our Allergan Aesthetics portfolio. For more information about AbbVie, please visit us at www.abbvie.com. Follow @abbvie on LinkedIn, Facebook, Instagram, X and YouTube.
The Manager, Procurement Management is responsible for managing the entire procurement process, from strategic sourcing to contracting, ensuring detailed execution aligned with category strategic vision. This role focuses on overseeing supplier selection and management, maintaining compliance with procurement policies, and executing tactical processes for supplier diversity and sustainability.
Responsibilities
- Manage activities from strategic sourcing to contracting, ensuring effective and detailed execution, including alignment with defined category strategic vision.
- Maintain compliance with procurement policy and fulfills business requirements of supplier diversity and sustainability, executing tactical processes to create value.
- Drive supplier management and ensures alignment to SRM strategy as determined by Procurement Lead and Category Managers, fostering a collaborative and innovative approach to supplier interactions.
- Implement risk mitigation plans developed in collaboration with Category Managers, providing tactical input on supplier performance and relaying the identification of procurement risks to safeguard the organizations interest and maintain operational resilience.
- Maintain excellence in all contract execution activities including source to contract and requisition to pay, owning the implementation of strategies to identify inefficiencies in process design and execution.
- Enable savings and assurance of supply, manage savings leakage across downstream procurement processes