Mechanical Engineer, Hardware Systems
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for any list of duties/requirements/benefits, and
for prose
3. Do NOT repeat the job title as a heading (the page already shows it)
4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it
5. Preserve ALL substantive information; do NOT invent or summarize away detail
6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text
8. Never create Pay/Schedule/Benefits sections unless the posting actually states them
9. Prefer a few substantive sections over many thin ones
10. Output ONLY the HTML fragment — no /, no markdown code fences
Let me analyze the job posting content:
- "About The Team" - this is about the team, could be a section
- "About The Role" - this is about the role, could be a section
- "In This Role, You Will" - this is responsibilities/duties
- "You Might Thrive In This Role If You" - this is requirements/qualifications
- "Preferred Skills" - this is preferred qualifications
- "About OpenAI" - this is company info, but contains a lot of boilerplate (EEO, background checks, privacy policy, etc.)
- "Compensation Range: $266K - $455K" - this is pay information
I need to structure this appropriately. The posting has:
- Team description
- Role description
- Responsibilities (list)
- Requirements (list)
- Preferred skills (list)
- Location/work model info (San Francisco, hybrid 3 days, relocation assistance)
- Compensation range
I should create sections for:
- About the team (or maybe combine with role?)
- About the role
- Responsibilities
- Requirements (or Qualifications)
- Preferred qualifications (or Skills)
- Location/Work model (maybe as a short paragraph)
- Pay (since compensation range is given)
But the rules say: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I should use those standard headings where appropriate.
Also: "Do NOT repeat the job title as a heading (the page already shows it)" - there's no job title in the provided text, so that's fine.
"do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it" - no job ID present.
"Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions" - The "About OpenAI" section contains a lot of EEO, background check, privacy policy, etc. That should be removed.
"include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text" - So I should only include sections that have real content.
"never create Pay/Schedule/Benefits sections unless the posting actually states them" - The posting states "Compensation Range: $266K - $455K", so Pay section is appropriate. Schedule: hybrid work model 3 days in office per week is mentioned, so maybe Schedule section. Benefits: not explicitly mentioned except relocation assistance, but that's minor. Could include in a short paragraph.
Let me structure:
1. About the team (from "About The Team")
2. About the role (from "About The Role")
3. Responsibilities (from "In This Role, You Will")
4. Requirements (from "You Might Thrive In This Role If You")
5. Preferred qualifications (from "Preferred Skills")
6. Work location & schedule (hybrid, San Francisco, relocation)
7. Pay (compensation range)
I'll use
for each section heading. For lists, use - . For prose, use
.
I need to preserve all substantive information. Let me extract each part.
About The Team: "OpenAI’s Hardware organization develops silicon and system-level solutions designed for the unique demands of advanced AI workloads. The team is responsible for building the next generation of AI-native silicon while working closely with software and research partners to co-design hardware tightly integrated with AI models. In addition to delivering production-grade silicon for OpenAI’s supercomputing infrastructure, the team also creates custom design tools and methodologies that accelerate innovation and enable hardware optimized specifically for AI."
About The Role: "We are looking for an experienced Mechanical Engineer with 7+ years of experience in design of IT hardware from chip/package to system levels. You’ll work alongside experts in thermal, mechanical, electrical, software, and systems engineering to support the design, analysis, and validation of mechanical and thermal systems that ensure the reliability, efficiency, and longevity of mission-critical hardware. This position requires strong analytical skills, hands-on testing experience, and the ability to work in a fast-paced, cross-disciplinary environment. This role is based in San Francisco, CA. We use a hybrid work model of 3 days in the office per week and offer relocation assistance to new employees."
In This Role, You Will (list):
- Lead mechanical design for AI supercomputer product in the data center application
- Collaborate with the cross functional team to design and optimize thermal solutions for data center hardware, including chips, power modules, and system-level cooling architectures
- Collaborate with cross-functional teams to integrate thermal management strategies into hardware design, from concept to mass production
- Design and validate mechanical systems, including chassis, enclosures, cooling systems, and high-power connections, ensuring alignment with performance and reliability standards.
- Perform 3D modeling, FEA, tolerance analysis, and prototyping, ensuring manufacturability and adherence to strict quality requirements.
- Conduct mechanical testing, including vibration, shock, and thermal cycling, to ensure long-term reliability under extreme operating conditions.
- Identify and evaluate new technologies and methodologies to improve mechanical and thermal performance in product design, and contribute to the development of new products and technology by providing expertise in mechanical design
- Develop appropriate specifications and test procedures as necessary to ensure desired reliability and performance of electronic equipment, collaborate, supervise, mentor, and motivate suppliers to design and develop excellent products, and mentor engineers in all aspects of concept development, analysis, design, and specification
- Lead the production and launch of new products and technologies and ensure compliance with relevant quality standards and regulation
- Partner with suppliers and manufacturers to support the development of custom mechanical and thermal components and ensure quality in production
You Might Thrive In This Role If You (requirements):
- Bachelor’s degree in Mechanical Engineering, or a related field (Master’s preferred).
- 7+ years of industry experience in mechanical design, simulation, and validation for IT hardware
- Proficiency in CAD tools and FEA
- Strong understanding of mechanical design, material properties, manufacturing methods, and test procedures
- Ability to analyze experimental data, identify root causes of mechanical or manufacturing issues, and implement corrective actions
- Strong problem-solving skills, with the ability to perform first-principles calculations to support design decisions.
- Self-driven, detail-oriented, and able to work independently or collaboratively in cross-functional engineering environments
Preferred Skills:
- 10+ years of industry experience in mechanical design, simulation, and validation for IT hardware
- Extensive experience with data center hardware or high-performance computing systems at scale
- Practical experience in co-developing advanced cooling technologies
- Deep understanding of reliability testing, failure analysis, and thermal stress modeling and testing for electronic components
- Experience working with suppliers and manufacturing partners to support new technology development and production ramp-up
Compensation Range: $266K - $455K
Now, I need to output HTML fragment. No markdown code fences. Just the HTML.
I'll create sections with h3 headings. For the team and role descriptions, they are prose, so use
. For lists, use
- .
I'll combine location/schedule into a short paragraph maybe under "Work location & schedule" or just include in About the role? The About the role already mentions location and hybrid model. But the rules suggest Schedule section if posting states it. It does state hybrid work model 3 days per week. So I could create a Schedule section. But the example headings include "Schedule". However, the posting doesn't have a separate schedule section; it's mentioned in About the Role. I could extract it into a Schedule section. But the rule: "include a section ONLY when the posting has real, specific content for it". The posting has specific content about schedule (hybrid 3 days). So I can create a Schedule section. Similarly, Pay section for compensation range.
Benefits: only relocation assistance mentioned, not a full benefits package. So maybe not a Benefits section.
I'll create:
- About the team
- About the role
- Responsibilities
- Requirements
- Preferred qualifications
- Schedule
- Pay
But note: "About the role" already includes location and schedule. I could keep it there and not duplicate. However, the rules say to use standard headings. I think it's okay to have a separate Schedule section with the hybrid info. But the location is also mentioned. Could combine into "Work location & schedule". But the example headings include "Schedule". I'll do Schedule.
Let me write the HTML.
I need to be careful: "Do NOT repeat the job title as a heading" - no job title in text.
"Output ONLY the HTML fragment — no /, no markdown code fences."
So I'll output something like:
About the team
...
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Preferred qualifications
- ...
...
Schedule
Hybrid work model: 3 days in the office per week. Role based in San Francisco, CA; relocation assistance offered.
Pay
Compensation range: $266K - $455K
But the "About the role" paragraph already includes location and schedule. If I include Schedule separately, I might duplicate. I could remove the schedule info from About the role and put it in Schedule. But the rule: "Preserve ALL substantive information; do NOT invent or summarize away detail." I can keep it in both? Better to not duplicate. I'll keep the About the role paragraph as is (including location and schedule), and then add a Schedule section that repeats? That would duplicate. Better to extract the schedule info from About the role and put it in Schedule, and keep About the role focused on role description. However, the About the role paragraph is a cohesive paragraph. I could split it: first part about role, second part about location/schedule. But the rule says to preserve all substantive information. I think it's okay to have the location/schedule in About the role and also have a Schedule section? That would be duplication. The instruction: "Remove duplicated lines". So I should avoid duplication.
Thus, I'll keep the About the role paragraph but remove the location/schedule sentences, and put them in Schedule. But the paragraph is: "We are looking for an experienced Mechanical Engineer with 7+ years of experience in design of IT hardware from chip/package to system levels. You’ll work alongside experts in thermal, mechanical, electrical, software, and systems engineering to support the design, analysis, and validation of mechanical and thermal systems that ensure the reliability, efficiency, and longevity of mission-critical hardware. This position requires strong
for prose 3. Do NOT repeat the job title as a heading (the page already shows it) 4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting content: - "About The Team" - this is about the team, could be a section - "About The Role" - this is about the role, could be a section - "In This Role, You Will" - this is responsibilities/duties - "You Might Thrive In This Role If You" - this is requirements/qualifications - "Preferred Skills" - this is preferred qualifications - "About OpenAI" - this is company info, but contains a lot of boilerplate (EEO, background checks, privacy policy, etc.) - "Compensation Range: $266K - $455K" - this is pay information I need to structure this appropriately. The posting has: - Team description - Role description - Responsibilities (list) - Requirements (list) - Preferred skills (list) - Location/work model info (San Francisco, hybrid 3 days, relocation assistance) - Compensation range I should create sections for: - About the team (or maybe combine with role?) - About the role - Responsibilities - Requirements (or Qualifications) - Preferred qualifications (or Skills) - Location/Work model (maybe as a short paragraph) - Pay (since compensation range is given) But the rules say: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I should use those standard headings where appropriate. Also: "Do NOT repeat the job title as a heading (the page already shows it)" - there's no job title in the provided text, so that's fine. "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it" - no job ID present. "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions" - The "About OpenAI" section contains a lot of EEO, background check, privacy policy, etc. That should be removed. "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text" - So I should only include sections that have real content. "never create Pay/Schedule/Benefits sections unless the posting actually states them" - The posting states "Compensation Range: $266K - $455K", so Pay section is appropriate. Schedule: hybrid work model 3 days in office per week is mentioned, so maybe Schedule section. Benefits: not explicitly mentioned except relocation assistance, but that's minor. Could include in a short paragraph. Let me structure: 1. About the team (from "About The Team") 2. About the role (from "About The Role") 3. Responsibilities (from "In This Role, You Will") 4. Requirements (from "You Might Thrive In This Role If You") 5. Preferred qualifications (from "Preferred Skills") 6. Work location & schedule (hybrid, San Francisco, relocation) 7. Pay (compensation range) I'll use
for each section heading. For lists, use - . For prose, use
.
I need to preserve all substantive information. Let me extract each part.
About The Team: "OpenAI’s Hardware organization develops silicon and system-level solutions designed for the unique demands of advanced AI workloads. The team is responsible for building the next generation of AI-native silicon while working closely with software and research partners to co-design hardware tightly integrated with AI models. In addition to delivering production-grade silicon for OpenAI’s supercomputing infrastructure, the team also creates custom design tools and methodologies that accelerate innovation and enable hardware optimized specifically for AI."
About The Role: "We are looking for an experienced Mechanical Engineer with 7+ years of experience in design of IT hardware from chip/package to system levels. You’ll work alongside experts in thermal, mechanical, electrical, software, and systems engineering to support the design, analysis, and validation of mechanical and thermal systems that ensure the reliability, efficiency, and longevity of mission-critical hardware. This position requires strong analytical skills, hands-on testing experience, and the ability to work in a fast-paced, cross-disciplinary environment. This role is based in San Francisco, CA. We use a hybrid work model of 3 days in the office per week and offer relocation assistance to new employees."
In This Role, You Will (list):
- Lead mechanical design for AI supercomputer product in the data center application
- Collaborate with the cross functional team to design and optimize thermal solutions for data center hardware, including chips, power modules, and system-level cooling architectures
- Collaborate with cross-functional teams to integrate thermal management strategies into hardware design, from concept to mass production
- Design and validate mechanical systems, including chassis, enclosures, cooling systems, and high-power connections, ensuring alignment with performance and reliability standards.
- Perform 3D modeling, FEA, tolerance analysis, and prototyping, ensuring manufacturability and adherence to strict quality requirements.
- Conduct mechanical testing, including vibration, shock, and thermal cycling, to ensure long-term reliability under extreme operating conditions.
- Identify and evaluate new technologies and methodologies to improve mechanical and thermal performance in product design, and contribute to the development of new products and technology by providing expertise in mechanical design
- Develop appropriate specifications and test procedures as necessary to ensure desired reliability and performance of electronic equipment, collaborate, supervise, mentor, and motivate suppliers to design and develop excellent products, and mentor engineers in all aspects of concept development, analysis, design, and specification
- Lead the production and launch of new products and technologies and ensure compliance with relevant quality standards and regulation
- Partner with suppliers and manufacturers to support the development of custom mechanical and thermal components and ensure quality in production
You Might Thrive In This Role If You (requirements):
- Bachelor’s degree in Mechanical Engineering, or a related field (Master’s preferred).
- 7+ years of industry experience in mechanical design, simulation, and validation for IT hardware
- Proficiency in CAD tools and FEA
- Strong understanding of mechanical design, material properties, manufacturing methods, and test procedures
- Ability to analyze experimental data, identify root causes of mechanical or manufacturing issues, and implement corrective actions
- Strong problem-solving skills, with the ability to perform first-principles calculations to support design decisions.
- Self-driven, detail-oriented, and able to work independently or collaboratively in cross-functional engineering environments
Preferred Skills:
- 10+ years of industry experience in mechanical design, simulation, and validation for IT hardware
- Extensive experience with data center hardware or high-performance computing systems at scale
- Practical experience in co-developing advanced cooling technologies
- Deep understanding of reliability testing, failure analysis, and thermal stress modeling and testing for electronic components
- Experience working with suppliers and manufacturing partners to support new technology development and production ramp-up
Compensation Range: $266K - $455K
Now, I need to output HTML fragment. No markdown code fences. Just the HTML.
I'll create sections with h3 headings. For the team and role descriptions, they are prose, so use
. For lists, use
- .
I'll combine location/schedule into a short paragraph maybe under "Work location & schedule" or just include in About the role? The About the role already mentions location and hybrid model. But the rules suggest Schedule section if posting states it. It does state hybrid work model 3 days per week. So I could create a Schedule section. But the example headings include "Schedule". However, the posting doesn't have a separate schedule section; it's mentioned in About the Role. I could extract it into a Schedule section. But the rule: "include a section ONLY when the posting has real, specific content for it". The posting has specific content about schedule (hybrid 3 days). So I can create a Schedule section. Similarly, Pay section for compensation range.
Benefits: only relocation assistance mentioned, not a full benefits package. So maybe not a Benefits section.
I'll create:
- About the team
- About the role
- Responsibilities
- Requirements
- Preferred qualifications
- Schedule
- Pay
But note: "About the role" already includes location and schedule. I could keep it there and not duplicate. However, the rules say to use standard headings. I think it's okay to have a separate Schedule section with the hybrid info. But the location is also mentioned. Could combine into "Work location & schedule". But the example headings include "Schedule". I'll do Schedule.
Let me write the HTML.
I need to be careful: "Do NOT repeat the job title as a heading" - no job title in text.
"Output ONLY the HTML fragment — no /, no markdown code fences."
So I'll output something like:
About the team
...
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Preferred qualifications
- ...
...
Schedule
Hybrid work model: 3 days in the office per week. Role based in San Francisco, CA; relocation assistance offered.
Pay
Compensation range: $266K - $455K
But the "About the role" paragraph already includes location and schedule. If I include Schedule separately, I might duplicate. I could remove the schedule info from About the role and put it in Schedule. But the rule: "Preserve ALL substantive information; do NOT invent or summarize away detail." I can keep it in both? Better to not duplicate. I'll keep the About the role paragraph as is (including location and schedule), and then add a Schedule section that repeats? That would duplicate. Better to extract the schedule info from About the role and put it in Schedule, and keep About the role focused on role description. However, the About the role paragraph is a cohesive paragraph. I could split it: first part about role, second part about location/schedule. But the rule says to preserve all substantive information. I think it's okay to have the location/schedule in About the role and also have a Schedule section? That would be duplication. The instruction: "Remove duplicated lines". So I should avoid duplication.
Thus, I'll keep the About the role paragraph but remove the location/schedule sentences, and put them in Schedule. But the paragraph is: "We are looking for an experienced Mechanical Engineer with 7+ years of experience in design of IT hardware from chip/package to system levels. You’ll work alongside experts in thermal, mechanical, electrical, software, and systems engineering to support the design, analysis, and validation of mechanical and thermal systems that ensure the reliability, efficiency, and longevity of mission-critical hardware. This position requires strong
. I need to preserve all substantive information. Let me extract each part. About The Team: "OpenAI’s Hardware organization develops silicon and system-level solutions designed for the unique demands of advanced AI workloads. The team is responsible for building the next generation of AI-native silicon while working closely with software and research partners to co-design hardware tightly integrated with AI models. In addition to delivering production-grade silicon for OpenAI’s supercomputing infrastructure, the team also creates custom design tools and methodologies that accelerate innovation and enable hardware optimized specifically for AI." About The Role: "We are looking for an experienced Mechanical Engineer with 7+ years of experience in design of IT hardware from chip/package to system levels. You’ll work alongside experts in thermal, mechanical, electrical, software, and systems engineering to support the design, analysis, and validation of mechanical and thermal systems that ensure the reliability, efficiency, and longevity of mission-critical hardware. This position requires strong analytical skills, hands-on testing experience, and the ability to work in a fast-paced, cross-disciplinary environment. This role is based in San Francisco, CA. We use a hybrid work model of 3 days in the office per week and offer relocation assistance to new employees." In This Role, You Will (list): - Lead mechanical design for AI supercomputer product in the data center application - Collaborate with the cross functional team to design and optimize thermal solutions for data center hardware, including chips, power modules, and system-level cooling architectures - Collaborate with cross-functional teams to integrate thermal management strategies into hardware design, from concept to mass production - Design and validate mechanical systems, including chassis, enclosures, cooling systems, and high-power connections, ensuring alignment with performance and reliability standards. - Perform 3D modeling, FEA, tolerance analysis, and prototyping, ensuring manufacturability and adherence to strict quality requirements. - Conduct mechanical testing, including vibration, shock, and thermal cycling, to ensure long-term reliability under extreme operating conditions. - Identify and evaluate new technologies and methodologies to improve mechanical and thermal performance in product design, and contribute to the development of new products and technology by providing expertise in mechanical design - Develop appropriate specifications and test procedures as necessary to ensure desired reliability and performance of electronic equipment, collaborate, supervise, mentor, and motivate suppliers to design and develop excellent products, and mentor engineers in all aspects of concept development, analysis, design, and specification - Lead the production and launch of new products and technologies and ensure compliance with relevant quality standards and regulation - Partner with suppliers and manufacturers to support the development of custom mechanical and thermal components and ensure quality in production You Might Thrive In This Role If You (requirements): - Bachelor’s degree in Mechanical Engineering, or a related field (Master’s preferred). - 7+ years of industry experience in mechanical design, simulation, and validation for IT hardware - Proficiency in CAD tools and FEA - Strong understanding of mechanical design, material properties, manufacturing methods, and test procedures - Ability to analyze experimental data, identify root causes of mechanical or manufacturing issues, and implement corrective actions - Strong problem-solving skills, with the ability to perform first-principles calculations to support design decisions. - Self-driven, detail-oriented, and able to work independently or collaboratively in cross-functional engineering environments Preferred Skills: - 10+ years of industry experience in mechanical design, simulation, and validation for IT hardware - Extensive experience with data center hardware or high-performance computing systems at scale - Practical experience in co-developing advanced cooling technologies - Deep understanding of reliability testing, failure analysis, and thermal stress modeling and testing for electronic components - Experience working with suppliers and manufacturing partners to support new technology development and production ramp-up Compensation Range: $266K - $455K Now, I need to output HTML fragment. No markdown code fences. Just the HTML. I'll create sections with h3 headings. For the team and role descriptions, they are prose, so use
. For lists, use
- .
I'll combine location/schedule into a short paragraph maybe under "Work location & schedule" or just include in About the role? The About the role already mentions location and hybrid model. But the rules suggest Schedule section if posting states it. It does state hybrid work model 3 days per week. So I could create a Schedule section. But the example headings include "Schedule". However, the posting doesn't have a separate schedule section; it's mentioned in About the Role. I could extract it into a Schedule section. But the rule: "include a section ONLY when the posting has real, specific content for it". The posting has specific content about schedule (hybrid 3 days). So I can create a Schedule section. Similarly, Pay section for compensation range.
Benefits: only relocation assistance mentioned, not a full benefits package. So maybe not a Benefits section.
I'll create:
- About the team
- About the role
- Responsibilities
- Requirements
- Preferred qualifications
- Schedule
- Pay
But note: "About the role" already includes location and schedule. I could keep it there and not duplicate. However, the rules say to use standard headings. I think it's okay to have a separate Schedule section with the hybrid info. But the location is also mentioned. Could combine into "Work location & schedule". But the example headings include "Schedule". I'll do Schedule.
Let me write the HTML.
I need to be careful: "Do NOT repeat the job title as a heading" - no job title in text.
"Output ONLY the HTML fragment — no /, no markdown code fences."
So I'll output something like:
About the team
...
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Preferred qualifications
- ... ...
Schedule
Hybrid work model: 3 days in the office per week. Role based in San Francisco, CA; relocation assistance offered.
Pay
Compensation range: $266K - $455K
But the "About the role" paragraph already includes location and schedule. If I include Schedule separately, I might duplicate. I could remove the schedule info from About the role and put it in Schedule. But the rule: "Preserve ALL substantive information; do NOT invent or summarize away detail." I can keep it in both? Better to not duplicate. I'll keep the About the role paragraph as is (including location and schedule), and then add a Schedule section that repeats? That would duplicate. Better to extract the schedule info from About the role and put it in Schedule, and keep About the role focused on role description. However, the About the role paragraph is a cohesive paragraph. I could split it: first part about role, second part about location/schedule. But the rule says to preserve all substantive information. I think it's okay to have the location/schedule in About the role and also have a Schedule section? That would be duplication. The instruction: "Remove duplicated lines". So I should avoid duplication. Thus, I'll keep the About the role paragraph but remove the location/schedule sentences, and put them in Schedule. But the paragraph is: "We are looking for an experienced Mechanical Engineer with 7+ years of experience in design of IT hardware from chip/package to system levels. You’ll work alongside experts in thermal, mechanical, electrical, software, and systems engineering to support the design, analysis, and validation of mechanical and thermal systems that ensure the reliability, efficiency, and longevity of mission-critical hardware. This position requires strong