Job Description
Job Title: Windows Kernel Driver Engineer
\n
Location: Redmond, WA
\n
Onsite/ Remote: Day 1 Onsite at customer location
\n
\n
Windows Kernel Driver Engineer
\n
Best fit signals (look for these on resumes):
\n
Kernel mode driver work (WDM/KMDF), debugging, dumps, lab bring up
\n
Device interaction debugging (hardware/firmware/software boundary) , ACPI/Power
\n
Drivers + Windows services + telemetry instrumentation + AI diagnostics
\n
Diagnostics pipelines / “make it observable” mindset
\n
HLK/HCK experience, release validation, build/release coordination
\n
Proven habits around quality gates and automation
\n
Core: Windows drivers, kernel mode, user mode, system integration, telemetry, automation, debugging tools
\n
Delivery environment: HLK compliance, build/release coordination, troubleshooting
\n
Hardware edge: bring up, debug hardware/firmware/software interaction
\n
Programming: C/C++ (explicitly called out), plus tool ecosystems like Git (and common low-level debug ecosystems)
\n
\n
What This Engineer Will Do
\n
Develop, test, and sustain Windows kernel mode and user mode drivers and system services
\n
Debug complex hardware / firmware / OS interactions
\n
Drive quality, validation, and release readiness (HLK, LKG, PST)
\n
Add telemetry and diagnostics to enable fast, remote issue resolution
\n
Collaborate with hardware, firmware, IHVs, and internal Windows teams
\n
\n
Required Candidate Capabilities
\n
Professional experience with Windows drivers or system software
\n
Proven kernel debugging and dump analysis
\n
Experience supporting release quality or validation
\n
Comfortable working across hardware and firmware boundaries
\n
Strong collaboration and ownership mindset
\n
\n
Highly Desired Experience
\n
HLK / driver signing / release pipelines
\n
Telemetry, diagnostics, or automation tooling
\n
Secure driver or system design practices
\n
Device bring up or early hardware validation