Product Design Engineering Intern, BS/MS, Summer 2027
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the 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. Prefer a few substantive sections over many thin ones.
We need to parse the posting: It's about an internship? Actually the posting includes "Please complete your application before October 9, 2026." etc. It includes benefits, location options, minimum qualifications, preferred qualifications, about the job, responsibilities, pay range.
We need to produce sections: maybe About the role (the "About The Job" paragraph), Responsibilities (the "Responsibilities" line and bullet?), Requirements (minimum qualifications), Qualifications (preferred qualifications?), Skills (maybe list of skills from qualifications?), Benefits (the benefits listed), Pay (the pay range), Schedule (maybe not present? There's no schedule info besides "full time for 12 weeks outside of university term time" maybe schedule? That could be considered schedule: 12 weeks full-time. But we should only include Schedule if posting actually states it. It does mention "available to work full time for 12 weeks outside of university term time." That's schedule info. So we can include Schedule section with that detail.
We must not include boilerplate like EEO, application instructions, etc. Also remove duplicated lines. Also remove "Participation in the internship program requires that you are located in the United States for the duration of the internship program." That's substantive? It's a requirement (location). Should we include that under Requirements? Probably yes. Also "This internship is intended for students in their penultimate academic year, who are pursuing a Bachelor's or Master's degree program in Mechanical Engineering, Computer Engineering, Computer Science, or a related technical field." That's also a requirement. Also "Google is a global company and, in order to facilitate efficient collaboration and communication globally, English proficiency is a requirement for this internship program." That's a requirement.
Also "To start the application process, you will need an updated CV or resume and a current unofficial or official transcript in English." That's application instruction -> remove.
Also "Click on the “Apply” button on this page and provide the required materials in the appropriate sections (PDFs preferred): ..." remove.
Also "In accordance with Washington state law, we are highlighting our comprehensive benefits package, which is available to all eligible US based Interns." That's benefits intro; we can keep benefits.
Also "Applicants in the County of Los Angeles: Qualified applications with arrest or conviction records will be considered for employment in accordance with the Los Angeles County Fair Chance Ordinance for Employers and the California Fair Chance Act." That's EEO/legal boilerplate; remove.
Similarly for San Francisco.
Also "Note: By applying to this position you will have an opportunity to share your preferred working location from the following: ..." That's location options; could be considered part of role? Might be considered substantive but not a standard heading. Could be included under About the role or maybe a separate section? The instruction says prefer few substantive sections over many thin ones. Could include location list under About the role as a paragraph.
Also "Minimum qualifications:" and "Preferred qualifications:" sections.
Also "About The Job" paragraph.
Also "Responsibilities Learn more about benefits at Google . Perform specific responsibilities which vary by project area." That's vague; we need to keep substantive responsibilities? It says "Perform specific responsibilities which vary by project area." That's not specific; maybe we should not include Responsibilities section if it's just filler? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The responsibilities line is vague; maybe we should omit Responsibilities section because it's not specific. However there is also "Learn more about benefits at Google ." That's boilerplate. So we might skip Responsibilities.
But we could include a Responsibilities section with the sentence "Perform specific responsibilities which vary by project area." That's still vague but it's the only content. Might be considered filler. Safer to omit.
Now Benefits: list: Health, dental, vision insurance; Sick Time: 40 hours/year (increased to 69 hours/year for Seattle) including 5 discretionary sick days per instance; Holidays: 13 paid days per year.
We need to format as
- for list.
Pay: "US: $86000 - $115000 (USD) + 0% bonus target". That's specific; include Pay section.
Schedule: "available to work full time for 12 weeks outside of university term time." That's schedule.
Also maybe "Participation in the internship program requires that you are located in the United States for the duration of the internship program." That's location requirement; could be under Requirements.
Now we need to decide headings: About the role (use the About The Job paragraph). Requirements (minimum qualifications + location + English proficiency + penultimate year etc). Qualifications (preferred qualifications). Skills maybe not needed; we could combine qualifications and skills. But we have both minimum and preferred qualifications; we could have Requirements (minimum) and Qualifications (preferred). Or we could have Requirements (minimum) and Skills (preferred). The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map: About the role -> About The Job paragraph. Requirements -> Minimum qualifications + location + English proficiency + penultimate year etc. Qualifications -> Preferred qualifications. Skills maybe not needed; we could omit if no specific skills list beyond qualifications. But we could put skills under Qualifications? Better to follow instruction: include a section ONLY when posting has real, specific content for it. We have content for About the role, Requirements, Qualifications, Benefits, Pay, Schedule. Possibly also Responsibilities? but we decided to skip.
Thus we will output:
About the role
... (the About The Job paragraph)
Requirements
- Currently pursuing a Bachelor's or Master's degree in Electrical Engineering, Computer Engineering, Product Design, or a related technical field.
- Internship experience, work experience, educational, or personal project experience with product design, or with Computer Aided Design (CAD) tools (e.g., PTC Creo, ProE, or Unigraphics NX) and mechanical simulation tools.
- Located in the United States for the duration of the internship program.
- Student in penultimate academic year (pursuing Bachelor's or Master's degree in Mechanical Engineering, Computer Engineering, Computer Science, or a related technical field).
- English proficiency.
Wait need to close ul.
But note: The minimum qualifications list includes "Currently pursuing a Bachelor's or Master's degree in Electrical Engineering, Computer Engineering, Product Design, or a related technical field." and "Internship experience, work experience, educational, or personal project experience with product design, or with Computer Aided Design (CAD) tools (e.g., PTC Creo, ProE, or Unigraphics NX) and mechanical simulation tools."
The internship intended for students in penultimate year pursuing Bachelor's or Master's in Mechanical Engineering, Computer Engineering, Computer Science, or related technical field. That's a bit overlapping but we keep both.
Also English proficiency.
Also location US.
Thus Requirements list.
Qualifications
- Currently attending a degree program in the US and available to work full time for 12 weeks outside of university term time.
- In their penultimate academic year or returning to a degree program after completion of the internship.
- Experience with Unigraphics NX/Teamcenter with proficiency in CAD, tolerance analysis, and structural finite element analysis.
- Familiarity with mechanical design of plastic and metal components, printed circuit boards (PCB) and flexible printed circuits (FPC), and acoustics used in consumer electronic products.
- Familiarity with electromechanical assemblies, manufacturing techniques, fabrication techniques, and rapid prototyping.
Note: The first two items about attending US and full time 12 weeks could also be schedule; but we already have schedule section. Might duplicate. Better to keep schedule separate: "available to work full time for 12 weeks outside of university term time." That's schedule. The "Currently attending a degree program in the US" is location requirement (already in Requirements). So we should not duplicate. So for Qualifications we should include the rest: penultimate year or returning after internship, experience with Unigraphics NX/Teamcenter, familiarity with mechanical design, familiarity with electromechanical assemblies etc.
Thus Qualifications list:
- In their penultimate academic year or returning to a degree program after completion of the internship.
- Experience with Unigraphics NX/Teamcenter with proficiency in CAD, tolerance analysis, and structural finite element analysis.
- Familiarity with mechanical design of plastic and metal components, printed circuit boards (PCB) and flexible printed circuits (FPC), and acoustics used in consumer electronic products.
- Familiarity with electromechanical assemblies, manufacturing techniques, fabrication techniques, and rapid prototyping.
Now Benefits section:
Benefits
- Health, dental, vision insurance
- Sick Time: 40 hours/year (increased to 69 hours/year for Seattle) including 5 discretionary sick days per instance
- Holidays: 13 paid days per year
Pay section:
Pay
US: $86000 - $115000 (USD) + 0% bonus target
Schedule section:
Schedule
Available to work full time for 12 weeks outside of university term time.
Now About the role paragraph: need to extract the "About The Job" paragraph:
"About The Job As a Product Design Engineer, you will help to reinvent the shape of electronics: balancing comfort, performance, and appearance. You will work on a team that balances these concepts in an innovative and harmonious design that complements and enables the technology. You will be comfortable working on the borders of risk, actively communicating among a team to establish a design direction, creating prototypes that prove it, and working to scale that prototype. Google is and always will be an engineering company. We hire people with a broad set of technical skills who are ready to address some of technology's greatest challenges and make an impact on millions, if not billions, of users. At Google, engineers not only revolutionize search, they routinely work on massive scalability and storage solutions, large-scale applications and entirely new platforms for developers around the world. From Google Ads to Chrome, Android to YouTube, Social to Local, Google engineers are changing the world one technological achievement after another."
We need to preserve all substantive information; do not invent or summarize away detail. So we keep that paragraph exactly as is, maybe with proper punctuation. Ensure we don't include the heading "About The Job" as text; we just use About the role
then ...
.
Now we need to ensure we didn't include any boilerplate like EEO,
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the 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. Prefer a few substantive sections over many thin ones. We need to parse the posting: It's about an internship? Actually the posting includes "Please complete your application before October 9, 2026." etc. It includes benefits, location options, minimum qualifications, preferred qualifications, about the job, responsibilities, pay range. We need to produce sections: maybe About the role (the "About The Job" paragraph), Responsibilities (the "Responsibilities" line and bullet?), Requirements (minimum qualifications), Qualifications (preferred qualifications?), Skills (maybe list of skills from qualifications?), Benefits (the benefits listed), Pay (the pay range), Schedule (maybe not present? There's no schedule info besides "full time for 12 weeks outside of university term time" maybe schedule? That could be considered schedule: 12 weeks full-time. But we should only include Schedule if posting actually states it. It does mention "available to work full time for 12 weeks outside of university term time." That's schedule info. So we can include Schedule section with that detail. We must not include boilerplate like EEO, application instructions, etc. Also remove duplicated lines. Also remove "Participation in the internship program requires that you are located in the United States for the duration of the internship program." That's substantive? It's a requirement (location). Should we include that under Requirements? Probably yes. Also "This internship is intended for students in their penultimate academic year, who are pursuing a Bachelor's or Master's degree program in Mechanical Engineering, Computer Engineering, Computer Science, or a related technical field." That's also a requirement. Also "Google is a global company and, in order to facilitate efficient collaboration and communication globally, English proficiency is a requirement for this internship program." That's a requirement. Also "To start the application process, you will need an updated CV or resume and a current unofficial or official transcript in English." That's application instruction -> remove. Also "Click on the “Apply” button on this page and provide the required materials in the appropriate sections (PDFs preferred): ..." remove. Also "In accordance with Washington state law, we are highlighting our comprehensive benefits package, which is available to all eligible US based Interns." That's benefits intro; we can keep benefits. Also "Applicants in the County of Los Angeles: Qualified applications with arrest or conviction records will be considered for employment in accordance with the Los Angeles County Fair Chance Ordinance for Employers and the California Fair Chance Act." That's EEO/legal boilerplate; remove. Similarly for San Francisco. Also "Note: By applying to this position you will have an opportunity to share your preferred working location from the following: ..." That's location options; could be considered part of role? Might be considered substantive but not a standard heading. Could be included under About the role or maybe a separate section? The instruction says prefer few substantive sections over many thin ones. Could include location list under About the role as a paragraph. Also "Minimum qualifications:" and "Preferred qualifications:" sections. Also "About The Job" paragraph. Also "Responsibilities Learn more about benefits at Google . Perform specific responsibilities which vary by project area." That's vague; we need to keep substantive responsibilities? It says "Perform specific responsibilities which vary by project area." That's not specific; maybe we should not include Responsibilities section if it's just filler? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The responsibilities line is vague; maybe we should omit Responsibilities section because it's not specific. However there is also "Learn more about benefits at Google ." That's boilerplate. So we might skip Responsibilities. But we could include a Responsibilities section with the sentence "Perform specific responsibilities which vary by project area." That's still vague but it's the only content. Might be considered filler. Safer to omit. Now Benefits: list: Health, dental, vision insurance; Sick Time: 40 hours/year (increased to 69 hours/year for Seattle) including 5 discretionary sick days per instance; Holidays: 13 paid days per year. We need to format as
- for list.
Pay: "US: $86000 - $115000 (USD) + 0% bonus target". That's specific; include Pay section.
Schedule: "available to work full time for 12 weeks outside of university term time." That's schedule.
Also maybe "Participation in the internship program requires that you are located in the United States for the duration of the internship program." That's location requirement; could be under Requirements.
Now we need to decide headings: About the role (use the About The Job paragraph). Requirements (minimum qualifications + location + English proficiency + penultimate year etc). Qualifications (preferred qualifications). Skills maybe not needed; we could combine qualifications and skills. But we have both minimum and preferred qualifications; we could have Requirements (minimum) and Qualifications (preferred). Or we could have Requirements (minimum) and Skills (preferred). The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map: About the role -> About The Job paragraph. Requirements -> Minimum qualifications + location + English proficiency + penultimate year etc. Qualifications -> Preferred qualifications. Skills maybe not needed; we could omit if no specific skills list beyond qualifications. But we could put skills under Qualifications? Better to follow instruction: include a section ONLY when posting has real, specific content for it. We have content for About the role, Requirements, Qualifications, Benefits, Pay, Schedule. Possibly also Responsibilities? but we decided to skip.
Thus we will output:
About the role
... (the About The Job paragraph)
Requirements
- Currently pursuing a Bachelor's or Master's degree in Electrical Engineering, Computer Engineering, Product Design, or a related technical field.
- Internship experience, work experience, educational, or personal project experience with product design, or with Computer Aided Design (CAD) tools (e.g., PTC Creo, ProE, or Unigraphics NX) and mechanical simulation tools.
- Located in the United States for the duration of the internship program.
- Student in penultimate academic year (pursuing Bachelor's or Master's degree in Mechanical Engineering, Computer Engineering, Computer Science, or a related technical field).
- English proficiency. Wait need to close ul. But note: The minimum qualifications list includes "Currently pursuing a Bachelor's or Master's degree in Electrical Engineering, Computer Engineering, Product Design, or a related technical field." and "Internship experience, work experience, educational, or personal project experience with product design, or with Computer Aided Design (CAD) tools (e.g., PTC Creo, ProE, or Unigraphics NX) and mechanical simulation tools." The internship intended for students in penultimate year pursuing Bachelor's or Master's in Mechanical Engineering, Computer Engineering, Computer Science, or related technical field. That's a bit overlapping but we keep both. Also English proficiency. Also location US. Thus Requirements list.
- Currently attending a degree program in the US and available to work full time for 12 weeks outside of university term time.
- In their penultimate academic year or returning to a degree program after completion of the internship.
- Experience with Unigraphics NX/Teamcenter with proficiency in CAD, tolerance analysis, and structural finite element analysis.
- Familiarity with mechanical design of plastic and metal components, printed circuit boards (PCB) and flexible printed circuits (FPC), and acoustics used in consumer electronic products.
- Familiarity with electromechanical assemblies, manufacturing techniques, fabrication techniques, and rapid prototyping.
- Health, dental, vision insurance
- Sick Time: 40 hours/year (increased to 69 hours/year for Seattle) including 5 discretionary sick days per instance
- Holidays: 13 paid days per year
Qualifications
Benefits
Pay
US: $86000 - $115000 (USD) + 0% bonus target
Schedule section:Schedule
Available to work full time for 12 weeks outside of university term time.
Now About the role paragraph: need to extract the "About The Job" paragraph: "About The Job As a Product Design Engineer, you will help to reinvent the shape of electronics: balancing comfort, performance, and appearance. You will work on a team that balances these concepts in an innovative and harmonious design that complements and enables the technology. You will be comfortable working on the borders of risk, actively communicating among a team to establish a design direction, creating prototypes that prove it, and working to scale that prototype. Google is and always will be an engineering company. We hire people with a broad set of technical skills who are ready to address some of technology's greatest challenges and make an impact on millions, if not billions, of users. At Google, engineers not only revolutionize search, they routinely work on massive scalability and storage solutions, large-scale applications and entirely new platforms for developers around the world. From Google Ads to Chrome, Android to YouTube, Social to Local, Google engineers are changing the world one technological achievement after another." We need to preserve all substantive information; do not invent or summarize away detail. So we keep that paragraph exactly as is, maybe with proper punctuation. Ensure we don't include the heading "About The Job" as text; we just useAbout the role
then...
. Now we need to ensure we didn't include any boilerplate like EEO,