2027 Summer Intern - Digital Product: Software Engineering
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to map content accordingly.
We must not repeat job title as heading (the page already shows it). No Job ID etc.
We need to preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions). So we need to strip out sections like "About GM", "Why Join Us", "Benefits Overview", "Non-Discrimination and Equal Employment Opportunities", "Accommodations", etc. Also remove "Our vision..." etc.
We need to keep sections: About Digital Products (maybe as About the role?), About The Opportunity (maybe Responsibilities?), Potential Team & Areas of Work (maybe Responsibilities?), Potential Skills & Contributions (maybe Skills?), Required Qualifications (Qualifications), Preferred Experience (maybe Skills?), Compensation (Pay), What You’ll Get From Us (Benefits), Work Arrangement (Schedule). Also maybe "About Digital Products" as About the role.
We need to decide which headings to include based on presence of content.
We have content for:
- About the role: description of Digital Products, intern can work on real products, learn from professionals, etc. So we can put that under About the role
with paragraphs.
- Responsibilities: The Opportunity section: "Depending on the team, you may contribute to application development, automation, data and integration services, software delivery, test tools, or lab and validation infrastructure. Assignments are connected to real team priorities and may include design, coding, testing, troubleshooting, documentation, and continuous improvement across the development lifecycle." Also Potential Team & Areas of Work list. So we can combine responsibilities.
- Requirements: maybe not separate; but we have Required Qualifications and Preferred Experience. Could put under Qualifications heading.
- Skills: Potential Skills & Contributions list.
- Benefits: What You’ll Get From Us (Benefits) list.
- Pay: Compensation line.
- Schedule: Work Arrangement (start dates, hybrid). Also maybe mention full-time 40 hours per week, 12 week summer internship period between May–August or June–September 2027. That's schedule info.
We must not create sections with filler like "commensurate with experience". We have actual content.
We need to output only HTML fragment, no /, no markdown fences.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We need to ensure we don't duplicate content.
Let's extract content precisely.
From posting:
"Job Description About Digital Products Digital Products owns the definition, development, and delivery of GM’s digital products and the customer experiences delivered through mobile applications, back-office platforms, and connected services. The organization brings together OnStar & Customer Experience Platforms and Digital Vehicle Experience and works closely with Vehicle Products to deliver digital contributors to the vehicle experience. Digital Products is an exciting place to begin your career because interns can work on real products, services, tools, and experiences that connect customers with GM. You will learn from experienced professionals, collaborate across product and engineering teams, and gain exposure to how digital products are built, tested, launched, and improved."
That's About the role.
"About The Opportunity Digital Products is looking for Software Engineer Interns and Software Test Engineer Interns who are excited to build reliable digital products and the systems that support them. Depending on the team, you may contribute to application development, automation, data and integration services, software delivery, test tools, or lab and validation infrastructure. Assignments are connected to real team priorities and may include design, coding, testing, troubleshooting, documentation, and continuous improvement across the development lifecycle."
That's responsibilities.
"Potential Team & Areas of Work Opportunities may be aligned to the following groups and product areas from the Digital Products intern intake: Consumer Digital Experiences (CDE): Mobile, Vehicle Commerce, Brand Services, and Loyalty Emerging and Strategic Businesses (ESB): GM Fleet OnStar Sales, Activation and Experience (OnStar SAE): Carrier & Vehicle Experience Services, Commerce, Global Contact Centers & OnStar Safety, and OnStar AI Engineering Physical and Virtual Test Platforms: Virtual Test Infrastructure, Virtualization Tools, Vehicle Reflash, Infotainment Lab Operations, HIL simulation integration, and lab operations Vehicle Software Integrity and Delivery: Calibration Management Tools, Greylock, Wired Programming, and VCAM Digital Vehicle Experience (DVE): Software engineering and software test opportunities supporting digital vehicle experiences"
That's also responsibilities (areas of work). Could be part of responsibilities.
"Potential Skills & Contributions Build or enhance software features, services, APIs, tools, or automation Write unit, integration, or end-to-end tests and help improve software quality Analyze data, investigate defects, and support troubleshooting or root-cause analysis Contribute to technical designs, requirements, documentation, or delivery plans Support software delivery, diagnostics, reflash, validation, lab tooling, or test infrastructure Collaborate with engineers, product managers, designers, analysts, technicians, and business partners"
That's skills.
"Required Qualifications Currently pursuing a Bachelor's Degree in Computer Science, Computer Engineering, Data Science, Information Systems, Mechanical Engineering, or related field.Must have at least one additional quarter/semester of school remaining following the completion of the internshipAvailability to work full-time, 40 hours per week, during the 12 week summer internship period between May–August or June–September 2027 Coursework, project, club, research, or prior experience demonstrating programming or software development Ability to communicate clearly, work collaboratively, and learn new technologies Interest in building reliable, customer-focused digital products Ability to work onsite at the assigned GM location with the manager and team"
Note: there is no punctuation between sentences; we need to parse.
"Preferred Experience Candidates are not expected to meet every qualification listed below. Depending on the needs of a specific Digital Product team, a combination of these skills and areas of knowledge may be relevant.Currently pursuing a Master’s Degree in Computer Science, Computer Engineering, Data Science, Information Systems, Mechanical Engineering, or related field. Experience with one or more programming languages such as Java, JavaScript/TypeScript, Python, C#, C++, or SQL Exposure to software testing, automation, APIs, databases, Git, CI/CD, observability, or integration tools Experience with mobile development, web development, backend services, data engineering, Salesforce, MuleSoft, or test platforms A class project, personal project, internship, portfolio, or code sample that demonstrates problem-solving"
"Compensation: The monthly salary range for this role is $6,400-$10,300 per month. GM will provide a one-time lump sum taxable stipend payment to eligible students selected for the 2027 Student Program - to help facilitate administration of relocation benefits, please apply using the permanent address you would move from."
That's Pay.
"What You’ll Get From Us (Benefits): Paid US GM Holidays GM Family First Vehicle Discount Program Result-based potential for growth within GM Intern events to network with company leaders and peers"
That's Benefits.
"Work Arrangement: Start dates for this internship role are May 24th and June 14th of 2027. Assignments will be based on team placement to ensure interns are located with their working team and leader. Hybrid: This role is categorized as hybrid. This means the successful candidate is expected to report to their designated work location three times per week, at minimum."
That's Schedule.
We also have "About GM", "Why Join Us", "Benefits Overview", "Non-Discrimination and Equal Employment Opportunities", "Accommodations" which we need to remove.
Now we need to produce HTML with headings only for sections that have real content.
We have content for:
- About the role (we have paragraph)
- Responsibilities (we have paragraphs + list of areas)
- Qualifications (we have Required Qualifications and Preferred Experience maybe combined)
- Skills (Potential Skills & Contributions)
- Benefits (What You’ll Get From Us)
- Pay (Compensation)
- Schedule (Work Arrangement)
We could also have a separate "Requirements" but we already have Qualifications covering requirements. The instructions say use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include both Requirements and Qualifications if we have distinct content. But we might combine Required Qualifications under Qualifications, and maybe Requirements could be empty; we should not create empty headings. So we only include headings where we have substantive content.
Thus we will include:
About the role
... (the paragraph)
Responsibilities
... (the opportunity paragraph)
- ... list of areas? Actually the Potential Team & Areas of Work is a list; we can turn each bullet into
- . Also the responsibilities paragraph includes design, coding, testing etc. Could be separate
but we can combine.
Better: After the paragraph, we can have with items: Consumer Digital Experiences (CDE): Mobile, Vehicle Commerce, Brand Services, and Loyalty; Emerging and Strategic Businesses (ESB): GM Fleet; OnStar Sales, Activation and Experience (OnStar SAE): Carrier & Vehicle Experience Services, Commerce, Global Contact Centers & OnStar Safety, and OnStar AI Engineering; Physical and Virtual Test Platforms: Virtual Test Infrastructure, Virtualization Tools, Vehicle Reflash, Infotainment Lab Operations, HIL simulation integration, and lab operations; Vehicle Software Integrity and Delivery: Calibration Management Tools, Greylock, Wired Programming, and VCAM; Digital Vehicle Experience (DVE): Software engineering and software test opportunities supporting digital vehicle experiences.
We need to preserve all info; we can keep as is.
Qualifications
We have Required Qualifications and Preferred Experience. Could combine into one or separate paragraphs. Since they are qualifications, we can list them as - ... each bullet. But the text is not bulletized; we need to parse into logical items.
Required Qualifications items:
- Currently pursuing a Bachelor's Degree in Computer Science, Computer Engineering, Data Science, Information Systems, Mechanical Engineering, or related field.
- Must have at least one additional quarter/semester of school remaining following the completion of the internship.
- Availability to work full-time, 40 hours per week, during the 12 week summer internship period between May–August or June–September 2027.
- Coursework, project, club, research, or prior experience demonstrating programming or software development.
- Ability to communicate clearly, work collaboratively, and learn new technologies.
- Interest in building reliable, customer-focused digital products.
- Ability to work onsite at the assigned GM location with the manager and team.
Preferred Experience items:
- Currently pursuing a Master’s Degree in Computer Science, Computer Engineering, Data Science, Information Systems, Mechanical Engineering, or related field.
- Experience with one or more programming languages such as Java, JavaScript/TypeScript, Python, C#, C++, or SQL.
- Exposure to software testing, automation, APIs, databases, Git, CI/CD, observability, or integration tools.
- Experience with mobile development, web development, backend services, data engineering, Salesforce, MuleSoft, or test platforms.
- A class project, personal project, internship, portfolio, or code sample that demonstrates problem-solving.
We can combine them into a single list under Qualifications, maybe with a note that preferred experience is optional. But we need to preserve all info; we can include both.
We could have two headings: Qualifications (Required) and Preferred Experience (maybe under Skills?). But the instructions only list Qualifications as a heading; we can put both required and preferred under Qualifications, maybe separate paragraphs.
Better: Use
Qualifications
then Required Qualifications:
...
for prose. We need to ensure we don't duplicate content. Let's extract content precisely. From posting: "Job Description About Digital Products Digital Products owns the definition, development, and delivery of GM’s digital products and the customer experiences delivered through mobile applications, back-office platforms, and connected services. The organization brings together OnStar & Customer Experience Platforms and Digital Vehicle Experience and works closely with Vehicle Products to deliver digital contributors to the vehicle experience. Digital Products is an exciting place to begin your career because interns can work on real products, services, tools, and experiences that connect customers with GM. You will learn from experienced professionals, collaborate across product and engineering teams, and gain exposure to how digital products are built, tested, launched, and improved." That's About the role. "About The Opportunity Digital Products is looking for Software Engineer Interns and Software Test Engineer Interns who are excited to build reliable digital products and the systems that support them. Depending on the team, you may contribute to application development, automation, data and integration services, software delivery, test tools, or lab and validation infrastructure. Assignments are connected to real team priorities and may include design, coding, testing, troubleshooting, documentation, and continuous improvement across the development lifecycle." That's responsibilities. "Potential Team & Areas of Work Opportunities may be aligned to the following groups and product areas from the Digital Products intern intake: Consumer Digital Experiences (CDE): Mobile, Vehicle Commerce, Brand Services, and Loyalty Emerging and Strategic Businesses (ESB): GM Fleet OnStar Sales, Activation and Experience (OnStar SAE): Carrier & Vehicle Experience Services, Commerce, Global Contact Centers & OnStar Safety, and OnStar AI Engineering Physical and Virtual Test Platforms: Virtual Test Infrastructure, Virtualization Tools, Vehicle Reflash, Infotainment Lab Operations, HIL simulation integration, and lab operations Vehicle Software Integrity and Delivery: Calibration Management Tools, Greylock, Wired Programming, and VCAM Digital Vehicle Experience (DVE): Software engineering and software test opportunities supporting digital vehicle experiences" That's also responsibilities (areas of work). Could be part of responsibilities. "Potential Skills & Contributions Build or enhance software features, services, APIs, tools, or automation Write unit, integration, or end-to-end tests and help improve software quality Analyze data, investigate defects, and support troubleshooting or root-cause analysis Contribute to technical designs, requirements, documentation, or delivery plans Support software delivery, diagnostics, reflash, validation, lab tooling, or test infrastructure Collaborate with engineers, product managers, designers, analysts, technicians, and business partners" That's skills. "Required Qualifications Currently pursuing a Bachelor's Degree in Computer Science, Computer Engineering, Data Science, Information Systems, Mechanical Engineering, or related field.Must have at least one additional quarter/semester of school remaining following the completion of the internshipAvailability to work full-time, 40 hours per week, during the 12 week summer internship period between May–August or June–September 2027 Coursework, project, club, research, or prior experience demonstrating programming or software development Ability to communicate clearly, work collaboratively, and learn new technologies Interest in building reliable, customer-focused digital products Ability to work onsite at the assigned GM location with the manager and team" Note: there is no punctuation between sentences; we need to parse. "Preferred Experience Candidates are not expected to meet every qualification listed below. Depending on the needs of a specific Digital Product team, a combination of these skills and areas of knowledge may be relevant.Currently pursuing a Master’s Degree in Computer Science, Computer Engineering, Data Science, Information Systems, Mechanical Engineering, or related field. Experience with one or more programming languages such as Java, JavaScript/TypeScript, Python, C#, C++, or SQL Exposure to software testing, automation, APIs, databases, Git, CI/CD, observability, or integration tools Experience with mobile development, web development, backend services, data engineering, Salesforce, MuleSoft, or test platforms A class project, personal project, internship, portfolio, or code sample that demonstrates problem-solving" "Compensation: The monthly salary range for this role is $6,400-$10,300 per month. GM will provide a one-time lump sum taxable stipend payment to eligible students selected for the 2027 Student Program - to help facilitate administration of relocation benefits, please apply using the permanent address you would move from." That's Pay. "What You’ll Get From Us (Benefits): Paid US GM Holidays GM Family First Vehicle Discount Program Result-based potential for growth within GM Intern events to network with company leaders and peers" That's Benefits. "Work Arrangement: Start dates for this internship role are May 24th and June 14th of 2027. Assignments will be based on team placement to ensure interns are located with their working team and leader. Hybrid: This role is categorized as hybrid. This means the successful candidate is expected to report to their designated work location three times per week, at minimum." That's Schedule. We also have "About GM", "Why Join Us", "Benefits Overview", "Non-Discrimination and Equal Employment Opportunities", "Accommodations" which we need to remove. Now we need to produce HTML with headings only for sections that have real content. We have content for: - About the role (we have paragraph) - Responsibilities (we have paragraphs + list of areas) - Qualifications (we have Required Qualifications and Preferred Experience maybe combined) - Skills (Potential Skills & Contributions) - Benefits (What You’ll Get From Us) - Pay (Compensation) - Schedule (Work Arrangement) We could also have a separate "Requirements" but we already have Qualifications covering requirements. The instructions say use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include both Requirements and Qualifications if we have distinct content. But we might combine Required Qualifications under Qualifications, and maybe Requirements could be empty; we should not create empty headings. So we only include headings where we have substantive content. Thus we will include:
About the role
... (the paragraph)
Responsibilities
... (the opportunity paragraph)
- ... list of areas? Actually the Potential Team & Areas of Work is a list; we can turn each bullet into
- . Also the responsibilities paragraph includes design, coding, testing etc. Could be separate
- but we can combine.
Better: After the paragraph, we can have
- ... each bullet. But the text is not bulletized; we need to parse into logical items.
Required Qualifications items:
- Currently pursuing a Bachelor's Degree in Computer Science, Computer Engineering, Data Science, Information Systems, Mechanical Engineering, or related field.
- Must have at least one additional quarter/semester of school remaining following the completion of the internship.
- Availability to work full-time, 40 hours per week, during the 12 week summer internship period between May–August or June–September 2027.
- Coursework, project, club, research, or prior experience demonstrating programming or software development.
- Ability to communicate clearly, work collaboratively, and learn new technologies.
- Interest in building reliable, customer-focused digital products.
- Ability to work onsite at the assigned GM location with the manager and team.
Preferred Experience items:
- Currently pursuing a Master’s Degree in Computer Science, Computer Engineering, Data Science, Information Systems, Mechanical Engineering, or related field.
- Experience with one or more programming languages such as Java, JavaScript/TypeScript, Python, C#, C++, or SQL.
- Exposure to software testing, automation, APIs, databases, Git, CI/CD, observability, or integration tools.
- Experience with mobile development, web development, backend services, data engineering, Salesforce, MuleSoft, or test platforms.
- A class project, personal project, internship, portfolio, or code sample that demonstrates problem-solving.
We can combine them into a single list under Qualifications, maybe with a note that preferred experience is optional. But we need to preserve all info; we can include both.
We could have two headings: Qualifications (Required) and Preferred Experience (maybe under Skills?). But the instructions only list Qualifications as a heading; we can put both required and preferred under Qualifications, maybe separate paragraphs.
Better: Use
Qualifications
thenRequired Qualifications:
- ...
- with items: Consumer Digital Experiences (CDE): Mobile, Vehicle Commerce, Brand Services, and Loyalty; Emerging and Strategic Businesses (ESB): GM Fleet; OnStar Sales, Activation and Experience (OnStar SAE): Carrier & Vehicle Experience Services, Commerce, Global Contact Centers & OnStar Safety, and OnStar AI Engineering; Physical and Virtual Test Platforms: Virtual Test Infrastructure, Virtualization Tools, Vehicle Reflash, Infotainment Lab Operations, HIL simulation integration, and lab operations; Vehicle Software Integrity and Delivery: Calibration Management Tools, Greylock, Wired Programming, and VCAM; Digital Vehicle Experience (DVE): Software engineering and software test opportunities supporting digital vehicle experiences.
We need to preserve all info; we can keep as is.
Qualifications
We have Required Qualifications and Preferred Experience. Could combine into one- or separate paragraphs. Since they are qualifications, we can list them as
- ... each bullet. But the text is not bulletized; we need to parse into logical items.
Required Qualifications items:
- Currently pursuing a Bachelor's Degree in Computer Science, Computer Engineering, Data Science, Information Systems, Mechanical Engineering, or related field.
- Must have at least one additional quarter/semester of school remaining following the completion of the internship.
- Availability to work full-time, 40 hours per week, during the 12 week summer internship period between May–August or June–September 2027.
- Coursework, project, club, research, or prior experience demonstrating programming or software development.
- Ability to communicate clearly, work collaboratively, and learn new technologies.
- Interest in building reliable, customer-focused digital products.
- Ability to work onsite at the assigned GM location with the manager and team.
Preferred Experience items:
- Currently pursuing a Master’s Degree in Computer Science, Computer Engineering, Data Science, Information Systems, Mechanical Engineering, or related field.
- Experience with one or more programming languages such as Java, JavaScript/TypeScript, Python, C#, C++, or SQL.
- Exposure to software testing, automation, APIs, databases, Git, CI/CD, observability, or integration tools.
- Experience with mobile development, web development, backend services, data engineering, Salesforce, MuleSoft, or test platforms.
- A class project, personal project, internship, portfolio, or code sample that demonstrates problem-solving.
We can combine them into a single list under Qualifications, maybe with a note that preferred experience is optional. But we need to preserve all info; we can include both.
We could have two headings: Qualifications (Required) and Preferred Experience (maybe under Skills?). But the instructions only list Qualifications as a heading; we can put both required and preferred under Qualifications, maybe separate paragraphs.
Better: Use