Global Commodity Manager - Mountain View, CA
Aeva · Mountain View, CA · 3 wk ago
On-sitePurchasingFull-time
We need to output HTML fragment with sections: About us? Actually "About us" is a section heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to those headings. The posting includes "About us" (company description), "Role Overview", "What you'll be doing" (responsibilities), "What you'll have" (requirements/qualifications), then benefits info. Also salary info: "Salary pay ranges are determined..." but not specific numbers, so we should not create Pay section because no specific numbers. Benefits: they list comprehensive medical, dental, vision, pre-tax commuter, 401k, life/disability, flexible time off, paid parental leave, 11 paid holidays. Also equity, bonus, other forms of compensation may be provided. So we can include Benefits section.
We should not repeat job title as heading. No Job ID. Remove boilerplate: Equal Opportunity Employer line, etc. Also remove "Aeva is an Equal Opportunity Employer..." line. Also remove "Depending on the position offered, equity, bonus, and other forms of compensation may be provided as part of a total compensation package, in addition to comprehensive medical..." Actually that's benefits; we keep that.
We need to preserve all substantive information. So include About us paragraph, Role Overview paragraph, Responsibilities (What you'll be doing) as list, Requirements/Qualifications (What you'll have) as list, Benefits as list. Possibly also Skills? Not separate. Could combine Requirements and Qualifications into one section? The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can have both Requirements and Qualifications if content distinguishes. But we have "What you'll have:" which includes both qualifications and nice-to-have. Could split into Requirements (must have) and Qualifications (nice to have). Let's parse:
Must have:
- Bachelor's degree in Engineering, Supply Chain Management, Business, or related technical field
- 8+ years progressive experience in Supply Chain, Commodity Management, or Sourcing role
- Extensive direct experience managing sourcing and supply of technical components relevant to high-tech or complex electro-mechanical products
- Demonstrated experience in either Automotive or Consumer Electronics industries, managing high-volume, high-quality component supply chains
- Proven ability to independently develop commodity strategies and execute complex, high-stakes negotiations
- Strong analytical skills and experience with cost modeling (TCO/Should-Cost)
Nice to Have:
- Master's degree in related field
- Previous experience in a startup environment and ability to thrive in ambiguity and rapid growth
- Technical background or direct experience managing components specific to Lidar, optical sensors, or complex sensing systems (e.g., MEMS, ASICs, custom optics, specialized materials)
- Experience with global supply chains, including sourcing and managing suppliers in Asia (APAC)
- Familiarity with Quality Management Systems (e.g., ISO/IATF 16949)
We can put Requirements as must-have list, Qualifications as nice-to-have list.
Benefits list: comprehensive medical, dental, and vision coverage; pre-tax commuter and health care/dependent care accounts; 401k plan; life and disability benefits; flexible time off; paid parental leave; 11 paid holidays annually; equity, bonus, and other forms of compensation may be provided as part of total compensation package.
We should not include Pay section because no specific numbers.
Schedule: not mentioned.
Thus output HTML with sections: About us (maybe heading "About the role"? Actually About us is company description; could use "About the role"? But instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use "About the role" for company description and role overview combined? But we have separate Role Overview paragraph. Could combine About us and Role Overview under "About the role". Or we could have two sections: "About the role" for company description, and maybe "Role Overview" not in list but we could treat as part of About the role. The instruction says use those headings for section headings; we can also add other headings if needed? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to those headings. The posting includes "About us" (company description), "Role Overview", "What you'll be doing" (responsibilities), "What you'll have" (requirements/qualifications), then benefits info. Also salary info: "Salary pay ranges are determined..." but not specific numbers, so we should not create Pay section because no specific numbers. Benefits: they list comprehensive medical, dental, vision, pre-tax commuter, 401k, life/disability, flexible time off, paid parental leave, 11 paid holidays. Also equity, bonus, other forms of compensation may be provided. So we can include Benefits section.
We should not repeat job title as heading. No Job ID. Remove boilerplate: Equal Opportunity Employer line, etc. Also remove "Aeva is an Equal Opportunity Employer..." line. Also remove "Depending on the position offered, equity, bonus, and other forms of compensation may be provided as part of a total compensation package, in addition to comprehensive medical..." Actually that's benefits; we keep that.
We need to preserve all substantive information. So include About us paragraph, Role Overview paragraph, Responsibilities (What you'll be doing) as list, Requirements/Qualifications (What you'll have) as list, Benefits as list. Possibly also Skills? Not separate. Could combine Requirements and Qualifications into one section? The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can have both Requirements and Qualifications if content distinguishes. But we have "What you'll have:" which includes both qualifications and nice-to-have. Could split into Requirements (must have) and Qualifications (nice to have). Let's parse:
Must have:
- Bachelor's degree in Engineering, Supply Chain Management, Business, or related technical field
- 8+ years progressive experience in Supply Chain, Commodity Management, or Sourcing role
- Extensive direct experience managing sourcing and supply of technical components relevant to high-tech or complex electro-mechanical products
- Demonstrated experience in either Automotive or Consumer Electronics industries, managing high-volume, high-quality component supply chains
- Proven ability to independently develop commodity strategies and execute complex, high-stakes negotiations
- Strong analytical skills and experience with cost modeling (TCO/Should-Cost)
Nice to Have:
- Master's degree in related field
- Previous experience in a startup environment and ability to thrive in ambiguity and rapid growth
- Technical background or direct experience managing components specific to Lidar, optical sensors, or complex sensing systems (e.g., MEMS, ASICs, custom optics, specialized materials)
- Experience with global supply chains, including sourcing and managing suppliers in Asia (APAC)
- Familiarity with Quality Management Systems (e.g., ISO/IATF 16949)
We can put Requirements as must-have list, Qualifications as nice-to-have list.
Benefits list: comprehensive medical, dental, and vision coverage; pre-tax commuter and health care/dependent care accounts; 401k plan; life and disability benefits; flexible time off; paid parental leave; 11 paid holidays annually; equity, bonus, and other forms of compensation may be provided as part of total compensation package.
We should not include Pay section because no specific numbers.
Schedule: not mentioned.
Thus output HTML with sections: About us (maybe heading "About the role"? Actually About us is company description; could use "About the role"? But instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use "About the role" for company description and role overview combined? But we have separate Role Overview paragraph. Could combine About us and Role Overview under "About the role". Or we could have two sections: "About the role" for company description, and maybe "Role Overview" not in list but we could treat as part of About the role. The instruction says use those headings for section headings; we can also add other headings if needed? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Safer to stick to those headings. So we need to map content to those headings.
We have: About the role (could include company description and role overview). Responsibilities (What you'll be doing). Requirements (must-have). Qualifications (nice-to-have). Benefits (list). No Skills separate; we could omit Skills heading.
Thus output:
About the role
About the role
... company description + role overview ...
Responsibilities
- ... each bullet ...
Requirements
- ... must-have ...
Qualifications
- ... nice-to-have ...
Benefits
- ... benefits ...
- for list; we can embed
- with inner text containing line breaks? Could also use
- and then within li include
- but that may be okay. Simpler: each bullet as a high-level duty; we can include the details inside the li separated by semicolons. But we need to preserve all detail; we can keep subheadings as part of li text.
Let's extract each:
Strategic Sourcing & Negotiation:
- Develop and execute sourcing strategies for assigned commodities and services critical to our technology
- Lead commercial negotiations with suppliers, focusing on achieving optimal cost, quality, delivery, and technology roadmap alignment
- Conduct comprehensive supplier risk assessments and develop mitigation plans
Supplier Relationship Management:
- Manage the full lifecycle of supplier relationships, from initial selection and qualification to ongoing performance management and business reviews
- Drive supplier performance improvement initiatives (cost reduction, lead time, on- time delivery, quality)
Cross-Functional Leadership:
- Act as the primary interface between Aeva Engineering/NPI teams and suppliers for new product introduction (NPI) development and qualification
- Work closely with Operations and Planning teams to develop capacity plans and ensure long-term continuity of supply in a dynamic growth environment
- Drive 'Design for Manufacturability/Supply Chain' considerations into early product design phases
Cost Management & Analysis:
- Establish, manage, and drive annual cost reduction targets for key commodities
- Develop and maintain component/service cost roadmaps and market intelligence
We'll put each as li.
Requirements (must-have):
- Bachelor's degree in Engineering, Supply Chain Management, Business, or a related technical field
- 8+ years of progressive experience in a Supply Chain, Commodity Management, or Sourcing role
- Extensive direct experience managing the sourcing and supply of technical components relevant to high-tech or complex electro-mechanical products
- Demonstrated experience in either the Automotive or Consumer Electronics industries, managing high-volume, high-quality component supply chains
- Proven ability to independently develop commodity strategies and execute complex, high-stakes negotiations
- Strong analytical skills and experience with cost modeling (TCO/Should-Cost)
Qualifications (nice-to-have):
- Master's degree in a related field
- Previous experience in a startup environment and a demonstrated ability to thrive in ambiguity and rapid growth
- Technical background or direct experience managing components specific to Lidar, optical sensors, or complex sensing systems (e.g., MEMS, ASICs, custom optics, specialized materials)
- Experience with global supply chains, including sourcing and managing suppliers in Asia (APAC)
- Familiarity with Quality Management Systems (e.g., ISO/IATF 16949)
Benefits:
- Comprehensive medical, dental, and vision coverage
- Pre-tax commuter and health care/dependent care accounts
- 401k plan
- Life and disability benefits
- Flexible time off
- Paid parental leave
- 11 paid holidays annually
- Equity, bonus, and other forms of compensation may be provided as part of a total compensation package
We should also mention that salary pay ranges are determined by role, level, location but no specific numbers; we omit Pay section.
Now ensure we removed boilerplate: Equal Opportunity Employer line, also "Salary pay ranges are determined..." we kept only as part of benefits? Actually we omitted it entirely because it's not specific; but we could include a brief statement about compensation being determined etc. However instruction: do not create Pay/Schedule/Benefits sections unless posting actually states them. Benefits we have. The salary statement is not a specific benefit; it's about pay determination. Since we are not making a Pay section, we could optionally include a short paragraph under About the role? But better to omit as it's not a benefit and not required. The instruction says preserve ALL substantive information; do not invent or summarize away detail. The salary statement is substantive? It says "Salary pay ranges are determined by role, level, and location. Within the range, the successful candidate’s starting base pay will be determined based on factors including job-related skills, experience, certifications, qualifications, relevant education or training, and market conditions. These ranges are subject to change in the future." That's substantive but not a specific number. Should we preserve it? Possibly we could include a brief paragraph under About the role or maybe a separate "Compensation" but we aren't allowed to create Pay section unless specific. However we could embed that info in a paragraph under About the role as it's still about compensation. The instruction says "Prefer a few substantive sections over many thin ones." It didn't forbid adding a paragraph about compensation under About the role. But we must not create a Pay section heading. So we could add a paragraph after About the role describing compensation determination. That would preserve info.
Similarly, the line about equity, bonus, etc we already included in Benefits.
Thus About the role paragraph will include company description, role overview, and compensation determination statement.
Let's craft:
Aeva’s mission is to bring the next wave of perception to a broad range of applications from automated driving to industrial robotics, consumer electronics, consumer health, security, and beyond. Aeva is transforming autonomy with its groundbreaking sensing and perception technology that integrates all key LiDAR components onto a silicon photonics chip in a compact module. Aeva 4D
- and then within li include
- with inner text containing line breaks? Could also use