Silicon Photonics Reliability Engineering Intern (Summer 2027)
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we should map headings to these generic names? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those exact headings? Probably we should use those headings as appropriate, but we can also use other headings if they match content? The examples given are typical headings. Likely we should rename sections to those standard headings. However we must preserve all substantive information; we can rephrase headings to match those categories. For example, "About GlobalFoundries" could be "About the role"? Not exactly. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It may mean we should use those headings when applicable; if a section doesn't match, we could still use a heading but maybe better to map content to those headings. Let's interpret: We should produce headings like About the role
, Responsibilities
, Requirements
, Qualifications
, Skills
, Benefits
, Pay
, Schedule
. Only include sections when posting has real specific content. So we need to decide which of these sections we have content for.
We have:
- About the role: we have "Summary Of Role" and maybe "About GlobalFoundries" and "Internship Program Overview". Could combine into About the role.
- Responsibilities: we have "Essential Responsibilities Include" and "Other Responsibilities". So we can put under Responsibilities.
- Requirements: we have "Required Qualifications". Could be Requirements.
- Qualifications: we have "Preferred Qualifications". Could be Qualifications (or Skills). But we already used Requirements for required; we could have Qualifications for preferred.
- Skills: maybe we could extract skills from qualifications? But we might not need a separate Skills section if not explicit. The instruction says prefer a few substantive sections over many thin ones. So we could combine Required and Preferred into Qualifications? But they said use headings like Requirements, Qualifications, Skills. Could treat Required Qualifications as Requirements, Preferred Qualifications as Qualifications, and maybe Skills as a subsection? But we could also put skills under Qualifications.
- Benefits: not mentioned explicitly; no benefits described. So we should not include Benefits.
- Pay: we have Expected Salary Range. So we can include Pay.
- Schedule: we have ability to work at least 40 hours per week. That's schedule info. So we can include Schedule.
Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Pay, Schedule.
We must not repeat job title as heading. No job title given explicitly but it's Reliability Engineering Intern. We'll not add heading for that.
We must use - for any list of duties/requirements/benefits. So for responsibilities list, we need to convert each responsibility into
- . For required qualifications list, each bullet into
- . For preferred qualifications list similarly.
We must use
for prose.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is a lot of EEO statement. We must remove that. Also remove lines about accommodation request? That is not EEO but maybe considered accommodation info; it's not boilerplate? It's about reasonable accommodation. Might be considered part of employment process; but it's not explicitly listed as boilerplate to remove. However it's somewhat generic; but it's substantive? It's about accommodation request. Might be considered part of application instructions? It says "If you need a reasonable accommodation for any part of the employment process, please contact us..." That's like application instruction. The instruction says remove application instructions. So we should remove that accommodation request paragraph. Also remove the line about offer conditioned upon pre-employment conditions etc. That's also boilerplate/legal. Remove that too. Also remove the EEO statement at the end.
Thus we keep: About GlobalFoundries, Internship Program Overview, Summary Of Role, Essential Responsibilities Include, Other Responsibilities, Required Qualifications, Preferred Qualifications, Expected Salary Range (though there is duplicate weird lines). Also we have "Expected Salary Range $20.00 - $40.0 Expected Salary Range $0.00 - $0.00 The exact Salary will be determined based on qualifications, experience and location." That seems messed up; we need to preserve the substantive info: Expected Salary Range $20.00 - $40.0 (maybe typo) and also mention that exact salary determined based on qualifications, experience and location. We'll include that.
We also have "#InternshipProgramUS" maybe a tag; we can ignore as metadata.
Now craft HTML.
Structure:
About the role
GlobalFoundries (GF) is a leading manufacturer of essential semiconductors, enabling AI at scale from the cloud to the physical world. Through deep partnerships with customers, GF delivers differentiated, power-efficient and high-performance solutions for high-growth markets. GF is a trusted and holistic technology partner for customers around the world. GF’s talented, global team remains focused every day on security, longevity and sustainability. For more information, visit www.gf.com.
Internship Program Overview: Our Interns & Co-ops are our entry-level talent pipeline for GF across the globe. Our goal is to provide students with a meaningful work experience that will equip them with the skills to embark on a career in the fast-paced and growing semiconductor industry after graduation. As an intern at GF, you’ll experience one-on-one mentorship, work assignments that prioritize your growth and potential, professional development opportunities, and the chance to network with executives.
Summary Of Role: GlobalFoundries is seeking a Reliability Engineering Intern to support the development and qualification of Silicon Photonics technologies involving CMOS devices and photonic components. Working with experienced reliability engineers and cross-functional teams, the intern will contribute to reliability testing, data analysis, failure-mechanism studies, literature reviews, lifetime modeling, and qualification activities for devices such as waveguides, modulators, photodetectors, and lasers.
Responsibilities
- Assist in the design and evaluation of reliability test structures for CMOS and Silicon Photonics devices.
- Support execution of reliability stress tests, laboratory measurements, and characterization activities for photonic and semiconductor devices.
- Collect, organize, validate, and analyze reliability data; summarize trends and communicate findings to engineering teams.
- Participate in development of reliability models, statistical analyses, and lifetime projections under the guidance of experienced engineers.
- Perform literature reviews related to Silicon Photonics reliability, degradation mechanisms, photonic-device failure modes, and applicable industry reliability standards.
- Assist with investigations of device reliability concerns and failure mechanisms involving waveguides, modulators, photodetectors, lasers, and related optical communication components.
- Support hardware planning, test readiness, and laboratory activities needed to meet technology-development and qualification project schedules.
- Collaborate with Technology Development, Manufacturing, Process Integration, Design Engineering, Test, and Reliability teams on photonic and CMOS qualification projects.
- Document experimental methods and results and prepare clear technical reports and presentations.
- Perform all activities in a safe and responsible manner and support all Environmental, Health, Safety & Security requirements and programs.
Requirements
- Education – At least a sophomore at time of application and actively pursuing a Bachelor’s, Master’s, or PhD in Photonics Engineering, Electrical Engineering, Materials Science, Physics, Applied Physics, Semiconductor Engineering, or related field through an accredited degree program during the time of internship.
- Must have at least an overall 3.0 GPA and be in good academic standing.
- Language Fluency - English (Written & Verbal)
- Ability to work at least 40 hours per week during the internship.
- Basic understanding of semiconductor device physics and an interest in semiconductor devices and photonics.
- Ability to analyze technical data, solve engineering problems, and work effectively in a collaborative environment.
Qualifications
- Prior related internship or co-op experience
- Demonstrated prior leadership experience in the workplace, school projects, competitions, etc.
- Strong interest in leveraging AI tools and emerging technologies to enhance productivity, streamline workflows, and support effective decision-making.
- Project management skills, i.e., the ability to innovate and execute on solutions that matter; the ability to navigate ambiguity.
- Strong written and verbal communication skills
- Strong planning & organizational skills
- Coursework or research experience in Silicon Photonics, optoelectronics, semiconductor devices, materials science, or reliability engineering.
- Familiarity with photonic devices such as waveguides, modulators, photodetectors, lasers, or optical communication systems.
- Experience with laboratory measurements, experimental research, or data analysis using Python, MATLAB, JMP, Minitab, Excel, or similar tools.
- Understanding of basic statistics and reliability concepts.
Pay
Expected Salary Range $20.00 - $40.0. The exact salary will be determined based on qualifications, experience and location.
Schedule
Ability to work at least 40 hours per week during the internship.
Check duplication: The ability to work 40 hours per week appears also in Requirements; we included it there. In Schedule we repeat same info; maybe we should not duplicate. But we need to include schedule info; we could keep it only in Schedule and remove from Requirements? However the requirement list includes that as a requirement; we should preserve all substantive info. Duplication is okay? The instruction says remove duplicated lines. That refers to duplicated lines in the posting; we should not repeat same info unnecessarily. Having it in both Requirements and Schedule is duplication across sections; maybe we should keep it only once. Since schedule is a separate section, we could keep it there and remove from Requirements. But then we lose a requirement that is explicitly stated. However the requirement is about ability to work 40 hrs/week; it's both a requirement and schedule info. We could keep it under Requirements and not have a separate Schedule section if schedule is same as that requirement. But we also have Pay section separate. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we can combine schedule into Requirements or Pay? But they gave Schedule as a possible heading. Since we have schedule info, we could include Schedule section and not duplicate in Requirements. However we would be dropping a requirement. But we could rephrase Requirements to not include that line, but that would be omitting substantive info (the requirement). So better to keep it in Requirements and not have Schedule section, or keep both but note it's duplicate.
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It may mean we should use those headings when applicable; if a section doesn't match, we could still use a heading but maybe better to map content to those headings. Let's interpret: We should produce headings like About the role
, Responsibilities
, Requirements
, Qualifications
, Skills
, Benefits
, Pay
, Schedule
. Only include sections when posting has real specific content. So we need to decide which of these sections we have content for.
We have:
- About the role: we have "Summary Of Role" and maybe "About GlobalFoundries" and "Internship Program Overview". Could combine into About the role.
- Responsibilities: we have "Essential Responsibilities Include" and "Other Responsibilities". So we can put under Responsibilities.
- Requirements: we have "Required Qualifications". Could be Requirements.
- Qualifications: we have "Preferred Qualifications". Could be Qualifications (or Skills). But we already used Requirements for required; we could have Qualifications for preferred.
- Skills: maybe we could extract skills from qualifications? But we might not need a separate Skills section if not explicit. The instruction says prefer a few substantive sections over many thin ones. So we could combine Required and Preferred into Qualifications? But they said use headings like Requirements, Qualifications, Skills. Could treat Required Qualifications as Requirements, Preferred Qualifications as Qualifications, and maybe Skills as a subsection? But we could also put skills under Qualifications.
- Benefits: not mentioned explicitly; no benefits described. So we should not include Benefits.
- Pay: we have Expected Salary Range. So we can include Pay.
- Schedule: we have ability to work at least 40 hours per week. That's schedule info. So we can include Schedule.
Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Pay, Schedule.
We must not repeat job title as heading. No job title given explicitly but it's Reliability Engineering Intern. We'll not add heading for that.
We must use - for any list of duties/requirements/benefits. So for responsibilities list, we need to convert each responsibility into
- . For required qualifications list, each bullet into
- . For preferred qualifications list similarly.
We must use
for prose.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is a lot of EEO statement. We must remove that. Also remove lines about accommodation request? That is not EEO but maybe considered accommodation info; it's not boilerplate? It's about reasonable accommodation. Might be considered part of employment process; but it's not explicitly listed as boilerplate to remove. However it's somewhat generic; but it's substantive? It's about accommodation request. Might be considered part of application instructions? It says "If you need a reasonable accommodation for any part of the employment process, please contact us..." That's like application instruction. The instruction says remove application instructions. So we should remove that accommodation request paragraph. Also remove the line about offer conditioned upon pre-employment conditions etc. That's also boilerplate/legal. Remove that too. Also remove the EEO statement at the end.
Thus we keep: About GlobalFoundries, Internship Program Overview, Summary Of Role, Essential Responsibilities Include, Other Responsibilities, Required Qualifications, Preferred Qualifications, Expected Salary Range (though there is duplicate weird lines). Also we have "Expected Salary Range $20.00 - $40.0 Expected Salary Range $0.00 - $0.00 The exact Salary will be determined based on qualifications, experience and location." That seems messed up; we need to preserve the substantive info: Expected Salary Range $20.00 - $40.0 (maybe typo) and also mention that exact salary determined based on qualifications, experience and location. We'll include that.
We also have "#InternshipProgramUS" maybe a tag; we can ignore as metadata.
Now craft HTML.
Structure:
About the role
GlobalFoundries (GF) is a leading manufacturer of essential semiconductors, enabling AI at scale from the cloud to the physical world. Through deep partnerships with customers, GF delivers differentiated, power-efficient and high-performance solutions for high-growth markets. GF is a trusted and holistic technology partner for customers around the world. GF’s talented, global team remains focused every day on security, longevity and sustainability. For more information, visit www.gf.com.
Internship Program Overview: Our Interns & Co-ops are our entry-level talent pipeline for GF across the globe. Our goal is to provide students with a meaningful work experience that will equip them with the skills to embark on a career in the fast-paced and growing semiconductor industry after graduation. As an intern at GF, you’ll experience one-on-one mentorship, work assignments that prioritize your growth and potential, professional development opportunities, and the chance to network with executives.
Summary Of Role: GlobalFoundries is seeking a Reliability Engineering Intern to support the development and qualification of Silicon Photonics technologies involving CMOS devices and photonic components. Working with experienced reliability engineers and cross-functional teams, the intern will contribute to reliability testing, data analysis, failure-mechanism studies, literature reviews, lifetime modeling, and qualification activities for devices such as waveguides, modulators, photodetectors, and lasers.
Responsibilities
- Assist in the design and evaluation of reliability test structures for CMOS and Silicon Photonics devices.
- Support execution of reliability stress tests, laboratory measurements, and characterization activities for photonic and semiconductor devices.
- Collect, organize, validate, and analyze reliability data; summarize trends and communicate findings to engineering teams.
- Participate in development of reliability models, statistical analyses, and lifetime projections under the guidance of experienced engineers.
- Perform literature reviews related to Silicon Photonics reliability, degradation mechanisms, photonic-device failure modes, and applicable industry reliability standards.
- Assist with investigations of device reliability concerns and failure mechanisms involving waveguides, modulators, photodetectors, lasers, and related optical communication components.
- Support hardware planning, test readiness, and laboratory activities needed to meet technology-development and qualification project schedules.
- Collaborate with Technology Development, Manufacturing, Process Integration, Design Engineering, Test, and Reliability teams on photonic and CMOS qualification projects.
- Document experimental methods and results and prepare clear technical reports and presentations.
- Perform all activities in a safe and responsible manner and support all Environmental, Health, Safety & Security requirements and programs.
Requirements
- Education – At least a sophomore at time of application and actively pursuing a Bachelor’s, Master’s, or PhD in Photonics Engineering, Electrical Engineering, Materials Science, Physics, Applied Physics, Semiconductor Engineering, or related field through an accredited degree program during the time of internship.
- Must have at least an overall 3.0 GPA and be in good academic standing.
- Language Fluency - English (Written & Verbal)
- Ability to work at least 40 hours per week during the internship.
- Basic understanding of semiconductor device physics and an interest in semiconductor devices and photonics.
- Ability to analyze technical data, solve engineering problems, and work effectively in a collaborative environment.
Qualifications
- Prior related internship or co-op experience
- Demonstrated prior leadership experience in the workplace, school projects, competitions, etc.
- Strong interest in leveraging AI tools and emerging technologies to enhance productivity, streamline workflows, and support effective decision-making.
- Project management skills, i.e., the ability to innovate and execute on solutions that matter; the ability to navigate ambiguity.
- Strong written and verbal communication skills
- Strong planning & organizational skills
- Coursework or research experience in Silicon Photonics, optoelectronics, semiconductor devices, materials science, or reliability engineering.
- Familiarity with photonic devices such as waveguides, modulators, photodetectors, lasers, or optical communication systems.
- Experience with laboratory measurements, experimental research, or data analysis using Python, MATLAB, JMP, Minitab, Excel, or similar tools.
- Understanding of basic statistics and reliability concepts.
Pay
Expected Salary Range $20.00 - $40.0. The exact salary will be determined based on qualifications, experience and location.
Schedule
Ability to work at least 40 hours per week during the internship.
Check duplication: The ability to work 40 hours per week appears also in Requirements; we included it there. In Schedule we repeat same info; maybe we should not duplicate. But we need to include schedule info; we could keep it only in Schedule and remove from Requirements? However the requirement list includes that as a requirement; we should preserve all substantive info. Duplication is okay? The instruction says remove duplicated lines. That refers to duplicated lines in the posting; we should not repeat same info unnecessarily. Having it in both Requirements and Schedule is duplication across sections; maybe we should keep it only once. Since schedule is a separate section, we could keep it there and remove from Requirements. But then we lose a requirement that is explicitly stated. However the requirement is about ability to work 40 hrs/week; it's both a requirement and schedule info. We could keep it under Requirements and not have a separate Schedule section if schedule is same as that requirement. But we also have Pay section separate. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we can combine schedule into Requirements or Pay? But they gave Schedule as a possible heading. Since we have schedule info, we could include Schedule section and not duplicate in Requirements. However we would be dropping a requirement. But we could rephrase Requirements to not include that line, but that would be omitting substantive info (the requirement). So better to keep it in Requirements and not have Schedule section, or keep both but note it's duplicate.
for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is a lot of EEO statement. We must remove that. Also remove lines about accommodation request? That is not EEO but maybe considered accommodation info; it's not boilerplate? It's about reasonable accommodation. Might be considered part of employment process; but it's not explicitly listed as boilerplate to remove. However it's somewhat generic; but it's substantive? It's about accommodation request. Might be considered part of application instructions? It says "If you need a reasonable accommodation for any part of the employment process, please contact us..." That's like application instruction. The instruction says remove application instructions. So we should remove that accommodation request paragraph. Also remove the line about offer conditioned upon pre-employment conditions etc. That's also boilerplate/legal. Remove that too. Also remove the EEO statement at the end. Thus we keep: About GlobalFoundries, Internship Program Overview, Summary Of Role, Essential Responsibilities Include, Other Responsibilities, Required Qualifications, Preferred Qualifications, Expected Salary Range (though there is duplicate weird lines). Also we have "Expected Salary Range $20.00 - $40.0 Expected Salary Range $0.00 - $0.00 The exact Salary will be determined based on qualifications, experience and location." That seems messed up; we need to preserve the substantive info: Expected Salary Range $20.00 - $40.0 (maybe typo) and also mention that exact salary determined based on qualifications, experience and location. We'll include that. We also have "#InternshipProgramUS" maybe a tag; we can ignore as metadata. Now craft HTML. Structure:
About the role
GlobalFoundries (GF) is a leading manufacturer of essential semiconductors, enabling AI at scale from the cloud to the physical world. Through deep partnerships with customers, GF delivers differentiated, power-efficient and high-performance solutions for high-growth markets. GF is a trusted and holistic technology partner for customers around the world. GF’s talented, global team remains focused every day on security, longevity and sustainability. For more information, visit www.gf.com.
Internship Program Overview: Our Interns & Co-ops are our entry-level talent pipeline for GF across the globe. Our goal is to provide students with a meaningful work experience that will equip them with the skills to embark on a career in the fast-paced and growing semiconductor industry after graduation. As an intern at GF, you’ll experience one-on-one mentorship, work assignments that prioritize your growth and potential, professional development opportunities, and the chance to network with executives.
Summary Of Role: GlobalFoundries is seeking a Reliability Engineering Intern to support the development and qualification of Silicon Photonics technologies involving CMOS devices and photonic components. Working with experienced reliability engineers and cross-functional teams, the intern will contribute to reliability testing, data analysis, failure-mechanism studies, literature reviews, lifetime modeling, and qualification activities for devices such as waveguides, modulators, photodetectors, and lasers.
Responsibilities
- Assist in the design and evaluation of reliability test structures for CMOS and Silicon Photonics devices.
- Support execution of reliability stress tests, laboratory measurements, and characterization activities for photonic and semiconductor devices.
- Collect, organize, validate, and analyze reliability data; summarize trends and communicate findings to engineering teams.
- Participate in development of reliability models, statistical analyses, and lifetime projections under the guidance of experienced engineers.
- Perform literature reviews related to Silicon Photonics reliability, degradation mechanisms, photonic-device failure modes, and applicable industry reliability standards.
- Assist with investigations of device reliability concerns and failure mechanisms involving waveguides, modulators, photodetectors, lasers, and related optical communication components.
- Support hardware planning, test readiness, and laboratory activities needed to meet technology-development and qualification project schedules.
- Collaborate with Technology Development, Manufacturing, Process Integration, Design Engineering, Test, and Reliability teams on photonic and CMOS qualification projects.
- Document experimental methods and results and prepare clear technical reports and presentations.
- Perform all activities in a safe and responsible manner and support all Environmental, Health, Safety & Security requirements and programs.
Requirements
- Education – At least a sophomore at time of application and actively pursuing a Bachelor’s, Master’s, or PhD in Photonics Engineering, Electrical Engineering, Materials Science, Physics, Applied Physics, Semiconductor Engineering, or related field through an accredited degree program during the time of internship.
- Must have at least an overall 3.0 GPA and be in good academic standing.
- Language Fluency - English (Written & Verbal)
- Ability to work at least 40 hours per week during the internship.
- Basic understanding of semiconductor device physics and an interest in semiconductor devices and photonics.
- Ability to analyze technical data, solve engineering problems, and work effectively in a collaborative environment.
Qualifications
- Prior related internship or co-op experience
- Demonstrated prior leadership experience in the workplace, school projects, competitions, etc.
- Strong interest in leveraging AI tools and emerging technologies to enhance productivity, streamline workflows, and support effective decision-making.
- Project management skills, i.e., the ability to innovate and execute on solutions that matter; the ability to navigate ambiguity.
- Strong written and verbal communication skills
- Strong planning & organizational skills
- Coursework or research experience in Silicon Photonics, optoelectronics, semiconductor devices, materials science, or reliability engineering.
- Familiarity with photonic devices such as waveguides, modulators, photodetectors, lasers, or optical communication systems.
- Experience with laboratory measurements, experimental research, or data analysis using Python, MATLAB, JMP, Minitab, Excel, or similar tools.
- Understanding of basic statistics and reliability concepts.
Pay
Expected Salary Range $20.00 - $40.0. The exact salary will be determined based on qualifications, experience and location.
Schedule
Ability to work at least 40 hours per week during the internship.
Check duplication: The ability to work 40 hours per week appears also in Requirements; we included it there. In Schedule we repeat same info; maybe we should not duplicate. But we need to include schedule info; we could keep it only in Schedule and remove from Requirements? However the requirement list includes that as a requirement; we should preserve all substantive info. Duplication is okay? The instruction says remove duplicated lines. That refers to duplicated lines in the posting; we should not repeat same info unnecessarily. Having it in both Requirements and Schedule is duplication across sections; maybe we should keep it only once. Since schedule is a separate section, we could keep it there and remove from Requirements. But then we lose a requirement that is explicitly stated. However the requirement is about ability to work 40 hrs/week; it's both a requirement and schedule info. We could keep it under Requirements and not have a separate Schedule section if schedule is same as that requirement. But we also have Pay section separate. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we can combine schedule into Requirements or Pay? But they gave Schedule as a possible heading. Since we have schedule info, we could include Schedule section and not duplicate in Requirements. However we would be dropping a requirement. But we could rephrase Requirements to not include that line, but that would be omitting substantive info (the requirement). So better to keep it in Requirements and not have Schedule section, or keep both but note it's duplicate.