> Markdown version of [/jobs/ext/4769695-staff-system-architecture-technical-program-manager](https://www.wearedevelopers.com/jobs/ext/4769695-staff-system-architecture-technical-program-manager). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Staff System & Architecture Technical Program Manager - **Company:** General Motors - **Location:** Sunnyvale, CA, United States - **Salary:** $159,400 - $245,000 - **Contract:** Permanent contract - **Skills:** Systems Engineering, Confluence, JIRA, Continuous Integration, Digital Technology, Software Engineering, Software Requirements Analysis, Software Systems, Systems Architecture, Systems Integration, Smartsheet, Lidar, Data Pipelines - **Published:** November 18, 2026 - **Apply:** https://generalmotors.wd5.myworkdayjobs.com/Careers_GM/job/Sunnyvale-California-United-States-of-America/Staff-System---Architecture-Technical-Program-Manager_JR-202624319 ## About the Role * 15+ years of experience in technical program management, systems engineering, architecture program leadership, or a related field. * Demonstrated success leading complex, cross-functional programs involving integrated hardware and software systems. * Experience coordinating system architecture, requirements, interfaces, dependencies, risks, and milestones across multiple teams or platforms. * Working knowledge of embedded systems, automotive vehicle or electrical/electronic (E/E) architecture, compute platforms, and system integration. * Ability to understand technical tradeoffs, structure decision-making, and drive follow-through without displacing engineering ownership of technical decisions. * Strong written, verbal, and executive communication skills; able to make complex system issues and recommended actions clear to varied audiences. * Proven ability to influence across organizational boundaries, establish accountability, and lead through ambiguity and changing priorities. What Will Give You A Competitive Edge (Preferred Qualifications) * Experience supporting autonomous vehicle programs or advanced driver-assistance systems (ADAS), including SCx or L2+/L3/L4 feature deployment. * Experience with sensor-suite integration, such as camera, RADAR, or lidar, and related sensing-performance or validation needs. * Familiarity with data pipelines and vehicle data offload, diagnostics and system health monitoring, functional safety, or compliance and validation processes. * Experience scaling architecture or platform capabilities across multiple vehicle lines, compute generations, or geographically distributed teams. * Familiarity with AV software development pipelines, CI/CD, and program tools such as Jira, Confluence, and Smartsheet. ## Description General Motors is seeking a Staff Technical Program Manager to lead system-level planning, integration, and cross-functional execution across our evolving autonomous vehicle architecture. This role will support SC3, the SC4L pullahead, SC4, and Digital System Development-programs with increasing technical complexity, compressed timelines, and dependencies spanning vehicle platforms, sensing, compute, hardware, software, data, and operations. Working in close partnership with engineering and program leaders, you will turn system and architecture objectives into an integrated plan: align assumptions and interfaces, drive timely technical decisions, surface system-level gaps and risks, and coordinate dependencies through resolution. You will establish clear ownership and a predictable operating rhythm so teams can make informed tradeoffs early and deliver a coherent, scalable system across vehicle programs. What You'll Do * Lead system-level program integration: Build and maintain an integrated view of architecture scope, milestones, interfaces, dependencies, decisions, risks, and mitigations across SC3, SC4L pullahead, SC4, centralized RADAR, and Digital System Development. * Drive architecture alignment: Partner with Systems, Vehicle, Hardware, Software, Sensor, Data, Safety, and program teams to align system requirements, assumptions, interfaces, and roadmaps across vehicle platforms and compute generations. * Coordinate end-to-end sensing integration: Connect sensing performance and sensor-suite needs with hardware and software integration, sensor cleaning and contamination mitigation, vehicle integration, and validation plans. * Accelerate decisions and issue resolution: Identify cross-team gaps, decision points, and schedule risks early; frame options and impacts; bring the right technical owners together; document decisions; and track actions to closure-particularly against SC4L pullahead timelines. * Establish clear accountability: Define owners, interfaces, milestones, and escalation paths across internal teams and partner organizations, including Munich and other cross-functional groups. * Create a predictable operating rhythm: Lead focused architecture and integration reviews, dependency and risk reviews, and milestone readiness checkpoints; maintain concise, decision-oriented program artifacts in tools such as Jira, Confluence, and Smartsheet. * Communicate program health: Provide clear, audience-appropriate updates on progress, key decisions, technical and integration risks, mitigations, and leadership asks. * Enable scalable delivery: Capture reusable architecture and integration practices, lessons learned, and planning mechanisms that improve alignment and feature portability across programs and vehicle lines. What Success Looks Like * Cross-functional teams share a current, consistent view of system scope, interfaces, assumptions, dependencies, and ownership. * Architecture and integration decisions are made with the right technical owners, documented, and delivered in time to protect program milestones. * System-level gaps and sensing, hardware, software, cleaning, and vehicle integration risks are surfaced early, with accountable mitigation plans. * SC4L pullahead and other program milestones have integrated plans and visible readiness, with fewer late surprises caused by unresolved cross-team dependencies. * Common integration approaches and lessons learned can be reused across SC3, SC4, and future vehicle programs., This role is categorized as hybrid. This means the selected candidate is expected to report to a specific location at least 3 times a week {or other frequency dictated by their manager}.