Test Engineer - Equipment & Cloud QA
- Discuss this with your agent
- Open in Claude
- Open in ChatGPT
Role details
Tech stack
+14 more
Job description
This is a hands-on, self-directed role for someone who treats quality as a craft and takes full ownership of their domain. You will write and execute test cases, track results and defects in Jira, verify that products behave correctly before they reach customers, and drive issues to closure across firmware, hardware, and software releases. You will serve as the critical quality bridge between U.S. and China-based engineering teams, working in Mandarin to unify test procedures and resolve defects directly at the source., Test Case Development & Execution - Residential & C&I
- Author & run test cases: write, maintain, and execute standardized functional, integration, and system-level test cases against residential and C&I batteries, inverters, gateways, and firmware.
- Edge & negative testing: test boundary conditions, fault handling, and error paths - not just the happy path - to surface defects before customers do.
- Regression testing: re-run affected cases after firmware/software changes to confirm fixes hold and nothing previously working has regressed.
Firmware & Hardware Validation
- Bench & lab testing: validate battery, inverter, and gateway behavior on the bench using standard lab instrumentation; reproduce reported field issues in a controlled setup.
- Firmware validation: verify ARM, DSP, and LCD firmware builds and version compatibility across products before release.
- Log analysis & root cause: pull and analyze device logs and telemetry to isolate root cause and give engineering a reproducible defect.
Cloud & Application Testing - Residential & C&I
- Validate platform behavior: verify Fortress portal, cloud platform, Installer app, and Homeowner app behavior against device-level data so what customers see matches what systems are doing.
- Find cloud/software defects: surface issues in data integrity, reporting, connectivity, and dispatch reflection, and confirm fixes before customer exposure.
Release Management, Defect Tracking & Coordination
- Track in Jira: log, prioritize, and track test results and defects in Jira; keep tickets clear, reproducible, and current through to verified closure.
- Release notes & QA sign-off: maintain release notes, publish version releases and product news, and provide final QA review before a build is released to production.
- Release tracking: keep the test process and release-tracking system current so status is visible at any time.
- Coordinate overseas: unify test steps between the China and U.S. teams and drive defect resolution directly with China-based engineering and manufacturing in Chinese (Mandarin)., * Test execution: 100% of planned test cases authored and executed each release cycle.
- Quality: defect escapes to customers trending to zero release over release.
- Defect handling: defects documented, reproducible, and tracked to verified closure within target turnaround.
- Release readiness: release notes, version releases, and QA sign-off completed on time for every build.
Requirements
- Self-starter: operates with minimal management oversight and sets their own pace and priorities.
- Owner mentality: treats their test domain as their own - entrepreneurial, accountable, and proactive about gaps.
- Fast on their feet: thinks quickly and acts quickly; comfortable making calls and moving without waiting to be told.
- Disciplined: detail-oriented with strong, reproducible documentation habits., * Bachelor’s degree in Engineering (Electrical, Software, Controls, Mechanical, or related) or equivalent hands-on technical experience.
- Professional fluency in Chinese (Mandarin), written and spoken, for technical defect discussions with overseas engineering and manufacturing teams.
- 2+ years in product testing, QA, or hardware/firmware/software validation, ideally in energy storage, power electronics, or a comparable hardware+software environment.
- Hands-on experience authoring and running test cases, documenting defects, and tracking them to resolution in Jira (or a comparable tool).
- Comfort testing across hardware, firmware, and software/cloud layers and comparing behavior between them, including basic log and telemetry analysis.
- Authorized to work in the U.S. and able to work on-site in Langhorne, PA., * Direct experience with battery energy storage systems (BESS), inverters, or power electronics, including bench testing with lab instrumentation (e.g., multimeter, oscilloscope, power analyzer, programmable loads/sources).
- Familiarity with communication protocols (Modbus, CAN bus, RS485, MQTT) and firmware/version management across embedded devices.
- Awareness of relevant safety/interconnection standards (e.g., UL 9540, UL 1741, IEEE 1547) and their role in product validation.
- Exposure to EMS/SCADA environments, cloud monitoring (e.g., Azure), or basic test automation/scripting.
- Experience unifying test procedures across distributed or overseas (China-based) engineering teams.
Benefits & conditions
Compensation: Target base salary of $70,000 - $90,000 per year, commensurate with experience, plus Fortress Power’s benefits package.
About the company
Fortress Power designs and manufactures residential and commercial battery energy storage systems that are reshaping how homes and businesses manage power. As their Test Engineer for Equipment & Cloud QA located in Langhorne, PA, you will own quality control and validation testing across the full product lineup, from physical hardware (batteries, inverters, gateways, and firmware) to the Fortress cloud platform, portal, and mobile/web applications.
Apply for this position
This job is hosted externally. Click below to view the full posting and apply.
Apply on www.dice.comGood distractions
Talks and stories from around this role — technically off-topic, practically not.
Moments
Explore playlistsVideos
See allRelated articles
See all
What is a Test Plan: Guide to Test Planning
A Guide to Green Tech and Green IT Careers
How to create a test plan for software testing
Integration And E2E Testing: Are They Complementary or Interchangeable?