← Zipline
Complex day at Zipline

Decide if the tracker ships despite disputed close-encounter positions

You’re the ai / ml engineer. Your team is in the room. Printed Oct 15, 2026.

The new tracker improves visibility while making close-encounter distance less certain.

A fleet release protects delivery capacity, while a hold protects against committing disputed position estimates into planner behavior.

Who you’d be doing this for

“The pharmacy called twice today because the delivery window kept moving after launch planning changed.”

Ndayisaba Mugabo · Transportation Operations Manager

Coordinates urgent medical deliveries that depend on predictable aircraft availability and mission duration.

What is at stake

The new tracker changes avoidance paths in close encounters, and the release window closes in five days. You must weigh a known tracking improvement against position estimates that are expensive to verify before deployment.

Why it isn’t already fixed

Every obvious fix costs something else. That’s the part you’d have to decide.

  • tracking improvement vs. geometric certainty
  • fleet capacity vs. conservative separation
  • replay coverage vs. field realism
  • release timing vs. validation confidence

Why Zipline

Long-range medical and retail deliveries depend on perception and motion planning agreeing on where nearby aircraft are during autonomous flight.

Written with these in mind

safety-critical ML engineerrobotics perception engineerautonomy systems engineer

Not your kind of problem? 71 more at Zipline, or browse every organization.

This is the setup. The work is inside.

Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.