UAS Support Engineer
Generate a McCoy IQ challenge in 30 seconds.
See how candidates think and approach the work this role demands, before the phone screen. We'll build a video challenge from this posting, and you can edit or share it before it goes live.
Key details
Job Description
The Problem
As Flock expands our fleet of autonomous Unmanned Aerial Systems (UAS) and docking infrastructure, ensures 24/7 critical field reliability requires high-integrity hardware-software integration. Operating in unpredictable real-world environments without constant on-site oversight means our drones and ground stations rely on seamless radio connectivity, pristine battery systems, and immediate diagnostic triage. You will serve as the technical bridge between field operations and core engineering by diving into telemetry, leading hardware bring-up, and ensuring field data directly drives our next generation of autonomous hardware.
What You'll Own
Diagnose & Triage Complex Fleet Issues
Telemetry & Analytics Monitoring in post-flight telemetry using diagnostic tools like Foxglove and Grafana, establishing performance KPIs and real-time visibility dashboards for vehicle heartbeats.
Hardware Bring-Up & Field Validation by leading hands-on bring-up, QA testing, and field validation of new docking hardware and drone airframes using industrial automation principles to ensure round-the-clock reliability.
Engineering Feedback Loops by translating edge-case hardware failures and signal into clear, actionable bug reports and design feedback for the core Engineering team.
Maintenance & Support Playbooks by developing, maintaining, and continuously refining preventative inspection schedules, technical SOPs, and troubleshooting guides to scale our global fleet capabilities.
What This Role is Not
This isn't a desk-only or purely remote role. You will work hands-on with physical hardware at our Atlanta facility and deploy directly to client sites (up to 25% travel).
This is not a high-level software development job. You won't write core drone flight software, build cloud platforms, or engineer embedded firmware from scratch; your focus is deep technical triage, telemetry analysis, and hardware-system integration.
This isn't a transactional help-desk ticket pusher. You are an engineer who owns the technical lifecycle, failure mode analysis, and continuous feedback loop between live operations and design teams.
What You Bring
Education & Background: Bachelor’s Degree in Mechanical Engineering, Electrical Engineering, Robotics, or proven hands-on experience in the UAS/Robotics space.
Domain Experience: 3+ years troubleshooting and maintaining Unmanned Aerial Systems, including multi-rotor flight hardware and autopilot firmware.
Diagnostics Stack: Hands-on proficiency with hardware diagnostic tools (Multimeters, Oscilloscopes) and telemetry/monitoring suites (Grafana, Foxglove, or similar).
Communication & RF Infrastructure: Deep familiarity with GPS, LTE, RF communications systems, and signal strength/throughput troubleshooting between UAS hardware and ground infrastructure.
Technical Translation: Strong written and verbal communication skills with a proven track record of converting complex hardware failures into clean engineering documentation.
Nice to Haves: Working knowledge of radar systems, familiarity with Battery Management Systems (BMS) and safe handling of Li-ion chemistries, and an FAA Part 107 Remote Pilot Certificate (required upon hire).
Logistics
Location & Travel: Onsite at our Atlanta-based manufacturing facility for hands-on collaboration, with up to 25% travel expected to client sites.
Compensation
In this role, you'll receive a starting salary between $100,000 and $140,000 as well as Flock Stock Options. Base salary is determined by job-related experience, education/training, as well as market indicators. Your recruiter will discuss this in depth with you during our first chat.
Why Flock 💚
Every community deserves to be safe. Flock builds the technology that makes that real: last year we supported over 1 million criminal investigations and helped locate more than 10,000 missing people. We're 1,700 people building the impossible with over $1B in funding, and the expectations are high on purpose. If you want a role where the stakes are real and the pace matches, this is it.
📍Some problems get solved faster in the same room, so we prioritize candidates in Atlanta and Boston. Hub-based roles mean real in-person time with your coworkers. Remote roles exist, and when a posting is open to remote work, it says so.
🌟 the impossible takes every kind of mind. Flock is an equal opportunity employer, and we know the best solutions come from diverse perspectives, experiences, and skills working together with mutual respect. Everyone is welcome to apply. If you need assistance or an accommodation due to a disability, email recruiting@flocksafety.com; your information stays confidential and is used only to arrange the right accommodation for your interviews.
💰 On compensation: we pay fairly for the work. Base salary is determined by job-related experience, education, training, and market indicators. The range in this posting covers base salary only and doesn't include equity, sales bonus plans where applicable, or benefits. The range may be adjusted over time, and this posting may span more than one career level.
📣 One last thing: all legitimate communication from Flock comes from an email ending in @flocksafety.com or noreply@ashbyhq.com. We never make offers through messaging apps or third parties, and we never request payment or sensitive personal information during hiring. If you encounter suspicious outreach about a Flock role, report it to recruiting@flocksafety.com.
Audit details(provenance, verification trail, raw fields)
Core fields
flock-safety:d892914b-8120-4bde-a90a-25416dfc017dProvenance
Flock SafetyVerification trail
- confirmed_closed2026-07-07 19:23:56Zvia ashby
evidence
{ "id": "d892914b-8120-4bde-a90a-25416dfc017d", "slug": "Flock Safety", "signal": "graphql:jobPosting:null" }
See how we measure for definitions, or our corrections log for known issues. Found something wrong? Flag a correction.
