Senior High Speed SerDes Validation Engineer

We need to output HTML fragment with sections: About the role? The posting includes description: NVIDIA intro, then "We are now looking for a Senior Validation Engineer...". We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We need to parse content: - About the role: Could be the introductory paragraph describing role? The posting says: "We are now looking for a Senior Validation Engineer in the DGX Server Product Engineering Team. In this role you will be working with a team of HW/SW engineers to develop and implement complex automated test plans for our industry leading GPU accelerated computing products." That's about the role. - Responsibilities: The bullet list after "What You Will Be Doing": Own validation of products from start to finish including test plan development, automation, design for validation requirements, resource planning, coverage metrics, test execution, bug resolution, and release to production. Collaborate with ODMs, component suppliers, and QA teams to ensure no gaps in coverage. Coordinate internal and external teams in different times zones. Develop system level stress and performance testing strategies using industry leading Deep Learning/AI applications. Solve complex system level hardware and software issues on GPU accelerated computing platforms. - Requirements/Qualifications/Skills: The posting has "What We Need To See" list: Ability to work on site in hardware lab environment 5 days a week; BSEE or BSCE or equivalent experience; High speed IO validation; 6+ years or more of experience in validating and debugging complex systems.; Developing/running real world workload and factory diagnosis tools; Outstanding verbal and written communication skills.; Proficient in collaborating across teams and suppliers to deliver quality products on tight schedules.; Familiarity with lab instrumentations like Oscilloscopes (Digital Multi Meter); High-speed SERDES validation experience (50GBaud/s and above) is a must.; Strong understanding of DSP-based high-speed SERDES architectures as well as coding experience with programming and scripting languages such as C/C++, JS and Python. - Ways To Stand Out From The Crowd: Experience with datacenter products including system management, security, networking, and storage.; Familiarity with Ethernet and InfiniBand switch architectures is a strong plus.; Hands-on experience with SERDES performance tuning would be a strong advantage.; Track record of continuous process improvement with a passion for tools and automation.; Proven knowledge in Circuit and Waveform analysis. - Pay: "Your base salary will be determined based on your location, experience, and the pay of employees in similar positions. The base salary range is 168,000 USD - 264,500 USD for Level 4, and 196,000 USD - 310,500 USD for Level 5. You will also be eligible for equity and benefits." - Benefits: Not explicitly listed beyond equity and benefits mention. Could include "You will also be eligible for equity and benefits." That's vague; but we can include a Benefits section with that statement? The rule: 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. Here we have Pay specifics (range). Benefits: only mention "eligible for equity and benefits" but no specifics. That might be considered vague; but it's still some content: equity and benefits. However it's not specific like health insurance, 401k, etc. Might be considered too vague? The rule says avoid filler/placeholder text like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "Eligible for equity and benefits" is not exactly placeholder but still vague. I'd lean to include Benefits section with that sentence. - Schedule: Not mentioned besides "Ability to work on site in hardware lab environment 5 days a week". That's schedule info (5 days a week onsite). So we can include Schedule section with that. We must not repeat job title as heading. No Job ID etc. We need to output only HTML fragment, no /, no markdown fences. Structure: Use

for each section heading. Then content: either

for prose, or

• for lists. We need to preserve all substantive information; do not invent or summarize away detail. Let's craft sections:

  About the role

  We are now looking for a Senior Validation Engineer in the DGX Server Product Engineering Team. In this role you will be working with a team of HW/SW engineers to develop and implement complex automated test plans for our industry leading GPU accelerated computing products.

  Responsibilities

  • Own validation of products from start to finish including test plan development, automation, design for validation requirements, resource planning, coverage metrics, test execution, bug resolution, and release to production.
  • Collaborate with ODMs, component suppliers, and QA teams to ensure no gaps in coverage.
  • Coordinate internal and external teams in different time zones.
  • Develop system level stress and performance testing strategies using industry leading Deep Learning/AI applications.
  • Solve complex system level hardware and software issues on GPU accelerated computing platforms.

  Requirements

  • Ability to work on site in hardware lab environment 5 days a week
  • BSEE or BSCE or equivalent experience
  • High speed IO validation
  • 6+ years or more of experience in validating and debugging complex systems
  • Developing/running real world workload and factory diagnosis tools
  • Outstanding verbal and written communication skills
  • Proficient in collaborating across teams and suppliers to deliver quality products on tight schedules
  • Familiarity with lab instrumentations like Oscilloscopes (Digital Multi Meter)
  • High-speed SERDES validation experience (50GBaud/s and above) is a must
  • Strong understanding of DSP-based high-speed SERDES architectures as well as coding experience with programming and scripting languages such as C/C++, JS and Python
  We could also separate Qualifications and Skills but we have many items; maybe combine into Requirements and Skills? The instruction says use headings like Requirements, Qualifications, Skills. We could split: Requirements (education, experience), Skills (technical). But we must not create thin sections. Let's think: We have many items; we could put all under Requirements. Or we could split: Requirements (education, experience, ability to work onsite) and Skills (technical). But we need to avoid filler. Let's decide: Use Requirements for education/experience/onsite, and Skills for technical abilities. However we need to ensure each section has substantive content. Let's extract: Education/experience/onsite: - Ability to work on site in hardware lab environment 5 days a week (maybe schedule) - BSEE or BSCE or equivalent experience - 6+ years or more of experience in validating and debugging complex systems - Developing/running real world workload and factory diagnosis tools - Outstanding verbal and written communication skills - Proficient in collaborating across teams and suppliers to deliver quality products on tight schedules Technical skills: - High speed IO validation - High-speed SERDES validation experience (50GBaud/s and above) is a must - Strong understanding of DSP-based high-speed SERDES architectures as well as coding experience with programming and scripting languages such as C/C++, JS and Python - Familiarity with lab instrumentations like Oscilloscopes (Digital Multi Meter) But also "High speed IO validation" maybe skill. We could also have a separate "Qualifications" for education/experience, and "Skills" for technical. But we need to avoid too many thin sections. However we have enough content for each. Let's plan sections: About the role Responsibilities Qualifications (education/experience/onsite) Skills (technical) Benefits (equity and benefits) Pay (salary range) Schedule (onsite 5 days a week) - but we already put onsite in Qualifications; maybe schedule separate. But schedule is basically the same as ability to work onsite 5 days a week. Could put under Schedule. Let's decide: - About the role - Responsibilities - Qualifications (education, experience, communication, collaboration) - Skills (technical: high speed IO, SERDES, DSP, lab instruments, programming languages) - Benefits (eligible for equity and benefits) - Pay (salary ranges) - Schedule (ability to work on site in hardware lab environment 5 days a week) Check for duplication: Qualifications includes ability to work onsite? We'll move that to Schedule only, not duplicate. Thus Qualifications: BSEE/BSCE or equivalent experience; 6+ years experience validating/debugging complex systems; developing/running real world workload and factory diagnosis tools; outstanding verbal/written communication skills; proficient in collaborating across teams and suppliers to deliver quality products on tight schedules. Skills: High speed IO validation; High-speed SERDES validation experience (50GBaud/s and above) is a must; Strong understanding of DSP-based high-speed SERDES architectures as well as coding experience with programming and scripting languages such as C/C++, JS and Python; Familiarity with lab instrumentations like Oscilloscopes (Digital Multi Meter). Benefits: You will also be eligible for equity and benefits. Pay: Your base salary will be determined based on your location, experience, and the pay of employees in similar positions. The base salary range is 168,000 USD - 264,500 USD for Level 4, and 196,000 USD - 310,500 USD for Level 5. You will also be eligible for equity and benefits. (But we already mentioned equity in Benefits; we could keep Pay section focusing on salary range only, and mention equity in Benefits.) Schedule: Ability to work on site in hardware lab environment 5 days a week. Now ensure we don't repeat content. In Pay we should not repeat equity line if we already have Benefits. We'll keep Pay just about salary range. Now produce HTML. Make sure to use

  headings,

  for prose,

  • for lists. Check for any boilerplate: The posting includes NVIDIA intro about GPU invention etc. That's not part of role specifics? It's general company description. Should we include that? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The intro about NVIDIA's history is substantive but not about the role. However the instruction also says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should structure the job posting content into those sections. The company intro could go under "About the role" or maybe a separate section like "About NVIDIA". But not listed as allowed headings. The allowed headings list includes those specific ones; we should only use those headings. The company intro could be considered part of "About the role"? It's about the company, not role. But we could include it in About the role paragraph as context. However the instruction says "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." It doesn't forbid other content outside those headings. But we should output only HTML fragment; we can include a

    for the company intro before any headings? The instruction says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills