Senior QA Engineer – Embedded / Bluetooth / Smart Wearables

Role Summary

We are seeking a hands-on Embedded QA Engineer for Amazon Smart Wearables who can independently diagnose and root‑cause complex device issues from Day 1 .

This role is not limited to test execution . The ideal candidate will demonstrate strong protocol‑level understanding (Bluetooth), deep log analysis expertise, Unix/Linux command‑line fluency, and scripting fundamentals to investigate failures across firmware, OS, connectivity, and cloud interactions .

This is a high‑ownership, onsite role supporting monthly releases, lab operations, and field testing for production wearable devices.

Mandatory Technical Requirements (NON‑NEGOTIABLE)

Embedded / Wearable Testing

• 3–7+ years of hands‑on QA experience in Embedded Systems, Smart Devices, Wearables, or IoT

• Experience testing shipping consumer hardware , not just POCs or simulators

• Strong understanding of hardware–software interaction , firmware behavior, and device states

Bluetooth & Connectivity (CRITICAL)

Candidates must demonstrate real Bluetooth troubleshooting experience , including:

• Hands‑on testing of Bluetooth Classic & BLE

• Working knowledge of Bluetooth profiles such as:

◦ A2DP

◦ HFP

◦ SPP

◦ GATT / BLE services

• Ability to debug:

◦ Pairing & reconnection failures

◦ Audio handoff issues

◦ State machine breakages

◦ Multi‑device interaction failures

❌ Candidates who only toggle Bluetooth, swap devices, or rely on retries will not qualify

​

Debugging, Logs & Root Cause Analysis (KEY DIFFERENTIATOR)

• Strong experience with log collection and deep analysis , including:

◦ Android logcat

◦ Firmware / system logs

◦ Bluetooth stack logs

◦ Crash traces and dumps

• Ability to trace failures across components (device ↔ OS ↔ protocol ↔ cloud)

• Demonstrated capability to:

◦ Isolate root cause

◦ Explain why a failure occurred

◦ Provide actionable inputs to developers

Candidates must show a systematic debugging methodology , not surface‑level observation

​

Operating Systems & Command Line

• Hands‑on experience with Unix/Linux terminals

• Comfortable using:

◦ grep, awk, sed, tail, diff

◦ adb shell commands

◦ Log filtering & correlation

• Ability to analyze issues without relying on GUI tools

Automation & Scripting (FOUNDATIONAL EXPECTATION)

• Working knowledge of Python or Java

• Ability to:

◦ Write basic scripts for log parsing, test utilities, or validation

◦ Modify or debug automation code if required

• Understanding of where automation fits in embedded/device testing

❌ Candidates with no coding exposure or no learning progression will not qualify

​

QA Process & Tools

• Strong understanding of:

◦ SDLC / STLC

◦ Test strategy, planning, coverage analysis

◦ Defect lifecycle & triage

• Tools:

◦ JIRA – defect tracking, sprint coordination

◦ TestRail – test case management

• Experience working in Agile / CI‑driven environments

Roles & Responsibilities

• Own feature‑level and system‑level validation for device releases

• Develop and execute structured test plans and test cases

• Perform:

◦ Regression testing

◦ Long‑running & stress testing

◦ Field testing and failure reproduction

• Investigate field‑reported customer issues by reproducing them in lab environments

• Analyze logs, isolate root cause, and drive closure with Amazon developers

• Collaborate daily with Amazon engineering teams (US‑based)

• Provide LabOps and onsite lab support

• Ensure repeatable, auditable testing methodologies

• Identify and contribute to future automation opportunities

• Support monthly release cycles for the duration of the engagement

• Work onsite daily at Amazon client location

Strongly Preferred

• Prior experience with:

◦ Amazon devices

◦ Google / Meta / Apple consumer electronics

• Experience testing:

◦ Wearables, audio devices, earbuds, smart glasses

• OTA update validation

• CI/CD test integration exposure

Ideal Candidate Profile (Quick Filter)

✅ Can debug Bluetooth failures beyond pairing issues

✅ Comfortable parsing logs independently

✅ Uses Unix terminal naturally

✅ Has written scripts (even basic)

✅ Understands system‑level failures, not just test steps

✅ Operates with ownership, not execution‑only mindset