Relocation opportunity to Lisbon, Portugal.
We are at Neera on a mission to restore human recovery by turning neuroscience and acoustics into everyday wellbeing. We empower people to sleep deeply, regulate stress effortlessly, and live with calm, clarity, and energy.
Neera is a complex hardware-software platform that includes multiple hardware units; including a “brain” unit, sensing and actuation modules, as well as a mobile app and backend infrastructure.
With the USA as our primary market, we move fast, operate lean, and aim to build a globally iconic brand.
As a Senior SDET, Hardware/Software Systems, you will own end-to-end testing for Neera’s hardware-software platform.
You will be expected to use modern AI coding assistants as a core part of your workflow, accelerating test script generation, building and maintaining automation frameworks, improving test coverage, and helping the product development team move faster without compromising quality.
You will be responsible for protecting the integrity of the entire platform. You will design, build, and maintain automated test infrastructure (and manual where appropriate) to ensure that our hardware, firmware, mobile software, and cloud architecture work seamlessly together.
Days 1-30: Orient & Audit
Your goal is to understand the Neera ecosystem top-to-bottom and baseline our current draft test coverage / approach
Deep-dive onboarding: spend structured time with the manufacturing, hardware, firmware, mobile and cloud teams to map the full system topology (from sensor nodes through processing unit up to the cloud APIs), and - get to know the device, of course.
Severity & Priority Definition: create and formalize a cross-team defect severity matrix (S0-S4). You must define clear criteria tailored to Neera’s hardware/software ecosystem - explicitly distinguishing between critical safety/etc. risks (e.g., S0: hardware thermal cutoff failure), core functional blockers and minor UI/UX bugs.
Define the Toolchain: propose and agree with the engineering team on the definitive testing languages, automation frameworks and CI/CD integration points we will use moving forward.
Multi-Layer Coverage Audit: Audit the current test suites and identify gaps across all critical coverage dimensions, such as:
Unit coverage: isolated firmware functions for each of the modules, cloud microservices, etc.
Functional coverage: mobile app UI, BLE pairing, session start/stop, etc.
Integration coverage: hub-to-haptics routing, cloud-to-hub provisioning, API handshakes, etc.
Health-related & safety coverage: hardware thermal thresholds, acoustic output limits and EMF mitigation checks.
(Bonus point) Regulatory & Compliance Coverage: readiness for UL 62368-1, FCC Part 15, CPSC, etc. standards.
Assess existing infrastructure: start running the first tests from the test suite end-to-end. Start identifying and document any broken, flaky or missing tests. (tip: Use your preferred vibe-coding / etc. tools to rapidly parse and document legacy test scripts)
Days 31-60: Build Foundations
Your goal is to transition from auditing to building the foundation / strategy for the next phase of development
Strategic planning: deliver a prioritized test strategy document covering Hardware-in-the-Loop (HIL), system integration, software regression and mobile automation, scoped for the next 6 months.
CI/CD integration: stand up at least one automated testing pipeline integrated directly into our CI/CD flow (e.g., automated firmware build checks, API smoke tests or a BLE handshake validation script).
HIL environment setup: establish a basic Hardware-in-the-Loop (HIL) test environment capable of validating at least one closed-loop sensor or DSP acoustic scenario.
Design for testability (DFT): collaborate with the engineering team to define, document, and implement DFT requirements for at least one active feature currently in development.
Get in touch with manufacturing partners: with manufacturing teams help, get in touch with manufacturing partners to learn more about MES / etc. system integration, QA / QC procedures and EOL testing approaches.
Days 61-90: Prove Value
Your goal is to demonstrate measurable improvements to product stability and prepare our hardware for scalable manufacturing.
Measurable coverage impact: Achieve and report a measurable improvement in automated regression test coverage on at least one critical platform layer (Firmware or Mobile).
Manufacturing readiness (EOL): deliver a working End-of-Line (EOL) manufacturing test checklist or a functional test fixture specification for at least one hardware module (e.g., the Hub or VAC Core) to share with our manufacturing partner.
Risk Mitigation: successfully identify, address and close the top 3 integration risk gaps you flagged during your Day 30 audit.
Roadmap Presentation: present a comprehensive 6-month testing and automation roadmap to the product and engineering leads, outlining resource needs and key milestones for the path to mass production.
End-to-End test strategy: design and implement comprehensive test coverage maps that span from bare-metal firmware (NXP/STM32 family) to the user-facing mobile application and cloud APIs.
System integration testing: develop hardware-in-the-loop (HIL) automation frameworks to simulate edge cases, test wired & wireless connectivity protocols and validate closed-loop sensor / DSP responses.
Automation framework development: build scalable, robust automated testing pipelines for CI/CD integration, ensuring every firmware and software release is rigorously regression-tested before deployment.
Cross-functional collaboration: work closely with hardware engineers, firmware developers, manufacturing, and the mobile/cloud teams to identify integration risks and define testability requirements (Design for Testability - DFT) early in the development cycle.
AI-Accelerated Development: utilize modern "vibe-coding" and AI-assisted engineering tools to rapidly generate test scripts, mock servers, and automated testing boilerplate.
Experience: 5+ years of experience as a software development engineer and/or engineer in test (SDET) or Systems Test Engineering roles, specifically working on connected hardware/IoT products.
Firmware & hardware familiarity: strong understanding of embedded systems (C/C++ environments, RTOS), serial communication protocols (I2C, SPI, UART), and wireless protocols (BLE, Wi-Fi, Matter).
Software & Cloud Testing: Proven experience testing mobile applications (iOS/Android) and cloud microservices (RESTful APIs, MQTT/WebSockets).
Test Automation Ecosystems: Proficiency in modern test automation frameworks and languages (Python and PyTest lib, Robot Framework, Appium, Selenium, Postman/Newman, etc.).
"Vibe-Coding" / AI-Assisted Development: High proficiency in using AI tools to accelerate development workflows. Must be familiar with tools such as:
Cursor, Claude, GitHub Copilot, Antigravity, or similar.
Advanced prompting for LLMs (Claude, GPT) to generate Python test scripts and CI/CD pipelines
Production & EOL Testing: experience designing or validating End-of-Line (EOL) test fixtures and PCBA test jigs (ICT/FCT). Familiarity with implementing "Golden Master" calibration tests on the manufacturing line
Audio / acoustic testing: Experience testing audio equipment, DSP algorithms, or setting up acoustic measurement sweeps (e.g., sine sweeps to detect harmonic distortion or "rattles")
Sensors: Experience testing systems involving IMUs, thermistors, light, and other environmental sensors
Send your CV to hello@neerasleep.com, with a short note on which role and what you’d want to own.