Principal Software Engineer- Test System Modernization

for each section. We need to decide which sections to include: About the role, Responsibilities, Requirements (maybe combine Required Qualifications and Skills?), Skills, Benefits, Pay, Schedule. Possibly also Preferred Qualifications as a separate section? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can choose. They said "Prefer a few substantive sections over many thin ones." So we might combine Required Qualifications and Skills into one "Requirements" section, and maybe Preferred Qualifications as part of Requirements or separate? Could be separate "Preferred Qualifications". But they said prefer few sections. Could combine Required and Preferred into "Qualifications". But they gave both Requirements and Qualifications as possible headings. We could have "Requirements" for required qualifications and "Preferred Qualifications" as separate if we want. But to keep few sections, maybe we have "Requirements" covering both required and preferred? However they'd be mixed. Better to have "Requirements" for required, and "Preferred Qualifications" as separate if we want to keep sections low. But we already have many sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. That's 6 sections. Adding Preferred Qualifications would be 7. That's okay. But we need to ensure we don't create thin sections. Preferred Qualifications has several bullet points; it's substantive. Thus sections: About the role, Responsibilities, Requirements (required qualifications), Preferred Qualifications, Benefits, Pay, Schedule. We must not include sections with filler. All have content. Now we need to format lists. For About the role: it's prose paragraph(s). Use

. Responsibilities: list of duties. We'll create

• for each bullet. We need to extract each duty statement. From "What You'll Do (Responsibilities):" we have sentences: - 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": list: - 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": - 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 could combine all these into responsibilities list. Now Required Qualifications (Your Skills & Abilities (Required Qualifications)): - 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 could split People Skills as separate bullet. Now Preferred Qualifications: - 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. Now 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. - This role is based remotely, but if the selected candidate lives within a specific mile radius of a GM hub, they will be expected to report to the location three times a week {or other frequency dictated by your manager}. - The selected candidate will be required to travel About the role

...

Responsibilities

• ...
...

Requirements

• ...