Senior Engineering Manager, Commercial Software
General Motors · Warren, MI · 1 mo ago
HybridFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. The posting includes:
- About the role: description paragraphs under "The Role" and maybe "What You’ll Do". That's responsibilities.
- Responsibilities: "What You’ll Do" bullet list (though not bullet but sentences). We'll need to put as
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. The posting includes:
- About the role: description paragraphs under "The Role" and maybe "What You’ll Do". That's responsibilities.
- Responsibilities: "What You’ll Do" bullet list (though not bullet but sentences). We'll need to put as - .
- Requirements / Qualifications: "Your Skills & Abilities (Required Qualifications)" list of bullet points.
- Preferred Qualifications: "What Will Give You A Competitive Edge (Preferred Qualifications)" list.
- Benefits: "Benefits Overview" mentions benefits but not specific details; just says "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." That's vague; not specific benefits like health insurance, 401k, etc. According to rule: never create Benefits section unless posting actually states them. It mentions benefits overview but no concrete benefits. Likely we should not create Benefits section because no specific benefits listed. However "Benefits Overview" is a heading but content is generic. The rule: "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')". The benefits overview is vague but not placeholder like "varies". It says "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." That's still vague but maybe considered filler? It doesn't list specific benefits like medical, dental, retirement, etc. I'd lean to omit Benefits section.
- Pay: not mentioned. So omit.
- Schedule: mentions hybrid: "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}. Relocation benefits are available for candidates who qualify under company policy." That's schedule info (hybrid expectation). So we can include Schedule section with that content.
- Also there is "About GM" and "Why Join Us" etc. Those could be considered "About the role"? Actually "About GM" is company overview, not role. Could be omitted as boilerplate? It's not required but could be included as "About the role"? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" containing the role description paragraphs (The Role). We'll put that.
- Responsibilities: "What You’ll Do" list.
- Requirements: maybe combine Required Qualifications and Preferred Qualifications? Could have Requirements (required) and Qualifications (preferred). But we have both Required and Preferred. We could make two sections: Requirements (required) and Qualifications (preferred). Or combine into Skills? The instruction list includes Skills as a possible heading. But we have "Your Skills & Abilities (Required Qualifications)" which is skills. So we could use
Skills
for required. And Qualifications
for preferred? However they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Requirements (maybe for required) and Qualifications (for preferred). Or Skills for required. Let's decide:
- About the role: description.
- Responsibilities: What You’ll Do.
- Requirements: Required Qualifications.
- Qualifications: Preferred Qualifications.
- Schedule: hybrid info.
We should not include Skills separately if we used Requirements. But we could also include Skills as required and Qualifications as preferred. However the instruction list includes both Skills and Qualifications; we can choose to use Requirements for required and Qualifications for preferred. That seems fine.
Now we need to preserve all substantive information, not invent or summarize away detail. We need to convert bullet points into - . The required qualifications list includes multiple sentences each as separate bullet? The text:
"Your Skills & Abilities (Required Qualifications)
Bachelor’s degree in computer science, engineering, information systems, or related technical field, or equivalent experience.
12+ years of experience in software engineering, technology, or related fields, including significant experience delivering large-scale software solutions.
5+ years of experience leading software engineering teams, including managers, senior technical leaders, and/or teams of teams.
Demonstrated experience leading engineering organizations of roughly 30+ engineers (ICs and managers), including hiring, performance management, coaching, and organizational design.
Demonstrated experience setting strategy and delivering complex, cross-functional software platforms or customer-facing products on-time.
Strong technical knowledge of cloud platforms, distributed systems, APIs, data platforms, mobile/web applications, software architecture, security, and service reliability.
Utilization of AI within developer lifecycle, business processes, and product development.
Experience operating business-critical services, including production readiness, observability, incident management, service-level objectives, and continuous improvement.
Demonstrated success hiring, developing, and retaining engineering managers and senior technical talent.
Strong executive communication, influence, negotiation, prioritization, and decision-making skills."
We'll make each line a
- .
Preferred qualifications list:
"Master's degree in computer science, engineering, information systems, or related technical field, or equivalent experience.
15+ years of experience in software engineering, technology, or related fields, including significant experience delivering large-scale software solutions.
Experience with connected vehicle, automotive, fleet, mobility, logistics, SaaS, or other data-intensive products.
Experience scaling web, mobile, and API-based products or platforms with external customers including Fortune 500 commercial partners with fleets of hundreds of thousands or millions of vehicles.
Demonstrated history of product development that leads to strong user and revenue growth shown via measurable KPIs.
Demonstrated ability to deliver products iteratively, on-time, and with sustained urgency in complex operational environments with many stakeholders across several organizations.
Experience with vehicle telemetry, real-time data streaming, transactional APIs, developer platforms, or external partner integrations.
Experience modernizing legacy platforms into scalable, observable, cloud-based architectures.
GM does not provide immigration-related sponsorship for this role. Do not apply for this role if you will need GM immigration sponsorship now or in the future. This includes direct company sponsorship, entry of GM as the immigration employer of record on a government form, and any work authorization requiring a written submission or other immigration support from the company (e.g., H1-B, OPT, STEM OPT, CPT, TN, J-1, etc).
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}. Relocation benefits are available for candidates who qualify under company policy."
Note: The last two bullet points about hybrid and relocation are actually under Preferred Qualifications? Actually they appear after the list but still part of the posting. However we already plan to put hybrid in Schedule section. The immigration note is also important; we should preserve that. It's not a benefit but a note about sponsorship. Where to place? Could be under Requirements? It's a condition. Could be its own section? Not in allowed headings. Could be placed under Requirements as a note. Or we could put under Qualifications? Probably better to include under Requirements (or a separate section like "Important Notes") but not allowed headings. We could incorporate into Requirements as a
- item. The instruction: preserve ALL substantive information. So we need to include that statement somewhere. Since we have no specific heading for legal notes, we could add it under Requirements as a list item. Or we could add a
after the list. The instruction says use
for prose. So we could add a paragraph after the Required Qualifications list: "GM does not provide immigration-related sponsorship for this role. Do not apply for this role if you will need GM immigration sponsorship now or in the future. This includes direct company sponsorship, entry of GM as the immigration employer of record on a government form, and any work authorization requiring a written submission or other immigration support from the company (e.g., H1-B, OPT, STEM OPT, CPT, TN, J-1, etc)." That's prose.
Similarly the hybrid and relocation info we plan to put under Schedule section as prose.
Now About the role: we have paragraphs under "The Role". We'll capture that as
maybe multiple paragraphs.
Responsibilities: "What You’ll Do" includes multiple sentences each starting with a verb. We'll make each as
- .
Now we need to output only HTML fragment, no /, no markdown.
Let's craft:
About the role
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. Commercial Software Engineering builds digital products and platforms that help fleet customers manage their operations and benefit from connected vehicle data. This Senior Software Engineering Manager is responsible for setting the technical and organizational direction and leading multiple engineering teams across the Commercial OnStar product and Commercial API areas. These areas span customer-facing experiences, vehicle telemetry, data streaming, transactional APIs, developer capabilities, and supporting platforms. This leader will shape strategy, strengthen execution, and build the organization required to deliver reliable, scalable, and customer-focused software. The role will partner with Product, Program, Vehicle Data, Infrastructure, Security, Privacy, Sales, Customer Support, and other enterprise teams to drive measurable business and customer outcomes.
Responsibilities
- Define and communicate the engineering strategy, roadmap, and operating plan for Commercial OnStar products and Commercial APIs.
- Lead multiple engineering teams through managers and senior technical leaders, establishing clear ownership, decision rights, priorities, and measures of success.
- Drive improvements in customer adoption, retention, revenue, onboarding, API usage, data quality, and service reliability.
- Use data and feedback to make tradeoffs, prioritize projects, and course-correct.
- Ensure strong team execution focused on urgency, iteration, consistency, and learning.
- Guide architecture, modernization, technical debt reduction, production readiness, observability, incident response, and service-level performance.
- Build effective partnerships across vehicle data, vehicle communications, middleware, infrastructure, consent, onboarding, billing, security, and privacy teams.
- Represent Commercial Software Engineering in executive discussions, major customer and partner engagements, and enterprise-level decisions.
- Attract, develop, and retain engineering leaders and technical talent while building a strong succession pipeline.
- Demonstrate managerial courage to challenge the status quo, simplify complex systems, and define creative solutions in a rapidly evolving software ecosystem.
Requirements
- Bachelor’s degree in computer science, engineering, information systems, or related technical field, or equivalent experience.
- 12+ years of experience in software engineering, technology, or related fields, including significant experience delivering large-scale software solutions.
- 5+ years of experience leading software engineering teams, including managers, senior technical leaders, and/or teams of teams.
- Demonstrated experience leading engineering organizations of roughly 30+ engineers (ICs and managers), including hiring, performance management, coaching, and organizational design.
Skills
for required. AndQualifications
for preferred? However they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Requirements (maybe for required) and Qualifications (for preferred). Or Skills for required. Let's decide: - About the role: description. - Responsibilities: What You’ll Do. - Requirements: Required Qualifications. - Qualifications: Preferred Qualifications. - Schedule: hybrid info. We should not include Skills separately if we used Requirements. But we could also include Skills as required and Qualifications as preferred. However the instruction list includes both Skills and Qualifications; we can choose to use Requirements for required and Qualifications for preferred. That seems fine. Now we need to preserve all substantive information, not invent or summarize away detail. We need to convert bullet points into- . The required qualifications list includes multiple sentences each as separate bullet? The text: "Your Skills & Abilities (Required Qualifications) Bachelor’s degree in computer science, engineering, information systems, or related technical field, or equivalent experience. 12+ years of experience in software engineering, technology, or related fields, including significant experience delivering large-scale software solutions. 5+ years of experience leading software engineering teams, including managers, senior technical leaders, and/or teams of teams. Demonstrated experience leading engineering organizations of roughly 30+ engineers (ICs and managers), including hiring, performance management, coaching, and organizational design. Demonstrated experience setting strategy and delivering complex, cross-functional software platforms or customer-facing products on-time. Strong technical knowledge of cloud platforms, distributed systems, APIs, data platforms, mobile/web applications, software architecture, security, and service reliability. Utilization of AI within developer lifecycle, business processes, and product development. Experience operating business-critical services, including production readiness, observability, incident management, service-level objectives, and continuous improvement. Demonstrated success hiring, developing, and retaining engineering managers and senior technical talent. Strong executive communication, influence, negotiation, prioritization, and decision-making skills." We'll make each line a
- . Preferred qualifications list: "Master's degree in computer science, engineering, information systems, or related technical field, or equivalent experience. 15+ years of experience in software engineering, technology, or related fields, including significant experience delivering large-scale software solutions. Experience with connected vehicle, automotive, fleet, mobility, logistics, SaaS, or other data-intensive products. Experience scaling web, mobile, and API-based products or platforms with external customers including Fortune 500 commercial partners with fleets of hundreds of thousands or millions of vehicles. Demonstrated history of product development that leads to strong user and revenue growth shown via measurable KPIs. Demonstrated ability to deliver products iteratively, on-time, and with sustained urgency in complex operational environments with many stakeholders across several organizations. Experience with vehicle telemetry, real-time data streaming, transactional APIs, developer platforms, or external partner integrations. Experience modernizing legacy platforms into scalable, observable, cloud-based architectures. GM does not provide immigration-related sponsorship for this role. Do not apply for this role if you will need GM immigration sponsorship now or in the future. This includes direct company sponsorship, entry of GM as the immigration employer of record on a government form, and any work authorization requiring a written submission or other immigration support from the company (e.g., H1-B, OPT, STEM OPT, CPT, TN, J-1, etc). 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}. Relocation benefits are available for candidates who qualify under company policy." Note: The last two bullet points about hybrid and relocation are actually under Preferred Qualifications? Actually they appear after the list but still part of the posting. However we already plan to put hybrid in Schedule section. The immigration note is also important; we should preserve that. It's not a benefit but a note about sponsorship. Where to place? Could be under Requirements? It's a condition. Could be its own section? Not in allowed headings. Could be placed under Requirements as a note. Or we could put under Qualifications? Probably better to include under Requirements (or a separate section like "Important Notes") but not allowed headings. We could incorporate into Requirements as a
- item. The instruction: preserve ALL substantive information. So we need to include that statement somewhere. Since we have no specific heading for legal notes, we could add it under Requirements as a list item. Or we could add a
after the list. The instruction says use
for prose. So we could add a paragraph after the Required Qualifications list: "GM does not provide immigration-related sponsorship for this role. Do not apply for this role if you will need GM immigration sponsorship now or in the future. This includes direct company sponsorship, entry of GM as the immigration employer of record on a government form, and any work authorization requiring a written submission or other immigration support from the company (e.g., H1-B, OPT, STEM OPT, CPT, TN, J-1, etc)." That's prose. Similarly the hybrid and relocation info we plan to put under Schedule section as prose. Now About the role: we have paragraphs under "The Role". We'll capture that as
maybe multiple paragraphs. Responsibilities: "What You’ll Do" includes multiple sentences each starting with a verb. We'll make each as
- .
Now we need to output only HTML fragment, no /, no markdown.
Let's craft:
About the role
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. Commercial Software Engineering builds digital products and platforms that help fleet customers manage their operations and benefit from connected vehicle data. This Senior Software Engineering Manager is responsible for setting the technical and organizational direction and leading multiple engineering teams across the Commercial OnStar product and Commercial API areas. These areas span customer-facing experiences, vehicle telemetry, data streaming, transactional APIs, developer capabilities, and supporting platforms. This leader will shape strategy, strengthen execution, and build the organization required to deliver reliable, scalable, and customer-focused software. The role will partner with Product, Program, Vehicle Data, Infrastructure, Security, Privacy, Sales, Customer Support, and other enterprise teams to drive measurable business and customer outcomes.
Responsibilities
- Define and communicate the engineering strategy, roadmap, and operating plan for Commercial OnStar products and Commercial APIs.
- Lead multiple engineering teams through managers and senior technical leaders, establishing clear ownership, decision rights, priorities, and measures of success.
- Drive improvements in customer adoption, retention, revenue, onboarding, API usage, data quality, and service reliability.
- Use data and feedback to make tradeoffs, prioritize projects, and course-correct.
- Ensure strong team execution focused on urgency, iteration, consistency, and learning.
- Guide architecture, modernization, technical debt reduction, production readiness, observability, incident response, and service-level performance.
- Build effective partnerships across vehicle data, vehicle communications, middleware, infrastructure, consent, onboarding, billing, security, and privacy teams.
- Represent Commercial Software Engineering in executive discussions, major customer and partner engagements, and enterprise-level decisions.
- Attract, develop, and retain engineering leaders and technical talent while building a strong succession pipeline.
- Demonstrate managerial courage to challenge the status quo, simplify complex systems, and define creative solutions in a rapidly evolving software ecosystem.
Requirements
- Bachelor’s degree in computer science, engineering, information systems, or related technical field, or equivalent experience.
- 12+ years of experience in software engineering, technology, or related fields, including significant experience delivering large-scale software solutions.
- 5+ years of experience leading software engineering teams, including managers, senior technical leaders, and/or teams of teams.
- Demonstrated experience leading engineering organizations of roughly 30+ engineers (ICs and managers), including hiring, performance management, coaching, and organizational design.