By playing, you agree to uListen's Terms and Privacy Policy and YouTube's Terms of Service.

Skydio VP of Product on How Skydio Ships Flying Robots With Just 20 Product Managers

Most people think of drones as toys. Alden Jones thinks of them as infrastructure.

Alden JonesguestCarlos González de Villaumbrosiahost

Aug 12, 202632mWatch on YouTube ↗

Summaries, chapters, transcripts, and FAQs on this page are made by uListen, not YouTube.

CHAPTERS

Jump to publisher timestamps

Chapter summaries

Why Skydio calls them “flying robots,” not drones
Alden Jones explains the shift in perception from drones as toys to tools and ultimately to infrastructure. He frames Skydio as building more than quadcopters: a broader suite of robots designed to solve real-world problems.
- •Drones are often perceived as toys, while Skydio sees a trajectory toward critical infrastructure
- •Skydio’s work goes beyond a quadcopter to a broader “robot solutions” approach
- •The company builds multiple robotic components to deliver end-to-end solutions
Building the full solution: platforms, base stations, and more
Alden describes the components needed to deliver a complete robotic solution, including robotic base stations and other hardware. The emphasis is on delivering a system, not just a single flying device.
- •Skydio builds different kinds of platforms, not only one drone type
- •Robotic base stations are part of the deployed solution
- •Additional robotics elements are involved (including robotic arms) to solve customer problems
Skydio at scale: ~1,000 people and fully vertically integrated
Alden gives a snapshot of Skydio’s scale and how the company operates across the full stack. He outlines in-house capabilities spanning software, hardware, manufacturing, and supply chain, with engineering largely in California and some global offices.
- •Skydio is just under 1,000 people including manufacturing in California
- •The company does software, hardware, logistics, supply chain, manufacturing, and chip-down design in-house
- •Engineering is primarily in California with additional global engineering offices
- •Go-to-market teams are distributed broadly
How product leadership works across hardware, software, and autonomy
Alden explains how his product organization is split between a core platform team and vertically-focused PMs tied to specific customer use cases. He also clarifies his scope across both hardware and software, working closely with engineering leadership.
- •A core platform product team owns hardware, core software, autonomy, embedded work, and connectivity
- •Vertically-focused PMs deliver specific value for particular customer use cases
- •Alden oversees both hardware and software product areas
- •Software autonomy leaders and the SVP of engineering partner across the stack
A non-engineer’s path to VP of Product: military, telco innovation, and customer success
Alden shares his unconventional background: a history degree, military service, and later an innovation role where he learned drones and technology. He describes how starting at Skydio in customer success helped him build technical depth through close work with engineering leaders and founders.
- •Alden is not an engineer and has a history degree
- •Military experience shaped his view of technology in critical situations
- •He taught himself technical concepts while experimenting with drones at a telco innovation role
- •He joined Skydio as the first customer success leader and built the function from scratch
- •He credits learning through deep collaboration with engineering leaders and the CEO/co-founder
The four primary use cases: response, ISR, security, and inspection
Alden outlines Skydio’s main categories of customer value, emphasizing the company’s focus on solving business and mission-critical problems. He positions Drone as First Responder (DFR) as part of “response,” and explains how defense ISR, security, and inspection fit into the portfolio.
- •Skydio focuses on four broad use cases: response (DFR), ISR, security, and inspection
- •ISR refers to intelligence, surveillance, and reconnaissance in military contexts
- •Security includes protecting large fixed sites and reducing reliance on roving patrols
- •Inspection involves digitizing infrastructure assets to improve business efficiency
Drone as First Responder (DFR) at scale: ingesting calls and placing docks strategically
Alden provides the scale and growth of Skydio’s DFR business, including how many calls they ingest and respond to. He explains how Skydio works with agencies’ historical 911 call data to decide where docking stations should be placed for faster response.
- •Skydio ingests millions of 911 calls monthly and responds to tens of thousands each month
- •Millions of Americans live within a short radius of a Skydio DFR dock, and that footprint is growing
- •Skydio maps an agency’s 911 calls and priorities to advise dock placement
- •The goal is faster, better information for public safety decisions
DFR compared to helicopters and radio dispatch: faster visuals, lower cost
Alden contrasts DFR with traditional public safety tools: helicopters and radio-based dispatch. He highlights helicopter operating costs and explains how officers often work with minimal context, while drones can provide immediate visual information.
- •Helicopters act as “flying cameras” but are expensive to operate
- •Cities can’t use helicopters to respond to the density of calls they receive
- •Traditional dispatch often provides only a one-line description with no images
- •DFR aims to reduce uncertainty in high-stress scenarios by providing visuals quickly
Measuring public safety impact: the DFR outcomes dashboard
Alden describes how Skydio measures DFR success using an outcomes dashboard focused on response and decision quality. He also highlights a metric where the drone’s fast arrival can prevent unnecessary dispatches, with customers self-reporting outcomes in the product.
- •Key metrics include whether the drone arrived first and overall response time
- •The system tracks whether the drone provided useful information to responders
- •Skydio tracks cases where an officer was not dispatched because the drone confirmed nothing was happening
- •Customers input outcomes directly in the product, and leaders review the metrics
Defense and ISR: drones as air support, with focus on camera-only intelligence
Alden explains defense use cases, from base security (a “mini city”) to tactical ISR. He shares personal experience from Iraq to illustrate how drones can reduce risk, and discusses the role of drones in modern conflict while emphasizing Skydio’s camera-only focus.
- •Alden describes military units as “mini cities” with security needs on base
- •Tactical ISR provides information to keep soldiers safe and support mission objectives
- •He contrasts past methods of investigating threats with using a drone for safer assessment
- •He notes modern battlefield reliance on drone air support and distinguishes camera drones from kinetic use
Defense success metrics and constraints: feedback is limited, stakes are high
Alden notes that while there are many flight metrics, tactical ISR users operate disconnected and air-gapped, limiting telemetry and feedback. He frames success in terms of mission outcomes and lives saved, acknowledging the seriousness of the domain.
- •Tactical ISR use is offline/air-gapped, limiting direct usage feedback
- •Skydio can cite some broad flight milestones, but not including tactical ISR users
- •He characterizes “lives saved” and mission accomplishment as core outcome measures
- •National security customer feedback comes through different channels than typical SaaS telemetry
Physical security: autonomous patrol, alarm response, and reducing false alarms
Alden describes stadiums and other sites as examples of physical security where drones provide rapid situational awareness. He explains two main security modes—autonomous patrol and response—and cites high false-alarm rates as a driver for using drones instead of sending guards.
- •Stadiums and large venues use drones for perimeter sweeps and hotspot visibility
- •Security use cases include autonomous patrol and responding to alarms
- •AI models can be used to identify customer-defined items of interest
- •Alden cites that most alarms are false alarms, making drone verification valuable
- •He argues the marginal cost of sending a drone (battery use) is very low
The autonomy and software layer: multi-drone operations and the “Minecraft” 3D model
Alden explains how Skydio enables one operator to manage multiple drones through autonomy and command software. He describes how onboard models and 360-degree sensing build a simplified 3D understanding of the environment, allowing safe navigation and recovery in abnormal situations like power loss.
- •Customers can operate multiple drones per pilot depending on the use case
- •Autonomy combines deep-learned models with 360-degree cameras and 3D world modeling
- •The 3D representation is compared to “Minecraft”—sufficient detail to avoid obstacles
- •Drones can handle scenarios like entering a parking structure and finding the way back out
- •Trustworthy autonomy is required for multi-drone scale and for off-nominal events
Regulators, trust, and the timeline for autonomous fleets
Alden describes Skydio’s collaborative approach with the FAA and the importance of earning regulatory trust through safety, autonomy, and demonstrated capability. He also suggests fully autonomous fleets are near-term and emphasizes that autonomy at scale is already happening in routine operations.
- •Skydio prioritizes earning regulators’ trust rather than taking an adversarial stance
- •They hired aviation safety and regulation experts and work with the FAA regularly
- •Alden says the company received major waivers due to demonstrated technical capability
- •He frames fully autonomous fleets as “very near term,” not a decade away
- •He notes many flights already include autonomous travel to and from the objective
From R&D to customer value: focusing on DFR, then expanding investment
Alden explains the company’s evolution from early R&D to delivering concrete customer value once key elements came together. He says Skydio prioritized making DFR successful, and after it scaled, the company “earned the right” to invest more broadly across other areas.
- •Early years were heavy on R&D with autonomy innovation but less delivered value
- •Customer closeness helped Skydio translate technology into real outcomes
- •Alden cites the combination of a core platform, the Dock, and remote ops software as a turning point
- •Skydio prioritized DFR as the top company goal before scaling other investments
- •He notes the military business has been significant but can be “lumpy” compared to other areas
The $3.5B investment commitment: supply chains, manufacturing, and revenue-funded growth
Alden describes a multi-year investment commitment covering production and broader company activity, including supply chain security and manufacturing focus. He emphasizes the commitment is driven by business revenue rather than debt-funded expansion.
- •Skydio committed to a large multi-year total investment plan announced by the CEO
- •Investment includes producing large volumes of drones and strengthening supply chains
- •Focus includes US manufacturing and allied/partnered supply chains
- •Alden says the commitment is revenue-funded rather than funded via debt
- •He notes the company could choose to raise more capital to pursue additional markets
Org design: customer-first philosophy, lean PM team, “no travel budget,” and strike teams
Alden lays out Skydio’s customer-first philosophy and how it shapes team structure and operating cadence. He describes a lean PM org, expectations to get direct customer signal, and “strikes” where engineers temporarily embed with vertical teams to deliver key capabilities before returning to the platform.
- •Org structure is grounded in a customer-first, mission-oriented philosophy
- •Skydio runs a lean product org of about 20 PMs across the stack
- •Alden expects PMs to personally gather signal by seeing the robot used in the real world
- •Product leaders pair with engineering leaders and teams to deliver outcomes
- •“Strikes” embed engineers with a vertical team for months to deliver a feature, then return to platform
Design, trust, and hardware cycles: intuitive UX and two-year major programs
Alden explains why design is essential even in a deeply technical robotics company, especially to build customer trust in autonomous actions. He then contrasts hardware and software iteration speed, describing Skydio’s typical two-year “major program” cadence with interim revisions and accessories.
- •Design helps ensure products are intuitive, feel safe, and build trust in autonomy
- •Customers need clarity about what the robot will do, especially with autonomous actions
- •Alden compares trust-building UX to how drivers see what a Tesla will do
- •Skydio’s typical major hardware program cycle is about two years
- •Hardware revisions and accessories can ship on shorter cycles to improve reliability and capability

Publisher timestamps

Get more out of YouTube videos.

Read along on your phone, search it beside the video, or ask your favorite AI app what was said.