About The Role

We started as roboticists ourselves. We know the pain of fragmented, proprietary systems that refuse to talk to each other. syncOS is our answer — and we believe it's what the industry has been waiting for. We are a young, passionate team chasing one big mission: #automateasia. If you love robots, hate inefficiency, and want to build solutions that run on real factory floors — read on.

The roles and responsibilities are

Build and own the test infrastructure that makes AMR acceptance testing repeatable across every MAG variant and hardware generation.
Run the released Botsync Artifact through independent, full-stack hardware-and-software verification before sign-off - commissioning-grade rigor applied in the lab, before it ever reaches a site.
Test infrastructure, end to end - Design, build, and maintain HIL rigs and physical test fixtures spanning every MAG AMR variant (lifter, forklift, counterbalance, conveyor, tugger) and hardware generation (R2/R3/new), so acceptance runs are repeatable, not improvised per release.
Deployment-profile automation - Build and own the automation that runs deployment-profile gates per site/variant/generation against the release candidate, replacing manual bench-testing with a repeatable regression pass.
Full-stack acceptance testing - Run the released candidate through hardware-level acceptance tests before sign-off, exercising hardware, firmware, and software together the way a commissioning engineer would on a live site - not layer by layer in isolation.
Independent verification, not build - Test and certify robot behavior across variants and generations without owning or patching the production robot software or hardware under test; defects go back to the owning Robotics team, never fixed in place.
Defect triage and traceability - Log, reproduce, and route hardware-surfaced defects to the correct Robotics or SyncOS team with enough rig data, logs, and repro steps to unblock a fix without back-and-forth.
Test tooling reuse - Turn one-off rigs and scripts into a reusable acceptance test catalog with clear ownership, so hardware coverage doesn't live in one bench setup or one person's head.
Cross-artifact acceptance support - Contribute the hardware-verification evidence that Acceptance QA + Release needs to cross-cut the robot and syncOS sides into a single Botsync Artifact sign-off.

How you'll work

You will partner closely with

Robotics Hardware & Software - You test what they build. You never patch their code or firmware; defects go back to them with rig data, not workarounds.
Robotics QA - They own per-stack regression suites feeding into the AMR release candidate; you own hardware-level acceptance testing of the released candidate itself, one layer up.
Head of QA / Acceptance QA + Release - Your test evidence feeds the artifact-level sign-off decision; the sign-off call itself sits with the team, independent of the teams whose work you're verifying.
Field Delivery - Think of this role as commissioning-before-commissioning: you catch the hardware/software issues they'd otherwise catch on-site, just earlier and in the lab. You don't own site commissioning itself - that stays with Field Delivery; you feed them a cleaner artifact and take their field findings back into your gates.
4-6 years in robotics, mechatronics, or hardware test engineering, ideally with mobile robot or AGV/AMR platforms - or a commissioning/field-integration background where hardware and software issues get debugged together, not in separate silos.
Hands-on experience building HIL rigs, test fixtures, or hardware test automation - not just running manual test scripts.
Genuinely full-stack: comfortable debugging a motor fault, a firmware quirk, and a software/workflow bug in the same test session - the way a commissioning engineer has to on-site, applied here before release.
Strong defect reproduction and reporting discipline - you can turn "it broke" into a repeatable rig scenario with clear evidence.
Experience with deployment or release-gate processes in a hardware-in-the-loop or physical-product context.
Independent judgment under pressure - comfortable holding a gate when a release is late and someone wants it waved through.
Scripting and automation ability (Python or similar) to build repeatable test harnesses, not one-off manual checks.
Bonus: exposure to AMR/AGV navigation, docking, or fleet-management concepts
Competitive salary
Comprehensive health benefits package
Hustle of a young startup, always something to do and something to improve
Opportunities for professional development and growth into management roles
Collaborative and inclusive work environment