Software Developer - Manufacturing Applications

We need to output HTML fragment with sections: headings

for each section present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, accommodations, etc. Also remove navigation, cookie, legal, duplicated lines, application instructions. Also remove "Work Arrangement – Onsite" maybe part of schedule? It says Work Arrangement – Onsite. That's schedule info. So we can include Schedule section with that content. Benefits: there is a Benefits Overview paragraph. Also "Relocation benefits are available for candidates who qualify under company policy." That's benefits. So we can include Benefits section with that content. Pay: not mentioned. So we should not include Pay section. Schedule: we have Work Arrangement – Onsite. Also "This role is categorized as onsite." So schedule: Onsite, full-time. So we can include Schedule section with that. We need sections: About the role (maybe from first paragraph?), Responsibilities (What You'll Do), Requirements (maybe required qualifications), Qualifications (maybe preferred qualifications?), Skills (Your Skills And Abilities (Required Qualifications) maybe that is skills). Actually the posting has "Your Skills And Abilities (Required Qualifications)" and "What Will Give You a Competitive Edge (Preferred Qualifications)". So we can map: Skills section = Required Qualifications. Qualifications section = Preferred Qualifications. Requirements maybe could be something else? The posting also has "What As a Software Developer - Manufacturing Applications, you will design, develop..." That's responsibilities. Also "Why" section maybe about role? Could be About the role. Let's decide sections: - About the role: include the introductory paragraphs describing role, why, impact. Could combine first few paragraphs up to "WHY". We'll include content: "Global Manufacturing Electrical & SDV is seeking a Software Developer - Manufacturing Applications to build and support the software applications used to validate vehicle electrical systems throughout the manufacturing process. These applications play a critical role in ensuring vehicles are tested, verified, and built correctly across GM assembly plants around the world. You will work across manufacturing, software engineering, IT, validation, and plant teams to develop reliable software solutions that support vehicle testing, diagnostics, issue resolution, and continuous quality improvements. This is a hands-on engineering role for someone who enjoys learning new technologies, solving complex technical problems, and working at the intersection of software, hardware, and manufacturing systems. This Role Is Ideal For Software engineers who enjoy solving real-world problems where software interacts directly with hardware, manufacturing systems, and vehicles. You'll thrive in this role if you enjoy troubleshooting complex issues, working across disciplines, and seeing your code have an immediate impact on vehicle quality and production operations. WHY Help transform how GM validates and builds vehicles by developing software applications that support electrical testing, diagnostics, and manufacturing quality. Your work will directly contribute to vehicle quality, process efficiency, issue resolution, and Electrical First Time Quality (EFTQ) across GM's global manufacturing footprint." But we must not repeat job title. It's okay. - Responsibilities: the "What You'll Do" bullet list. We'll convert to

• . - Requirements: maybe the "Required Qualifications" (Your Skills And Abilities (Required Qualifications)). But we already used Skills for that. Let's think: The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which content maps to which heading. We have: - About the role: intro. - Responsibilities: What you'll do. - Requirements: maybe the mandatory qualifications? Could be "Strong programming experience..." etc. That is required qualifications. - Qualifications: maybe the preferred qualifications? Or could be education? Actually "What Will Give You a Competitive Edge (Preferred Qualifications)" includes preferred qualifications and also Bachelor's degree etc. That could be Qualifications. - Skills: maybe the "Your Skills And Abilities (Required Qualifications)" is skills. But we already used that for Requirements. Hmm. We need to avoid duplication. Let's map: - Requirements: Required qualifications (strong programming experience, etc.) - Qualifications: Preferred qualifications (experience with automotive manufacturing, etc.) plus Bachelor's degree. - Skills: maybe we could omit if content overlaps. But we need to include sections only when there is real specific content. We could omit Skills if we think it's covered. But we have content for Skills (Your Skills And Abilities (Required Qualifications)). That is essentially same as Requirements. To avoid duplication, we could treat that as Skills and not have Requirements. But we need to preserve all substantive info; we can't omit required qualifications. So we need a section for them. Let's decide: Option: Use Requirements for required qualifications, Qualifications for preferred qualifications + education, and omit Skills (since it's duplicate). But the instruction says we can have few substantive sections over many thin ones. So we can combine required and preferred into one Qualifications? But they ask for separate headings; we can still omit Skills if not needed. However we have content for Skills (Your Skills And Abilities (Required Qualifications)). If we omit Skills heading, we would lose that content unless we put it elsewhere. We could put that content under Requirements. That seems fine: Requirements heading will contain the required qualifications (skills). Then Qualifications heading will contain preferred qualifications + education. That covers all. Thus sections: - About the role - Responsibilities - Requirements - Qualifications - Benefits - Schedule We will not include Pay (no info). We'll not include Skills. Now we need to extract content for each. About the role: combine the introductory paragraphs up to "WHY". Let's capture: "Global Manufacturing Electrical & SDV is seeking a Software Developer - Manufacturing Applications to build and support the software applications used to validate vehicle electrical systems throughout the manufacturing process. These applications play a critical role in ensuring vehicles are tested, verified, and built correctly across GM assembly plants around the world. You will work across manufacturing, software engineering, IT, validation, and plant teams to develop reliable software solutions that support vehicle testing, diagnostics, issue resolution, and continuous quality improvements. This is a hands-on engineering role for someone who enjoys learning new technologies, solving complex technical problems, and working at the intersection of software, hardware, and manufacturing systems. This Role Is Ideal For Software engineers who enjoy solving real-world problems where software interacts directly with hardware, manufacturing systems, and vehicles. You'll thrive in this role if you enjoy troubleshooting complex issues, working across disciplines, and seeing your code have an immediate impact on vehicle quality and production operations. WHY Help transform how GM validates and builds vehicles by developing software applications that support electrical testing, diagnostics, and manufacturing quality. Your work will directly contribute to vehicle quality, process efficiency, issue resolution, and Electrical First Time Quality (EFTQ) across GM's global manufacturing footprint." We need to ensure we don't include duplicated lines. The "WHY" heading is part of the text; we can keep as sentence. Responsibilities: the bullet list under "What You'll Do". Let's capture each line: - Design, develop, test, and maintain software applications used to support vehicle manufacturing and electrical system validation across GM's global manufacturing network. - Debug and troubleshoot complex software, hardware, and system integration issues affecting manufacturing test processes. - Support software validation activities using test benches, development hardware, and production vehicles. - Collaborate with manufacturing, product engineering, IT, and plant teams to develop and deploy reliable software solutions. - Contribute to technical problem solving, root cause investigations, and implementation of corrective actions. - Improve application performance, reliability, usability, and maintainability through continuous improvement initiatives. - Support integration of software solutions with manufacturing equipment, plant systems, vehicle communication networks, and enterprise platforms. - Participate in code reviews, testing activities, technical documentation, and software release processes. We'll put each as
• . Requirements: the "Your Skills And Abilities (Required Qualifications)" bullet list: - Strong programming experience in C, C++, C#, or similar object-oriented programming languages. - Experience designing, developing, testing, and supporting software applications. - Demonstrated ability to troubleshoot and debug complex issues involving software, hardware, and system integrations. - Experience working with source control tools and modern software development practices. - Ability to work effectively with cross-functional teams including manufacturing, engineering, IT, and operations. - Strong problem-solving skills, attention to detail, and willingness to learn new technologies. We'll put as
• . Qualifications: preferred qualifications plus Bachelor's degree. Let's gather: From "What Will Give You a Competitive Edge (Preferred Qualifications)": - Experience with automotive manufacturing, end-of-line testing, vehicle diagnostics, or manufacturing test systems. - Familiarity with vehicle communication protocols such as CAN, UDS, or DoIP. - Experience developing software that interfaces with hardware, firmware, or embedded systems. - Familiarity with GitHub, Jira, Visual Studio, or similar software development tools. - Experience with vehicle electrical systems, validation environments, or plant-floor applications. - Experience supporting production-critical software applications in manufacturing or industrial environments. - Experience working in an assembly plant, manufacturing facility, or operational technology environment. - Bachelor's degree in Computer Science, Software Engineering, Electrical Engineering, Computer Engineering, or equivalent practical experience. Also there is statement: "This role is categorized as onsite. This means the selected candidate is expected to report to a specific location on a full-time basis." That's schedule, not qualifications. Also "Relocation benefits are available for candidates who qualify under company policy." That's benefits. Thus Qualifications section will contain those bullet points. Benefits: we have "Benefits Overview From day one, we're looking out for your well-being–at work and at home–so you can focus on realizing your ambitions. Learn how GM supports a rewarding career that rewards you personally by visiting Total Rewards resources." plus "Relocation benefits are available for candidates who qualify under company policy." We'll combine into a paragraph or list? It's prose. We'll put as

  maybe two sentences. Schedule: we have "Work Arrangement – Onsite" and "This role is categorized as onsite. This means the selected candidate is expected to report to a specific location on a full-time basis." Also maybe mention full-time. We'll put as

  describing onsite, full-time. Now we need to output only HTML fragment, no /, no markdown fences. We'll produce:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  ...

  Qualifications

  ...

  Benefits

  ...

  Schedule

  ...

  Make sure to preserve all substantive info. Let's craft the text precisely. About the role paragraph: Let's copy exactly the sentences we selected, ensuring no extra fluff. I'll write: Global Manufacturing Electrical & SDV is seeking a Software Developer - Manufacturing Applications to build and support the software applications used to validate vehicle electrical systems throughout the manufacturing process. These applications play a critical role in ensuring vehicles are tested, verified, and built correctly across GM assembly plants around the world. You will work across manufacturing, software engineering, IT, validation, and plant teams to develop reliable software solutions that support vehicle testing, diagnostics, issue resolution, and continuous quality improvements. This is a hands-on engineering role for someone who enjoys learning new technologies, solving complex technical problems, and working at the intersection of software, hardware, and manufacturing systems. This Role Is Ideal For Software engineers who enjoy solving real-world problems where software interacts directly with hardware, manufacturing systems, and vehicles. You'll thrive in this role if you enjoy troubleshooting complex issues, working across disciplines, and seeing your code have an immediate impact on vehicle quality and production operations. WHY Help transform how GM validates and builds vehicles by developing software applications that support electrical testing, diagnostics, and manufacturing quality. Your work will directly contribute to vehicle quality, process efficiency, issue