What you will own
The HPP software architecture, platform roadmap, and engineering standards: reuse boundaries, service and library strategy, and the design rules product teams build on.
System design for a long-lifecycle instrument host: hardware–software integration, device communication, driver contracts, diagnostics, serviceability, and recovery.
The platform lifecycle: image customization, factory provisioning, build and CI, installer and field update, rollback, and long-term servicing.
Security and compliance readiness for a connected instrument: OS hardening, vulnerability remediation, third-party component governance, SBOM, and a secure software development lifecycle.
Technical leadership across hardware, firmware, QA, security, manufacturing, service, and product teams, including mentoring engineers and growing the platform capability of the organization.
Qualifications
Bachelor’s or Master’s degree in Computer Engineering, Electrical Engineering, Electronics Engineering, Computer Science, or a related discipline.
Typically 10 or more years in embedded software, firmware, or system-level software, including several years owning architecture or technical direction for a shipped product.
Strong C/C++ and object-oriented design, including multi-threaded, high-performance software with explicit resource, latency, and reliability constraints.
Proven ownership of a complex embedded platform on Windows or Linux: software architecture, design patterns, performance, reliability, update and recovery, and cybersecurity. Either path meets this bar:
Windows. Windows 10/11 IoT Enterprise, or another long-lifecycle Windows embedded product: services, user-mode and kernel-mode boundaries, image customization, installer and servicing, recovery, and system debugging.
Linux. Embedded Linux platform ownership (Yocto, Buildroot, or a custom BSP): kernel and device-driver integration, system services, image build, boot chain, and field update with rollback. You will ramp on Windows system architecture, the Windows image and servicing model, and the team’s toolchain.
Working knowledge of board-level interfaces such as I2C, UART, SPI, USB, PCIe, Ethernet, and TCP/IP, and of the storage the platform depends on (NOR, NAND, eMMC, SD, EEPROM, or an equivalent managed device).
Secure-development practice for products that stay in the field for years: vulnerability handling, third-party component control, SBOM generation, and security updates over the support life. Familiarity with expectations such as the EU Cyber Resilience Act or IEC 62443 is an advantage.
A record of setting technical direction, writing decisions down, and aligning hardware, firmware, security, and product stakeholders around a multi-year architecture.
You will work in
Windows 10/11 IoT Enterprise, including LTSC, and the installed base of long-lifecycle Windows images those products already ship.
Visual Studio and a scripted build and release pipeline (MSBuild, CMake, or both), with automated test and image or installer promotion.
Windows diagnostics: WinDbg, ETW, Windows Performance Analyzer, crash-dump analysis, and driver verification. Equivalent depth with Linux tracing, perf, and crash analysis is a valid starting point on the Linux path.
Strong advantage
Architecture decisions you wrote down and carried across hardware, firmware, security, and product teams, covering performance, reliability, security, or long-term servicing.
A reuse standard other instrument teams build on: common services, libraries, or platform configuration held stable across products and board revisions.
Secure boot or verified boot, measured boot, or an equivalent trust chain, and a recovery design that survives a failed update.
Modern C++ and a hardware-abstraction or service boundary that lets product teams move across board revisions without rewriting the host stack.
Diagnostics and serviceability built into the platform: structured logging, crash capture, health reporting, and a recovery path that manufacturing and service can run.
Careers Privacy Statement***Keysight is an Equal Opportunity Employer.***
Keysight is hiring an Embedded Software Architect to own the host-processor software platform used in our Windows-based test and measurement instruments. You will set the architecture, the platform roadmap, and the technical standards for Host Processor Platform (HPP) products: how the instrument boots, how software is built and updated, how the host talks to hardware, and how the platform stays secure and serviceable across a long product life.
This is a platform role. The operating system you will ship is Windows, including long-lifecycle IoT Enterprise images. Architects who have owned that kind of platform on embedded Linux are encouraged to apply. We hire for system architecture, and we expect Linux platform owners to become proficient on the Windows stack.
What you will own
The HPP software architecture, platform roadmap, and engineering standards: reuse boundaries, service and library strategy, and the design rules product teams build on.
System design for a long-lifecycle instrument host: hardware–software integration, device communication, driver contracts, diagnostics, serviceability, and recovery.
The platform lifecycle: image customization, factory provisioning, build and CI, installer and field update, rollback, and long-term servicing.
Security and compliance readiness for a connected instrument: OS hardening, vulnerability remediation, third-party component governance, SBOM, and a secure software development lifecycle.
Technical leadership across hardware, firmware, QA, security, manufacturing, service, and product teams, including mentoring engineers and growing the platform capability of the organization.
Bachelor’s or Master’s degree in Computer Engineering, Electrical Engineering, Electronics Engineering, Computer Science, or a related discipline.
Typically 10 or more years in embedded software, firmware, or system-level software, including several years owning architecture or technical direction for a shipped product.
Strong C/C++ and object-oriented design, including multi-threaded, high-performance software with explicit resource, latency, and reliability constraints.
Proven ownership of a complex embedded platform on Windows or Linux: software architecture, design patterns, performance, reliability, update and recovery, and cybersecurity. Either path meets this bar:
Windows. Windows 10/11 IoT Enterprise, or another long-lifecycle Windows embedded product: services, user-mode and kernel-mode boundaries, image customization, installer and servicing, recovery, and system debugging.
Linux. Embedded Linux platform ownership (Yocto, Buildroot, or a custom BSP): kernel and device-driver integration, system services, image build, boot chain, and field update with rollback. You will ramp on Windows system architecture, the Windows image and servicing model, and the team’s toolchain.
Working knowledge of board-level interfaces such as I2C, UART, SPI, USB, PCIe, Ethernet, and TCP/IP, and of the storage the platform depends on (NOR, NAND, eMMC, SD, EEPROM, or an equivalent managed device).
Secure-development practice for products that stay in the field for years: vulnerability handling, third-party component control, SBOM generation, and security updates over the support life. Familiarity with expectations such as the EU Cyber Resilience Act or IEC 62443 is an advantage.
A record of setting technical direction, writing decisions down, and aligning hardware, firmware, security, and product stakeholders around a multi-year architecture.
You will work in
Windows 10/11 IoT Enterprise, including LTSC, and the installed base of long-lifecycle Windows images those products already ship.
Visual Studio and a scripted build and release pipeline (MSBuild, CMake, or both), with automated test and image or installer promotion.
Windows diagnostics: WinDbg, ETW, Windows Performance Analyzer, crash-dump analysis, and driver verification. Equivalent depth with Linux tracing, perf, and crash analysis is a valid starting point on the Linux path.
Strong advantage
Architecture decisions you wrote down and carried across hardware, firmware, security, and product teams, covering performance, reliability, security, or long-term servicing.
A reuse standard other instrument teams build on: common services, libraries, or platform configuration held stable across products and board revisions.
Secure boot or verified boot, measured boot, or an equivalent trust chain, and a recovery design that survives a failed update.
Modern C++ and a hardware-abstraction or service boundary that lets product teams move across board revisions without rewriting the host stack.
Diagnostics and serviceability built into the platform: structured logging, crash capture, health reporting, and a recovery path that manufacturing and service can run.
Careers Privacy Statement***Keysight is an Equal Opportunity Employer.***
