Anduril interview, and the question that comes before the code.

Anduril decides two things before it looks at your code. The first call confirms that you can work on export-controlled defence systems at all, which means a US citizen or lawful permanent resident, with a security clearance or the eligibility to get one for about half of the open roles. The second is whether you have a real reason to build weapons and sensors for a living, and the question is asked on the recruiter screen and again by a senior leader in the last hour. The technical loop after that is fast and practical: a coding screen whose prompt is underspecified on purpose, then a final round of about four hours where each problem grows new constraints as you solve the last ones. Candidates report replies the next day and an offer within three to four weeks.

Will I get shortlisted at Anduril? →Run a free mock interview →

Both are free. Either one starts by pasting an Anduril posting: that is what makes the read and the questions Anduril’s rather than generic.

01

Who Anduril hires

Different tracks, one bar

Anduril hires across software, hardware and deployed roles at a pace few companies match, with hundreds of open requisitions at any time and a headcount that nearly doubled through 2025. Software covers perception, backend and ML infrastructure, autonomy and the Lattice platform; hardware covers mechanical, electrical, embedded, thermal and manufacturing engineering for products such as Ghost, Altius and Roadrunner; mission software engineers are cleared engineers who travel to customer sites. What every track favours is depth in a domain over breadth, engineers who own a problem end to end and ship under real constraints, and a considered answer to why this work. Roles are restricted to US persons because the work falls under ITAR and export controls, and visa sponsorship is not offered for them.

The software loop is the best documented and the one most accounts describe. Hardware roles run a different sequence with a technical presentation, and mission roles add the clearance and travel. The process is division specific, and candidates who have sat it say the recruiter is the only reliable source for the shape of yours.

  • Track · Software

    Software engineering, all domains

    A recruiter screen, a 60-minute coding screen on HackerRank, then a final round of about four hours: two coding sessions, one object-oriented or system design session, and one behavioural conversation with a senior leader. The coding prompts are multi-phase: a simplified problem first, then the constraints shift, and working code across each phase matters more than complexity analysis. Embedded software in the drone division is reported as domain-heavy rather than algorithmic.

  • Track · Hardware

    Mechanical, electrical, embedded and manufacturing

    Accounts on Glassdoor describe a recruiter call, two conversations with chief engineers, then an onsite built around a technical presentation of your own work and five or six individual interviews. Electrical candidates report three to five rounds over two to four weeks: fundamentals for 45 minutes, hardware design and power electronics for 45 to 60, a behavioural and project deep dive, and a panel or system discussion. Mechanical and structural rounds go at mechanics of materials, GD&T, composites, DFM, lamination and buckling; thermal rounds at electronics cooling under environmental constraints.

  • Track · Mission

    Mission software engineer, deployed

    The company's own engineers with a clearance who travel to customer sites. The loop is the software one with the clearance questions carrying real weight, and a cleared role takes six to eight weeks rather than the four an uncleared one takes. Where a role sponsors a clearance, candidates describe a conditional offer followed by three to nine months in interim Secret status before final adjudication.

02

What is the Anduril interview process?

Round by round

The published accounts agree on the software shape and disagree on the details, and they say so themselves: one recent guide states plainly that candidate experiences do not support a single universal Anduril sequence or timeline. One account has two engineers on the coding screen, another has one; one final round has four sessions, another three. What more than one account reports is below. Timing is the predictable part: candidates describe hearing back the day after each round, first contact to offer in three to four weeks for an uncleared role, an average of 28 days from recruiter screen to offer, and six to eight weeks where a clearance is involved.

01
Recruiter screen
30 to 60 minutes by phone or video

Your background, which area you want to build in (perception, backend infrastructure, ML infrastructure or ML), your motivation for defence work specifically, and the eligibility questions: citizenship or permanent residence, and whether you hold or could obtain a clearance. Product awareness is noticed here.

02
Technical phone screen
60 minutes on HackerRank, with one or two engineers

A deliberately ambiguous prompt in phases. You solve a simplified version, then the constraints change, and clarifying the requirements is part of what is graded. Reported problems include a football team photo arrangement one candidate was told was confusing on purpose, and graph cycle detection. Time and space complexity matters less than usual; working code across each phase matters more.

03
Coding, two sessions
60 minutes each, in a final round of about four hours, virtual or in person

Collaborative problems that layer on constraints as you go, with no formal test gates between phases. One reported sequence: the shortest distance between two points, then obstacles blocking the direct path, then the shortest path around them. Others involve a collection of robots with task prioritisation, drone management, and graph manipulation. Difficulty sits at a practical LeetCode medium.

04
Object-oriented or system design
60 minutes

Anduril expects you to write the classes and interfaces rather than talk about them: a data structure or component from scratch, such as a doubly linked list with insert, delete and search, graded on decomposition, edge cases and how you respond to a refactor. System design ranges from a URL shortener or Tetris to lower-latency components specific to autonomous systems, and at senior levels to managing drones in the field, taking a signal from the drone and sending instructions back.

05
Behavioural, with a senior leader
45 to 60 minutes

A deep walk through the CV: the scale and scope of your projects, the technical challenge in each and how you solved it, a conflict and how you handled it, how you make important decisions, and how you would rate your own performance at your last company. The why-defence question returns here, deeper than on the screen.

06
After the loop
Replies within a day; an offer within three to four weeks

Candidates report hearing back the day after each round. For roles that sponsor a clearance the offer is conditional and the interim Secret period runs three to nine months before adjudication.

Cleared roles: six to eight weeks
03

What Anduril screens for

What every round is really testing

Anduril says what it screens for more openly than most, because the mission question is a filter rather than a formality and the coding format is built to expose one habit.

  • A considered reason to work in defence. The question is asked twice, by a recruiter and by a senior leader, and growth narratives alone are named as insufficient
  • Clarifying before solving. The screen prompts are underspecified on purpose, and asking what the problem actually is counts as part of the answer
  • Adapting when the constraints change. Every coding round shifts the problem mid-way, and candidates who defend their first solution rather than reshape it stall
  • Ownership and speed under real constraints. The behavioural round goes at what you personally decided, what went wrong and what you did about it
  • Depth in a domain over breadth, and genuine product knowledge: candidates who can name Lattice, Ghost, Altius or Roadrunner and say why that one do better than generalists
04

Anduril interview questions

Candidate-reported themes

Behavioural ground is concentrated in the recruiter screen and the last hour with a senior leader, and it is narrower than at most companies: the mission, your CV in depth, and how you decide. The technical prompts below are the ones candidates report by name; AI tools are prohibited in the interviews.

Behavioural & motivation

  • Why Anduril, and why defence?
  • Which area do you want to work in: perception, backend infrastructure, ML infrastructure or ML, and why?
  • Walk me through your CV, project by project.
  • Tell me about a project's scale and scope, the hardest technical challenge in it, and how you solved it.
  • Tell me about a conflict that arose on a project and how you handled it.
  • How do you make important decisions?
  • How would you rate your performance at your previous company?

Technical

  • Multi-phase coding: A simplified problem, then new constraints: shortest distance between two points, then obstacles, then the path around them. Working code at each phase over asymptotic analysis
  • Graphs and structures: BFS, DFS, cycle detection and union-find; heaps, sliding windows, geometry; hash maps, parsing, arrays and strings; a collection of robots with task prioritisation
  • Object-oriented design, written out: A doubly linked list with insert, delete and search, or a component from scratch, with the classes and interfaces actually coded and refactored on request
  • System design: A URL shortener, Tetris, a notification service; sensor data processors and other low-latency components; at senior levels, drones in the field that send a signal and receive instructions back
  • Hardware fundamentals, hardware track: Synchronous buck converters, RC transients, decoupling capacitor selection, PCB trace capacitance and inductance; GD&T, composites, DFM, lamination theory, electronics cooling

These are the reported themes — your loop is role-specific. Paste the actual posting and Calibrd predicts the questions for that exact role and level.

Scan an Anduril posting →
05

Pay

What the offer looks like
IC4 · Senior Software Engineer$321K total
IC5 · Lead Software Engineer$380K total

Levels.fyi for software engineers at Anduril in the United States, read on 11 September 2026. The overall median package is $247K and reported packages run from $227K at IC2 to $517K at IC7. IC4, Senior Software Engineer, has a median of $321K made up of roughly $207K base, $111K a year in stock and a small bonus; IC5, Lead, is $380K with $223K base and $153K in stock. Levels.fyi labels the same ladder L3 to L7 on some of its pages and IC2 to IC7 on others, with different medians, so treat the figures as an order of magnitude. Stock is options plus RSUs on a four-year schedule, a quarter after the first year and monthly after that, and Anduril is private, so the stock half is priced by its last funding round rather than by a market. Hardware and mission roles are on their own scales and are not covered here.

06

How to prepare for an Anduril interview

In order
  1. 01Decide what you think about defence work before the first call, and be able to say which product and why. The question is asked by the recruiter and again by a senior leader, and a growth story on its own is reported as the answer that does not survive the second time.
  2. 02Check your eligibility before you apply. Roles are limited to US citizens and lawful permanent residents under export controls, about half need a clearance at Secret or above, and sponsorship is not offered. A cleared role adds weeks and an interim period after the offer.
  3. 03Rehearse the multi-phase format rather than single problems. Take a LeetCode medium, solve the simple version, then add a constraint yourself and rework it aloud; the rounds grade how you adapt when the problem changes, and defending the first version is the reported way to stall.
  4. 04Ask what the problem is before you solve it. Screen prompts are underspecified on purpose, one candidate was told so by the interviewer, and the clarifying questions are part of the score.
  5. 05Write the classes. The design round expects working code for a data structure or component, with edge cases handled and a refactor accepted mid-way, so practise implementing a doubly linked list or an LRU cache cleanly from nothing.
  6. 06For senior roles, prepare one design in the company's own domain: a fleet of drones in the field, the signal each one sends, the instructions that go back, and where latency, encoding and encryption sit. Web-scale designs still appear, but the domain one is what separates levels.
  7. 07Know your CV to the number. The last hour is a project-by-project walk with a senior leader who asks about scale, the hardest challenge, a conflict and your own rating of your performance, and vague answers are what that round exists to catch.
  8. 08For hardware roles, prepare a technical presentation of one project you owned, from design through test to what failed, because the onsite is built around it and around five or six people asking about it afterwards.

This guide covers Anduril's software loop in depth, with the hardware and mission tracks described where the accounts allow. The eligibility rules apply to every role because the work is export-controlled. For management and leadership roles the loop is similar but the bar shifts to people, delivery and strategy, so pair it with the leadership interview prep hub. The bar for your exact role comes from the role-by-role guides, and the prep that actually transfers is spoken, so run a mock interview before the real one.

07

FAQ & sources

The short answers
What is Anduril's interview process?

The published accounts agree on the software shape and disagree on the details, and they say so themselves: one recent guide states plainly that candidate experiences do not support a single universal Anduril sequence or timeline. One account has two engineers on the coding screen, another has one; one final round has four sessions, another three. What more than one account reports is below. Timing is the predictable part: candidates describe hearing back the day after each round, first contact to offer in three to four weeks for an uncleared role, an average of 28 days from recruiter screen to offer, and six to eight weeks where a clearance is involved. Recruiter screen: Your background, which area you want to build in (perception, backend infrastructure, ML infrastructure or ML), your motivation for defence work specifically, and the eligibility questions: citizenship or permanent residence, and whether you hold or could obtain a clearance. Product awareness is noticed here. Technical phone screen: A deliberately ambiguous prompt in phases. You solve a simplified version, then the constraints change, and clarifying the requirements is part of what is graded. Reported problems include a football team photo arrangement one candidate was told was confusing on purpose, and graph cycle detection. Time and space complexity matters less than usual; working code across each phase matters more. Coding, two sessions: Collaborative problems that layer on constraints as you go, with no formal test gates between phases. One reported sequence: the shortest distance between two points, then obstacles blocking the direct path, then the shortest path around them. Others involve a collection of robots with task prioritisation, drone management, and graph manipulation. Difficulty sits at a practical LeetCode medium. Object-oriented or system design: Anduril expects you to write the classes and interfaces rather than talk about them: a data structure or component from scratch, such as a doubly linked list with insert, delete and search, graded on decomposition, edge cases and how you respond to a refactor. System design ranges from a URL shortener or Tetris to lower-latency components specific to autonomous systems, and at senior levels to managing drones in the field, taking a signal from the drone and sending instructions back. Behavioural, with a senior leader: A deep walk through the CV: the scale and scope of your projects, the technical challenge in each and how you solved it, a conflict and how you handled it, how you make important decisions, and how you would rate your own performance at your last company. The why-defence question returns here, deeper than on the screen. After the loop: Candidates report hearing back the day after each round. For roles that sponsor a clearance the offer is conditional and the interim Secret period runs three to nine months before adjudication.

What does Anduril look for in candidates?

Anduril says what it screens for more openly than most, because the mission question is a filter rather than a formality and the coding format is built to expose one habit. A considered reason to work in defence. The question is asked twice, by a recruiter and by a senior leader, and growth narratives alone are named as insufficient Clarifying before solving. The screen prompts are underspecified on purpose, and asking what the problem actually is counts as part of the answer Adapting when the constraints change. Every coding round shifts the problem mid-way, and candidates who defend their first solution rather than reshape it stall Ownership and speed under real constraints. The behavioural round goes at what you personally decided, what went wrong and what you did about it Depth in a domain over breadth, and genuine product knowledge: candidates who can name Lattice, Ghost, Altius or Roadrunner and say why that one do better than generalists

What questions does Anduril ask in interviews?

Behavioural ground is concentrated in the recruiter screen and the last hour with a senior leader, and it is narrower than at most companies: the mission, your CV in depth, and how you decide. The technical prompts below are the ones candidates report by name; AI tools are prohibited in the interviews. Why Anduril, and why defence? Which area do you want to work in: perception, backend infrastructure, ML infrastructure or ML, and why? Walk me through your CV, project by project. Tell me about a project's scale and scope, the hardest technical challenge in it, and how you solved it. Tell me about a conflict that arose on a project and how you handled it. How do you make important decisions? How would you rate your performance at your previous company? Multi-phase coding Graphs and structures Object-oriented design, written out System design Hardware fundamentals, hardware track

How do I prepare for an Anduril interview?

Decide what you think about defence work before the first call, and be able to say which product and why. The question is asked by the recruiter and again by a senior leader, and a growth story on its own is reported as the answer that does not survive the second time. Check your eligibility before you apply. Roles are limited to US citizens and lawful permanent residents under export controls, about half need a clearance at Secret or above, and sponsorship is not offered. A cleared role adds weeks and an interim period after the offer. Rehearse the multi-phase format rather than single problems. Take a LeetCode medium, solve the simple version, then add a constraint yourself and rework it aloud; the rounds grade how you adapt when the problem changes, and defending the first version is the reported way to stall. Ask what the problem is before you solve it. Screen prompts are underspecified on purpose, one candidate was told so by the interviewer, and the clarifying questions are part of the score. Write the classes. The design round expects working code for a data structure or component, with edge cases handled and a refactor accepted mid-way, so practise implementing a doubly linked list or an LRU cache cleanly from nothing. For senior roles, prepare one design in the company's own domain: a fleet of drones in the field, the signal each one sends, the instructions that go back, and where latency, encoding and encryption sit. Web-scale designs still appear, but the domain one is what separates levels. Know your CV to the number. The last hour is a project-by-project walk with a senior leader who asks about scale, the hardest challenge, a conflict and your own rating of your performance, and vague answers are what that round exists to catch. For hardware roles, prepare a technical presentation of one project you owned, from design through test to what failed, because the onsite is built around it and around five or six people asking about it afterwards.

  • 01Exponent, Anduril software engineer interview guidethe six sessions in three stages, the 60-minute HackerRank screen in phases, the two coding sessions with layered constraints, the OOD round, the behavioural round with a senior leader, the citizenship restriction to US citizens and permanent residents, and the domain areas the recruiter asks about.
  • 02Exponent, a new-grad candidate's Anduril loopthe recruiter question about perception, backend infra, ML infra or ML; the photo-arrangement screen the interviewer said was confusing on purpose; the shortest-distance problem growing obstacles; the doubly linked list design; replies the next day.
  • 03TechPrep, Anduril's interview process 2026the three to four week timeline, the 30 to 60 minute recruiter screen on motivation for defence, the deliberately ambiguous screen prompt, the four-round final day, the graph and geometry topics, that Anduril expects classes and interfaces to be written, and the resume walkthrough with senior leadership.
  • 04interviewing.io, Anduril interview process and questionsthe recruiter call, the technical or hiring-manager hour, the four-hour onsite of two coding, one design and one behavioural; the practical LeetCode-medium level; the robots, drones and graph examples; Tinyurl and Tetris; the drones-in-the-field design for L5 and L6; and that AI use is prohibited.
  • 05Blind, Anduril interview threadthe intro call confirming mission alignment, citizenship and clearance eligibility; a coding screen with two engineers at easy-to-medium difficulty; a final loop of two technical and two behavioural interviewers; a domain-heavy embedded loop in the drone division; and that the process is division specific.
  • 06ClearedJobs, Anduril careers and how to get hiredthat roughly half of open requisitions require a clearance at Secret or above with a meaningful share at TS/SCI, the 600 to 900 active requisitions, the growth from about 4,490 to about 8,200 employees through 2025, the 28-day average from recruiter screen to offer, six to eight weeks for cleared roles, and the three to nine months of interim Secret status after a conditional offer.
  • 07Snubber, Anduril interview questions and process 2026that recent candidate experiences do not support one universal sequence or timeline; the technical project presentation for some engineering roles; the hardware topic areas by discipline; and the screening for mission alignment, first-principles judgment, speed and product knowledge of Lattice, Ghost, Altius and Roadrunner.
  • 08NoraHQ, Anduril electrical engineer interview guide 2026the three to five rounds over two to four weeks for electrical engineers, their lengths, and the fundamentals asked: buck converters, RC transients, decoupling capacitors and PCB trace effects.
  • 09Glassdoor, Anduril engineer interview experiencesthe hardware sequence of a recruiter call, two chief engineer conversations, and an onsite with a presentation and five or six individual interviews; a difficulty rating of 2.8 out of 5; and an average of 23 days to hire for engineer applicants.
  • 10Levels.fyi, Anduril Industries Software Engineer, United Statesthe $247K median, the $227K to $517K range from IC2 to IC7, the IC4 and IC5 bands with base and stock, and the four-year options-plus-RSU vesting schedule. Read 11 September 2026.

Prep for a real Anduril role

Practise your Anduril interview, out loud.

Paste a real Anduril posting and Calibrd predicts the questions for that role and level, benchmarks the pay, and flags the gaps an interviewer will probe in your CV — then listens to your spoken answers and coaches them. Your first mock is free.

Free to start · No card · Your resume stays yours, encrypted, remove it anytime

Anduril Interview: Clearance, the Loop and Pay — Calibrd