Senior Software Engineer

Onto Innovation is a leader in process control, combining global scale with an expanded portfolio of leading-edge technologies that include: 3D metrology spanning the chip from nanometer-scale transistors to micron-level die-interconnects; macro defect inspection of wafers and packages; metal interconnect composition; factory analytics; and lithography for advanced semiconductor packaging. Our breadth of offerings across the entire semiconductor value chain helps our customers solve their most difficult yield, device performance, quality, and reliability issues. Onto Innovation strives to optimize customers’ critical path of progress by making them smarter, faster and more efficient.

Job Summary & Responsibilities

Role Summary

If you like the idea of being the person who owns the GitHub platform for a large, modern Windows product organization, designing the runners, container images, workflows, and release plumbing that everyone else builds on, this role is for you. You will be joining a sharp, tight-knit engineering organization that shares knowledge generously, challenges each other in good faith, and has a lot of fun solving hard problems together. The role fills a specific gap in our coverage: the person who takes it will both lean on the team and make the team better.

The portfolio is primarily C# on .NET (the range from .NET Framework 4.8 through .NET 9, plus .NET Standard 2.0 shared libraries) and significant C++ on Windows, all in git on GitHub Enterprise. You own the GitHub side of the platform (runners, container images, Actions workflows, signing, release plumbing) so product teams can build, test, sign, package, and ship cleanly. Teams own the contents of their builds; you own that the path exists, is fast, and works.

This is a Copilot-augmented role, focused on cloud GitHub Copilot on GitHub itself (PR review and summarization, Copilot in Actions, custom Copilot skills and agents). IDE Copilot in Visual Studio and VS Code is what product teams use; you enable and govern it. Conceptual depth beats tenure with any single toolchain: you should understand why an approach is correct and recognize when a Copilot, Stack Overflow, or vendor answer is wrong.

Responsibilities

Platform: build, test, sign, and ship

• Design and maintain shared GitHub Actions CI/CD (reusable workflows, composite actions, matrix builds) that product teams compose into their own pipelines, with first-class C# / MSBuild / .NET and C++ / vcpkg / CMake build paths.

• Own the NuGet story end-to-end: internal feed, large internal package artifacts, versioning, retention, and CI restore performance.

• Design and operate the runner fleet: cloud-hosted Windows-first (plus Linux) VMs running containerized CI/CD jobs from custom images (Packer / Azure Image Builder), including a GPU-passthrough image. Pick the right orchestrator for the workload, keep toolchains pinned and reproducible, and own the operational details (driver / CUDA pinning, runner registration, ephemeral vs warm pools).

• Own packaging, signing, and release plumbing: WiX (v4 / v5+) MSI templates, NuGet packaging, Authenticode signing (HSM / cloud signing), SemVer / changelog automation, install / upgrade scaffolding.

• Provide the test integration surface in CI (VSTest / MSTest / NUnit / xUnit for .NET, plus the C++ test frameworks in use, including hardware-in-the-loop where applicable).

• Build automation and observability tooling (Python, PowerShell, Bash) and manage the runner and image fleet as infrastructure as code so it is reproducible, reviewable, and auditable. Tool choice is open; propose the right one when the need is real.

Security and operations

• Drive supply-chain security: signed commits, Authenticode for Windows binaries (Sigstore / cosign for containers), SBOMs, Dependabot / CodeQL / Trivy, OIDC to cloud, and secret / cert lifecycle.

• Operate the platform as a product: SLOs (pipeline success, queue time, build duration), disaster recovery for runners / registry / NuGet feed / secrets / IaC state, and audit evidence.

• Hold an on-call rotation, lead blameless post-mortems, track DORA metrics, and eliminate CI/CD bottlenecks.

Partnership with engineering

• Act as the in-house GitHub subject-matter expert and first responder for broken pipelines. Triage in a blameless way: separa