Senior Technical Program Manager, Global Supply Chain – LiDAR & Optical Circuit Switches (OCS)
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for lists,
for prose
3. Do NOT repeat job title as heading
4. Do NOT put Job ID/requisition numbers as headings
5. Preserve ALL substantive information
6. Remove boilerplate (cookie/navigation/legal/EEO/scam-warning)
7. Include section ONLY when posting has real specific content
8. Never emit heading followed by filler/placeholder text
9. Never create Pay/Schedule/Benefits sections unless posting actually states them
10. Output ONLY HTML fragment - no html/body, no markdown code fences
Let me analyze the content:
- "About us" - company description
- "The Role" - role description
- "Key Responsibilities" - list of responsibilities
- "Core Values We Look For" - values
- "Required Qualifications" - education, experience, specific skills
- "Nice to Have" - additional qualifications
- "Life at Voyant" - culture/benefits
- "Equal Opportunity Employer" - boilerplate (should remove)
- "Compensation Range: $130K - $200K" - pay info
I need to structure this into appropriate sections. The rules say use h3 for section headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule".
Let me map:
- "About us" + "The Role" → could be "About the role" section
- "Key Responsibilities" → "Responsibilities"
- "Core Values We Look For" → maybe "Qualifications" or separate? The rules mention "Qualifications" as a heading. Core values are part of what they look for.
- "Required Qualifications" → "Requirements" or "Qualifications"
- "Nice to Have" → could be part of Qualifications or separate "Skills"
- "Life at Voyant" → "Benefits" (since it mentions catered lunch, culture)
- "Compensation Range" → "Pay"
I should not include EEO boilerplate.
Now, I need to ensure each section has real content. No placeholder text.
Let me draft the HTML:
About the role
Voyant Photonics builds silicon photonic chips that steer and switch light at high speed. They power next generation, chip-scale FMCW LiDAR for robotics and autonomy, and optical circuit switches (OCS) for AI data centers. Based in NYC, we're a hands-on team designing, building, and deploying frontier hardware to solve problems that matter, from how machines see to how AI scales.
We're looking for a Senior Technical Program Manager to build and run the global supply chain behind both of our product lines, LiDAR and OCS. You'll own supply chain programs from prototype sourcing through high-volume manufacturing. That means coordinating wafer foundries, packaging and test partners, component suppliers and contract manufacturers across North America, Asia and Europe. You'll work closely with engineering, operations, procurement, quality, finance and our customers to make sure we can build what we design, on time, at target cost and at scale.
Responsibilities
- Supply chain program ownership: Lead end-to-end supply chain programs for LiDAR and OCS, covering sourcing strategy, supplier selection, capacity, cost targets and delivery schedules, all aligned to product NPI milestones.
- Global supplier and partner management: Manage relationships with silicon photonics foundries, OSAT/packaging partners, contract manufacturers and key component suppliers (lasers, photodetectors, fiber arrays, micro-optics, MEMS, ASICs and PCBAs). Run quarterly business reviews and supplier scorecards, and support contract negotiations with procurement.
- Demand and capacity planning: Run the sales and operations planning (S&OP) process. Translate customer forecasts from very different markets, such as robotics and industrial customers for LiDAR and hyperscalers for OCS, into wafer starts, assembly and test capacity, and inventory plans that account for long lead times.
- NPI-to-volume transition: Drive manufacturing transfers, line qualification, yield ramps and second-source qualification as products move from prototype through EVT/DVT/PVT into mass production.
- Supply risk and resilience: Identify and mitigate single-source, capacity, geopolitical and tariff risks. Build dual-sourcing strategies, buffer inventory plans and business continuity plans for critical parts.
- Cost management: Own BOM cost roadmaps, should-cost models and cost-down programs. Track landed cost, including freight, duties and yield loss, against product cost targets.
- Supplier quality and change control: Partner with quality engineering on supplier qualification, PPAP-style releases, product change notifications (PCNs), corrective actions (SCARs) and engineering change control across the supply base.
- Logistics and trade compliance: Oversee global logistics, Incoterms, customs and country-of-origin requirements, and make sure export control and trade compliance obligations are met for both product lines.
- Systems, metrics and process: Build and scale supply chain processes and tools (ERP/MRP, BOM management, supplier portals). Define and report KPIs such as on-time delivery, lead time, inventory turns, supplier yield and cost versus plan.
- Executive and stakeholder communication: Give clear, concise status, risk and decision briefings to executives, the board, customers and cross-functional teams.
Qualifications
Required
- Education: Bachelor's degree in Engineering, Supply Chain Management, Operations or a related technical field. MBA or Master's degree preferred.
- Experience: 6+ years in technical program management, supply chain or operations for hardware products. At least 5 of those years should be spent scaling complex hardware to volume production with global suppliers.
- Semiconductor and photonics supply chain: Direct experience with wafer foundries, OSATs and contract manufacturers, ideally in photonics, optoelectronics or semiconductors.
- Global supplier management: A proven record managing suppliers in multiple regions, including Asia, and leading commercial and technical discussions alongside procurement.
- Planning and analytics: Strong command of demand and capacity planning, S&OP and ERP/MRP systems, with the ability to build data-driven models and turn them into decisions.
- Program management rigor: Mastery of schedule, budget and risk management for cross-functional programs that span engineering, operations and external partners.
Nice to have
- Automotive and industrial supply chains: Experience with automotive or industrial quality and supply standards such as IATF 16949, AEC-Q qualification and APQP/PPAP, which are relevant to LiDAR customers.
- Data center supply chains: Familiarity with hyperscaler supply requirements, customer supply agreements and data center qualification standards (e.g., Telcordia GR-468), which are relevant to OCS customers.
- Optical component sourcing: Experience sourcing lasers, photodetectors, fiber assemblies, micro-optics, MEMS or other optoelectronic components.
- Manufacturing quality systems: Hands-on use of PFMEA, control plans, change control and PCN management to keep a multi-tier supply base stable.
- Trade compliance: Working knowledge of export controls, tariffs, country-of-origin rules and multi-region manufacturing footprints.
- External test partners: Experience managing contract test houses, including test transfer, correlation and capacity planning.
- Certifications and mindset: APICS/ASCM (CPIM or CSCP) or PMP certification is a plus. Comfort with ambiguity and a bias toward action in a fast-moving startup.
Benefits
We build frontier hardware from our lab and office in Midtown Manhattan, where optical tables, lab benches and electronics sit alongside traditional office space. Our work is hands-on and primarily in person, but we don't run on a rigid 9-to-5. We partner with customers across time zones, so some calls start early or run late, and we adjust schedules around them. We run a high-trust, high-accountability environment: you'll own meaningful work, move quickly and often wear more than one hat. Voyant provides catered lunch every day at HQ, and we're a diverse group of food lovers from around the world who enjoy sharing food, culture and technical ideas around the lunch table.
Pay
Compensation range: $130K - $200K
I should not include "Core Values We Look For" as a separate heading? The rules say use h3 for section headings like "Qualifications". The core values are part of what they look for, but they are listed separately. I could include them under Qualifications or as a separate "Values" section? The rules don't mention "Values" as a standard heading. The standard headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Core Values We Look For" could be part of Qualifications or maybe "Requirements". But the posting has "Core Values We Look For" as a separate section. I think I should include it as a subsection under Qualifications or as a separate h3? The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says "e.g." so it's not exhaustive. But they prefer a few substantive sections over many thin ones. The core values are three bullet points: Respect, Ownership, Simplicity + Clarity. That's substantive. I could make a "Values" section or include in Qualifications. Since the rules say "Qualifications" is a heading, and core values are what they look for, I'll include them under Qualifications as a subsection.
But the posting has "Core Values We Look For" before "Required Qualifications". I'll keep the order: maybe "Qualifications" with subsections "Core values", "Required", "Nice to have". However, the rules say use h3 for section headings. Subsections could be h4. That's fine.
I'll structure:
Qualifications
Core values
... three values ...
Required
... required ...
Nice to have
... nice to have ...
That seems good.
Also, "Life at Voyant" includes benefits (catered lunch) and schedule info (not rigid 9-5, some early/late calls). The rules say include Benefits and Schedule sections only if posting actually states them. It does state catered lunch and schedule flexibility. So I'll include Benefits and maybe Schedule? The posting says "we don't run on a rigid 9-to-5... some calls start early or run late, and we adjust schedules around them." That's schedule info. I could include a Schedule section. But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits (catered lunch) and schedule (flexible, not rigid 9-5). So I'll include both.
But the "Life at Voyant" section also includes culture description. I'll put that under Benefits, and maybe create a Schedule section for the schedule details. However, the rules prefer a few substantive sections over many thin ones. The schedule info is brief.
for prose 3. Do NOT repeat job title as heading 4. Do NOT put Job ID/requisition numbers as headings 5. Preserve ALL substantive information 6. Remove boilerplate (cookie/navigation/legal/EEO/scam-warning) 7. Include section ONLY when posting has real specific content 8. Never emit heading followed by filler/placeholder text 9. Never create Pay/Schedule/Benefits sections unless posting actually states them 10. Output ONLY HTML fragment - no html/body, no markdown code fences Let me analyze the content: - "About us" - company description - "The Role" - role description - "Key Responsibilities" - list of responsibilities - "Core Values We Look For" - values - "Required Qualifications" - education, experience, specific skills - "Nice to Have" - additional qualifications - "Life at Voyant" - culture/benefits - "Equal Opportunity Employer" - boilerplate (should remove) - "Compensation Range: $130K - $200K" - pay info I need to structure this into appropriate sections. The rules say use h3 for section headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". Let me map: - "About us" + "The Role" → could be "About the role" section - "Key Responsibilities" → "Responsibilities" - "Core Values We Look For" → maybe "Qualifications" or separate? The rules mention "Qualifications" as a heading. Core values are part of what they look for. - "Required Qualifications" → "Requirements" or "Qualifications" - "Nice to Have" → could be part of Qualifications or separate "Skills" - "Life at Voyant" → "Benefits" (since it mentions catered lunch, culture) - "Compensation Range" → "Pay" I should not include EEO boilerplate. Now, I need to ensure each section has real content. No placeholder text. Let me draft the HTML:
About the role
Voyant Photonics builds silicon photonic chips that steer and switch light at high speed. They power next generation, chip-scale FMCW LiDAR for robotics and autonomy, and optical circuit switches (OCS) for AI data centers. Based in NYC, we're a hands-on team designing, building, and deploying frontier hardware to solve problems that matter, from how machines see to how AI scales.
We're looking for a Senior Technical Program Manager to build and run the global supply chain behind both of our product lines, LiDAR and OCS. You'll own supply chain programs from prototype sourcing through high-volume manufacturing. That means coordinating wafer foundries, packaging and test partners, component suppliers and contract manufacturers across North America, Asia and Europe. You'll work closely with engineering, operations, procurement, quality, finance and our customers to make sure we can build what we design, on time, at target cost and at scale.
Responsibilities
- Supply chain program ownership: Lead end-to-end supply chain programs for LiDAR and OCS, covering sourcing strategy, supplier selection, capacity, cost targets and delivery schedules, all aligned to product NPI milestones.
- Global supplier and partner management: Manage relationships with silicon photonics foundries, OSAT/packaging partners, contract manufacturers and key component suppliers (lasers, photodetectors, fiber arrays, micro-optics, MEMS, ASICs and PCBAs). Run quarterly business reviews and supplier scorecards, and support contract negotiations with procurement.
- Demand and capacity planning: Run the sales and operations planning (S&OP) process. Translate customer forecasts from very different markets, such as robotics and industrial customers for LiDAR and hyperscalers for OCS, into wafer starts, assembly and test capacity, and inventory plans that account for long lead times.
- NPI-to-volume transition: Drive manufacturing transfers, line qualification, yield ramps and second-source qualification as products move from prototype through EVT/DVT/PVT into mass production.
- Supply risk and resilience: Identify and mitigate single-source, capacity, geopolitical and tariff risks. Build dual-sourcing strategies, buffer inventory plans and business continuity plans for critical parts.
- Cost management: Own BOM cost roadmaps, should-cost models and cost-down programs. Track landed cost, including freight, duties and yield loss, against product cost targets.
- Supplier quality and change control: Partner with quality engineering on supplier qualification, PPAP-style releases, product change notifications (PCNs), corrective actions (SCARs) and engineering change control across the supply base.
- Logistics and trade compliance: Oversee global logistics, Incoterms, customs and country-of-origin requirements, and make sure export control and trade compliance obligations are met for both product lines.
- Systems, metrics and process: Build and scale supply chain processes and tools (ERP/MRP, BOM management, supplier portals). Define and report KPIs such as on-time delivery, lead time, inventory turns, supplier yield and cost versus plan.
- Executive and stakeholder communication: Give clear, concise status, risk and decision briefings to executives, the board, customers and cross-functional teams.
Qualifications
Required
- Education: Bachelor's degree in Engineering, Supply Chain Management, Operations or a related technical field. MBA or Master's degree preferred.
- Experience: 6+ years in technical program management, supply chain or operations for hardware products. At least 5 of those years should be spent scaling complex hardware to volume production with global suppliers.
- Semiconductor and photonics supply chain: Direct experience with wafer foundries, OSATs and contract manufacturers, ideally in photonics, optoelectronics or semiconductors.
- Global supplier management: A proven record managing suppliers in multiple regions, including Asia, and leading commercial and technical discussions alongside procurement.
- Planning and analytics: Strong command of demand and capacity planning, S&OP and ERP/MRP systems, with the ability to build data-driven models and turn them into decisions.
- Program management rigor: Mastery of schedule, budget and risk management for cross-functional programs that span engineering, operations and external partners.
Nice to have
- Automotive and industrial supply chains: Experience with automotive or industrial quality and supply standards such as IATF 16949, AEC-Q qualification and APQP/PPAP, which are relevant to LiDAR customers.
- Data center supply chains: Familiarity with hyperscaler supply requirements, customer supply agreements and data center qualification standards (e.g., Telcordia GR-468), which are relevant to OCS customers.
- Optical component sourcing: Experience sourcing lasers, photodetectors, fiber assemblies, micro-optics, MEMS or other optoelectronic components.
- Manufacturing quality systems: Hands-on use of PFMEA, control plans, change control and PCN management to keep a multi-tier supply base stable.
- Trade compliance: Working knowledge of export controls, tariffs, country-of-origin rules and multi-region manufacturing footprints.
- External test partners: Experience managing contract test houses, including test transfer, correlation and capacity planning.
- Certifications and mindset: APICS/ASCM (CPIM or CSCP) or PMP certification is a plus. Comfort with ambiguity and a bias toward action in a fast-moving startup.
Benefits
We build frontier hardware from our lab and office in Midtown Manhattan, where optical tables, lab benches and electronics sit alongside traditional office space. Our work is hands-on and primarily in person, but we don't run on a rigid 9-to-5. We partner with customers across time zones, so some calls start early or run late, and we adjust schedules around them. We run a high-trust, high-accountability environment: you'll own meaningful work, move quickly and often wear more than one hat. Voyant provides catered lunch every day at HQ, and we're a diverse group of food lovers from around the world who enjoy sharing food, culture and technical ideas around the lunch table.
Pay
Compensation range: $130K - $200K
I should not include "Core Values We Look For" as a separate heading? The rules say use h3 for section headings like "Qualifications". The core values are part of what they look for, but they are listed separately. I could include them under Qualifications or as a separate "Values" section? The rules don't mention "Values" as a standard heading. The standard headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Core Values We Look For" could be part of Qualifications or maybe "Requirements". But the posting has "Core Values We Look For" as a separate section. I think I should include it as a subsection under Qualifications or as a separate h3? The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says "e.g." so it's not exhaustive. But they prefer a few substantive sections over many thin ones. The core values are three bullet points: Respect, Ownership, Simplicity + Clarity. That's substantive. I could make a "Values" section or include in Qualifications. Since the rules say "Qualifications" is a heading, and core values are what they look for, I'll include them under Qualifications as a subsection.
But the posting has "Core Values We Look For" before "Required Qualifications". I'll keep the order: maybe "Qualifications" with subsections "Core values", "Required", "Nice to have". However, the rules say use h3 for section headings. Subsections could be h4. That's fine.
I'll structure:
Qualifications
Core values
... three values ...
Required
... required ...
Nice to have
... nice to have ...
That seems good.
Also, "Life at Voyant" includes benefits (catered lunch) and schedule info (not rigid 9-5, some early/late calls). The rules say include Benefits and Schedule sections only if posting actually states them. It does state catered lunch and schedule flexibility. So I'll include Benefits and maybe Schedule? The posting says "we don't run on a rigid 9-to-5... some calls start early or run late, and we adjust schedules around them." That's schedule info. I could include a Schedule section. But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits (catered lunch) and schedule (flexible, not rigid 9-5). So I'll include both.
But the "Life at Voyant" section also includes culture description. I'll put that under Benefits, and maybe create a Schedule section for the schedule details. However, the rules prefer a few substantive sections over many thin ones. The schedule info is brief.
Required
- ... required ...
Nice to have
- ... nice to have ...