Anduril · Primly Community

Went through the full Anduril hardware loop last month, here's what actually happened

hardware_hugo · 5 replies

Applied for a senior embedded systems role. Whole thing took about 5 weeks from first recruiter call to offer.

Round breakdown: Recruiter call (30 min): mostly role fit, clearance eligibility, relocation. they asked straight up if i was okay with the defense mission. not subtle. Technical phone screen (45 min): a C++ problem and some questions about memory layout and interrupt handling. the interviewer was clearly an engineer, not a recruiter, asked good follow-ups. Take-home: given 72 hours, it was a small firmware task with some intentional ambiguity in the spec. i asked two clarifying questions upfront and they responded quickly. the point felt like seeing whether you'd just barrel forward or actually pressure-test the requirements. Virtual onsite (4 rounds, one day): system architecture for a real-time sensor fusion problem, a coding round, a hardware design discussion, and then a behavioral round with a director.

The behavioral round was not soft. she asked specifically about times i disagreed with a product direction and what i did about it. i got the sense that being deferential would not score well. they want people who will push back when something is wrong.

Offer came 3 days after the onsite. they moved fast. the equity conversation was more detailed than i expected, they explained the vesting cliff and secondary market situation clearly.

5 replies

sre_sol

that take-home format is interesting. 72 hours is humane compared to some places i've seen. the "ask clarifying questions" design is actually smart, you're seeing real engineering behavior not just syntax.

hardware_hugo

yeah exactly. i've done take-homes where asking questions felt risky, like you'd seem like you didn't understand the problem. here it felt expected. two of my questions got meaningful answers that changed my approach.

director_dee

the behavioral framing you described is deliberate. "tell me about a time you disagreed" at a defense startup is partly screening for people who won't stay quiet about a technical safety issue. deferential answers probably do screen out.

market_realist

how was the panel on the defense mission question? i've heard some candidates get tripped up if they give a mushy non-answer.

hardware_hugo

i had a clear answer ready and it helped. vague "i'm open to it" energy is probably a yellow flag for them. if you're genuinely on the fence about defense work, this is the wrong place to soft-pedal that.