> Markdown version of [/jobs/ext/4257565-robotics-release-engineer](https://www.wearedevelopers.com/jobs/ext/4257565-robotics-release-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Robotics Release Engineer

- **Company:** Fieldai's Irvine
- **Location:** Irvine, CA, United States
- **Experience:** Experienced
- **Contract:** Permanent contract
- **Skills:** JIRA, Automation of Tests, Bash Shell, Command-Line Interface, Linux, Firmware, Python (Programming Language), Release Management, Software Engineering, System Testing, Scripting, Mobile Robots, Git, Integration Tests, Bug Reporting, Lidar, Testrail
- **Published:** October 22, 2026
- **Apply:** https://startup.jobs/robotics-release-engineer-system-validation-fieldai-10537152

## About the Role

* 3+ years in QA, system test, integration test or release validation for robotics, autonomous vehicles, drones, industrial automation or another hardware-software product.
 * Experience planning and running structured test campaigns: writing test plans, executing against acceptance criteria, tracking coverage and reporting status to stakeholders.
 * Hands-on comfort with physical systems. You are willing to walk a robot through a building for hours, work on your feet, and be safety-conscious around moving machinery.
 * Strong written communication. You write bug reports and status updates that others can act on without a follow-up conversation.
 * Fluency with Jira or a similar tracker, and with a disciplined bug lifecycle: triage, severity, reproduction, verification, closure.
 * Comfort on Linux, in a terminal and over SSH: installing builds, pulling logs, checking a process, running a command-line tool.
 * Working familiarity with git: checking out a branch or tag, reading a pull request, finding what changed between two builds.
 * Judgement to separate a blocker from a nuisance, and the confidence to say a build is not ready.
 * Reliability and ownership. Releases run on a fixed calendar and you will be the person others depend on., * Experience as a release manager, release coordinator or QA lead responsible for a go/no-go call.
 * Robotics or autonomy domain knowledge: ROS, SLAM and localization, navigation, mission planning, LiDAR, cameras.
 * Experience validating software on a fleet: multiple robot platforms, firmware versions, configurations or deployment paths.
 * Scripting or test-automation experience, for example Python or Bash to automate a test step, parse logs or collect data.
 * Experience with simulation-based testing or with hardware-in-the-loop setups.
 * Experience with test management tools such as Xray, TestRail or Zephyr.
 * Experience working alongside field or deployment engineers and customers.
 * Background in a safety-critical or regulated domain.

## Description

* Plan and execute release validation for each release: new-feature validation, end-to-end operational scenarios, and regression across robot platforms, compute, firmware and configurations.
 * Run end-to-end autonomous missions on real mobile robots in our test facility, the way a customer runs them: setup, navigation, data capture and recovery.
 * Verify each release candidate: install the build, run the regression set, confirm hotfixes, and report status to the release team.
 * Write clear, reproducible bug reports in Jira with datasets, logs, robot, build and steps attached.
 * Own the pass/fail evidence that feeds the go/no-go decision: pass and fail counts, deferred bugs and known-issue lists.
 * Prepare the release handover for the engineers who deploy at customer sites: what was validated, what was not, and what to watch.
 * Confirm late fixes on the next release candidate before they ship.
 * Build and maintain the release test-case library so each release plan starts from a curated, versioned set.
 * Partner with our test automation and infrastructure engineers so the scenarios you run by hand become automated simulation and robot tests.
 * Improve the release process itself: checklists, templates and retrospectives.