← Back to Directory

Anduril

Mid-sized

Screna has 4 Anduril interview write-ups. The most reported round is the technical phone screen (3).

4 interview notes · updated Sep 2026

Anduril·Software Engineer·Technical Phone Screen

Aug 2026
Went through a recruiter screen and a technical interview at Anduril, a company I really had my heart set on. Got rejected, which stung pretty bad considering how much prep I put in. The coding problem threw me off and I took too long to get through it.
  • Solve a coding problem (specific problem not disclosed).

“Got there eventually but way too slow.”

View Post

Anduril·Technical Program Manager·Technical Phone Screen

Jun 2026
Interviewed for a TPM role at Anduril and got asked about tooling. Pretty standard screen, nothing too wild.
  • What tools do you use day-to-day as a TPM, and which ones are you most comfortable with?

“Rattled off the usual suspects.”

View Post

Anduril·Software Engineer·Technical Phone Screen

Jun 2026
Anduril Industries coding round for a software engineer role. One problem, optimization-flavored, took me longer than it should have to nail down the edge cases.
  • You have a list of rod lengths. You can cut any rod into pieces of a single chosen integer length. Each cut has a fixed cost, and each resulting piece earns revenue proportional to its length and a sale price. If a rod divides evenly into k pieces, you only need k-1 cuts; otherwise k cuts. You can also skip a rod entirely if it would hurt your profit. Find the integer cut length that maximizes total profit across all rods.

“I got the basic structure pretty fast: iterate over candidate sale lengths, simulate the cuts, track profit.”

View Post

Anduril·Technical Program Manager·Onsite - Behavioral / Leadership

Apr 2026
Behavioral round for a TPM role at Anduril. Just one question from what I remember, pretty standard ownership-type prompt but it required a solid story so I had to think fast.
  • Describe a situation where you stepped up to own a project that wasn't originally yours to lead.

“I fumbled the opener a bit, started talking about the project context for too long before getting to what I actually did.”

View Post