QA Software Engineer, Consumer Products

In this role, you will:

• Test infrastructure & frameworks: Design, implement, and maintain a unified test framework for device software (unit, integration, system/end-to-end), with adapters for GitHub/Linear/Slack and reproducible runs.
• CI/CD integration & releases: Integrate test suites with Buildkite, enforce promotion criteria (staging/prod), auto-file regressions, and publish traceable artifacts and release notes.
• Hardware-in-the-loop lab design & orchestration: Plan and bring up racks, power/networking, and orchestration for device testing; support automated flashing, provisioning, and telemetry capture.
• Automation tooling: Develop tools for API/firmware validation, result triage, log capture, and replayable bug reports.
• Quality signals, metrics, and flake control: Stand up dashboards and alerts for pass rates, stability, and release readiness; detect and quarantine flaky tests; drive root-cause analysis with owners; and track DORA-style delivery metrics to guard release health.
• Vendor enablement: Write clear procedures for QA vendor technicians, review their reports, and maintain a queue of rig maintenance/repairs.
• Cross-team collaboration: Partner with embedded/system software teams on testability and with release infrastructure engineers on pipelines, signing, rollouts, and rollback/forward strategies.

You might thrive in this role if you:

• Have deep experience in software quality/test engineering for hardware products shipped at scale, with a strong automation focus.
• Are proficient in Python, C, C++, or Rust, and have solid Linux fundamentals (processes, networking, storage, udev/systemd).
• Have experience building CI/CD pipelines, artifact management, and environment isolation.
• Have demonstrated success designing and operating hardware-in-the-loop labs and device orchestration at scale.
• Are fluent with test reliability techniques such as failure triage, flake detection/quarantine, and signal quality guardrails.
• (Nice to have) Experience with device-lab frameworks (e.g., LAVA, OpenHTF) and results pipelines (dashboards/alerting).
• (Nice to have) Knowledge of release-readiness safeguards: staged rollouts, rollback plans, and signed firmware/software artifacts in CI/CD.