Principal Software Engineer – Core OS, Vehicle Compute
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. No Job ID.
We need to preserve all substantive information. So we need to include:
- About the role: The paragraph starting "The Core OS group is a newly formed team..." maybe also the preceding paragraph about GM product teams? Actually "Job Description At General Motors, our product teams..." is introductory fluff but could be considered About the role? Might be considered generic. But we can include a short paragraph about GM's mission? However we should avoid boilerplate. The initial paragraph about GM product teams is somewhat generic but still substantive about the company's mission. Might be okay to include as About the role? The instruction: "Prefer a few substantive sections over many thin ones." We could combine the introductory paragraph and The Role into About the role.
Better: Section "About the role" containing the description of Core OS group and the role responsibilities overview (maybe combine with What You’ll Do?). But we also need a separate Responsibilities section? The instructions say use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should follow that.
Thus:
- About the role: brief overview of the team and role purpose (maybe first two paragraphs: "At General Motors..." and "The Role The Core OS group...").
- Responsibilities: the bullet list under "What You’ll Do". Use
- .
- Requirements: maybe combine Required Qualifications and Preferred Qualifications? Actually Requirements could be Required Qualifications. Qualifications could be Preferred? But they said we can have Skills section. Let's map:
- Requirements: Required Qualifications (Bachelor's degree, 15+ years, etc.)
- Skills: maybe the list of skills under Required Qualifications? Actually they are part of Requirements. Could also have Skills section for "Your Skills & Abilities (Required Qualifications)" but that's same as Requirements. To avoid duplication, we can have Requirements (including education, experience, proven experience, deep expertise, strong knowledge, experience leading, proficiency, strong communication). Then Skills could be the "What Will Give You a Competitive Edge (Preferred Qualifications)"? But they said Skills section for skills. Might be better to have Skills for both required and preferred? However we need to avoid thin sections. Perhaps combine Required and Preferred into Qualifications? But they said we can have Qualifications section. Let's think: The headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use:
- About the role: intro.
- Responsibilities: What You’ll Do.
- Requirements: Required Qualifications (education, years, proven experience, deep expertise, strong knowledge, experience leading, proficiency, communication).
- Qualifications: Preferred Qualifications (Master's, hands-on hypervisor, automotive safety, container runtimes, Yocto, health monitoring, AUTOSAR, OTA, open-source contributions, vision influence).
- Skills: maybe we could list specific technical skills like "Type 1 hypervisors, RTOS, Embedded Linux internals, Secure boot, Arm SoC, Git, CI/CD, etc." but those are already in Requirements. Could omit Skills section if no distinct content. But we need to avoid empty headings. So maybe we skip Skills.
- Benefits: list of benefits.
- Pay: salary range.
- Schedule: hybrid expectation.
We must not include boilerplate like "About GM", "Why Join Us", "Benefits Overview", "Non-Discrimination", "Accommodations". Also remove "Compensation: The compensation information is a good faith estimate only..." but we can keep the salary range sentence. We'll extract the salary range: "$216,400 –$450,400". Note there is a missing space after dash? We'll keep as is.
We also need to preserve the sentence about actual base salary varying based on factors and geography. That's substantive? It's part of compensation description. We can include that in Pay section.
Benefits: list includes medical, dental, vision, HSA, FSA, retirement savings plans, paid vacation and holidays, tuition assistance, employee assistance programs, life insurance, GM vehicle discounts. We'll put as
.
Schedule: "This role is categorized as hybrid. This means the selected candidate is expected to report to a specific location at least 3 times a week {or other frequency dictated by their manager}. This job may be eligible for relocation benefits." We'll put as .
Now ensure we don't repeat any content. Let's craft HTML.
We'll start with
About the role
then containing the combined intro: "At General Motors, our product teams are redefining mobility. Through a human-centered design process, we create vehicles and experiences that are designed not just to be seen, but to be felt. We’re turning today’s impossible into tomorrow’s standard —from breakthrough hardware and battery systems to intuitive design, intelligent software, and next-generation safety and entertainment features. Every day, our products move millions of people as we aim to make driving safer, smarter, and more connected, shaping the future of transportation on a global scale. The Core OS group is a newly formed team building the operating-system foundation GM's next generation of vehicle software runs on: hypervisors and virtualization, safety partitioning and health management, container runtime and workload orchestration, and the boot and secure-boot chain that let Linux, Android, and QNX share a single high-compute platform safely and efficiently. As Principal Software Engineer, you are the senior technical authority and system architect for that layer — you'll determine which platform problems matter most, then define the architecture and drive the solutions that solve them, setting long-term direction for virtualization, partitioning, and platform services across GM's vehicle compute. Your influence extends well past your own code: establishing the technical interfaces to the silicon, guest OS, and functional-safety organizations, driving decisions with hypervisor and silicon partners, and guiding engineers across multiple teams toward a foundation that must hold up to production performance, reliability, and safety requirements in millions of vehicles."
That seems to capture the introductory and role description.
Next Responsibilities:
Responsibilities
then with each bullet from "What You’ll Do". Let's list them:
- Define and drive the architecture and long-term roadmap for GM’s Core OS layer, including hypervisors, virtualization, virtual machine lifecycle, resource partitioning, inter-virtual-machine communication, and the boot and secure-boot chain.
- Architect the multi-operating-system foundation that enables embedded Linux, including Yocto-based distributions, Android, and QNX to run on shared vehicle compute with consistent platform services and interfaces.
- Establish the platform safety architecture, including freedom from interference between partitions, health monitoring, fault detection and recovery, in partnership with functional safety and cybersecurity organizations.
- Define the container and workload-management architecture for on-vehicle execution, including isolation, lifecycle management, resource governance, and updateability.
- Own the system-level performance strategy across compute efficiency, latency, boot time, memory footprint, and deterministic behavior, and lead optimization efforts across software and hardware boundaries.
- Drive build-versus-buy and technology-selection decisions for hypervisor, real-time operating system, and runtime components, and lead technical relationships with the corresponding suppliers.
- Provide technical mentorship and direction to Staff and Senior Software Engineers while establishing engineering standards and review practices for the new organization.
- Lead complex investigations and root-cause analyses across virtualization, operating-system, and silicon boundaries.
- Represent Core OS in technical councils, architecture reviews, and cross-functional design forums, and define ownership boundaries with adjacent platform teams.
Make each as - .
Next Requirements:
Requirements
then with required qualifications:
- Bachelor’s degree in Computer Science, Electrical Engineering, Computer Engineering, or a related field; or equivalent experience.
- Fifteen or more years of experience in embedded, kernel-level, or systems software development, including production-grade systems.
- Proven experience architecting operating-system or virtualization platforms for high-performance or safety-critical systems.
- Deep expertise in at least two of the following areas: Type 1 hypervisors and virtualization, Real-time operating systems, Embedded Linux internals, Secure boot and platform integrity.
- Strong knowledge of Arm system-on-chip (SoC) architecture, including memory management, interrupt and input/output virtualization, and hardware-enforced isolation mechanisms.
- Experience leading multi-team or cross-functional technical programs from concept through production.
- Proficiency with modern development tools and practices, including Git, GitHub, continuous integration and continuous delivery (CI/CD), automated testing, and performance profiling.
- Strong communication and influence skills across technical, cross-functional, and executive audiences.
Next Qualifications (Preferred): Qualifications
then with preferred qualifications:
- Master’s degree or equivalent experience in Computer Science, Electrical Engineering, Computer Engineering, or a related field.
- Hands-on architecture experience with hypervisor technologies such as Gunyah, QNX Hypervisor, Xen, or KVM/Arm, including virtio-based device virtualization.
- Expertise in automotive functional safety, including Automotive Safety Integrity Level (ASIL) decomposition, safety-island architecture, freedom-from-interference arguments, and safety-framework integration.
- Experience with container runtimes and workload orchestration in resource-constrained or embedded environments.
- Familiarity with Yocto-based Linux distributions, Android Open Source Project (AOSP) or Android Automotive, and QNX Software Development Platform (SDP) as guest or host environments.
- Familiarity with health monitoring, fail-operational and fail-safe mechanisms, and platform-resiliency design.
- Experience with Adaptive Automotive Open System Architecture (AUTOSAR), Software Defined Vehicle Open Architecture for Embedded Edge (SOAFEE), or comparable automotive platform standards.
- Experience with over-the-air (OTA) and continuous-update architectures.
- Contributions to open-source virtualization or operating-system projects.
- Proven ability to set technical vision, influence across organizations, and represent a company in cross-industry engagements.
Next Benefits: Benefits
then list:
- medical
- dental
- vision
- Health Savings Account
- Flexible Spending Accounts
- retirement savings plans
- paid vacation and holidays
- tuition assistance
- employee assistance programs
- life insurance
- GM vehicle discounts
We could phrase as items.
Next Pay: Pay
then containing: "The salary range for this role is $216,
for prose. We must not repeat job title as heading. No Job ID. We need to preserve all substantive information. So we need to include: - About the role: The paragraph starting "The Core OS group is a newly formed team..." maybe also the preceding paragraph about GM product teams? Actually "Job Description At General Motors, our product teams..." is introductory fluff but could be considered About the role? Might be considered generic. But we can include a short paragraph about GM's mission? However we should avoid boilerplate. The initial paragraph about GM product teams is somewhat generic but still substantive about the company's mission. Might be okay to include as About the role? The instruction: "Prefer a few substantive sections over many thin ones." We could combine the introductory paragraph and The Role into About the role. Better: Section "About the role" containing the description of Core OS group and the role responsibilities overview (maybe combine with What You’ll Do?). But we also need a separate Responsibilities section? The instructions say use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should follow that. Thus: - About the role: brief overview of the team and role purpose (maybe first two paragraphs: "At General Motors..." and "The Role The Core OS group..."). - Responsibilities: the bullet list under "What You’ll Do". Use
- .
- Requirements: maybe combine Required Qualifications and Preferred Qualifications? Actually Requirements could be Required Qualifications. Qualifications could be Preferred? But they said we can have Skills section. Let's map:
- Requirements: Required Qualifications (Bachelor's degree, 15+ years, etc.)
- Skills: maybe the list of skills under Required Qualifications? Actually they are part of Requirements. Could also have Skills section for "Your Skills & Abilities (Required Qualifications)" but that's same as Requirements. To avoid duplication, we can have Requirements (including education, experience, proven experience, deep expertise, strong knowledge, experience leading, proficiency, strong communication). Then Skills could be the "What Will Give You a Competitive Edge (Preferred Qualifications)"? But they said Skills section for skills. Might be better to have Skills for both required and preferred? However we need to avoid thin sections. Perhaps combine Required and Preferred into Qualifications? But they said we can have Qualifications section. Let's think: The headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use:
- About the role: intro.
- Responsibilities: What You’ll Do.
- Requirements: Required Qualifications (education, years, proven experience, deep expertise, strong knowledge, experience leading, proficiency, communication).
- Qualifications: Preferred Qualifications (Master's, hands-on hypervisor, automotive safety, container runtimes, Yocto, health monitoring, AUTOSAR, OTA, open-source contributions, vision influence).
- Skills: maybe we could list specific technical skills like "Type 1 hypervisors, RTOS, Embedded Linux internals, Secure boot, Arm SoC, Git, CI/CD, etc." but those are already in Requirements. Could omit Skills section if no distinct content. But we need to avoid empty headings. So maybe we skip Skills.
- Benefits: list of benefits.
- Pay: salary range.
- Schedule: hybrid expectation.
We must not include boilerplate like "About GM", "Why Join Us", "Benefits Overview", "Non-Discrimination", "Accommodations". Also remove "Compensation: The compensation information is a good faith estimate only..." but we can keep the salary range sentence. We'll extract the salary range: "$216,400 –$450,400". Note there is a missing space after dash? We'll keep as is.
We also need to preserve the sentence about actual base salary varying based on factors and geography. That's substantive? It's part of compensation description. We can include that in Pay section.
Benefits: list includes medical, dental, vision, HSA, FSA, retirement savings plans, paid vacation and holidays, tuition assistance, employee assistance programs, life insurance, GM vehicle discounts. We'll put as
- .
Schedule: "This role is categorized as hybrid. This means the selected candidate is expected to report to a specific location at least 3 times a week {or other frequency dictated by their manager}. This job may be eligible for relocation benefits." We'll put as
- .
Next Requirements:
Requirements
then- with required qualifications:
- Bachelor’s degree in Computer Science, Electrical Engineering, Computer Engineering, or a related field; or equivalent experience.
- Fifteen or more years of experience in embedded, kernel-level, or systems software development, including production-grade systems.
- Proven experience architecting operating-system or virtualization platforms for high-performance or safety-critical systems.
- Deep expertise in at least two of the following areas: Type 1 hypervisors and virtualization, Real-time operating systems, Embedded Linux internals, Secure boot and platform integrity.
- Strong knowledge of Arm system-on-chip (SoC) architecture, including memory management, interrupt and input/output virtualization, and hardware-enforced isolation mechanisms.
- Experience leading multi-team or cross-functional technical programs from concept through production.
- Proficiency with modern development tools and practices, including Git, GitHub, continuous integration and continuous delivery (CI/CD), automated testing, and performance profiling.
- Strong communication and influence skills across technical, cross-functional, and executive audiences.
Next Qualifications (Preferred):
Qualifications
then- with preferred qualifications:
- Master’s degree or equivalent experience in Computer Science, Electrical Engineering, Computer Engineering, or a related field.
- Hands-on architecture experience with hypervisor technologies such as Gunyah, QNX Hypervisor, Xen, or KVM/Arm, including virtio-based device virtualization.
- Expertise in automotive functional safety, including Automotive Safety Integrity Level (ASIL) decomposition, safety-island architecture, freedom-from-interference arguments, and safety-framework integration.
- Experience with container runtimes and workload orchestration in resource-constrained or embedded environments.
- Familiarity with Yocto-based Linux distributions, Android Open Source Project (AOSP) or Android Automotive, and QNX Software Development Platform (SDP) as guest or host environments.
- Familiarity with health monitoring, fail-operational and fail-safe mechanisms, and platform-resiliency design.
- Experience with Adaptive Automotive Open System Architecture (AUTOSAR), Software Defined Vehicle Open Architecture for Embedded Edge (SOAFEE), or comparable automotive platform standards.
- Experience with over-the-air (OTA) and continuous-update architectures.
- Contributions to open-source virtualization or operating-system projects.
- Proven ability to set technical vision, influence across organizations, and represent a company in cross-industry engagements.
Next Benefits:
Benefits
then- list:
- medical
- dental
- vision
- Health Savings Account
- Flexible Spending Accounts
- retirement savings plans
- paid vacation and holidays
- tuition assistance
- employee assistance programs
- life insurance
- GM vehicle discounts
We could phrase as items.
Next Pay:
Pay
thencontaining: "The salary range for this role is $216,
. Now ensure we don't repeat any content. Let's craft HTML. We'll start with
About the role
thencontaining the combined intro: "At General Motors, our product teams are redefining mobility. Through a human-centered design process, we create vehicles and experiences that are designed not just to be seen, but to be felt. We’re turning today’s impossible into tomorrow’s standard —from breakthrough hardware and battery systems to intuitive design, intelligent software, and next-generation safety and entertainment features. Every day, our products move millions of people as we aim to make driving safer, smarter, and more connected, shaping the future of transportation on a global scale. The Core OS group is a newly formed team building the operating-system foundation GM's next generation of vehicle software runs on: hypervisors and virtualization, safety partitioning and health management, container runtime and workload orchestration, and the boot and secure-boot chain that let Linux, Android, and QNX share a single high-compute platform safely and efficiently. As Principal Software Engineer, you are the senior technical authority and system architect for that layer — you'll determine which platform problems matter most, then define the architecture and drive the solutions that solve them, setting long-term direction for virtualization, partitioning, and platform services across GM's vehicle compute. Your influence extends well past your own code: establishing the technical interfaces to the silicon, guest OS, and functional-safety organizations, driving decisions with hypervisor and silicon partners, and guiding engineers across multiple teams toward a foundation that must hold up to production performance, reliability, and safety requirements in millions of vehicles." That seems to capture the introductory and role description. Next Responsibilities:
Responsibilities
then- with each bullet from "What You’ll Do". Let's list them:
- Define and drive the architecture and long-term roadmap for GM’s Core OS layer, including hypervisors, virtualization, virtual machine lifecycle, resource partitioning, inter-virtual-machine communication, and the boot and secure-boot chain.
- Architect the multi-operating-system foundation that enables embedded Linux, including Yocto-based distributions, Android, and QNX to run on shared vehicle compute with consistent platform services and interfaces.
- Establish the platform safety architecture, including freedom from interference between partitions, health monitoring, fault detection and recovery, in partnership with functional safety and cybersecurity organizations.
- Define the container and workload-management architecture for on-vehicle execution, including isolation, lifecycle management, resource governance, and updateability.
- Own the system-level performance strategy across compute efficiency, latency, boot time, memory footprint, and deterministic behavior, and lead optimization efforts across software and hardware boundaries.
- Drive build-versus-buy and technology-selection decisions for hypervisor, real-time operating system, and runtime components, and lead technical relationships with the corresponding suppliers.
- Provide technical mentorship and direction to Staff and Senior Software Engineers while establishing engineering standards and review practices for the new organization.
- Lead complex investigations and root-cause analyses across virtualization, operating-system, and silicon boundaries.
- Represent Core OS in technical councils, architecture reviews, and cross-functional design forums, and define ownership boundaries with adjacent platform teams.
Make each as
- .
Next Requirements: