Specialist QA, Hardware & Payments

United States·Atlantamid

Other

1 views0 saves0 applied

Apply Now

Quick Summary

Requirements Summary

defines what the lab must hold to cover supported customer setups, and partners with the hardware owner on procurement. Hardware performance: measures startup time, responsiveness, memory and CPU use,

Technical Tools

Other

At Qu you’ll find a fun, dynamic, and diverse culture that celebrates team and individual success. Our people are down to earth, trail blazin’ folks who value innovation.

While mostly virtual, we collaborate closely to produce leading-edge software solutions much needed in the restaurant industry.

Qu's restaurant software runs on physical hardware: POS terminals, payment devices, kitchen displays, kiosks and their peripherals. This role is the hands-on owner of quality for that layer, starting with payment devices and payment integrations. The person builds and runs the end-to-end hardware lab, certifies devices and OS versions before customers get them, and tests payment flows on real terminals.

Success at six months looks like this:

A current certified-hardware list that product, support and sales can rely on.
Payment device regression runs on real terminals every release.
Device and payment issues found in the lab before release, not in customer stores.

E2E hardware setup: builds and maintains lab setups that mirror a customer store: POS terminals, payment devices, KDS, kiosks, printers, cash drawers, scanners and store network.
Hardware and OS certification: certifies new device models, firmware and OS versions (Windows and Android) against Qu product requirements, and keeps the certified-hardware list current.
Lab definition: defines what the lab must hold to cover supported customer setups, and partners with the hardware owner on procurement.
Hardware performance: measures startup time, responsiveness, memory and CPU use, peripheral reliability and long-run stability, and tests behavior on weak or lost networks.
Payments integration testing: tests card-present flows on real terminals (chip, contactless, magstripe, PIN, tips, voids, refunds, offline payments) across gateway and processor integrations.
Certification and field issues: runs test scripts for payment processor and EMV certifications, and reproduces device and payment issues reported from stores.
Quality practice: writes and maintains device test cases, automates repeatable checks where it pays off, and works in Qu's AI-first delivery workflow, where AI agents support test design, code review and automation.

Requirements

~1 min read

Industry experience here means payment and POS-class hardware, not restaurant POS only. This keeps the real must-have and widens the pool in both target cities.

5+ years in QA or QE, with at least 3 years hands-on with physical devices: POS terminals, payment terminals, kiosks, or retail and hospitality hardware.
Hands-on payment device testing: card-present flows on real terminals (chip, contactless, magstripe, PIN) in integrated or semi-integrated setups.
Device or OS certification: has certified devices, firmware or OS versions against a requirement set and kept a supported-hardware list.
Lab setup and troubleshooting: device provisioning, peripherals, and store networking basics (Wi-Fi, Ethernet, IP setup, network throttling).
Windows and Android device skills: reads device and app logs (for example adb logcat, Windows Event Viewer) to separate hardware causes from software causes.
Clear written English: precise bug reports, repro steps and test evidence for engineers and external partners.
Able to work on-site in Atlanta or DC for regular lab work.

These help, but a strong candidate without them stays in the process. The interview panel should screen on the must-haves only.

Restaurant or hospitality POS experience.
EMV Level 3 or payment processor certification experience; working knowledge of PCI DSS, P2PE and PCI PTS.
Experience with terminal families such as Verifone, Ingenico or PAX, and with payment gateways.
Test automation for devices or kiosks (for example Appium or Playwright), plus scripting in Python, C# or similar.
Device performance tools (Android Studio Profiler, Windows Performance Monitor) and MDM tools for managing device fleets.
Uses AI tools to design tests, analyze logs or speed up test creation.
Works well with distributed teams across time zones; most of Qu's QA team is in Buenos Aires.