Position summary
You own hands-on hardware testing for Neybo, across every stage of the device's life: from a bare board on the bench running the day's firmware build, to units closer to a production sample.
You run the full test cycle on every new firmware build: functional tests, regression checks against previously working features, and hardware benchmarks such as thermal behavior under load, memory use and throughput benchmarks, and Wi-Fi stability across frequencies and channels. When something breaks, you localize whether the cause sits in hardware or firmware before handing it to the right team.
Key responsibilities
Testing on every build
- Run the full functional test suite on every new firmware build, checking that previously working features still hold after a new feature or patch
- Test the device across every hardware version, from a bare board running the team's daily build to units closer to a production sample
- Move testing onto real vendor dev boards once they arrive, running full functional and regression cycles as the application layer gets integrated into a unified firmware image
Benchmarks and diagnostics
- Run hardware benchmarks on each build: CPU performance vs thermal stability and throttling, memory use and throughput benchmarks under various synthetic and app loads, and Wi-Fi stability across frequencies and channels
- Localize each defect to hardware or firmware before handing it to the right team
- Test hardware codec performance across different application scenarios
- Test and validate speech interaction scenarios involving wake-word, voice quality enhancement algorithms and speech recognition running in parallel with other applications
- Record results from every test run in a structured, repeatable format
Hands-on experience
- Reflash boards and physically operate test equipment as part of the daily testing cycle
- Use hardware debug tools (UART, ADB) and protocols (SSH, Telnet, TFTP)
- Keep pace with the firmware team's release cadence, so every new build gets validated quickly
- Analyze running Linux processes and identify the most CPU- and memory-intensive ones under various conditions
Required qualifications
- 2-3+ years of hands-on hardware QA or embedded device testing experience
- Hardware testing experience directly on physical boards and finished devices across build iterations
- Regression testing experience on firmware running on real hardware
- Working knowledge of hardware benchmarks: CPU performance vs thermal stability and throttling, memory use and throughput under synthetic and app loads, Wi-Fi stability across frequencies and channels
- Comfortable with a repeating, hands-on cycle of reflashing boards and working directly with hardware
- Experience working with headless Linux interfaces (CLI: terminal, tmux)
- Familiarity with system benchmarking tools: top, htop, tinymembench, etc.
- Basic measurement/diagnostics equipment skills: multimeter, oscilloscope, thermal camera, bench power supply
- Experience with a serial console or JTAG for pulling device logs and debug output
- English B2+, written and spoken
Preferred qualifications
- Experience writing structured defect reports: reproduction steps, environment, expected and actual result
- Basic electronics knowledge for localizing issues at the hardware/firmware boundary
- Experience testing voice-interface or similar consumer IoT devices
Technology stack
- Multimeter, oscilloscope, and other bench measurement equipment
- Serial console, JTAG, SSH, U-Boot console for device logs and debug output
- Vendor dev boards and production sample hardware
Success metrics
- Every new firmware build gets a full functional and regression pass before it moves to the next stage
- Hardware benchmarks (CPU vs thermal throttling, memory throughput, Wi-Fi stability) tracked and reported on each build
- Structured test reports and logs showing development progress and open issues to the HW/FW team
- Defects localized to hardware or firmware accurately before handoff