Saronic closed a $1.75 billion Series D at a $9.25 billion valuation at the end of March 2026, and it is trying to hire hundreds of engineers in Austin to get autonomous boats into the water for the U.S. Navy. The interview loop mirrors that urgency. It runs fast, it stays unusually friendly for defense tech, and it leans hard on whether you can build and ship a working system rather than whether you can recite Dijkstra from memory.
Founded in 2022 by former Navy SEAL Dino Mavrookas and Doug Lambert, Saronic builds autonomous surface vessels, the small and mid-sized uncrewed boats the Pentagon wants in volume under the Replicator initiative. The current lineup runs from the roughly six-foot Spyglass up through Cutlass and Corsair to the much larger Marauder. The pitch to candidates is physical and specific: the company owns its shipyard, writes its own autonomy stack in Rust and C++, and expects to be turning out more than twenty vessels a year by 2027. If you want your code steering something real within a few months of writing it, that is the reason to look.
The loop, round by round
Most candidates describe a four-stage process that wraps in one to two weeks, which is quick by any standard and very quick for a company doing government work. A recruiter reaches out or responds, you do a technical screen or two, you present a past project, and you come onsite. Offers tend to land within days of the final round.
| Stage | Format | Typical length | What Saronic is checking |
|---|---|---|---|
| Recruiter screen | Call covering background, why defense, logistics, work authorization | 15 to 30 min | Mission fit, US-person status, team and level match |
| Technical screen | One or two medium coding problems in a shared editor | 45 to 60 min | Data-structure fluency, speed, clean code under a clock |
| Project presentation | You walk through a hard technical problem you personally owned | 45 min | Technical depth, real ownership, ability to defend choices |
| Onsite loop | Three back-to-back interviews plus a floor and dock tour | 3 to 4 hrs | System design, more coding, behavioral, physical-world judgment |
The recruiter screen is the one place work authorization comes up early, and it matters more here than at a typical startup. Saronic builds hardware for the U.S. military, which puts most engineering roles under ITAR. In practice the company hires US persons, meaning citizens or green-card holders, and some roles will eventually need a security clearance. If you are on a visa, ask about your specific role before investing time. It is not a reflection on you, it is export-control law, and a good recruiter will tell you straight.
What the coding round actually looks like
The technical screen is standard medium-difficulty algorithm work, delivered at a brisk pace. Candidates report two problems in 45 minutes, which tells you the bar is speed plus correctness, not a single hard puzzle you agonize over. Expect arrays, hash maps, intervals, and string parsing. The interviewers are described as friendly and willing to nudge, so talking through your approach out loud pays off more than silent brilliance.
The framing often carries a maritime or telemetry flavor, even when the underlying problem is a classic. A few examples in the spirit of what gets asked:
- Given a stream of sensor timestamps, find the longest window in which no reading arrived.
- Merge overlapping intervals of vessel activity into consolidated operating windows.
- Parse a nested config and return the value at a dotted path like
autonomy.planner.max_speed. - Rate-limit outbound telemetry to N messages per second while always keeping the newest message.
None of that is exotic. The gaps-and-windows question is a sliding window. Merging activity is the interval-sort pattern. The rate limiter is a token bucket or a fixed-window counter, and if you know why the sliding-window variant avoids the boundary burst, say so. Write real code, handle the empty input and the single-element case without being reminded, and state your time and space complexity before they ask.
The project presentation is where offers are won
The 45-minute presentation is the round people underprepare for, and it carries a lot of weight. You pick a technical problem you owned end to end and walk a couple of engineers through it. They will interrupt. They want the messy parts: the constraint that forced a rewrite, the tradeoff you got wrong the first time, the thing that failed in production and what you changed.
Pick a project with real engineering tension, ideally one touching systems, embedded, data pipelines, or anything with a physical or real-time component. A CRUD app with a clean Kanban board will not land. A story about a control loop that missed its deadline under load, or a data pipeline that silently dropped messages until you added backpressure, will. Come with numbers. How many messages per second, what the latency budget was, how you measured it, what broke at the tail. Saronic is a hardware company at its center, and it screens for people who reason about failure modes in the physical world, where a passing test suite is not the finish line.
System design and the autonomy stack
For senior software and infrastructure roles, one onsite slot is system design, and the prompts skew toward fleet operations rather than consumer scale. You are more likely to design the telemetry backbone for two hundred boats over intermittent radio links than to design Twitter. Prompts that fit the domain:
- Design the pipeline that ingests, stores, and serves telemetry from a fleet of autonomous vessels, some of them offline for hours.
- Design a way to push a new autonomy model to boats at sea safely, including rollback when a boat is mid-mission.
- Design the ground-station software an operator uses to monitor and override a squad of vessels in real time.
The reasoning they reward looks different from a web system-design answer. Intermittent connectivity is the default, not an edge case. A boat can lose its link for an hour and has to keep operating safely on its own, then reconcile when it reconnects. Over-the-air updates cannot brick a $500,000 vessel forty miles offshore, so you talk about staged rollout, health checks, and automatic rollback. Bandwidth is scarce, so you prioritize what telemetry goes over the link first. If you have worked on IoT, robotics, or anything with unreliable networks, lean on that experience.
Autonomy and embedded roles go deeper on the low-level stack. Saronic writes performance-sensitive code in Rust and C++, so expect questions on the memory model, why the borrow checker rules out a whole class of concurrency bugs, and how you would avoid heap allocation in a hot control loop. Sensor fusion comes up for perception work: how you combine GPS, IMU, radar, and camera data when one sensor drops out or feeds you garbage. Real-time constraints are fair game too, including how you keep a control loop deterministic and what a watchdog timer is actually protecting you from.
Behavioral, and why they ask about the mission
The behavioral questions are ordinary STAR territory: a time you disagreed with a teammate, a project that slipped and how you handled it, the hardest bug you chased down. What is less ordinary is the weight placed on why you want to be here. Saronic is a defense company, and the people who do well there tend to have a real reason to build for the military rather than a passing interest. You do not need a flag-waving speech. You do need a coherent answer to why this problem and why now that survives a follow-up question.
They also probe for comfort with ambiguity and speed. This is a company scaling from a few hundred people toward thousands while shipping hardware on Navy timelines. Stories where you moved fast with incomplete information, owned a decision without a committee, and cleaned up your own mess land better than stories where the process was perfect.
Compensation and the equity question
Saronic does not publish comp, and the numbers move as the company grows, so treat any figure you see as a starting point to verify. Austin base salaries for experienced software engineers sit in a competitive range for a venture-backed startup, generally below the very top of FAANG cash but not far off. The real story is equity. A company that climbed to a $9.25 billion valuation this fast means early and mid-stage grants have already appreciated, and the pitch to new hires rests on the next leg of that curve. Ask for the strike price, the current preferred price, the total shares outstanding, and the vesting schedule, then do your own math. Check Levels.fyi and Built In Austin for reported ranges, and remember that a private-company grant is a bet, not a bank balance.
One practical note for anyone weighing an offer: defense-tech equity is illiquid and the exit timeline is uncertain, IPO chatter aside. Weigh it against your risk tolerance and your read on the company, not against a headline valuation.
How to prepare without overthinking it
Grind medium problems on arrays, hash maps, intervals, and sliding windows until 45 minutes for two of them feels comfortable, because the pace is the hard part, not the difficulty. Rehearse your project talk out loud, timed, with the numbers memorized and a clear answer to what you would do differently. If you are targeting autonomy or embedded, be ready to write and reason about Rust or C++ in the room rather than describe them from memory, and hold a real opinion on determinism, memory safety, and failure handling. And come with a genuine answer to why defense, because the engineers who get the most out of Saronic are the ones who wanted to put something real in the water to begin with.
Practice the behavioral round:
