Job Description
Job Description The Role: We are seeking a Senior Software Architect to both define infrastructure software requirements and develop the automated tests that prove those requirements. In this role you will translate ECU‑level requirements into smaller, deployable chunks (Solutions and POD‑level requirements), and ensure each of those pieces can be independently implemented, integrated, and verified. You will act as a technical lead and subject‑matter expert across this flow – working with ECU‑level requirements owners, Mechatronics Infrastructure system engineers, and software implementers who write code within the POD construct – so that requirements are clear, testable, and backed by robust automation. You will coach other engineers, shape test and requirements architecture, and ensure our infrastructure solutions meet safety, quality, and performance expectations for GM’s global vehicle portfolio. What You’ll do: Technical Leadership & Requirements Authoring Own the technical direction and serve as the primary technical contact in one or more infrastructure Solutions (e.g., Communications, Controller Safety, Cybersecurity, Data Management, Diagnostics, Programming, Moding) from concept through deployment and sustainment, providing guidance on requirement scope, breakdown, and prioritization to peers and leadership. Lead cross‑functional workgroups (ECU‑level requirements owners, Mechatronics Infrastructure system engineers, SW implementation teams, bench/HIL and vehicle test) to gather, rationalize, and negotiate requirements into clear, testable infrastructure requirements that define interfaces involving PODs, Solutions, application, middleware, software generation tooling, and the BSW in general. Test Automation Design & Implementation Write high‑quality test scenarios in Gherkin format (Given/When/Then) that capture expected behavior, negative paths, and non‑functional requirements for Solutions and PODs. Implement and maintain automation code that binds Gherkin scenarios to reusable C++ step definitions and analyze results to identify defects, performance issues, and systemic gaps in requirements or implementation to ensure fast, reliable feedback for infrastructure software changes. Work with system and software engineers to triage, root‑cause, and close issues discovered by automated tests; feed learnings back into requirements, test cases, and coding guidelines, and drive improvements in built‑in quality by influencing design for testability and edge‑case coverage. Collaboration, Standards & Continuous Improvement Manage and refine the team backlog for requirements and test automation work within your area, working closely with other team members to balance feature, enabler, and quality items. Coach and mentor other engineers in requirements authoring, Python test development, infrastructure concepts (AUTOSAR, SOME/IP, Ethernet, diagnostics), and good testing practices; help onboard new team members and rotations. Maintain and grow deep knowledge of relevant standards and technologies, including AUTOSAR, UDS, J1979, J1979-2, J1979-3, DoIP, and service‑oriented communication (e.g., SOME/IP, DDS, REST). Help define and refine guidelines for infrastructure requirements, Gherkin scenarios, test case authoring, and traceability from ECU‑level requirements to Solution/POD requirements and automated tests/results. Evaluate new tools, frameworks, and methods in requirements management, test automation, and data analysis; pilot promising approaches and scale those that demonstrably improve coverage, stability, or developer productivity. Your Skills & Abilities (Required Qualifications) Bachelor’s degree in Computer Science, Software Engineering, Electrical/Computer Engineering, or related technical field; or equivalent experience. 5+ years of relevant software experience, including test automation for embedded or distributed systems. Strong proficiency in C++ for test automation or tooling (frameworks, fixtures, data parsing, reporting). Working knowledge of AUTOSAR Classic concepts and configuration, or equivalent embedded platform experience. Practical experience with automotive communication protocols such as CAN, LIN, and Ethernet, and familiarity with diagnostic protocols like UDS and DoIP. Solid understanding of the software development lifecycle, testing methodologies, and CI/CD practices. Demonstrated ability to analyze complex issues, decompose them into testable scenarios, and drive issues to closure across a multi‑stakeholder environment. Strong written and verbal communication skills; able to explain infrastructure behavior, constraints,