What you will do

• Integrate & tune platform autonomy (SLAM, perception, planning, safety monitors) to each robot via launch files, YAML params, kinematics, sensor configs, and feature flags.
• Author behaviors (BehaviorTree.CPP) for mapping, coverage, docking, recovery, and spot‑cleaning; enforce safe defaults and guardrails.
• Commission sites: bring‑up robots on bench and in customer environments; validate mapping quality, coverage KPIs, docking reliability, and recovery efficacy.
• Triage & RCA incidents: analyze rosbag, telemetry; deliver mitigations and clean RCAs; escalate upstream only when platform change is required.
• Test & release: write robot‑level integration tests; run UAT with APL/PM; verify staged rollout; own rollback plan and operator checklists.
• Telemetry & tooling: add counters (success/failure, interventions), author scripts for log capture, param diffing, health checks, and golden‑path smoke tests; contribute deterministic sim scenarios to reproduce field issues.
• Enable field & manufacturing: create site playbooks along with Pre-Sales Team; train Field Ops; provide NPI with hooks for factory bring‑up and diagnostics.

What you need to succeed (must‑haves)

• 0–3 years in robotics/embedded/automation with production ROS/ROS2 experience (launch, QoS, lifecycle management).
• Strong Linux (Ubuntu), networking, and bash; proficient Python; comfortable reading C++.
• Hands‑on with LiDAR/depth/IMU integration, TF trees, time sync, calibration basics; familiarity with Nav2, SLAM backends, recovery behaviors, and coverage concepts.
• Proven field debugging (ros2 topic/record, rviz/rqt, perf tools), CAN/serial familiarity, and disciplined Git/CI workflows.
• Clear written & verbal communication; calm and structured under pressure; customer empathy.