First-time day at Skydio

Unify MES and fleet-upload sites without a disruptive backfill

Published Oct 28, 2026

You’re the data engineer. Your team is in the room.

The setting

makes drones for public safety agencies, government, and businesses. Its use onboard software to fly missions on their own, for work such as inspection, emergency response, and site security.

A dock-site search cannot be trusted when one location arrives in two forms.

Fast reuse of fleet data depends on preserving source detail while giving model users one stable location field.

Who you’d be doing this for

“I pulled the dock slice twice, and both runs left out flights I know we captured.”

Kamau Wanjala · Computer Vision Engineer · a character in this brief

Uses curated flight logs and media to select training and evaluation data from docked fleet operations.

What is at stake

Dock-site searches are omitting captured flights from the curated dataset. You must weigh a quick schema mapping against preserving source-level provenance.

Why it isn’t already fixed

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

  • fast correction vs source-level provenance
  • one searchable location field vs distinct source meanings
  • unattended ingestion vs visible malformed records
  • dataset completeness vs stable model versions

Why Skydio

Dock-based fleet operations depend on autonomy models learning from the specific sites where aircraft fly.

Written with these in mind

data reliability builderML data platform engineerschema and lineage specialist

Not your kind of problem? 74 more at Skydio, or browse every organization.

Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.

The organization context comes from public information. The situation and characters are written for the brief.

Job postings it was written from

Public descriptions of the work at Skydio. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.

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.

Other live briefs connected to this one, and what connects them.

Similar problems at other organizations

Like this one, each of these turns on fixing one thing without breaking another.

The same setting, from another role

Each is set around Skydio’s Skydio autonomous drones, written for a different role. They’re separate briefs, not the same scenario.

Other problems with a similar purpose

In each of these, as in this one, the aim is to make a machine-driven decision dependable and fair at the exact real-world moment a customer is counting on it.