- ZENITH INFOTEK LLC
- Full-Time
- 82 days ago
Windows Firmware Engineer.
Before you go
Before you leave us, sign up for our email alerts
We don't do job spam, just the best digital jobs delivered straight to your inbox.
Windows Firmware Engineer: our view in 3 lines...
- The Role:This role is for an experienced engineer focused on validation for Windows OS images, firmware, drivers, and related device systems.
- The Person:The person will design and execute validation, build automation frameworks and test scripts, integrate automation into CI/CD pipelines and lab workflows, and carry out test execution, debugging, and failure analysis.
- Requirements:The ideal candidate has 5 to 10 years of experience in Validation, Firmware, Tester, or Engineer work, plus Python, Azure DevOps, Windows OS architecture, software testing, automation, and debugging.
About the role
Benefits:
- Dental insurance
- Training & development
- Vision insurance
Role – Windows Firmware EngineerÂ
Â
Location – Redmond, WA (5 Days Onsite)
Â
Â
Responsibilities
 Design and execute validation for OS images, firmware, and drivers.
 Develop and maintain automation frameworks and test scripts (Python preferred).
 Integrate automation into CI/CD pipelines (Azure DevOps) and lab workflows.
Perform test execution (black box / grey box), debugging, and failure analysis.
Create and maintain test plans, test cases, and validation documentation.
Collaborate with cross-functional teams (HW, FW, SW, DV, PM) to ensure product quality.
 Qualifications
5 to 10 years of experience in Validation / Firmware / Tester / Engineer
 Strong understanding of Windows OS architecture and device validation.
 Experience in software testing, automation, and debugging.
 Bachelor's degree in Computer Science / Engineering (or equivalent).
 Strong communication skills.
 Preferred Experience
Experience with Xbox / gaming platform validation.
 Firmware, driver, and OS validation.
 Automation tool and framework development.
 Hardware bring-up, debugging, and failure analysis.
 Experience with touch or device subsystems.
Â

