Obsolescence Manager
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to parse the posting.
Key sections:
- Intro: "Join us in pioneering breakthroughs..." etc. This is about the company and role description. Could be "About the role" or maybe "About the role" includes description.
- "What You Will Do": list of duties.
- "What You Will Have": qualifications/requirements.
- "What Makes You Successful": skills/competencies.
- "Base Pay Range For This Position Is $115,980 - $159,478" plus note about factors. That's Pay.
- Benefits: "The Company offers the following benefits for this position, subject to applicable eligibility requirements: medical insurance, dental insurance, vision insurance, 401(k) retirement plan. life insurance, long-term and short-term disability insurance, paid parking/public transportation, paid time off, paid sick and safe time."
- Hybrid remote note: "**This role is designed to be supported on a hybrid basis to the Palo Alto, CA HQ with full remote flexibility for the right experience/skillset**" This is schedule/location info. Could be Schedule section.
- Also there is "Who we are:" etc. That's company description, maybe part of About the role.
- Also there is "How we work:" etc. Might be considered About the role.
- There's also "#LS-OS1" maybe a tag, ignore.
- There's also "If this is a commission eligible position..." but not commission eligible? It says "If this is a commission eligible position the commission eligibility will be in accordance with the terms of the Company's plan." That's not specific; we can ignore as boilerplate? It's not a definite statement; it's conditional. Probably we should not include as it's not concrete.
- Also "Equal Employment Opportunity Statement", "Reasonable Accommodations", "California Privacy Notice", "Export Control", "Data Privacy", "Beware of Job Scams", etc. All boilerplate to remove.
- Also "To find out more about Siemens Healthineers businesses, please visit our company page here." That's application instruction? Remove.
- Also "Register here to get started." Remove.
Thus we need sections: About the role (intro + who we are + how we work?), Responsibilities (What You Will Do), Requirements (What You Will Have), Skills (What Makes You Successful), Benefits, Pay, Schedule (hybrid remote). Possibly also Qualifications? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave a list but we can choose which to include based on content. We have content for About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Qualifications maybe overlapping with Requirements; but we have "What You Will Have" which includes education/experience etc. That could be Requirements or Qualifications. We'll map "What You Will Have" to Requirements (or Qualifications). Since they listed both Requirements and Qualifications as possible headings, we need to decide. The content includes education, experience, etc. That's typical for Requirements. We'll use Requirements heading. Skills heading for "What Makes You Successful". Benefits heading for benefits list. Pay heading for pay range. Schedule heading for hybrid/remote note.
We must not repeat job title as heading. So no heading for "Obsolescence Manager". Good.
We need to preserve all substantive information. Let's extract.
About the role: combine introductory paragraph(s) and "Who we are:" and "How we work:" maybe.
Intro: "Join us in pioneering breakthroughs in healthcare. For everyone. Everywhere. Sustainably. Our inspiring and caring environment forms a global community that celebrates diversity and individuality. We encourage you to step beyond your comfort zone, offering resources and flexibility to foster your professional and personal growth, all while valuing your unique contributions. Would you like to help shape the future of healthcare? At Siemens Healthineers, we rely on people who dedicate their energy and passion to this goal. We are seeking an Obsolescence Manager to own and manage the component lifecycle management process across Varian products. This role is responsible for coordinating supplier component discontinuations, maintaining an obsolescence backlog, tracking lifecycle risks, and partnering with cross-functional teams to support timely resolution of obsolescence-related activities. As the business process owner for obsolescence management, you will leverage HOTT (Healthineers Obsolescence Transparency Tool) and established lifecycle management processes to support risk identification, prioritization, reporting, and execution."
Then "Who we are:" paragraph: "We are a team of more than 72,000 highly dedicated Healthineers in more than 70 countries. As a leader in medical technology, we constantly push the boundaries to create better outcomes and experiences for patients, no matter where they live or what health issues they are facing. Our portfolio is crucial for clinical decision-making and treatment pathways."
Then "How we work:" paragraph: "When you join Siemens Healthineers, you become one in a global team of scientists, clinicians, developers, researchers, professionals, and skilled specialists, who believe in each individual’s potential to contribute with diverse ideas. We are from different backgrounds, cultures, religions, political and/or sexual orientations, and work together, to fight the world’s most threatening diseases and enable access to care, united by one purpose: to pioneer breakthroughs in healthcare. For everyone. Everywhere. Sustainably."
We can combine these into About the role section.
Responsibilities: list from "What You Will Do". Each bullet is a sentence. We'll put each as
- .
Let's extract bullet points:
- Manage component lifecycle transitions, supplier discontinuation notifications (PDNs), product change notifications (PCNs), and end-of-life (EOL) events impacting Varian products.
- Serve as the primary owner of the obsolescence management process and HOTT deployment within the organization.
- Maintain and prioritize an obsolescence backlog and coordinate activities needed to address lifecycle risks.
- Collect and analyze lifecycle risk data from suppliers, internal systems, and key stakeholders.
- Assess product, manufacturing, service, and inventory impacts associated with component obsolescence.
- Coordinate mitigation activities across Engineering, Procurement, Manufacturing, Service, Quality, Regulatory Affairs, and Product Management.
- Support Last Time Buy (LTB) planning activities, including demand consolidation and inventory assessments.
- Escalate high-risk obsolescence issues and help drive resolution with appropriate stakeholders.
- Develop and maintain reports, dashboards, and metrics to provide visibility into lifecycle risks and mitigation activities.
- Identify opportunities to improve lifecycle management processes, tools, and workflows.
That's all.
Requirements: from "What You Will Have". Let's extract:
- Bachelor's degree in Supply Chain, Operations, Business, Engineering, Quality, Procurement, or a related field (or equivalent experience) with 5+ years of relevant experience, or a Master's degree with 3+ years of relevant experience.
- Experience in supply chain, operations, procurement, manufacturing, quality, project management, product lifecycle management, or related business functions.
- Experience working in medical device, semiconductor, electronics, consumer products, industrial manufacturing, automotive, aerospace, or other complex product environments.
- Experience coordinating cross-functional projects, processes, or operational activities.
- Knowledge of component lifecycle management, supplier discontinuations, end-of-life (EOL) activities, and Last Time Buy (LTB) processes.
- Experience working with ERP, PLM, and reporting systems (SAP and Power BI preferred).
We'll list each as
- .
Skills: from "What Makes You Successful". Extract:
- Strong organizational, analytical, and problem-solving skills.
- An ability to coordinate and influence stakeholders across multiple functions.
- Effective communication and collaboration skills.
- Experience managing multiple priorities in a structured and disciplined manner.
- Strong attention to detail and follow-through.
- Process-oriented mindset with a focus on execution and continuous improvement.
- Comfortable working in a fast-paced environment with evolving priorities.
- Fluent English communication skills.
We'll list each as
- .
Benefits: list from "The Company offers the following benefits for this position, subject to applicable eligibility requirements:" then list:
- medical insurance
- dental insurance
- vision insurance
- 401(k) retirement plan
- life insurance
- long-term and short-term disability insurance
- paid parking/public transportation
- paid time off
- paid sick and safe time
We'll list each as
- .
Pay: "The Base Pay Range For This Position Is $115,980 - $159,478". Also note: "Factors which may affect starting pay within this range may include geography/market, skills, education, experience, and other qualifications of the successful candidate." Also "If this is a commission eligible position the commission eligibility will be in accordance with the terms of the Company's plan. Commissions are based on individual performance and/or company performance." This is conditional; maybe we can include note about factors but not commission. The instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The pay range is specific, so we include Pay section. The factors note is also specific (geography/market, skills, education, experience, other qualifications). That's substantive. The commission note is conditional; maybe we can include as a note but it's not definite. Safer to include only the base pay range and factors. We'll put both in
maybe.
Schedule: from "**This role is designed to be supported on a hybrid basis to the Palo Alto, CA HQ with full remote flexibility for the right experience/skillset**". That's specific. So Schedule section with that statement.
We should also maybe include location? It's Palo Alto, CA HQ. Already in schedule note.
Now we need to output HTML fragment only, no /, no markdown fences.
We'll structure:
About the role
... combined paragraphs ...
Responsibilities
- ...
...
Requirements
...
Skills
...
Benefits
...
Pay
The Base Pay Range For This Position Is $115,980 - $159,478. Factors which may affect starting pay within this range may include geography/market, skills, education, experience, and other qualifications of the successful candidate.
Schedule
This role is designed to be supported on a hybrid basis to the Palo Alto, CA HQ with full remote flexibility for the right experience/skillset.
We need to ensure we didn't include any boilerplate. Check that we didn't inadvertently include EEO etc. We removed.
Check for
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting. Key sections: - Intro: "Join us in pioneering breakthroughs..." etc. This is about the company and role description. Could be "About the role" or maybe "About the role" includes description. - "What You Will Do": list of duties. - "What You Will Have": qualifications/requirements. - "What Makes You Successful": skills/competencies. - "Base Pay Range For This Position Is $115,980 - $159,478" plus note about factors. That's Pay. - Benefits: "The Company offers the following benefits for this position, subject to applicable eligibility requirements: medical insurance, dental insurance, vision insurance, 401(k) retirement plan. life insurance, long-term and short-term disability insurance, paid parking/public transportation, paid time off, paid sick and safe time." - Hybrid remote note: "**This role is designed to be supported on a hybrid basis to the Palo Alto, CA HQ with full remote flexibility for the right experience/skillset**" This is schedule/location info. Could be Schedule section. - Also there is "Who we are:" etc. That's company description, maybe part of About the role. - Also there is "How we work:" etc. Might be considered About the role. - There's also "#LS-OS1" maybe a tag, ignore. - There's also "If this is a commission eligible position..." but not commission eligible? It says "If this is a commission eligible position the commission eligibility will be in accordance with the terms of the Company's plan." That's not specific; we can ignore as boilerplate? It's not a definite statement; it's conditional. Probably we should not include as it's not concrete. - Also "Equal Employment Opportunity Statement", "Reasonable Accommodations", "California Privacy Notice", "Export Control", "Data Privacy", "Beware of Job Scams", etc. All boilerplate to remove. - Also "To find out more about Siemens Healthineers businesses, please visit our company page here." That's application instruction? Remove. - Also "Register here to get started." Remove. Thus we need sections: About the role (intro + who we are + how we work?), Responsibilities (What You Will Do), Requirements (What You Will Have), Skills (What Makes You Successful), Benefits, Pay, Schedule (hybrid remote). Possibly also Qualifications? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave a list but we can choose which to include based on content. We have content for About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Qualifications maybe overlapping with Requirements; but we have "What You Will Have" which includes education/experience etc. That could be Requirements or Qualifications. We'll map "What You Will Have" to Requirements (or Qualifications). Since they listed both Requirements and Qualifications as possible headings, we need to decide. The content includes education, experience, etc. That's typical for Requirements. We'll use Requirements heading. Skills heading for "What Makes You Successful". Benefits heading for benefits list. Pay heading for pay range. Schedule heading for hybrid/remote note. We must not repeat job title as heading. So no heading for "Obsolescence Manager". Good. We need to preserve all substantive information. Let's extract. About the role: combine introductory paragraph(s) and "Who we are:" and "How we work:" maybe. Intro: "Join us in pioneering breakthroughs in healthcare. For everyone. Everywhere. Sustainably. Our inspiring and caring environment forms a global community that celebrates diversity and individuality. We encourage you to step beyond your comfort zone, offering resources and flexibility to foster your professional and personal growth, all while valuing your unique contributions. Would you like to help shape the future of healthcare? At Siemens Healthineers, we rely on people who dedicate their energy and passion to this goal. We are seeking an Obsolescence Manager to own and manage the component lifecycle management process across Varian products. This role is responsible for coordinating supplier component discontinuations, maintaining an obsolescence backlog, tracking lifecycle risks, and partnering with cross-functional teams to support timely resolution of obsolescence-related activities. As the business process owner for obsolescence management, you will leverage HOTT (Healthineers Obsolescence Transparency Tool) and established lifecycle management processes to support risk identification, prioritization, reporting, and execution." Then "Who we are:" paragraph: "We are a team of more than 72,000 highly dedicated Healthineers in more than 70 countries. As a leader in medical technology, we constantly push the boundaries to create better outcomes and experiences for patients, no matter where they live or what health issues they are facing. Our portfolio is crucial for clinical decision-making and treatment pathways." Then "How we work:" paragraph: "When you join Siemens Healthineers, you become one in a global team of scientists, clinicians, developers, researchers, professionals, and skilled specialists, who believe in each individual’s potential to contribute with diverse ideas. We are from different backgrounds, cultures, religions, political and/or sexual orientations, and work together, to fight the world’s most threatening diseases and enable access to care, united by one purpose: to pioneer breakthroughs in healthcare. For everyone. Everywhere. Sustainably." We can combine these into About the role section. Responsibilities: list from "What You Will Do". Each bullet is a sentence. We'll put each as
maybe. Schedule: from "**This role is designed to be supported on a hybrid basis to the Palo Alto, CA HQ with full remote flexibility for the right experience/skillset**". That's specific. So Schedule section with that statement. We should also maybe include location? It's Palo Alto, CA HQ. Already in schedule note. Now we need to output HTML fragment only, no /, no markdown fences. We'll structure:
About the role
... combined paragraphs ...
Responsibilities
- ... ...
Requirements
-
...
Skills
-
...
Benefits
-
...
Pay
The Base Pay Range For This Position Is $115,980 - $159,478. Factors which may affect starting pay within this range may include geography/market, skills, education, experience, and other qualifications of the successful candidate.
Schedule
This role is designed to be supported on a hybrid basis to the Palo Alto, CA HQ with full remote flexibility for the right experience/skillset.
We need to ensure we didn't include any boilerplate. Check that we didn't inadvertently include EEO etc. We removed. Check for