Senior Procurement Specialist

BioNTech SE · Cambridge, MA · 4 wk ago

Purchasing$99k–$159k/yrContract

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes description of role (Your Contribution) which can be Responsibilities. Also "A Good Match" includes qualifications/requirements. "Your benefits and remuneration" includes Pay and Benefits. There's no explicit Schedule. There's location Cambridge, US full time but we shouldn't repeat job title. We can include a short paragraph for location and job type maybe under About the role? The instruction: do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a

with location and full time maybe. We need sections: About the role (maybe a brief intro), Responsibilities (list), Requirements (maybe education/experience), Qualifications (maybe preferred qualifications), Skills (maybe analytical etc), Benefits, Pay. Schedule not present, so omit. We must preserve all substantive info, not invent. Use

for any list of duties/requirements/benefits. Use
for prose. We need to extract responsibilities from "Your Contribution:" paragraph. It's a long paragraph with many sentences. We can break into bullet list for clarity but must preserve all info. Could keep as prose
but instruction: use
- for any list of duties/requirements/benefits. The responsibilities are a list of duties; we can convert each sentence into
- . Ensure we don't lose any detail. Let's parse responsibilities: - Begin building a local presence for Procurement in Cambridge, MA. - Provide business support with an initial focus on research and development areas. - Collaborate with Global Procurement as well as US Finance, Legal, Compliance and other business stakeholders. - Support US operational procurement activities, including monitoring and management of requisitioning, purchase order issuance, invoice issue resolution and transaction follow-up. - Manage the external procurement service provider to ensure results align with standards and expectations. - Collaboratively work to resolve issues and support day to day operations for BioNTech US Inc. - Contribute to transformation initiatives, including system and process initiatives, to deliver and implement ongoing improvements within the region. - Build and develop skills and capabilities to support and execute future-state operations. - Apply analytical skills to evaluate and analyze transactional and master data to identify trends, exceptions, bottlenecks and opportunities for improvement. - Develop, recommend and execute actionable improvements. - Assess & improve catalog content and utilization. - Maintain and/or act as reviewer of various data types. - Support and/or execute internal controls, as assigned. - Lead local sourcing activities for lower complexity activities or contribute to more complex initiatives, in collaboration with Global Procurement Category Management. - Support supplier management activities. - Develop and share local/regional market and category insights as inputs to global initiatives. That's many items. Now Requirements: "A Good Match:" includes: - Bachelor’s degree in Business, Supply Chain Management, Finance, Economics, Life Sciences, or a related field. - 3-8 years of experience in procurement, strategic sourcing, purchasing, supply chain, finance, operations or related discipline - At least 2 years of Research & Development-related category experience (and/or equivalent professional experience) - Experience supporting sourcing events, supplier management and procurement operations. - Working knowledge of Source to Pay processes - Ability to work effectively in an evolving and transforming environment with developing processes and systems. Preferred qualifications (we could put under Qualifications or Skills). The posting says "Preferred qualifications:" then list: - Prior experience within a multinational biopharmaceutical/life sciences company - Prior experience with SAP S4 and Ariba or Coupa (or other similar procurement technologies) across Source to Pay process (including both Source to Contract and Purchase to Pay) - Prior experience working within an SAP (or similar ERP) implementation project We could treat these as Qualifications (preferred) or Skills. The instruction: Use headings like Qualifications, Skills. We can put required qualifications under Requirements, and preferred under Qualifications. Skills maybe from analytical skills etc but we already have some in responsibilities. Could create Skills section for analytical skills, ability to work in evolving environment, etc. But we might avoid duplication. Better to put skills under Skills: analytical skills, ability to work effectively in evolving environment, etc. However we already have those in responsibilities/requirements. To avoid duplication, we could keep them only once. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include all info, but we can place them in appropriate sections without duplication? If we split, we might duplicate. Safer to keep all info in one place, maybe under Responsibilities and Requirements, and not create Skills if it would duplicate. But we need to follow instruction: Use headings only when posting has real specific content for it. If we create Skills section, we need to have content. We could extract skills like "Analytical skills", "Ability to work effectively in an evolving and transforming environment", "Working knowledge of Source to Pay processes". Those are indeed skills. We can put them under Skills. But then they'd also appear elsewhere (maybe under Responsibilities or Requirements). That would be duplication, which might be considered repeating info, but not prohibited? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not forbidden but could be considered redundant. Better to avoid duplication by moving those items to Skills and removing from elsewhere? But then we might lose context. However we could keep them in both places; it's still preserving info, just duplicated. Might be acceptable but could be seen as not ideal. I'd prefer to avoid duplication by placing them only once. Let's decide: We'll put required education/experience under Requirements. Preferred experience under Qualifications. Skills we can extract: Analytical skills, ability to work effectively in evolving environment, working knowledge of Source to Pay processes. But those are already in Requirements (working knowledge of Source to Pay processes is there; ability to work effectively in evolving environment is there). So if we move them to Skills, we would need to remove from Requirements to avoid duplication. But the requirement list includes those items; we could keep them there and not have Skills section. That seems simpler: we have Requirements covering education, experience, knowledge, abilities. Qualifications covering preferred experience. Benefits and Pay sections. Thus sections: About the role (maybe a short paragraph summarizing role?), Responsibilities (list), Requirements (list), Qualifications (list), Benefits (list), Pay (maybe a paragraph with pay range). No Schedule. We need to include location and full time somewhere. Could put in About the role paragraph: "Located in Cambridge, MA, this full-time position..." etc. Now craft HTML. We'll start with a
  for location and employment type maybe as part of About the role. Section headings:
  About the role
  , then
  ...
  Then
  Responsibilities
  - . Then
    Requirements

Senior Procurement Specialist

About the role

Responsibilities

Requirements

Qualifications

Benefits

Pay

Similar jobs