Job Description
Vacancy Status: This posting is for an existing vacancy within the organization and is open to new applications.

AI Disclosure: As part of the application process, Artificial Intelligence will be used in the hiring process for this role

Work Arrangement: Hybrid: This role is categorized as hybrid. This means the successful candidate is expected to report to Markham or Oshawa office three times per week, at minimum.

Why Work for Us

General Motors is transforming into a technology-driven company with a bold vision of Zero Crashes, Zero Emissions, and Zero Congestion. You will be at the forefront of revolutionizing software, controls, and virtual development for future vehicles, working in inclusive teams and modern, flexible work environments.

About the Role

The Staff System Architect – CoSim Architecture & Virtual Integration will define and lead the end-to-end architecture for General Motors’ scalable, domain-agnostic co-simulation and virtual integration ecosystem. This role will establish the technical foundation used to integrate embedded software, virtual ECUs, plant and behavioral models, network and vehicle services, test environments, and engineering data across multiple vehicle domains, programs, variants, and model years. The successful candidate will set the long-term architecture and technical roadmap for building, scaling, operating, and continuously improving the CoSim platform. The role is intentionally domain agnostic: the architect will partner with domain specialists and enable consistent platform capabilities rather than own only one vehicle domain. This role requires a systems thinker who can move between architecture, hands‑on technical problem solving, integration contracts, software and model interfaces, execution patterns, quality governance,



and stakeholder alignment. The architect will work closely with Simulation Integration Engineers, System and Software Architects, Plant Modeling, CoSim Package/Variant, Pipeline & Execution, Build & Toolchain, Diagnostics, Quality, program, and supplier teams. The role is not a CI/CD platform-owner position; it defines the CoSim architecture and collaborates with specialized teams that provide automation and pipeline capabilities.

Key Responsibilities

Define and evolve the end-to-end CoSim/SIL architecture, including system boundaries, interfaces, ownership models, reusable patterns, non-functional requirements, and architectural decision records. Create a scalable reference architecture for integrating plant models, behavioral models, virtual ECUs, infrastructure vECUs, network behavior, embedded software, supplier assets, and test services into cohesive and repeatable virtual environments. Establish platform standards for CoSim package structure, APIs, model and software interfaces, dependency management, versioning, documentation, release notes, and deployment across supported execution environments. Define integration and execution patterns that enable the repeatable assembly, validation, and use of CoSim assets; partner with Pipeline & Execution and Build & Toolchain teams on automation, quality gates, and execution enablement rather than owning CI/CD platforms.



Lead integration patterns for reusable cross-domain services such as activation and lifecycle behavior, diagnostics access, non-volatile memory behavior, network simulation, fault injection, configuration, logging, and test orchestration. Define and govern variant, configuration, and content-management strategies across programs, regions, model years, feature sets, and test environments; ensure reproducible package and workplace composition. Partner with systems and test engineering teams to translate requirements and test intent into simulation bills of material, executable CoSim assets, test configurations, and traceable release content. Establish integration requirements and acceptance criteria for supplier and partner assets, including FMUs/FMI, SSP packages, vECUs, C/C++ libraries, AUTOSAR components, models, and communication interfaces. Define data and traceability architecture connecting capabilities, features, packages, variants/configurations, test plans, executions, logs, metrics, defects, and release decisions. Drive observability and engineering insights through consistent logging, metrics, dashboards, health indicators, coverage reporting, and trend analysis for virtual assets and execution infrastructure. Ensure architecture decisions account for performance, fidelity, scalability, reusability, maintainability, reliability, security, safety, and ease of adoption by distributed engineering teams. Establish architecture governance, conduct design and integration reviews, resolve cross-team technical trade-offs, and maintain a practical roadmap aligned with SDV and virtual development strategy. Lead technical alignment across global teams and organizational boundaries; influence without direct auth

📌 Staff Systems Engineering (Markham)
🏢 General Motors
📍 Markham