Principal Software Engineer - Build System Modernization

General Motors · Austin, TX · 3 wk ago

HybridEngineeringFull-time

We need to output HTML fragment with sections: h3 headings for sections present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. The posting includes: - The Role: description (maybe "About the role") - What You'll Do: responsibilities - Key Deliverables (maybe also responsibilities) - Measures of Success (maybe part of responsibilities) - Your Skills & Abilities (Required Qualifications): qualifications - What Will Give You A Competitive Edge (Preferred Qualifications): maybe also qualifications or skills - Compensation: salary range (Pay) - Benefits: description - Schedule: remote, expectation to report three times a week if near hub, relocation benefits. So schedule info present. We need to avoid repeating job title as heading. Use h3 for each section heading. We need to use ul/li for any list of duties/requirements/benefits, and p for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO etc. Also remove duplicated lines, application instructions. We need to include sections only when posting has real specific content. So we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills?, Benefits, Pay, Schedule. But we must not create thin sections with filler. Let's map content. About the role: The Role: General Motors is seeking a software engineering leader to modernize and scale the build systems that support software-defined vehicles. This role will help lead the transition from a legacy Make-based system to Bazel, Google’s open-source build tool, improving speed, reliability, and robustness across the engineering organization. The successful candidate will drive this capability at scale, influence technical direction across teams, and help establish lofty platform capability goals. That's substantive. Responsibilities: What You'll Do: list of bullet-like sentences. Also Key Deliverables and Measures of Success could be part of responsibilities. We'll combine into a responsibilities section with ul/li items. Requirements: maybe "Hold a bachelor’s degree in software engineering or have equivalent experience, along with 15 years of software development experience." plus other required qualifications: deep understanding of real-time software architecture, experience shipping high-quality safety-critical products, problem-solving, managing multiple projects, expertise building production systems, proficiency in Python and at least one additional engineering-tooling language, experience with AI-assisted developer productivity, etc. Also "Your Skills & Abilities (Required Qualifications):" list. Qualifications: maybe "What Will Give You A Competitive Edge (Preferred Qualifications):" list. Skills: maybe we could combine required qualifications as Skills? But the instruction says use sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. Typically Requirements = required qualifications (education, experience). Qualifications = preferred qualifications. Skills = maybe specific technical skills (Bazel, Python, etc). But we have overlapping. We need to avoid thin sections. Let's see if we can assign: - Requirements: education (bachelor's or equivalent) + 15 years experience + deep understanding of real-time software architecture + experience shipping high-quality safety-critical products + ability to manage multiple projects + expertise building production systems. - Qualifications: preferred qualifications (Master's/PhD, experience in embedded software, automotive, GM tools, AI assistants, knowledge systems, evaluating AI quality). - Skills: maybe list of technical skills: proficiency in Python and at least one additional engineering-tooling language, experience with AI-assisted developer productivity, coding agents, code intelligence, knowledge retrieval, workflow orchestration, evaluating AI-enabled engineering workflows, large-scale migration from Make/shell to Bazel, Bazel rules, macros, toolchains, etc. However many of these appear in responsibilities/deliverables. Might be better to put Skills as a list of specific technical competencies: Bazel, Python, additional language, AI-assisted developer productivity, etc. But we need to avoid duplication. Given the instruction: "Use

for any list of duties/requirements/benefits, and
for prose." So we can have multiple lists. We need to preserve ALL substantive information; not invent or summarize away detail. So we must include all details from the posting, but we can group them logically. Let's extract all substantive bullet points: From "What You'll Do:" (list): - Lead software engineering productivity and effectiveness by identifying opportunities, shaping strategies, improving processes, guiding change, and connecting initiatives to deliver greater value through innovation, learning, and simplification. - Lead high-impact efforts hands-on, solve complex and unusual problems, and communicate effectively as a coach and mentor while balancing technical command with empathy. - Modernize a large embedded-software build and test system by transitioning legacy Make- or shell-based workflows to Bazel and establishing scalable, reproducible, secure, and developer-friendly infrastructure across repositories, toolchains, CI/CD, testing, and release processes. - Assess current build, test, dependency, toolchain, and hardware workflows to define a phased Bazel migration strategy and rollout model. - Design and implement reusable Bazel rules, macros, toolchains, platforms, configuration patterns, and repository standards, while migrating embedded applications, libraries, generated code, firmware, cross-compilation flows, and platform variants with validated build parity and reproducibility. - Integrate Bazel with enterprise CI/CD, testing, release, artifact, deployment, observability, security, and infrastructure workflows, and optimize the platform through caching, parallelism, reliability practices, documentation, training, legacy Make retirement, and continuous improvement. - Measure success through target repositories migrated with validated build and test parity; faster clean and incremental builds, CI queues, and developer feedback; increased reproducibility, approved hermetic-toolchain adoption, cache effectiveness, and CI capacity; and lower build, pipeline, and flaky-test rates. - Improve diagnosis and recovery time while ensuring complete artifact provenance, test evidence, and security-policy compliance for releases, strong developer adoption, reduced support burden, and measurable productivity improvement. From "Key Deliverables": - Assess current Make-based build, test, dependency, toolchain, and hardware workflows, then define a phased Bazel migration strategy and rollout model. - Design and implement reusable Bazel rules, macros, toolchains, platforms, configuration patterns, and repository standards for embedded software. - Migrate embedded applications, libraries, generated code, firmware, cross-compilation flows, and platform variants while ensuring build parity and reproducibility. - Integrate Bazel with enterprise CI/CD, testing, release, artifact, deployment, observability, security, and infrastructure workflows. - Optimize and operationalize the platform through caching, parallelism, reliability practices, documentation, training, legacy Make retirement, and continuous improvement. From "Measures of Success": - Target repositories migrated with validated build and test parity. - Reduced clean and incremental build time, CI queue time, and developer feedback time. - Increased reproducibility, approved hermetic-toolchain adoption, cache effectiveness, and CI capacity. - Lower build, pipeline, and flaky-test rates, with improved diagnosis and recovery time. - Complete artifact provenance, test evidence, and security-policy compliance for releases. - Strong developer adoption, reduced support burden, and measurable productivity improvement. These are somewhat repetitive with What You'll Do. We need to preserve all info, but we can combine similar points without losing detail. However we must not "summarize away detail". If we combine, we might lose some nuance. But we can keep them as separate items even if similar; that's okay. From "Hold a bachelor’s degree in software engineering or have equivalent experience, along with 15 years of software development experience." - Bring a deep understanding of real-time software architecture and experience shipping high-quality, safety-critical products in automotive, embedded, safety-related, calibration, or systems-engineering environments. - Demonstrate exceptional problem-solving and analytical abilities, keen attention to detail, and the ability to manage multiple projects and priorities in fast-paced, action-oriented decision-making environments. - Bring strong expertise building and maintaining production software systems, proficiency in Python and at least one additional engineering-tooling language, and experience with AI-assisted developer productivity, coding agents, code intelligence, knowledge retrieval, or workflow orchestration. - Evaluate AI-enabled engineering workflows using measurable quality, adoption, and productivity outcomes. From "Your Skills & Abilities (Required Qualifications):" list: - Bachelor's degree in software engineering or or equivalent experience - 15+ years of experience in software development - Deep understanding of software architecture for real time systems - Experience shipping high quality safety critical products - 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 - Strong expertise building and maintaining production software systems, with proficiency in Python and at least one additional language used in engineering tooling environments - Automotive, embedded, safety-related, calibration, or systems-engineering environments. - Large-scale migration from Make or shell-based build orchestration to Bazel. - AI-assisted developer productivity, coding agents, code intelligence, knowledge retrieval, or workflow orchestration. - Evaluation of AI-enabled engineering workflows using measurable quality, adoption, and productivity outcomes. Note some duplication with earlier. From "What Will Give You A Competitive Edge (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 From Compensation: - The compensation information is a good faith estimate only. It is based on what a successful applicant might be paid in accordance with applicable state laws. The actual base salary a successful candidate will be offered within this range will vary based on factors relevant to the position, as well as geography of the selected candidate. The Salary Range The range for this role is 201,000 and 400,000. The actual base salary a successful candidate will be offered within this range will vary based on factors relevant to the position. - Bonus Potential: An incentive pay program offers payouts based on company performance, job level, and individual performance. From 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}. Relocation benefits are available for candidates who qualify under company policy. Also there is "Company Vehicle Upon successful completion of a motor vehicle report review, you will be eligible to participate in a company vehicle evaluation program, though which you will be assigned a General Motors vehicle to drive and evaluate. Note: program participants are required to purchase/lease a qualifying GM vehicle every four years unless one of a limited number of exceptions applies." This is a benefit? Could be part of Benefits. We need to include Benefits section with list of benefits. Schedule: remote, expectation to report three times a week if near hub, relocation benefits. So schedule info. We must not include boilerplate like EEO, Non-Discrimination, Accommodations, etc. Now we need to produce HTML fragment with h3 headings and appropriate content. We need to decide which sections to include: - About the role (h3) - Responsibilities (h3) (combining What You'll Do, Key Deliverables, Measures of Success) - Requirements (h3

Principal Software Engineer - Build System Modernization

Similar jobs