Staff Software Engineer - Build System Modernization

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job description. Key sections: - About the role: The first paragraph(s) describing 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." We can put that under

About the role

with

. - Responsibilities: The "What You'll Do:" bullet list. We need to extract bullet points. List items: - 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. We can put these under

Responsibilities

with

• . - Requirements / Qualifications: There's a "Hold a bachelor’s degree in software engineering or have equivalent experience, along with 15 years of software development experience." Also "Your Skills & Abilities (Required Qualifications):" list. We need to decide sections: maybe "Qualifications" and "Skills". The instruction says use headings like Qualifications, Skills. We can combine or separate. We have: - Bachelor's degree in software engineering or equivalent experience. - 12+ years of experience in software development (note earlier said 15 years; but we keep both? The "Your Skills & Abilities" says 12+ years. We'll preserve both statements; but we must not invent. We'll include both as separate bullet points? Might be duplicate. We'll include both as separate bullet points under Qualifications. - 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. We can put these under

  Qualifications

  (or Requirements). The instruction says use headings like Qualifications, Skills. We have a "Skills & Abilities (Required Qualifications)" heading already. So we can use

  Skills

  for that list. But we also have degree and years etc. Could be under Qualifications. Let's decide:

  Qualifications

  for degree, years, deep understanding, safety-critical experience, problem-solving, managing multiple projects, action-oriented decision-making, expertise building production systems, proficiency in Python + another language, automotive/embedded etc. Then

  Skills

  for large-scale migration, AI-assisted developer productivity, evaluation of AI-enabled workflows. However the list includes also those under Skills & Abilities. Might be okay. Alternatively combine all under Qualifications. But we need to avoid thin sections. We'll make two sections: Qualifications and Skills. Now 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." We can put under

  Benefits

  with
  • each item. Pay: The posting includes compensation: "The Salary Range The range for this role is 171,150 and 288,500." Also "Compensation The compensation information is a good faith estimate only..." and "Bonus Potential An incentive pay program offers payouts based on company performance, job level, and individual performance." We need to include Pay section only if posting actually states them. It does state salary range and bonus potential. So we can include

    Pay

    with

    describing salary range and bonus potential. Schedule: No mention of schedule (e.g., full-time, remote). Not present, so we omit Schedule section. About GM: There's "About GM Our vision is a world with Zero Crashes, Zero Emissions and Zero Congestion and we embrace the responsibility to lead the change that will make our world better, safer and more equitable for all." Also "Why Join Us ..." and "Benefits Overview ..." plus Non-Discrimination etc. Those are boilerplate; we should remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About GM" and "Why Join Us" might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About GM" is not exactly legal boilerplate; it's company description. Might be considered okay to keep? The instruction says "Prefer a few substantive sections over many thin ones." Could include an "About the company" section but not listed as allowed headings. Allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add extra headings like About GM. So we omit that. Also "Company Vehicle" section: "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-like detail. Could be included under Benefits? It's a specific perk. We could add a bullet under Benefits: "Company vehicle evaluation program (eligible after MVR review; participants required to purchase/lease a qualifying GM vehicle every four years unless exceptions apply)." That seems appropriate. Now we need to output only HTML fragment, no /, no markdown. We'll produce:

    About the role

    ...

    Responsibilities

    • ...
    ...

    Qualifications

    • ...
    ...

    Skills

    • ...
    ...

    Benefits

    • 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
    • Company vehicle evaluation program (eligible after motor vehicle report review; participants required to purchase/lease a qualifying GM vehicle every four years unless exceptions apply)

    Pay

    The salary range for this role is $171,150 to $288,500. An incentive pay program offers payouts based on company performance, job level, and individual performance.

    We need to ensure we preserve all substantive information. Also include the note about compensation being good faith estimate etc. Might include that in Pay section. Let's craft Pay paragraph: "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 for this role is $171,150 to $288,500. An incentive pay program offers payouts based on company performance, job level, and individual performance." Now check for any other substantive info: "Hold a bachelor’s degree in software engineering or have equivalent experience, along with 15 years of software development experience." We have degree and years but we used 12+ years from Skills & Abilities. We should include both 15 years and 12+ years? The posting says both: earlier says 15 years, later says 12+ years. We should preserve both. We'll include two bullet points: "Bachelor's degree in software engineering or equivalent experience" and "15 years of software development experience" and also "12+ years of experience in software development" maybe redundant but we can keep both as separate bullets. However to avoid duplication, we could note "15+ years of software development experience (with 12+ years specified)". But better to keep both as they appear. We'll include bullet: "15 years of software development experience" and bullet: "12+ years of experience in software development". Might be seen as duplicate but it's preserving info. Now also "Hold a bachelor’s degree in software engineering or have equivalent experience, along with 15 years of software development experience." That's one sentence. We'll split. Now also "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." That's covered. Now also "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." We'll capture. Now also "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." We'll capture. Now also "Evaluate AI-enabled engineering workflows using measurable quality, adoption, and productivity outcomes." captured. Now also "Your