Who Gets Hired
Skydio builds flying robots that operate autonomously where GPS fails and pilots can't reach. Every hire is a bet on someone who moves between simulation and the flight line without losing the thread. The 1,047-person workforce spans autonomy algorithms, embedded firmware, airframe design, supply-chain orchestration, and the legal and go-to-market functions that turn a prototype into a program of record for the U.S. Border Patrol, ODOT, and LNG Canada. The question isn't whether your discipline appears on the org chart — it's whether you can operate at the intersection of them.
This guide maps the five things a candidate needs to know: the roles Skydio fills, how compensation is structured, what the multi-stage interview entails, where work happens across three global sites, and which personal traits predict long-term success.
Three vice presidents report to CTO Abe Bachrach: Juraj Kabzan leads Autonomy, Ben Thompson owns Hardware, and Ryan Reading runs Software Engineering. That triad defines the core technical teams. Autonomy hires computer-vision PhDs and robotics generalists who ship perception stacks for autonomous flight. Hardware recruits mechanical, electrical, and thermal engineers who iterate airframes and docks on weekly cadences. Software Engineering absorbs full-stack, embedded, and infrastructure engineers who turn flight data into fleet management. LinkedIn lists 73 open roles across Engineer, Embedded Software Engineer, Mechanical Engineer, System Engineer, Design Engineer, Manufacturing Engineer, and their manager equivalents — a taxonomy that mirrors the three-VP structure.
Product and program functions sit beside engineering, not below it. Alden Jones (VP Product) and CJ Johnston (VP Hardware Ops) coordinate roadmaps that fold in regulatory, supply-chain, and customer-deployment constraints. Mindy Hsu (VP Supply Chain) and Morgan Culver (Recruiting Manager) round out the operations layer that keeps materials moving from vendors to the Hayward production line.
Legal and compliance have grown into a dedicated pillar. Brendan Groves (Chief Legal Officer) and Molly Braese (Head of Global Compliance) oversee a team posting roles like Full Stack Product Counsel and Senior Employment Counsel — evidence that airspace regulation and export control are treated as product requirements, not afterthoughts. Macario Namie (CMO) and Callan Carpenter (CRO) lead commercial teams that include Account Executives, Growth Marketing, and field engineers who embed with utility inspectors and first responders.
Intern and new-grad pipelines feed every technical ladder. The careers page frames autonomy as a craft learned by shipping, not by publishing alone. Two European R&D offices, Zürich and Tampere, extend the autonomy and software teams across time zones; this move, announced on LinkedIn, signals that the next hiring wave will be distributed by design. The Official Board maps 19 executive leaders; the teams they own are the hiring funnels. If your resume reads like a single-discipline specialist, the door stays closed. The roles that open it live at the seams.
Pay Bands and Equity
Skydio's compensation sits in the upper tier for venture-backed robotics, reflecting the Bay Area cost base and the premium for engineers who ship autonomy on hardware. Zero G Talent's board data shows a board-wide salary band of $93,000–$244,000 with a median of $180,000 across 67 salaried roles. Third-party aggregates converge on the same number: HireOven reports $178,500 median total pay from 94 posted salaries; RecruitingFromScratch calculates $179,000 across 96 public postings from 2025–2026. Three independent sources clustering around $179–180K signal a stable, well-calibrated pay structure.
| Role | Base Salary Range |
|---|---|
| Staff Software Engineer, Full Stack | $200,000–$275,000 |
| Staff Product Manager, Vehicle AI | $196,500–$250,000 |
| Director, Global Supply Management – Mechanicals | $184,000–$262,000 |
| Full Stack Product Counsel | $225,000–$300,000 |
| Senior Employment Counsel | $225,000–$275,000 |
| Director, Growth Marketing | $150,000–$250,000 |
The spread within each band (typically $75K–$100K) reflects level granularity and experience variance, not location differentials; virtually every posting is tagged San Mateo, California.
Equity is the lever that pushes total compensation above the base median. Skydio's Series F closed at a $4.4 billion post-money valuation in 2026. The most recent secondary-market transaction priced shares at $10.02 as of June 30, 2026. Employees granted options at or near the 409A price (typically a discount to the preferred price) hold paper gains if the secondary market holds. The $10.02 mark also serves as a rough benchmark for refresher grants: a $50,000 annual equity component translates to roughly 5,000 shares at current pricing.
Benefits data is thinner in public sources, but the pattern across Skydio's peer set (Anduril, Shield AI) points to comprehensive medical, dental, and vision; 401(k) matching; generous hardware allowances; and flexible PTO. The U.S. manufacturing footprint and defense contracts also mean some roles carry security-clearance sponsorship, negotiated per requisition rather than published.
The compensation picture sharpens against the hiring bar: Skydio pays for engineers who bridge autonomy software and systems validation. A pure web full-stack engineer without robotics fluency lands in the lower half of the Staff band. The candidate who has shipped perception stacks on embedded compute and written the integration tests that catch edge cases in flight negotiates from the top.
Inside the Interview Loop
The Skydio interview loop typically runs five to six rounds over four to six weeks, though candidates with direct autonomy or cloud infrastructure experience can move from application to offer in two to three weeks. Techprep.app and InterviewQuery report the same cadence: each stage consumes roughly a week, and the timeline compresses when your background maps cleanly to the open role.
A 30-minute recruiter screen opens the process. The conversation covers your background, why you want to work on drone software specifically, and high-level technical experience. InterviewQuery notes this step filters for genuine interest in autonomy and robotics before investing engineering time.
Next comes a 60-minute video call with a peer engineer. Depending on the target team (backend, embedded, or full-stack), you either live-code a medium-difficulty problem or walk through a focused domain discussion. Techprep.app reports some teams have shifted toward work-sample problems: implementing a telemetry-system component rather than solving a standalone graph puzzle. Clean, readable code under time pressure matters more than algorithmic cleverness.
Many teams then assign a take-home project. Candidates consistently report eight to ten hours of work. The prompts are grounded in realistic scenarios: fetching and plotting OpenStreetMap data to generate a flight plan, or writing a path-planning algorithm that avoids obstacles while maintaining performance. The expectation is production-quality code, clean API design, and real-world architecture decisions — not a polished LeetCode solution.
The virtual onsite loop packs four to five hours of back-to-back sessions: a technical presentation, live coding, system design, and a behavioral deep-dive. The presentation round is a signature element you won't find at most companies. You prepare a roughly 30-minute talk on a complex project you owned or significantly contributed to, delivered with slides, followed by 10 to 15 minutes of panel Q&A. Indeed reviewers describe it as two parts: introduce yourself, then deep-dive one project. The panel evaluates how you reasoned through trade-offs, handled ambiguity, and understand the system you're describing — not just what you built.
Dataford.io's percentile analysis reveals what the loop actually tests:
| Skill Area | Percentile |
|---|---|
| Debugging and Root Cause Analysis | 100th |
| C++ Proficiency | 100th |
| Drone-Experience Relevance | 100th |
| DSA and Algorithmic Problem Solving | 96th |
| Control Systems / Input Lag / Planning | Low 90s |
| Camera Feed Diagnostics | 89th |
| Flight Testing Methodology | 85th |
If your answers never tie back to diagnosing or evaluating real system behavior, you miss the signal.
Behavioral questions go beyond standard experience prompts. Techprep.app highlights a recurring safety-and-reliability thread: your philosophy on testing, how you've handled silent failures in production, how you collaborate with hardware or autonomy engineers operating under very different constraints. Generic cloud architecture answers fall flat. Mention real constraints such as CPU budgets on embedded hardware, thermal throttling, cellular latency, and battery life, and explain how those constraints shaped your design decisions.
Choosing the right project for the presentation matters more than picking the most impressive-sounding one. Techprep.app advises selecting a project where you made a hard architectural decision and can articulate why you chose one approach over another. The panel wants to see the reasoning, not the resume highlight.
In 2026, interviewers began asking how candidates use AI coding tools like Copilot or Cursor. Being able to explain how you validate and debug AI-generated output, rather than just accepting it, registered as a positive signal. CEO Adam Bry put the hiring philosophy plainly: "the combination of the fire and passion to do hard things and then the horsepower to get it done." Potential and ceiling outweigh checklist experience.
Candidate reports from 89 interviews show 72 percent rate the difficulty as medium, 20 percent as hard, and 8 percent as easy. The aggregate offer rate in that dataset is 0 percent, a statistical artifact of the sample and not a promise, while InterviewQuery estimates that 3 to 5 percent of applicants ultimately receive offers. Recruiters generally share high-level feedback if you reach later stages, though detailed technical notes stay internal.
Where that loop lands you depends on which of Skydio's three sites you join.
Three Sites, Three Modes
Skydio's physical footprint maps directly to the three pillars of its operation: domestic manufacturing, core autonomy engineering, and a European research hub focused on the next generation of flight software. The company designs, assembles, and supports every aircraft in the United States, a fact it repeats across its own channels and job listings. That commitment anchors the Hayward facility. It also explains why the engineering center of gravity sits in San Mateo, and why the Zurich and Tampere offices were opened with a narrow, technical mandate.
Hayward: The Factory Floor
The manufacturing facility in Hayward, California spans 70,000 square feet and employs more than 200 operators, engineers, technicians, warehouse staff, and production planners. Skydio's own site describes it as the place where "we design, assemble, and support all of our products right here in the United States." A LinkedIn post from the company puts the figure at 60,000 square feet with a "team of 200+" — the discrepancy is minor; the scale and the domestic-only claim are consistent. This is where the X2, X2D, and Skydio 2/2+ Enterprise airframes come together. The floor houses final assembly, quality test, and the support logistics that keep customer flights running. Roles tied to this site, including supply chain, mechanical integration, and production test, require people who can move between a CAD model and a torque wrench without losing traceability.
San Mateo: The Engineering and Corporate Hub
Job postings on the Zero G Talent board cluster in San Mateo: Staff Software Engineer Full Stack, Staff Product Manager Vehicle AI, Director Global Supply Management Mechanicals, and multiple counsel roles all list the city as the work location. That concentration signals San Mateo as the primary corporate and software engineering campus. This is where the autonomy stack, cloud platform, fleet management tools, and integration APIs are built. It is also where the 45-integration catalog, spanning Drone as First Responder, CAD, and situational awareness partners, is maintained. The work here is almost entirely software and systems integration, but it stays tethered to hardware through the test engineers who split time between San Mateo labs and Hayward production lines.
Zurich and Tampere: Autonomy Research, Not Sales
Skydio's newest site is a research and development office in Zurich, Switzerland, opened as its second European R&D location and the first dedicated specifically to flight autonomy. The company's announcement and coverage from Europe Says describe the focus: autonomous multi-drone systems, GPS-denied navigation, and real-time edge computing. Greater Zurich Area's profile of the opening notes the office sits "at the heart of Europe's robotics hub" and targets "the next generation of autonomous flying robots." Notably, the Zurich team includes returning Skydio alumni — a signal that the company treats this as a deep-tech lab, not a sales outpost. The work enabled here feeds the core autonomy roadmap: swarming, denied-environment operation, and onboard compute that doesn't rely on a cloud link. Roles hired into Zurich will sit closer to ETH Zurich's robotics ecosystem than to any customer deployment.
Tampere, Finland, hosts the first European office, focused on embedded software and simulation infrastructure that supports the autonomy stack. The site leverages the region's dense robotics talent pool and university partnerships. Together, the two European offices extend the autonomy team's working day across time zones without handing off ownership — a distributed model built for depth, not coverage.
The Pattern
Three sites, three distinct modes of work. Hayward turns carbon fiber, PCBs, and firmware into a certified aircraft. San Mateo builds the software brain and the enterprise integrations that make the aircraft useful at scale. Zurich and Tampere push the autonomy frontier, covering multi-agent, denied-GPS, and edge-heavy capabilities that the next product line will require. The geographic split is not arbitrary; it mirrors the technical stack. Candidates should know which layer they want to operate in, because the day-to-day (cleanroom, IDE, or research lab) could not be more different.
Who Lasts
Skydio's employee reviews converge on a consistent profile: people who treat autonomy engineering as a craft, not a resume line, and who measure progress by whether a drone actually ships to a police department or a utility crew. Glassdoor's 2024 Best Places to Work recognition reflects a culture reviewers describe as "vibrant" and "filled with smart, friendly colleagues committed to impactful projects." Indeed reviewers add it's "a great place to work if you want to work hard and join a team of dedicated and intelligent employees," with the caveat that "you are responsible for your own work."
That ownership expectation appears repeatedly. The company's public messaging, "Serving the most pressing needs of the industries our civilization runs on," maps to deployments where 30-second response times for Brookhaven PD, 60% faster inspections for ODOT, and flare monitoring for LNG Canada are the daily reality. Engineers who thrive here tend to have already worked on systems where software meets physics: computer vision pipelines that must run on embedded compute, state estimation that fails safely when GPS drops, planning stacks that handle dynamic obstacles at speed. The interview process selects for this blend of depth and breadth, but the day-to-day filters for it again: a perception engineer who can't explain their validation strategy to a hardware lead won't last.
Collaboration at Skydio is cross-functional by necessity. The X10 platform integrates multiple sensor types with an autonomy stack that runs on embedded compute. That integration forces perception, planning, controls, and firmware teams to share a common vocabulary — coordinate frames, latency budgets, failure modes. Reviewers who mention "cliquish" dynamics on Glassdoor often describe silos forming when teams stop speaking that shared language. The people who stay are the ones who reach across the boundary.
Mission alignment acts as a retention filter. The customer roster, including NYPD, Oklahoma City PD, CalTrans, Dominion Energy, American Electric Power, and U.S. Border Patrol, means every release touches public safety or critical infrastructure. Employees who cite "impactful projects" as a motivator tend to have prior experience in defense, aerospace, or regulated industries where the cost of failure is measured in lives or millions of dollars. They're comfortable with the rigor that entails: extensive documentation, hardware-in-the-loop test campaigns, time in the field with operators who don't care about your architecture — they care that the drone comes home.
The counter-signal is worth noting. Glassdoor reviews flag management inconsistency and occasional cliquishness. That suggests the environment rewards self-starters who can navigate ambiguity without waiting for a perfectly structured onboarding. The "responsible for your own work" refrain cuts both ways: autonomy in the cultural sense mirrors autonomy in the technical sense. If you need a ticket assigned, a spec frozen, and a standup to unblock you, the pace will frustrate you. If you treat an underspecified problem as an invitation to prototype, validate, and ship, the trajectory is steep.
In practice, the longest-tenured engineers share three traits: they've shipped robotics products that touched dirt, they write code that survives contact with hardware, and they can explain a failure mode to a non-technical stakeholder without jargon. The company's growth, with five million customer flights and counting, means the next hire will face harder integration challenges, not easier ones. The people who thrive are already preparing for them.
Working in frontier tech? Zero G Talent tracks the openings: see every open Skydio role, browse frontier tech jobs, the companies hiring, and the people building the field.