Principal Engineer, System Validation
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections that have real specific content.
From posting:
- About The Role: paragraph describing role. That's content.
- What You'll Own: list of responsibilities (multiple bullet points). That's responsibilities.
- Basic Qualifications: list of qualifications (multiple bullet points). That's requirements/qualifications.
- Preferred Qualifications: list of preferred qualifications. Could be under Qualifications or Skills? Probably Qualifications.
- Salary Range: $185,000 - $290,000 => Pay section.
- Location: San Jose, CA (On-site) maybe schedule? Not schedule. Could be under Schedule? Not exactly. There's no explicit schedule info. So we should not create Schedule section unless present. No schedule.
- Benefits: none mentioned. So skip Benefits.
- Skills: maybe not explicit separate; but we could include under Qualifications? The instruction: Use headings for sections like Skills if present. Not present explicitly. So we can omit Skills.
- About the role heading: we have About The Role.
- Responsibilities: we have What You'll Own.
- Requirements: Basic Qualifications.
- Qualifications: Preferred Qualifications.
- Pay: Salary Range.
We must not repeat job title as heading. No Job ID etc.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points exactly as given (maybe rephrase? Must preserve info, not summarizing away detail. We can keep bullet points as - with the text.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. The posting includes Note To Recruiters, Equal Opportunity Employer statement. Those are boilerplate; we should remove them. Also "Principals only..." etc. Remove.
Also location line: "Principle Engineer, System Validation Location: San Jose , CA (On-site)" - we need to keep location? It's substantive? It's location info. Should we keep? It's not a heading; we can put in a
maybe. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Location is minor metadata; we can include in a short
. Probably include location.
We also have "Ayar Labs is shattering AI data bottlenecks..." paragraph at start. That's about company; maybe part of About the role? Could be included in About the role section? The About The Role heading already has description. The introductory paragraph could be considered part of About the role? Might be considered company overview; but we can include it under About the role as prose. However we must not invent or summarize away detail; we need to preserve all substantive information. So we should include that introductory paragraph as part of About the role section (maybe before the heading? But heading is About The Role; we can put a
after heading containing that intro plus the role description.
But we must not duplicate content. The About The Role section currently has a paragraph: "Ayar Labs builds optical I/O technology for hyperscale AI infrastructure. This role owns reliability qualification at the system and fleet level: building the test infrastructure and evidence base that proves our products are ready for large-scale deployment, and then partnering directly with customers and integration partners to carry that evidence through joint qualification programs and pilot deployments. You will be responsible for both the engineering (test infrastructure, statistical reliability planning, standards compliance) and the relationship (translating technical evidence into the specific commitments our partners need to move forward)." That's already there. The introductory paragraph before that is about company mission. Should we include it? It's substantive; we could put it as a
before the About the role heading? But heading must be
for section headings. We could have a
before the heading? The instruction: use
for section headings. It doesn't forbid other
outside sections. But we likely want to keep everything under sections. Could put the company overview inside About the role section as a preceding
. That would preserve it.
Thus About the role section:
About the role
then containing company overview + role description.
Now Responsibilities:
Responsibilities
then - each bullet from What You'll Own.
We need to ensure we capture each bullet exactly.
Let's list bullets:
- Test infrastructure and evidence generation: Design, build, and operate custom test infrastructure that emulates real system-level electrical, thermal, and workload conditions ahead of, or independent of, any single customer's specific hardware. This includes sourcing or generating representative workload and power profiles and using them to drive continuous, long-duration test campaigns.
- Reliability statistics and demonstration planning: Define statistical sample sizes and test durations needed to demonstrate specific reliability and confidence targets, and apply the right methodology to each failure population in the system rather than a single blanket target.
- Standards and compliance: Ensure that test infrastructure, interfaces, and telemetry are built against relevant industry interconnect and management standards, so evidence generated internally holds up when reviewed by, or transferred to, an external partner's platform.
- Staged qualification execution: Execute staged qualification gates, from lab-level interoperability and functional testing through environmental and stress testing to live pilot deployment, applying a reliability / availability / serviceability lens throughout rather than treating any one dimension in isolation.
- Fault injection and lifecycle monitoring: Design and run fault-injection and failure-mode testing, including scenarios that exercise field-serviceable components under representative operating conditions, in partnership with customer and integration-partner operations teams.
- Economic modeling and fleet reporting: Provide reliability and performance data into cost-of-ownership and total-cost modeling shared with customers, and own ongoing fleet reliability reporting and incident response once products reach production.
- Cross-functional partnership: Serve as the primary technical point of contact with Tier-1 integration partners and hyperscale customer engineering teams across the qualification lifecycle, from early technical evidence through pilot sign-off and into steady-state operations.
Now Basic Qualifications bullets:
- 5+ years in fleet/systems reliability engineering for large-scale infrastructure, with a BS in Electrical Engineering, Computer Engineering, or a related field.
- You've built or operated test infrastructure that validates a component or subsystem's behavior before it is deployed into a customer's actual system, using representative rather than production hardware.
- You've defined and executed statistical reliability demonstration plans (sample sizes, test durations, confidence and reliability targets) for hardware components, and can explain the methodology behind them, not just apply a lookup table.
- You've worked with die-to-die, chip-to-chip, or board-level interconnect standards and telemetry or management interfaces relevant to high-speed data center hardware.
- You've partnered directly with external OEM or hyperscale customer engineering teams on a joint qualification or certification program, and are comfortable owning that relationship technically.
- Comfort operating a live, continuously running test or fleet environment: on-call coverage, incident response, and building the telemetry pipeline that turns raw sensor data into fleet-level reliability statistics.
- Strong written and verbal communication skills; you will regularly translate internal engineering data into evidence and documentation for external partners.
Preferred Qualifications bullets:
- MS in Electrical Engineering, Computer Engineering, or a related field.
- Experience with FPGA-based test or signal-generation systems.
- Experience characterizing or emulating real compute or network workload behavior for use in a test or validation environment.
- Background in data-center fleet operations, site-reliability engineering, or customer-facing qualification and certification processes.
- Familiarity with co-packaged optics, silicon photonics, or other emerging interconnect packaging technologies.
Salary Range: $185,000 - $290,000.
Location: San Jose, CA (On-site). We'll put in a
maybe before sections.
We must not include any boilerplate like Note To Recruiters, Equal Opportunity Employer, etc.
Now produce HTML fragment.
Structure:
Location: San Jose, CA (On-site)
About the role
Ayar Labs is shattering AI data bottlenecks by moving data at the speed of light. As pioneers of co-packaged optics (CPO), we are using light instead of electricity to move data faster, further, and with a fraction of the energy needed to fuel the explosive growth of AI models. Backed by industry giants like NVIDIA, AMD, Mediatek and Intel and manufactured in partnership with the world’s leading semiconductor ecosystem, Ayar Labs’ co-packaged optics solution is key to unleashing next-generation AI scale-up architectures. Ayar Labs builds optical I/O technology for hyperscale AI infrastructure. This role owns reliability qualification at the system and fleet level: building the test infrastructure and evidence base that proves our products are ready for large-scale deployment, and then partnering directly with customers and integration partners to carry that evidence through joint qualification programs and pilot deployments. You will be responsible for both the engineering (test infrastructure, statistical reliability planning, standards compliance) and the relationship (translating technical evidence into the specific commitments our partners need to move forward).
Responsibilities
- Test infrastructure and evidence generation: Design, build, and operate custom test infrastructure that emulates real system-level electrical, thermal, and workload conditions ahead of, or independent of, any single customer's specific hardware. This includes sourcing or generating representative workload and power profiles and using them to drive continuous, long-duration test campaigns.
- Reliability statistics and demonstration planning: Define statistical sample sizes and test durations needed to demonstrate specific reliability and confidence targets, and apply the right methodology to each failure population in the system rather than a single blanket target.
- Standards and compliance: Ensure that test infrastructure, interfaces, and telemetry are built against relevant industry interconnect and management standards, so evidence generated internally holds up when reviewed by, or transferred to, an external partner's platform.
- Staged qualification execution: Execute staged qualification gates, from lab-level interoperability and functional testing through environmental and stress testing to live pilot deployment, applying a reliability / availability / serviceability lens throughout rather than treating any one dimension in isolation.
- Fault injection and lifecycle monitoring: Design and run fault-injection and failure-mode testing, including scenarios that exercise field-serviceable components under representative operating conditions, in partnership with customer and integration-partner operations teams.
- Economic modeling and fleet reporting: Provide reliability and performance data into cost-of-ownership and total-cost modeling shared with customers, and own ongoing fleet reliability reporting and incident response once products reach production.
- Cross-functional partnership: Serve as the primary technical point of contact with Tier-1 integration partners and hyperscale customer engineering teams across the qualification lifecycle, from early technical evidence through pilot sign-off and into steady-state operations.
Requirements
- 5+ years in fleet/systems reliability engineering for large-scale infrastructure, with a BS in Electrical Engineering, Computer Engineering, or a related field.
- You've built or operated test infrastructure that validates a component or subsystem's behavior before it is deployed into a customer's actual system, using representative rather than production hardware.
- You've defined and executed statistical reliability demonstration plans (sample sizes, test durations, confidence and reliability targets) for hardware components, and can explain the methodology behind them, not just apply a lookup table.
- You've worked with die-to-die, chip-to-chip, or board-level interconnect standards and telemetry or management interfaces relevant to high-speed data center hardware.
- You've partnered directly with external OEM or hyperscale customer engineering teams on a joint qualification or certification program, and are comfortable owning that relationship technically.
- Comfort operating a live, continuously running test or fleet environment: on-call coverage, incident response, and building the telemetry pipeline that turns raw sensor data into fleet-level reliability statistics.
- Strong written and verbal communication skills; you will regularly translate internal engineering data into evidence and
maybe. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Location is minor metadata; we can include in a short
. Probably include location. We also have "Ayar Labs is shattering AI data bottlenecks..." paragraph at start. That's about company; maybe part of About the role? Could be included in About the role section? The About The Role heading already has description. The introductory paragraph could be considered part of About the role? Might be considered company overview; but we can include it under About the role as prose. However we must not invent or summarize away detail; we need to preserve all substantive information. So we should include that introductory paragraph as part of About the role section (maybe before the heading? But heading is About The Role; we can put a
after heading containing that intro plus the role description. But we must not duplicate content. The About The Role section currently has a paragraph: "Ayar Labs builds optical I/O technology for hyperscale AI infrastructure. This role owns reliability qualification at the system and fleet level: building the test infrastructure and evidence base that proves our products are ready for large-scale deployment, and then partnering directly with customers and integration partners to carry that evidence through joint qualification programs and pilot deployments. You will be responsible for both the engineering (test infrastructure, statistical reliability planning, standards compliance) and the relationship (translating technical evidence into the specific commitments our partners need to move forward)." That's already there. The introductory paragraph before that is about company mission. Should we include it? It's substantive; we could put it as a
before the About the role heading? But heading must be
for section headings. We could have a
before the heading? The instruction: use
for section headings. It doesn't forbid other
outside sections. But we likely want to keep everything under sections. Could put the company overview inside About the role section as a preceding
. That would preserve it. Thus About the role section:
About the role
thencontaining company overview + role description. Now Responsibilities:
Responsibilities
then- each bullet from What You'll Own.
We need to ensure we capture each bullet exactly.
Let's list bullets:
- Test infrastructure and evidence generation: Design, build, and operate custom test infrastructure that emulates real system-level electrical, thermal, and workload conditions ahead of, or independent of, any single customer's specific hardware. This includes sourcing or generating representative workload and power profiles and using them to drive continuous, long-duration test campaigns.
- Reliability statistics and demonstration planning: Define statistical sample sizes and test durations needed to demonstrate specific reliability and confidence targets, and apply the right methodology to each failure population in the system rather than a single blanket target.
- Standards and compliance: Ensure that test infrastructure, interfaces, and telemetry are built against relevant industry interconnect and management standards, so evidence generated internally holds up when reviewed by, or transferred to, an external partner's platform.
- Staged qualification execution: Execute staged qualification gates, from lab-level interoperability and functional testing through environmental and stress testing to live pilot deployment, applying a reliability / availability / serviceability lens throughout rather than treating any one dimension in isolation.
- Fault injection and lifecycle monitoring: Design and run fault-injection and failure-mode testing, including scenarios that exercise field-serviceable components under representative operating conditions, in partnership with customer and integration-partner operations teams.
- Economic modeling and fleet reporting: Provide reliability and performance data into cost-of-ownership and total-cost modeling shared with customers, and own ongoing fleet reliability reporting and incident response once products reach production.
- Cross-functional partnership: Serve as the primary technical point of contact with Tier-1 integration partners and hyperscale customer engineering teams across the qualification lifecycle, from early technical evidence through pilot sign-off and into steady-state operations.
Now Basic Qualifications bullets:
- 5+ years in fleet/systems reliability engineering for large-scale infrastructure, with a BS in Electrical Engineering, Computer Engineering, or a related field.
- You've built or operated test infrastructure that validates a component or subsystem's behavior before it is deployed into a customer's actual system, using representative rather than production hardware.
- You've defined and executed statistical reliability demonstration plans (sample sizes, test durations, confidence and reliability targets) for hardware components, and can explain the methodology behind them, not just apply a lookup table.
- You've worked with die-to-die, chip-to-chip, or board-level interconnect standards and telemetry or management interfaces relevant to high-speed data center hardware.
- You've partnered directly with external OEM or hyperscale customer engineering teams on a joint qualification or certification program, and are comfortable owning that relationship technically.
- Comfort operating a live, continuously running test or fleet environment: on-call coverage, incident response, and building the telemetry pipeline that turns raw sensor data into fleet-level reliability statistics.
- Strong written and verbal communication skills; you will regularly translate internal engineering data into evidence and documentation for external partners.
Preferred Qualifications bullets:
- MS in Electrical Engineering, Computer Engineering, or a related field.
- Experience with FPGA-based test or signal-generation systems.
- Experience characterizing or emulating real compute or network workload behavior for use in a test or validation environment.
- Background in data-center fleet operations, site-reliability engineering, or customer-facing qualification and certification processes.
- Familiarity with co-packaged optics, silicon photonics, or other emerging interconnect packaging technologies.
Salary Range: $185,000 - $290,000.
Location: San Jose, CA (On-site). We'll put in a
maybe before sections. We must not include any boilerplate like Note To Recruiters, Equal Opportunity Employer, etc. Now produce HTML fragment. Structure:
Location: San Jose, CA (On-site)
About the role
Ayar Labs is shattering AI data bottlenecks by moving data at the speed of light. As pioneers of co-packaged optics (CPO), we are using light instead of electricity to move data faster, further, and with a fraction of the energy needed to fuel the explosive growth of AI models. Backed by industry giants like NVIDIA, AMD, Mediatek and Intel and manufactured in partnership with the world’s leading semiconductor ecosystem, Ayar Labs’ co-packaged optics solution is key to unleashing next-generation AI scale-up architectures. Ayar Labs builds optical I/O technology for hyperscale AI infrastructure. This role owns reliability qualification at the system and fleet level: building the test infrastructure and evidence base that proves our products are ready for large-scale deployment, and then partnering directly with customers and integration partners to carry that evidence through joint qualification programs and pilot deployments. You will be responsible for both the engineering (test infrastructure, statistical reliability planning, standards compliance) and the relationship (translating technical evidence into the specific commitments our partners need to move forward).
Responsibilities
- Test infrastructure and evidence generation: Design, build, and operate custom test infrastructure that emulates real system-level electrical, thermal, and workload conditions ahead of, or independent of, any single customer's specific hardware. This includes sourcing or generating representative workload and power profiles and using them to drive continuous, long-duration test campaigns.
- Reliability statistics and demonstration planning: Define statistical sample sizes and test durations needed to demonstrate specific reliability and confidence targets, and apply the right methodology to each failure population in the system rather than a single blanket target.
- Standards and compliance: Ensure that test infrastructure, interfaces, and telemetry are built against relevant industry interconnect and management standards, so evidence generated internally holds up when reviewed by, or transferred to, an external partner's platform.
- Staged qualification execution: Execute staged qualification gates, from lab-level interoperability and functional testing through environmental and stress testing to live pilot deployment, applying a reliability / availability / serviceability lens throughout rather than treating any one dimension in isolation.
- Fault injection and lifecycle monitoring: Design and run fault-injection and failure-mode testing, including scenarios that exercise field-serviceable components under representative operating conditions, in partnership with customer and integration-partner operations teams.
- Economic modeling and fleet reporting: Provide reliability and performance data into cost-of-ownership and total-cost modeling shared with customers, and own ongoing fleet reliability reporting and incident response once products reach production.
- Cross-functional partnership: Serve as the primary technical point of contact with Tier-1 integration partners and hyperscale customer engineering teams across the qualification lifecycle, from early technical evidence through pilot sign-off and into steady-state operations.
Requirements
- 5+ years in fleet/systems reliability engineering for large-scale infrastructure, with a BS in Electrical Engineering, Computer Engineering, or a related field.
- You've built or operated test infrastructure that validates a component or subsystem's behavior before it is deployed into a customer's actual system, using representative rather than production hardware.
- You've defined and executed statistical reliability demonstration plans (sample sizes, test durations, confidence and reliability targets) for hardware components, and can explain the methodology behind them, not just apply a lookup table.
- You've worked with die-to-die, chip-to-chip, or board-level interconnect standards and telemetry or management interfaces relevant to high-speed data center hardware.
- You've partnered directly with external OEM or hyperscale customer engineering teams on a joint qualification or certification program, and are comfortable owning that relationship technically.
- Comfort operating a live, continuously running test or fleet environment: on-call coverage, incident response, and building the telemetry pipeline that turns raw sensor data into fleet-level reliability statistics.
- Strong written and verbal communication skills; you will regularly translate internal engineering data into evidence and