Hermeus is trying to do something no one has done at rate: build an aircraft that will fly past Mach 5, land, and fly again. That reusability is the whole difference between it and the hypersonic-missile companies it gets grouped with. A missile is expendable, so its structure only has to survive one flight. An airframe that comes home and turns around for another sortie has to hold aerothermal and structural margin across many flights, which is a harder materials and design problem, and it shapes who they hire. Per the Series C release, the program is pre-supersonic today: the Quarterhorse Mk 2.1 demonstrator has flown, supersonic is next, then Mach 3, with Mach-5 reusability the longer-term target. The work you would join now is flight-test iteration toward those milestones.
The money is why this loop is worth preparing for right now. In April 2026 Hermeus closed a $350 million Series C that reached a $1 billion valuation, split into roughly $200 million of equity led by Khosla Ventures and about $150 million of debt, with Founders Fund, RTX Ventures, and In-Q-Tel among the investors. TechCrunch reported the staff was already approaching 300 employees, and the raise funds hiring and production. It rides the same 2026 defense-tech wave as Anduril and Castelion, so if you are weighing several of these bets, the broader set of company interview guides gives context.
What a reusable Mach-5 airframe demands of you
Read the product as an engineering brief and the interview follows from it. The signature problem is propulsion. Flying from a standstill to hypersonic speed on one vehicle means an engine that starts as a turbojet and hands off to ramjet operation at high Mach, and getting that transition to work is the thing Hermeus has spent years on. Around that sit the problems any high-speed reusable vehicle has: aerothermal loads that would melt a poorly designed leading edge, structures that survive repeated thermal cycling, guidance and control at speeds where small errors compound fast, and, for the uncrewed Darkhorse, flight autonomy, which here leans on classical GNC and deterministic mission logic more than learned, ML-based control policies.
So interviewers care less about whether you have memorized an algorithm and more about whether you can reason from physics and constraints toward a design that flies and survives the flight home. For hardware and aero roles that means thermodynamics, gas dynamics, structures, or GNC reasoning done out loud, usually anchored to something you built. For software it means embedded and flight-adjacent work: real-time systems, hardware-in-the-loop testing, ground and test software, controls, and simulation, not web CRUD. The common thread is ownership of an ambiguous problem, and the loop filters hard against people who need a fully specified ticket before they start.
Where you fit: the role families
Openings cluster into a few groups, and which one you are interviewing for tells you what the discipline round looks like. Flight software, embedded, and controls engineers work on the code that flies the vehicle and the software that tests it on the ground. Propulsion, aerodynamics, and thermal engineers own the engine transition, the airframe, and the heat. GNC and autonomy engineers handle guidance, navigation, control, and Darkhorse’s uncrewed mission logic. Manufacturing and test engineers push prototypes toward repeatable production, which for a reusable vehicle also means turnaround and inspection between flights. The bar across all of them is first-principles reasoning about real systems, not LeetCode volume.
A reconstructed view of the loop
I checked Glassdoor and a few interview aggregators for candidate reports. There is some real signal (a short HR screen, then a technical round anchored hard to your resume) but not enough to map a full loop, so the table below blends that with the standard ex-SpaceX aerospace process rather than an official script. Expect roughly four to six touchpoints weighted toward the team you would join. On wall-clock time, candidate reports on Glassdoor put the average process near 37 days across a small number of reports, though engineering roles run much longer, up to roughly six months.
| Hermeus interview stage | Format and length | Who runs it | What it screens for |
|---|---|---|---|
| Recruiter screen | ~30 min phone | Recruiter | U.S.-person/ITAR eligibility, mission motivation, on-site and relocation willingness, resume walk |
| Hiring-manager technical call | ~45-60 min video | Team lead you would report to | Domain depth, how you reason about a real problem, ownership of past projects |
| Discipline round | On-site panel, half to full day | Engineers on the team | First-principles design and tradeoffs; coding for software, design review for hardware/aero, process for manufacturing |
| Practical exercise | Whiteboard or short take-home | Team | Concrete problem-solving: a coding problem, a sizing calculation, or a test/production plan |
| Mission and pace | ~45 min | Founder or senior leader | Why defense, why now, bias to ship, comfort with pace and ambiguity |
The discipline round is where most candidates pass or fail. Software candidates should expect practical coding at a data-structures level plus embedded and real-time questions; the bar is clean, correct code and clear reasoning about timing and failure behavior, not exotic dynamic-programming puzzles. Reviewing the core coding patterns covers the algorithmic slice, and a short study plan keeps that from eating your prep budget, because the flight-software and hardware-in-the-loop conversation matters more here than raw LeetCode. Representative prompts for this kind of loop run along these lines:
- Embedded/real-time: “You have a 1 kHz control loop that must never miss its deadline. How do you schedule it, and what do you do when a sensor read comes back late or corrupt?” and “How would you ingest high-frequency telemetry from the engine during a test without dropping samples?”
- Aero/thermal design review: “Size the thermal margin on a wing leading edge for a sustained Mach 3 pass. Give me a rough heat-flux estimate, the material you would pick, and where your margin comes from.”
- Manufacturing and test: “The vehicle just flew once. Walk me through inspection and turnaround before it flies again, and tell me where that fights a decision made in the original design.”
Expect someone to push until you defend your reasoning with numbers or revise it; revising under pressure is a good sign.
The ITAR gate, and where Hermeus is
Before any technical round matters, there is a hard eligibility gate. The engineering work involves export-controlled technical data and defense articles under ITAR, so almost every role requires you to be a U.S. person: a citizen, national, lawful permanent resident, refugee, or asylee. Some roles go further and require the ability to obtain a security clearance, which is a separate and narrower gate. The distinction between ITAR “U.S. person” status and an actual clearance trips a lot of candidates up, and the Castelion interview guide walks through it in detail, so if you are unsure which one applies to you, read that before you burn a loop. If you are on a visa and need sponsorship, Hermeus cannot hire you right now regardless of how strong your engineering is, and the recruiter screen confirms that fast.
Location is the other early filter. Per the Series C announcement, Hermeus is moving its headquarters to El Segundo, California, with the Atlanta site shifting toward production. Roles are on-site by default, and flight-test work adds travel. This is a build-and-fly-hardware company, not a remote one, so if relocation or long hours are dealbreakers, sort that out before you invest in the loop. That puts Hermeus in the same Southern California defense-hardware cluster as Anduril, and if you are running parallel processes, the Anduril guide, the SpaceX guide, and the True Anomaly guide help calibrate how these loops differ.
Reading the comp without a number to anchor on
There is no reliable public levels.fyi figure for Hermeus yet, so any precise total-comp number you are quoted is a guess. California pay-transparency law means the actual base range is printed on the El Segundo job listings themselves, so read the range on the specific req, not a blended average. Atlanta and other-state reqs may not carry a posted range, so for those you are comparing against the broader market for ex-SpaceX aerospace and defense startups, which tend to pay competitive base with meaningful early-stage equity and lighter cash bonuses than big tech.
The part most people misjudge is the equity. At a company that just marked a $1 billion valuation, the strike price and dilution math matter as much as the headline base. Run any offer through a total-comp calculator so the equity is valued realistically against the current valuation and your expected vesting. When the number comes back, the mechanics in a good salary-negotiation walkthrough apply here as much as anywhere.
How to prepare
Come in fluent in the mission and specific about your own work. Hermeus screens for people who want to build fast military aircraft and can say why without either flinching or sloganeering, so have a real answer to why defense and why now. Then bring one or two projects you can go deep on: what you built, the constraints, the tradeoffs, and what you would do differently. Vague ownership claims fall apart fast in that round. Postings skew toward experienced engineers, but the bar favors demonstrated hands-on building, so a serious rocketry or Formula SAE project or an internship where you owned real flight software or hardware can count, provided you defend the decisions the way a senior would.
The mission round is a genuine filter on pace and ownership, so prepare a couple of tight stories. If your ownership stories tend to ramble, the STAR-method structure keeps them to the point, and running your resume through a resume checker first is worth it, because a flight- or hardware-heavy resume with quantified results reads very differently from a generic software one.
Hermeus is not hiring you to optimize a known system. It is hiring you to build one that does not exist yet, an aircraft that will fly past Mach 5 and come home to do it again, under real security constraints and on a timeline that assumes you move fast. The loop is designed to tell you whether that is the best job you could have or the worst.
Practice the behavioral round:
