# Inside Neros Technologies’ Interview Loop for Drone Engineers

Source: https://www.techinterview.org/post/3233477537/neros-technologies-interview-guide/
Updated: 2026-10-01 · techinterview.org

Neros Technologies is a Torrance, California defense company that mass-produces low-cost FPV attack drones (Archer) and is building out autonomy (Archer AI) and a counter-drone interceptor (Bandit). Its engineering interview is not published anywhere, so the loop below, a recruiter screen, a hiring-manager technical call, a discipline-specific team panel, a practical build or design exercise, and a mission-and-ownership round, is reconstructed from Neros's own public job postings and from how comparable defense-hardware startups hire, not from a leaked script. The hard gate is eligibility: every ITAR-controlled role requires you to be a "U.S. person," and most work is on-site in Torrance. Unlike most startups its age, Neros posts real salary ranges because California law requires it; one Torrance Senior Firmware Engineer req lists $195,000 to $273,000, so read the band on the specific job rather than an aggregator's guess.

This is Neros Technologies, the Torrance, California drone maker at neros.tech (not Nero AG, the German Nero Burning ROM software maker), founded in 2023 by former competitive FPV racers Soren Monroe-Anderson and Olaf Hichwa.

What Neros builds shapes the whole interview, so start there. Archer is a first-person-view attack drone designed to be cheap, NDAA-compliant, and buildable at scale without Chinese components, the kind of expendable system that has reshaped the war in Ukraine. On top of it the company is adding Archer AI, an autonomy layer with features like terminal guidance and GPS-denied position hold, and Bandit, a high-speed interceptor meant to knock down Class 2 and 3 threats including Shahed-style attack drones. The Torrance factory is sized to build a million drones a year, and the company has said it already turns out about a thousand a week. That combination, throwaway hardware at volume plus a real autonomy push, is why Neros hires across electrical, firmware, embedded, autonomy, software, and manufacturing at once.

The money is why this loop is worth preparing for now. In August 2026 Neros [raised a $250 million Series C at a $2.5 billion valuation](https://www.neros.tech/articles/neros-raises-250m-series-c-at-2-5b-valuation-to-scale-autonomous-and-interceptor-drone-programs), co-led by Sequoia Capital and the American Strategic Technology Fund, roughly tripling its valuation from under a year earlier and landing months after the U.S. Army awarded it a [framework contract worth up to $500 million](https://www.defensedaily.com/neros-500-million-army-deal-could-cover-hundreds-of-thousands-of-archer-fpv-drones/army/) for Archer drones. It rides the same 2026 defense-tech wave as Anduril, Castelion, and True Anomaly, and the closest comparable in hiring shape is [Mach Industries](/companies/mach-industries-interview-guide/). If you are weighing several of these bets, the broader set of [company interview guides](/companies/) puts them side by side.

## Why the bar is "can you own a subsystem"

A drone built at rate has to come off the line cheaply, survive the field, and increasingly fly and strike with less human input, so the engineers Neros is shortest on are the ones who can own a whole piece of that: a flight-software stack, a power board, a perception pipeline, a motor line. The company calls this role a "responsible engineer," effectively a senior-plus individual contributor who owns a system or subsystem outright, and per a [Sourcery profile](https://www.sourcery.vc/p/breaking-inside-neros-factory) it historically ran only a handful across the entire Archer program. The job board reflects that: it skews senior, with no intern or new-grad postings up. Scaling three product lines at once stretches those owners thin, which is the biggest thing the interview screens for, so an interviewer wants to watch you take an underspecified hardware or autonomy problem and drive it to something that both works and manufactures.

By discipline: firmware and embedded roles lean on real-time behavior, flight software, sensor integration, and C or C++ (sometimes Rust) on constrained hardware; electrical covers PCB design, power, RF, and components sourcing under a no-China supply-chain rule; autonomy covers perception, state estimation and navigation, and holding or guiding a vehicle when GPS is jammed; software covers the ground and platform systems that command fleets and move telemetry, where [Go](/post/3233474456/go-golang-interview-questions-2025-goroutines-channels-interfaces-error-handling-context-generics-concurrency-patterns/) and Python show up; manufacturing covers design-for-manufacturing and process work that keeps a line running past a thousand units a week. A small set of flight-facing roles, FPV Specialist and Test Pilot, rewards real stick time.

## The interview loop, round by round

Neros has not published its hiring process and there are almost no public candidate reports, so the structure below is pieced together from its public Greenhouse postings and from how comparable defense-hardware and autonomy teams tend to run their loops. Read it as an informed sketch, not an official script. Plan for roughly four to six touchpoints concentrated on the team you would join, and a fast process given the production ramp.

| Stage | Likely format | Who runs it | What it likely screens for |
| --- | --- | --- | --- |
| Recruiter screen | ~30 min phone | Recruiter | ITAR U.S.-person eligibility, on-site willingness, mission motivation, resume walk |
| Hiring-manager technical call | ~45-60 min video | Team lead you would report to | Depth in your discipline, how you reason about a real problem, ownership of past work |
| Discipline team panel | On-site, half to full day | Engineers on the team | First-principles design and tradeoffs; coding for software and firmware, design review for hardware, DFM for manufacturing |
| Practical exercise | Whiteboard, live build, or short take-home | Team | Working code, a back-of-envelope sizing, or a process plan |
| Mission and ownership | ~45 min | Founder or senior leader | Why defense, bias to ship, comfort with pace and ambiguity |

The on-site panel is likely where most offers are won or lost, and it changes shape by discipline. Firmware and embedded candidates should expect practical coding plus real-time and sensor questions, with the bar being clean, correct code and clear reasoning about timing, interrupts, and what happens when a sensor lies to you. Software and platform candidates are the more familiar case for this site's readers: expect backend system design, commanding a drone fleet and moving telemetry at scale, alongside practical coding, so the [system design interview guides](/system-design-interview-guides/) hub is the right warm-up. A competitive-programming grind is the wrong preparation across the board; refreshing the core [coding patterns](/algorithm-patterns-cheat-sheet/) covers the algorithmic slice, and a short [study plan](/study-plan/) keeps it from swallowing your whole prep window.

Autonomy candidates get pushed on perception, state estimation, and how a vehicle holds position or guides to a target once GPS is denied, the exact problem Archer AI solves. That work today is more classical estimation and guidance than deep learning, with the funded R&D pushing toward learned perception and multi-drone swarming, so both estimation and ML backgrounds are in scope; if yours is self-driving rather than aerial, the [Applied Intuition](/post/3233477460/applied-intuition-interview-guide/) and [Waymo](/post/3233476865/waymo-interview-loop-safety-round/) loops drill the same skills. Hardware candidates face a design review anchored to something they actually built: why you sized it that way, what failed, what you would change. Manufacturing candidates get asked how they would hold a thousand-a-week line and where a design fights the process. Whichever track you are on, an interviewer will keep pressing on your tradeoffs, and revising an answer under that pressure reads as a strength.

## The screen that has nothing to do with engineering

Before any technical round matters, there is a hard eligibility gate, and Neros states it plainly in its postings: the hire "will have access to information and items controlled by the International Traffic in Arms Regulation (ITAR), and, therefore, must be a 'U.S. Person' or otherwise eligible to receive an export license." The same postings define a U.S. person to include citizens, noncitizen U.S. nationals, lawful permanent residents (green-card holders), and certain other classes such as asylees and refugees. If you are on a visa and would need sponsorship, Neros cannot put you into an ITAR-controlled role right now no matter how strong your engineering is, which is why the recruiter raises eligibility first. Some defense roles add clearance requirements on top of ITAR, and Neros does not attach a clearance gate to every posting, so confirm which applies to the specific job.

Location is the other fixed constraint. Most engineering roles sit in Torrance and are on-site, with a smaller presence in Tennessee, Washington D.C., and overseas (including a Ukraine office). Building drones at rate is a physical, in-the-factory job, so if relocating to the Los Angeles area or working next to a production line will not work for you, settle that before you spend a loop finding out.

## How to read the comp

Neros is more transparent on pay than most startups its age, a side effect of California law, which forces the real ranges onto the individual job listings. One Torrance [Senior Firmware Engineer, Platform req](https://job-boards.greenhouse.io/nerostechnologies/jobs/5195308007) posts $195,000 to $273,000; other firmware, embedded, and test reqs list their own, lower bands by level and discipline. Open the specific job you want and read its range rather than trusting a blended figure or an aggregator estimate.

Base is only part of the picture at a company that just tripled its valuation; the equity is where the upside sits and the part candidates most often misprice. Run any offer through a [total-comp calculator](/total-comp-calculator/) that values the grant against the current valuation and your vesting rather than treating its headline as cash, and the mechanics in a solid [salary-negotiation walkthrough](/post/3233474669/salary-negotiation-2026/) apply once you have an offer. If a grant is repriced after a markup, the option strike price can matter more to your outcome than a few thousand dollars of base, so ask about it.

## How to prepare

Lead with the mission and be specific about your own work. Neros wants people who genuinely want to build weapons for national defense and can say why without flinching or reaching for slogans, so have a real answer to why this and why now. Then pick one or two projects you can defend for forty-five minutes: the constraints, the tradeoffs you chose, the numbers, and what you would do differently. A loose claim of "ownership" collapses fast under follow-ups from an engineer who has shipped the real thing, so bring something you drove, a flight-controller firmware build, a power board you spun, an autonomy capstone, even a serious FPV racing rig, and know every decision in it.

Then prep by track: firmware and embedded candidates drill practical coding and sharpen real-time, sensor, and flight-software fundamentals; software candidates rehearse backend system design for fleet command and telemetry alongside coding; autonomy candidates reason about perception and GPS-denied navigation from first principles; hardware candidates rehearse sizing and defending a design; manufacturing candidates get concrete about rate production and DFM. The mission-and-ownership round is a real filter on pace and judgment, so shape two tight stories with the [STAR method](/post/3233460379/behavioral-interview-questions-2026-star-method-amazon-leadership-principles-and-winning-answers/) instead of winging them, and put your resume through a [resume checker](/resume-checker/) first, since a hardware resume with quantified results reads very differently from a generic software one.

The job is standing up a drone industrial base the United States did not have three years ago, shipping cheap autonomous aircraft by the thousand under export-control rules that shrink the hiring pool to U.S. persons willing to be in a Torrance factory. The interview is tuned to find people energized rather than drained by that. If the idea of your firmware or perception stack flying on a weapon system sounds like the work you have been waiting for, Neros is one of the few places hiring for exactly it right now.