Hardware Test Engineer (R&D Validation)

Keywords Studios•Fort Collins, CO

1d•$40•Onsite

About The Position

We’re looking for a Hardware Test Engineer to own test case development and execution for R&D products and proof-of-concept systems. You’ll help shape our lab infrastructure and test workflows, and you’ll partner closely with engineering teams to turn ambiguous requirements into clear, repeatable tests. Success in this role comes from technical curiosity, strong documentation habits, and comfort working across hardware, software, and embedded systems.

Requirements

Proven experience writing and executing hardware test cases independently
Strong hands-on experience using electronic lab equipment (scope, spectrum analyzer, electronic load, etc.)
Solid documentation skills: you can create clear procedures, test plans, and reports
Comfortable working in tools like TestRail, Jira, and Word/Docs
Ability to manage multiple priorities and still deliver on-time, high-quality results
Clear communication skills with technical teams and stakeholders
Comfortable using engineering math to set pass/fail limits and sanity-check results
Able to work in a dynamic R&D environment with evolving requirements and tight timelines
Scripting experience in Python, C++, or similar
Advanced mathematical skills for calculation of design equations
Background in optics, sensors, robotics, or advanced hardware systems
Experience with embedded triage (hardware/firmware/OS boundaries)

Nice To Haves

Experience with Linux and command-line environments
Experience modifying existing scripts/codebases and turning SOPs into repeatable tooling
Automation experience in Python, C++, or similar

Responsibilities

Start your day by checking the validation queue (new builds, incoming hardware, priority asks), then pick the highest-impact tests to run based on program needs and lab availability.
Translate engineering asks and ambiguous requirements into clear test cases: define setup, steps, pass/fail criteria, data to capture, and how results will be reported.
Set up benches and fixtures, verify calibration/readiness, and run subsystem and full-system tests while capturing measurements, logs, and observations.
Use lab tools (oscilloscope, spectrum analyzer, electronic load, etc.) to characterize behavior, validate performance, and isolate failure modes.
Document results the same day: update the test case with real-world notes, attach artifacts (photos, plots, logs), and summarize outcomes in a short, readable format.
When something fails, reproduce it, narrow the conditions, collect “good vs bad” comparisons, and walk engineers through what you’re seeing so the team can move quickly toward the root cause.
Keep the test repository clean and usable: maintain templates, naming conventions, versioning, and test coverage so others can run the same tests with consistent outcomes.
Create small improvements that make testing faster and more repeatable: simple scripts, data capture helpers, automation hooks, or fixture tweaks that reduce manual effort.
Participate in regular syncs with hardware/firmware/software teams to align on upcoming changes, risks, and what needs validation before the next milestone.
Help keep the lab running smoothly: track shared resources, note equipment issues early, and maintain safe, organized workspaces so testing doesn’t get blocked.