ZipRecruiter

Log In

1

Temporary Windows Device Driver Jobs (NOW HIRING)

Nwis

Windows Kernel Developer

Sterling, VA

Nightwing is seeking experienced Windows Kernel Developers to support the design, development ... Strong understanding of operating system architecture and device drivers * Experience with system ...

Nightwing

Windows Kernel Developer

Sterling, VA · On-site

Nightwing is seeking experienced Windows Kernel Developers to support the design, development ... Strong understanding of operating system architecture and device drivers * Experience with system ...

AgreeYa Solutions

.Net Developer

Franklin, TN

$47.75 - $63/hr

Resolve deep-seated technical issues related to Windows OS stability, driver conflicts, and device connectivity in a dealership environment. Data Management: Maintain the back-end SQL databases and ...

Sumeru Solutions

Android Engineer

Santa Clara, CA

... device drivers, camera drivers, camera framework, imaging or camera apps Optimization of algorithms on real systems Experience with Linux, Windows Familiar as a developer with Linux, MacOSX, and ...

next page

Showing results 1-20

All JobsTemporary Windows Device Driver Jobs

Temporary Windows Device Driver information

What are the key skills and qualifications needed to thrive as a Temporary Windows Device Driver Developer, and why are they important?

To thrive as a Temporary Windows Device Driver Developer, you need strong experience in C/C++ programming, knowledge of Windows kernel architecture, and a background in computer engineering or a related field. Familiarity with Windows Driver Kit (WDK), Visual Studio, and debugging tools like WinDbg is typically required, along with relevant Microsoft certifications being advantageous. Excellent problem-solving abilities, attention to detail, and effective communication skills help you collaborate with teams and address complex technical issues. These skills ensure the development of reliable, efficient drivers that maintain system stability and meet project timelines.

What are some common challenges faced by Temporary Windows Device Driver developers, and how can they prepare for them?

Temporary Windows Device Driver developers often face tight deadlines and the need to quickly adapt to unfamiliar hardware or software environments. Since these roles are typically project-based, you may have limited time to learn about proprietary systems or integrate with legacy code. To succeed, it's important to have strong problem-solving skills, be comfortable with Windows kernel-mode programming, and maintain clear communication with hardware teams and QA engineers. Staying up-to-date on the latest Windows Driver Kit (WDK) updates and best practices can also help you hit the ground running.

What does a Temporary Windows Device Driver do?

A Temporary Windows Device Driver is a professional who develops or maintains drivers—software that allows Windows operating systems to communicate with hardware devices—on a temporary or contract basis. Their main responsibilities include writing, testing, debugging, and updating device driver code to ensure hardware compatibility and performance. They often work for companies needing short-term expertise for product launches, hardware updates, or troubleshooting specific device issues. These specialists may also help with documentation and support during the integration of new hardware components.

What is the difference between Temporary Windows Device Driver vs Windows Driver Developer?

AspectTemporary Windows Device DriverWindows Driver Developer
CredentialsBasic knowledge of Windows drivers, possibly no formal certificationAdvanced certifications like Microsoft Certified: Windows Driver Development
Work EnvironmentShort-term projects, testing, or troubleshooting in IT or hardware labsLong-term development, design, and maintenance in software or hardware companies
Employer & IndustryIT departments, hardware manufacturers, testing labsSoftware companies, hardware vendors, tech firms

The main difference is that a Temporary Windows Device Driver is typically a short-term, task-specific role focused on testing or troubleshooting, while a Windows Driver Developer is a more experienced professional involved in designing and maintaining drivers long-term.

What cities are hiring for Temporary Windows Device Driver jobs? Cities with the most Temporary Windows Device Driver job openings:
What are the most commonly searched types of Windows Device Driver jobs? The most popular types of Windows Device Driver jobs are:
What states have the most Temporary Windows Device Driver jobs? States with the most job openings for Temporary Windows Device Driver jobs include:
Temporary Windows Device Driver jobs near you
Windows Driver Validation Engineer

Windows Driver Validation Engineer

Sustainable Talent

Santa Clara, CA

$50 - $80/hr

Full-time, Contractor

PTO

Posted 11 days ago

Job description

Sustainable Talent is partnering with Nvidia a global leader who's been transforming computer graphics, PC gaming, and accelerated computing for over 25 years. We are looking for a Windows Driver Validation Engineer to support our client's team onsite in Santa Clara, CA.

This is a full-time (W-2) 6 month contract role. We offer competitive pay $50/hr - $80/hr based on factors like experience, education, location, etc. and provide full benefits, PTO, and amazing company culture!

In this role you will be responsible for test and analysis of issues across internal and OEM Windows platform configurations. The role ensures CI/CD quality, Windows driver compliance, OEM readiness (HLK/WHQL where applicable), and release readiness across system-level builds.

Key Responsibilities:

• Device Setup & Configuration: Flash Windows OS builds onto boards and OEM devices; install and validate SoC, GPU, USB, display, and platform drivers; configure Windows debugging tools (e.g., WinDbg/KDNET); enable and collect crash dumps and system logs.

• Perform Windows system-level and driver-level validation across functional, stress, power management (Modern Standby, S3/S4), and performance scenarios.

• Investigate Windows system crashes (e.g., BSOD), analyze memory dumps and Windows event logs, and support root cause analysis in collaboration with driver and platform teams.

• Develop and execute automated and manual test plans across internal and OEM Windows configurations, validating multiple driver and software build versions.

• Conduct exploratory testing to identify subsystem-level issues (USB, display, PCIe, power management, etc.).

• Triage internal and OEM defects; reproduce failures, collect logs and crash dumps, document findings, and track issue resolution through release readiness.

• Work closely with BSP, driver, OEM QA, and automation teams to ensure CI/CD build stability, validation coverage, and certification readiness (HLK/WHQL where applicable).

• Prepare detailed test execution reports and communicate validation results to internal and external stakeholders.

Skillset:

• 5–8 years of Windows system-level or driver-level testing experience (application-level QA experience alone is not sufficient).

• Hands-on experience with Windows platform validation, driver installation, and driver debugging.

• Proficiency using Windows debugging tools such as WinDbg or KDNET; experience analyzing crash dumps, memory dumps, and Windows event logs.

• Strong understanding of Windows power management, including Modern Standby, ACPI, and S3/S4 sleep states.

• Experience configuring UEFI/BIOS settings and flashing Windows OS builds onto hardware platforms.

• Demonstrated experience in defect triage, log analysis, reproduction of issues, and root cause support.

• Experience working with CI/CD pipelines supporting Windows builds and regression validation.

• Familiarity with Windows Driver Kit (WDK), HLK/WHQL certification processes, or OEM device validation is strongly preferred.

• Experience validating USB4, DisplayPort (DP) tunneling, PCIe, or platform drivers is a plus.

Sustainable Talent is a M/F+, disabled, and veteran equal employment opportunity and affirmative action employer.

Apply