Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

8 stories

Likes earn the author +10 XP for the first 3 likes each day

AndurilSoftware Engineer
Aug 2026

Onsite Coding Went Great, Then the HM's System Design Round Sank It

This role was billed as fullstack, but the interviews barely touched anything front-end related. And the final round — I got screwed over by the hiring manager. The phone screen was on 4/17. After I finished it we just chatted. The next day HR told me I passed and moved on to the onsite (VO). VO Coding 1 Question 1: a simple calculator that only needs to support addition and subtraction. ["+", 1,…

RejectedOnsite0
AndurilSoftware Engineer
Reported Aug 2026

Anduril Software Engineer Interview Experience: automated recruiter messages and essays

A recruiter contacted me with a message that looked AI-generated. I asked to speak with a real person, but each reply returned to the same automated tone. She eventually gave me a "role" that also felt automated, apparently tailored from my resume and describing a city office I knew Anduril did not have. After more back-and-forth, she said she would put my resume in the system only if I wrote thr…

No response0
AndurilSoftware Engineer
Reported Jul 2026

Anduril Software Engineer interview: C++ screen and graph clusters

I went through a familiar sequence: recruiter contact, a technical coding screen, and an on-site. In the Zoom technical round, we briefly covered my background before moving into C++. I had to read basic lines of code and explain pointers, references, lambdas, and move semantics. The second half was a programming challenge using depth-first search to identify node clusters in a graph. The on-site…

HR Screen0
AndurilSoftware Engineer
Reported Jul 2026

Anduril Software Engineer interview: drone equations and a demanding onsite

After an HR chat, I had a coding screen that was closer to a simulation than a standard textbook prompt. I had to calculate drone-related equations, so pattern matching was not enough to rush through it. Passing that screen led to an in-person onsite with system design, a cultural or motivational discussion, and two coding challenges. It felt difficult because the formats required both technical…

0
AndurilSoftware Engineer
Reported Jul 2026

Anduril Software Engineer interview: cantilever beam questions and a nontechnical thermal screen

The recruiter screens were brief and mostly light. Technical questions did appear, but not consistently. In a screen about mechanical design, I got basic cantilever-beam questions. A separate thermal recruiter screen had no technical questions at all, which made the experience feel somewhat inconsistent from interviewer to interviewer. I did not get an offer from this stage. It felt comparatively…

0
AndurilSoftware Engineer
Reported Jul 2026

Anduril Software Engineer interview: conventional flow and onsite concerns

I went through a conventional recruiter, tech-screen, and onsite flow. The questions covered data structures and algorithms, system design, and why I wanted to work at Anduril. The onsite was the main day, but the atmosphere did not match what I had hoped for. At one point, it felt like everyone was tired and the logistics were chaotic, based on how the interviewers talked about their situation.…

Technical Screen0
AndurilSoftware Engineer
Reported Jul 2026

Anduril Software Engineer Interview Experience: Mock application work and a project presentation

My experience began with easy coordination. Reaching the recruiter and scheduling interviews was smooth. From there, the questions were tightly connected to the actual job and how effective I could be in it. I expected a typical interview structure, but it had a stronger performance element than I was used to. I had to demonstrate my abilities through mock application-style work, not just theory.…

HR Screen0
AndurilSoftware Engineer
Reported Jul 2026

Anduril Software Engineer interview experience: HackerRank and ghosting

I started with a recruiter conversation that was kind and upbeat. Afterward, I received a HackerRank assignment, completed it, and waited. Then the process went quiet and I was ghosted. The positive recruiting call made the lack of any follow-up after the take-home feel especially abrupt. From what I saw, the broader process usually went from recruiter conversations to an engineering screen and t…

No responseTake-home Project0

What are interview experiences?

An interview experience is a candidate's own account of a hiring loop — not a question bank entry. It tells you the shape of the process: how many rounds there were, what each round actually tested, how long the gaps between them ran, and what the recruiter said at the end. That context is the part a question list cannot give you.

How to read them

Weight recent write-ups more heavily — interview loops change, often within a year. Read several for the same company and role rather than one: a single account tells you what one interviewer asked, while five tell you what the bar is. Note the outcome badge too, since a rejection write-up usually explains the gap far more precisely than an offer one.

Share your own

Every published experience earns 50 XP, and each of the first 3 likes it receives in a day earns you 10 XP more. Likes must come from established accounts; like-for-like swaps and likes from your own second account are not paid. Write it while the details are fresh — the round order, the exact prompts, and how much time you were given are what the next reader needs.

Share your experience to earn XP