Vacancy Status:

This posting is not for an existing vacancy within the organization and is open to new applications. (New Head Count)

AI Disclosure:

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

Hybrid:

This role is categorized as hybrid. This means the successful candidate is expected to report to Markham Elevation Center three times per week, at minimum

About the role:

The Staff System Architect – CoSim Diagnostics, NVM, Network & Data/Release owns the end‑to‑end architecture for:

• Diagnostic access, NVM life‑cycle behavior, and network behavior/corruption models in L3/L4 CoSim and related pipelines, and
• The data model, traceability, dashboards, and documentation connecting capabilities, packages, configs, tests, and results for the Virtualization organization.

You will define how these behaviors and data flows are modeled, integrated into pipelines and exposed to test, quality, and program stakeholders, while ensuring alignment with security, safety, and release governance.

Key Responsibilities

1) CoSim & Virtual Platform Architecture (Diagnostics / NVM / Network)

• Own diagnostic access in L3/L4 CoSim and related pipelines.
• Define and implement diagnostics integration, including:
  • Support for off‑board tools (J2534‑equivalent) into CoSim.
  • Robust handling of RIDs/DIDs and associated diagnostic data flows.
  • DoIP flows in CoSim across virtual ECUs and networks.
• Provide clear diagnostic access methods and patterns for test and integration teams.
• Design and maintain NVM simulation behavior in CoSim:
  • Initialize from provided NVM snapshots.
  • Save on sleep and restore on boot.
  • Support behavior per configuration/variant.
• Own sleep/wakeup and power mode behavior in HWIO_SIM and related components, ensuring realistic ECU life‑cycle behavior.
• Define and document NVM strategies for virtual environments and ensure consistent application across programs.
• Develop and maintain network behavior models for virtual environments, with a focus on Ethernet/SOME-IP and CAN.
• Implement corruption/injection capabilities (e.g., frame drops, bit flips, latency/jitter, malformed frames) to support TFRP and other tests.
• Ensure network behavior models integrate cleanly with diagnostics and NVM behaviors for end‑to‑end test scenarios.
• Define where diagnostics, NVM, and network features integrate into:
  • L3/L4 CoSim pipelines
  • SOLE/SystemBench
  • SILART and related execution environments
• Provide clear APIs, configurations, and integration contracts so pipelines can reliably configure and consume these capabilities.
• Work closely with Pipeline & Execution, Plant Modeling, CoSim Package/Variant, and Build & Toolchain teams to ensure seamless, reproducible behavior in CI/CD and execution flows.

2) Data / Release, Traceability & Documentation (SILART & Virtualization)

• Define and maintain the traceability data model connecting:
  • Capabilities features packages variants/configs test plans runs metrics.
• Implement and maintain data integrations to:
  • Ingest logs/results from GMSIM, SOLE, Autobot/BDDbot, etc., into metrics stores (e.g., InSPIRE or equivalent).
• Build and support dashboards and reports (e.g., Power BI or similar) covering:
  • Execution metrics, coverage, and trends.
  • Package and variant health for CoSim/SILART.
• Standardize release documentation, including:
  • Markdown release notes for CoSim packages, wired into SOLE/portals.
  • High‑level “ what changed / what was tested / under whic