Principle Software Engineering – Continuous Integration

Job Description
Vacancy Status:No: 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 roleHybrid
- This role is categorized as hybrid. This means the successful candidate is expected to report to Markham, ON three times per week, at minimum.
Specific job responsibilities include:The architect will:Establish the end-to-end CI/CD reference architecture for Platform Software delivery across component, pillar, system-of-systems, and release-train flows.
Define how independently delivered software components are built, versioned, validated, combined, promoted, and consumed by downstream teams and release processes.
Create a coherent quality-gating strategy that protects the core mainline and prevents known-bad software, invalid configurations, incompatible artifacts, and insufficient test evidence from advancing.
Connect developer workflows, GitHub Enterprise, cloud build infrastructure, artifact repositories, virtual and physical test environments, dashboards, and release systems into a traceable delivery path.
Advise senior engineering and program leadership on release risk, pipeline health, quality signal confidence, architectural tradeoffs, and investment priorities.
Lead cross-functional technical decisions when ownership spans multiple teams, organizations, suppliers, or software domains.
Key DeliverablesEnd-to-end delivery architectureArchitect the target-state flow for all software and non-code inputs required to produce a VeSCoM release, including embedded binaries, containers, MCU and SoC images, calibration, configuration, network and interface artifacts, and test assets.
Define clear entry and exit criteria for each stage of the delivery pipeline, from pull request and component build through integrated build, validation, release candidate, and VeSCoM publication.
Establish the relationship between pillar-level CI/CD pipelines and the system
- level integration pipeline, including dependency management, build composition, artifact promotion, and last-known-good baselines.
Define build-once, promote-many practices using immutable, traceablevartifacts and reproducible configurations wherever practical.
Design the pipeline to support multiple delivery cadences and release trains without allowing local team velocity to compromise system-level quality.
Identify manual handoffs, duplicated builds, late integration points, ambiguous ownership, and other sources of delivery delay or quality escape; replace them with standardized, automated controls.
Quality gates and mainline protectionDefine a tiered quality-gating model that applies the right test depth and quality evidence at the right point in the software flow.
Establish blocking gates for pull requests, component integration, cross
- component compatibility, system integration, release-candidate readiness, and VeSCoM promotion.
Ensure gates fail fast and provide actionable diagnostics, clear ownership, and a defined path to resolution or formally governed exception handling.
Develop policies for rejecting failing changes, preventing direct or unsafe mainline integration, re-queuing changes against the latest integrated state, and preserving a known-good baseline.
Define objective criteria for distinguishing product failures from infrastructure, environment, test-quality, and data-quality failures so that the pipeline does not produce misleading signals.
Establish guardrails for flaky tests, quarantined tests, waived results, incomplete execution, invalid manifests, missing artifacts, and test environments that are not representative of the target vehicle system.
Partner with BiQS, embedded software product teams, validation organizations, and the CI/CD platform team to translate quality principles into executable, measurable pipeline policy.
Embedded and vehicle-system integrationEvaluate how software components interact across ECUs, MCUs, SoCs, containers, vehicle services, communication networks, diagnostics, calibration, and configuration management.
Define integration checks for interface compatibility, version alignment, dependencies, resource budgets, boot and deployment behavior, communication health, and system configuration integrity.
Ensure the pipeline validates the interactions that matter at vehicle level—not only whether individual components compile or pass isolated tests.
Incorporate appropriate levels of unit, static, component, integration, simulation, CoSIM, SIL, HIL, bench, and system validation into the delivery strategy.
Establish the conditions under which test results are considered valid, including the required software baseline, model or vECU version, test manifest, hardware configuration, and environment health.
Drive earlier detection of cross-subsystem defects and compatibility issues before they reach late-stage vehicle integration or customer release activity.
GitHub En