Principal Software Engineer- Test System Modernization
- for any list of duties/requirements/benefits. Use
for prose. We must not repeat job title as heading. The page already shows it, so we don't add heading for "Principal Software Engineer". We'll start with About the role (maybe from "The Role" paragraph). Then Responsibilities (What You'll Do). Then Requirements (Your Skills & Abilities (Required Qualifications)). Then Qualifications (What Will Give You a Competitive Edge (Preferred Qualifications)). Then Skills (maybe combine? Actually they have Skills & Abilities (Required Qualifications) and Preferred Qualifications. Could treat Required as Requirements, Preferred as Qualifications. Skills maybe not separate; but we can include Skills section if there is a list of skills. The posting includes "Your Skills & Abilities (Required Qualifications):" which includes many bullet-like sentences. We could put that under Requirements. Then "What Will Give You a Competitive Edge (Preferred Qualifications):" under Qualifications. Then maybe Skills section could be omitted or we could combine. But instruction: Prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. That's 7 sections. We need to extract content. Let's parse: About the role: The first paragraph after "Job Description The Role". Actually the text: "Job Description The Role General Motors is seeking a Principal Software Engineer to shape and scale the engineering platforms that build, test, integrate, validate, and deliver embedded software for software-defined vehicles. This role is for a hands-on technical leader who can turn ambiguous, cross-team problems into durable architecture, practical standards, and measurable improvements in engineering effectiveness, release confidence, and product quality. The successful candidate will lead a major capability across multiple teams, influence technical direction beyond their immediate organization, and connect software, tooling, infrastructure, test, and release activities into a coherent engineering system." We'll put that in
under About the role. Responsibilities: Under "What You'll Do (Responsibilities):" then a list of bullet-like sentences separated by periods. We need to convert to
- . Let's extract each responsibility:
- Be a critical leader of software engineering productivity and effectiveness.
- Identify opportunities, strategies, process improvements, and lead the change.
- Be hands-on by leading high impact efforts.
- Be a strong communicator, coach, and mentor.
- Analyze unusual and difficult problems effectively.
- Ability to connect multiple initiatives together to deliver higher value.
- Visualize required innovation, learning and simplification in this space and transition the team to execute what is required to achieve.
- Maintain command skills and empathy at the same time.
- Lead the modernization of a large-scale embedded software test system.
- Define and modernize a standardized, fully automated, headless framework across virtual and physical environments to enable full-suite testing multiple times per day.
Then "Key Deliverables" maybe part of responsibilities? It's a separate bullet list but could be considered responsibilities. We'll include them as responsibilities as well.
Key Deliverables:
- Define the architecture and roadmap for standardized test execution, configuration and variation management, traceability, quality gates, regression selection, and results reporting.
- Establish change-impact analysis and risk-based regression strategies using Gears, Pure Variants, or equivalent tools to determine test applicability and optimize re-testing.
- Standardize test-result schemas, metadata, diagnostics, and artifacts; enable storage in Databricks for analytics, trend analysis, data mining, and reporting.
- Develop APIs and integrations connecting test execution, test management, issue tracking, failure triage, and diagnostic tools.
- Improve test robustness, failure triage, execution speed, and deployment efficiency across CI/CD pipelines and physical and virtual test environments.
Then "Measures of Success" maybe also responsibilities? Could be considered outcomes. We could include them under Responsibilities as well, but maybe better to keep as part of Responsibilities. However the instruction: Use
- for any list of duties/requirements/benefits. Measures of Success is a list of outcomes; could be considered duties? Might be okay to include as responsibilities. But we could also treat them as part of Responsibilities. Let's include them.
Measures of Success:
- Faster, more reliable test deployment and execution.
- More efficient regression testing through accurate change-impact analysis.
- Standardized, traceable test results accessible through Databricks and documented APIs.
- Faster failure identification, triage, and resolution.
- Clear test applicability across software, hardware, configuration, and platform variants.
We'll combine all into one
- under Responsibilities.
Requirements (Required Qualifications): List:
- Bachelor's degree in computer science, computer engineering, electrical engineering, software engineering, systems engineering or a related technical field; or equivalent practical experience.
- Typically, 15 or more years experience validating software systems, including substantial experience leading architecture across organizations.
- Deep understanding of software architecture for real time systems.
- Experience shipping high quality safety critical products.
- Experience architecting large-scale CI/CD, embedded test automation, and build-to-test pipelines.
- Expertise in variation management, configuration comparison, change-impact analysis, and risk-based regression testing.
- Experience with test-result data modeling, Databricks, analytics, data mining, and API development.
- Proficiency with embedded systems, Linux, Git, Python, Bash, Robot Framework, containers, and infrastructure as code.
- Demonstrated ability to integrate automated diagnostics and issue-management workflows.
- People Skills: Exceptional problem-solving and analytical abilities, with a keen attention to detail.
- Demonstrated ability to manage multiple projects and priorities in a fast-paced environment.
- Demonstrated ability to work in an action-oriented decision-making environment.
We'll put each as
- .
Qualifications (Preferred Qualifications): List:
- Master’s degree or PhD in Computer Science, Software Engineering, Machine Learning, AI, or a related field.
- Experience in embedded software development, automotive software, systems engineering, or safety-related toolchains.
- Familiarity with GM engineering tools, engineering workflows, or internal platform environments.
- Experience building AI assistants, coding agents, or domain-specific AI capabilities for engineers.
- Experience with knowledge systems, vector search, ranking, workflow orchestration, or code intelligence platforms.
- Experience supporting large engineering communities through reusable tools, templates, and automation.
- Experience evaluating AI quality in production systems using measurable outcomes such as acceptance rate, time saved, precision and recall, hallucination reduction, or workflow completion rate.
Benefits: The posting includes "Benefits GM offers a variety of health and wellbeing benefit programs. Benefit options include medical, dental, vision, Health Savings Account, Flexible Spending Accounts, retirement savings plan, sickness and accident benefits, life insurance, paid vacation & holidays, tuition assistance programs, employee assistance program, GM vehicle discounts and more." Also later "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." We'll include the list.
Pay: Salary range: $238,700 and $365,700. Also bonus potential: "An incentive pay program offers payouts based on company performance, job level, and individual performance." We'll include that.
Schedule: Remote role, but if within specific mile radius of a GM hub, expected to report to location three times a week {or other frequency dictated by your manager}. Selected candidate will be required to travel About the role
...
Responsibilities
- ... ...
Requirements
-
...
Qualifications
-
...
Benefits
-
...
Pay
...
Schedule
...
Make sure no extra whitespace? It's fine. Now craft content precisely. About the role paragraph: Combine the two sentences: "General Motors is seeking a Principal Software Engineer to shape and scale the engineering platforms that build, test, integrate, validate, and deliver embedded software for software-defined vehicles. This role is for a hands-on technical leader who can turn ambiguous, cross-team problems into durable architecture, practical standards, and measurable improvements in engineering effectiveness, release confidence, and product quality. The successful candidate will lead a major capability across multiple teams, influence technical direction beyond their immediate organization, and connect software, tooling, infrastructure, test, and release activities into a coherent engineering system." We'll put as one. Responsibilities list: We'll include all bullet points we identified. Let's list them: - Be a critical leader of software engineering productivity and effectiveness. - Identify opportunities, strategies, process improvements, and lead the change. - Be hands-on by leading high impact efforts. - Be a strong communicator, coach, and mentor. - Analyze unusual and difficult problems effectively. - Ability to connect multiple initiatives together to deliver higher value. - Visualize required innovation, learning and simplification in this space and transition the team to execute what is required to achieve. - Maintain command skills and empathy at the same time. - Lead the modernization of a large-scale embedded software test system. - Define and modernize a standardized, fully automated, headless framework across virtual and physical environments to enable full-suite testing multiple times per day. - Define the architecture and roadmap for standardized test execution, configuration and variation management, traceability, quality gates, regression selection, and results reporting. - Establish change-impact analysis and risk-based regression strategies using Gears, Pure Variants, or equivalent tools to determine test applicability and optimize re-testing. - Standardize test-result schemas, metadata, diagnostics, and artifacts; enable storage in Databricks for analytics, trend analysis, data mining, and reporting. - Develop APIs and integrations connecting test execution, test management, issue tracking, failure triage, and diagnostic tools. - Improve test robustness, failure triage, execution speed, and deployment efficiency across CI/CD pipelines and physical and virtual test environments. - Faster, more reliable test deployment and execution. - More efficient regression testing through accurate change-impact analysis. - Standardized, traceable test results accessible through Databricks and documented APIs. - Faster failure identification, triage, and resolution. - Clear test applicability across software, hardware, configuration, and platform variants. That's many items; okay. Requirements list: - Bachelor's degree in computer science, computer engineering, electrical engineering, software engineering, systems engineering or a related
- .
Qualifications (Preferred Qualifications): List:
- Master’s degree or PhD in Computer Science, Software Engineering, Machine Learning, AI, or a related field.
- Experience in embedded software development, automotive software, systems engineering, or safety-related toolchains.
- Familiarity with GM engineering tools, engineering workflows, or internal platform environments.
- Experience building AI assistants, coding agents, or domain-specific AI capabilities for engineers.
- Experience with knowledge systems, vector search, ranking, workflow orchestration, or code intelligence platforms.
- Experience supporting large engineering communities through reusable tools, templates, and automation.
- Experience evaluating AI quality in production systems using measurable outcomes such as acceptance rate, time saved, precision and recall, hallucination reduction, or workflow completion rate.
Benefits: The posting includes "Benefits GM offers a variety of health and wellbeing benefit programs. Benefit options include medical, dental, vision, Health Savings Account, Flexible Spending Accounts, retirement savings plan, sickness and accident benefits, life insurance, paid vacation & holidays, tuition assistance programs, employee assistance program, GM vehicle discounts and more." Also later "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." We'll include the list.
Pay: Salary range: $238,700 and $365,700. Also bonus potential: "An incentive pay program offers payouts based on company performance, job level, and individual performance." We'll include that.
Schedule: Remote role, but if within specific mile radius of a GM hub, expected to report to location three times a week {or other frequency dictated by your manager}. Selected candidate will be required to travel About the role
- for any list of duties/requirements/benefits. Measures of Success is a list of outcomes; could be considered duties? Might be okay to include as responsibilities. But we could also treat them as part of Responsibilities. Let's include them.
Measures of Success:
- Faster, more reliable test deployment and execution.
- More efficient regression testing through accurate change-impact analysis.
- Standardized, traceable test results accessible through Databricks and documented APIs.
- Faster failure identification, triage, and resolution.
- Clear test applicability across software, hardware, configuration, and platform variants.
We'll combine all into one
- . Let's extract each responsibility:
- Be a critical leader of software engineering productivity and effectiveness.
- Identify opportunities, strategies, process improvements, and lead the change.
- Be hands-on by leading high impact efforts.
- Be a strong communicator, coach, and mentor.
- Analyze unusual and difficult problems effectively.
- Ability to connect multiple initiatives together to deliver higher value.
- Visualize required innovation, learning and simplification in this space and transition the team to execute what is required to achieve.
- Maintain command skills and empathy at the same time.
- Lead the modernization of a large-scale embedded software test system.
- Define and modernize a standardized, fully automated, headless framework across virtual and physical environments to enable full-suite testing multiple times per day.
Then "Key Deliverables" maybe part of responsibilities? It's a separate bullet list but could be considered responsibilities. We'll include them as responsibilities as well.
Key Deliverables:
- Define the architecture and roadmap for standardized test execution, configuration and variation management, traceability, quality gates, regression selection, and results reporting.
- Establish change-impact analysis and risk-based regression strategies using Gears, Pure Variants, or equivalent tools to determine test applicability and optimize re-testing.
- Standardize test-result schemas, metadata, diagnostics, and artifacts; enable storage in Databricks for analytics, trend analysis, data mining, and reporting.
- Develop APIs and integrations connecting test execution, test management, issue tracking, failure triage, and diagnostic tools.
- Improve test robustness, failure triage, execution speed, and deployment efficiency across CI/CD pipelines and physical and virtual test environments.
Then "Measures of Success" maybe also responsibilities? Could be considered outcomes. We could include them under Responsibilities as well, but maybe better to keep as part of Responsibilities. However the instruction: Use