ー Quality engineering, test automation, CI/CD validation, and operational documentation for retail robotics operations As a Product Quality Engineer for Robotics Applications, you will improve the release quality, reliability, and usability of software used in real retail robotics operations.
This role focuses on the application layer of our robotics system, including store-facing applications, operator tools, dashboards, backend services, and robot-adjacent components used in production operations.
You will design and execute practical test cases, build automated tests and CI/CD validation checks, create lightweight QA tools and log analysis utilities, and maintain operational documentation and FAQs. Your work will help reduce escaped defects, repeated support inquiries, unclear product behavior, repetitive manual validation, and release risk.
This is not a pure manual testing role. We are looking for someone who can understand product requirements, real-world store operations, software behavior, system constraints, and production signals, then translate them into effective test plans, automation strategies, internal tools, and operational knowledge assets. Responsibilities
Design and maintain release test cases for robotics applications, including store-facing tablet applications, operator tools, dashboards, backend services, OPM, RobotClient, ShelfClient, and related components.
Review product specifications and release scopes from a quality perspective, and identify missing edge cases, ambiguous behavior, and operational risks before implementation or release.
Break down product requirements, operational flows, and edge cases into concrete test scenarios, expected results, and regression coverage.
Execute release validation and coordinate test results with Engineering, Product, Operations, CS/CX, and BizDev stakeholders.
Build and maintain automated tests, CI/CD validation checks, log analysis utilities, and lightweight internal tools that improve release confidence and reduce repetitive manual validation.
Build and improve lightweight quality engineering practices for release readiness, regression testing, defect triage, test automation, observability, CI/CD validation, and post-release learning.
Analyze field issues, support inquiries, logs, monitoring signals, and incident patterns, then convert recurring problems into test cases, automation candidates, documentation improvements, or product improvement proposals.
Create and maintain internal and external documentation, FAQs, troubleshooting guides, and release notes based on release changes, field issues, and recurring support inquiries.
Help define and track quality metrics such as escaped defects, regression coverage, release readiness, repeated support issues, automation coverage, and documentation effectiveness.
Requirements
3+ years of experience in quality engineering, test automation, software engineering, or a similar technical role involving automated testing, CI/CD validation, or production issue investigation.
Experience designing test cases from product requirements, user flows, business rules, or operational scenarios.
Experience executing release testing for production software used by real users.
Experience building or maintaining automated tests, CI/CD validation, QA tools, log analysis tools, or other engineering systems that improve software quality.
Experience with at least one of the following: Testing mobile or tablet applications on real devices.
Validating API behavior using tools such as Postman, curl, Swagger/OpenAPI, or automated API test frameworks.
Experience using logs, monitoring dashboards, metrics, or error tracking tools to investigate defects, validate fixes, or monitor post-release behavior.
Ability to understand complex systems involving multiple applications, APIs, backend services, mobile/tablet applications, and operational workflows.
Strong attention to detail, especially around edge cases, state transitions, error handling, data consistency, and regression risk.
Experience creating clear documentation, FAQs, troubleshooting guides, or release notes for non-engineering stakeholders.
Ability to communicate clearly with Engineering, Product, Operations, CS/CX, and BizDev teams.
Working knowledge of software development workflows using GitHub, issue tracking tools, CI/CD, and agile development practices.
Business-level Japanese and working-level English communication skills.
Nice to Have
Experience combining real-device testing, API validation, and logs/monitoring to investigate end-to-end product behavior.
Experience with test automation for web, mobile, tablet, desktop, or Unity-based applications.
Experience with tools such as Playwright, Cypress, Selenium, Appium, XCTest, NUnit, xUnit, or similar frameworks.
Experience testing or working with applications built with Unity, .NET/C#, React, or similar technologies.
Experience with SQL or database queries to investigate data consistency issues.
Experience testing applications connected to hardware, IoT devices, robotics systems, or edge devices.
Experience testing workflows involving real-world operations, hardware states, asynchronous events, or multi-system state transitions.
Experience working in retail, logistics, robotics, operations-heavy SaaS, or mission-critical field software.
Experience improving QA processes in a startup or fast-changing product environment.
Technology Environment
You may work with technologies across our robotics applications and platform, including:
Frontend / Applications: TypeScript, React, C#, Blazor, Unity, Tailwind, shadcn/ui
Backend: .NET
Cloud Infrastructure: Terraform, Azure, Kubernetes
Data Stores: PostgreSQL, MongoDB, Redis
IoT / Edge: .NET, C++, Python, ROS, NVIDIA Jetson AGX, IoT boards
CI/CD and Quality: GitHub Actions, SonarQube, Ansible
Prior experience with all of these technologies is not required. We value the ability to understand system behavior, identify quality risks, build practical validation tools, and improve software quality through engineering.
What Success Looks Like
Release test coverage becomes clearer, more reusable, and easier to execute.
Repeated field issues and support inquiries are converted into test cases, automated checks, documentation, or product improvements.
Manual release validation effort is reduced through practical automation and CI/CD validation.
Logs, monitoring signals, and production feedback are used more effectively to investigate issues and validate fixes.
Release risks are identified earlier, before they become production incidents.
Robotics applications become easier for CS/CX, BizDev, Operations, and store staff to understand and support.
Automated checks and lightweight internal tools improve release confidence without creating unnecessary process overhead.
Quality feedback from production is continuously reflected back into testing, documentation, and product development.