System Integration & Test Engineer
About RX360
RX360 is an early-stage startup building a connected wearable for senior care: a device with safety-critical features (SOS, fall detection, medication reminders) and biometric sensing, paired with a companion app and pharmacy integration. We're iterating fast through dev, proto, and scale builds across US and China manufacturing partners, on a path from tens of units to tens of thousands.
The role
Founding engineer in our Product Integration & Test function. You'll own two areas that usually belong to two people — and that's the point: - -
System integration test: proving hardware, firmware, and app work as one product — on dev boards during bring-up, and end-to-end on sealed units over BLE.
Manufacturing test: proving we can build it repeatably — owning the factory test stations (PCBA test, pre-seal assembly test, final test) through proto builds and into volume.
You don't need to be a deep specialist in either; you need real hands-on experience in both and the judgment to know when a failure is a design problem, a firmware problem, or a line problem.
What you'll do - - - - -
Define and run integration test cycles for each build: pass/fail criteria tiered by what actually blocks (P0 gates vs. record-only), covering connectivity, safety flows, sensors, display, audio, haptics, power/charging, and OTA.
Support dev-board and first-article bring-up alongside EE and firmware — flashing, debug (SWD/J-Link), logging, isolating cross-domain bugs to a named owner.
Own the factory test stations end-to-end: station definitions, limits, fixtures, and the factory test firmware/software plan; establish golden units and tune limits against them.
Run test dry-runs before builds, support builds on-site (US SMT and China FATP), analyze per-station yield, and feed failures back into design.
Own system-level acceptance on finished units — pairing, dock charging, guided functional checks, soak tests — and the final flash/verify/pack flow before units ship.
Build automation where it pays off (Python/pytest, CI) and run disciplined manual test where it doesn't; coordinate with external QA/lab partners as we scale.
What we're looking for - - - - - -
5–10 years in hardware/software product development with hands-on time in both system integration testing and factory/NPI test — you've debugged a bug at the
HW–FW–app boundary and stood at a line watching your test station run.
Shipped at least one connected hardware product through proto/EVT-style builds.
Comfortable at the bench: schematics, debuggers, logic analyzers, flashing embedded devices.
Python (or similar) for test automation and yield/data analysis.
Practical grasp of manufacturing test: gate vs. record-only trade-offs, limits and guard-banding, golden units, fixtures, yield Pareto.
Clear written test plans and readouts; startup temperament — you create structure where none exists and are comfortable being the only person in your discipline.
Nice to have - - -
Wearables or other small battery-powered BLE devices; Nordic nRF / Zephyr.
Display, audio, haptics, or optical sensor (PPG) test experience.
Working directly with CMs and SMT houses; willingness to travel for builds (Mandarin a plus).
Why this role
You'll define the function, not fill a seat — the benches, stations, and quality bar for a product that keeps seniors safe will be yours to build, and the team grows around what you set up.
