Lead Fleet Perfomance Engineer

Dexory; Yalesville (CT); On-site; USD 140,000 - 210,000; Full time

Job summary

Dexory seeks a senior reliability leader to own fleet health across our robotics-powered fleet. You will define what to measure, how to report, and lead responses to failures using logs, telemetry, and configuration data.

You will collaborate with Software, Service, and Engineering teams to build pre-failure detection, establish alerting, and drive data quality. Leadership and execution will be key to advancing reliable hardware and software together.

Qualifications

• Substantial engineering experience in reliability, SRE, or robotics operations.
• Fluency with telemetry and observability tools and time-series data.
• Strong analytical ability to separate signal from noise and assess system health.

Responsibilities

• Define and own fleet health: metrics, targets and reporting.
• Investigate fleet-wide behavior from logs and telemetry; quantify impact and severity.
• Own data capture, logging pipelines, telemetry coverage, and reliability data quality.
• Own alert thresholds, escalation, and response processes.
• Develop pre-failure detection for robot subsystems.
• Own fleet configuration management and drift detection.
• Drive a monthly fleet health report to Service and Engineering.
• Hire, coach and grow the team; stay hands-on with data and robots.

Skills

Reliability engineering

Telemetry & observability

SQL

Python

ROS or robotics stack

Linux

Education

Bachelor's degree in a relevant field

Tools

Grafana

Job description

At Dexory, we're developing advanced software powered by cutting-edge robots that are transforming the very face of global logistics. With infectious enthusiasm, our unique blend of disciplines work in harmony to produce results at pace. From hardware and manufacturing to software, AI and commercial, we're one team – one heart – that beats, learns and grows together.

We're only interested in the best ideas, no matter where they're from. We're doers. Game-changers.

Out-of-the-box thinkers who put merit before all else. A group of ambitious and disciplined individuals who are passionate about turning theory into rubber, metal and results.

Purpose.

Build the function that knows what the fleet is doing, what it will do next, and what to fix first.

Responsibilities

• Define and own fleet health: what we measure, what good looks like, and how it is reported.
• Investigate fleet-wide behaviour from logs and telemetry: spot a warning appearing on a handful of robots, work out which release or configuration change introduced it, quantify how many robots are exposed and how badly, and judge the real operational severity.
• Own the fleet's diagnostic data capture — work with other teams for rosbag recording rules, log pipelines, telemetry coverage. If a failure cannot be investigated because the data was not recorded, that is a reliability defect.
• Own alert thresholds, alert quality, resolution and escalation;
• Develop pre-failure detection of robot subsystems
• Own fleet configuration management: baselines, drift detection, change visibility, and driving the configuration itself towards something manageable rather than hand-tuned per robot.
• Own fleet data quality and the hardware health foundation: component-level tracking, and a monthly fleet health report to Service and Engineering.
• preventive maintenance intervals set from fleet data,
• Work alongside V&V on release candidate analysis: interpret what RC robots are showing, catch regressions before wide rollout, and recommend proceed, hold or roll back. V&V owns the release decision; you supply the evidence behind it.
• Build the top-failure-modes register and drive the highest-impact items to resolution with Engineering.
• Report fleet health to the interested teams (Service, Engineering, Software).
• Hire, coach and grow the team; stay hands-on with data and robots.

• Hire, coach and grow the team; stay hands-on with data and robots.

You'll need

• Substantial engineering experience in reliability, SRE, platform operations, robotics operations or a strongly data-driven engineering role.
• Fluency with telemetry and observability: Grafana or similar, time-series data, SQL, Python.
• The analytical judgement to separate signal from noise, and to tell the difference between a robot that is unusual and a robot that is failing.
• Enough systems depth to be credible with engineers: Linux, logs, distributed systems, and ideally ROS or another robotics stack.
• The ability to argue a case from evidence and hold a position with engineering and hardware teams.
• The discipline to protect proactive work from reactive pull.