Talk me through your work experience in the past year.

"The process was pretty simple from the early start, but they emphasize a lot on matching Anduril's core values and see if you're a culture fit. I would have better prepared my stories and gaps for the behavioral interview. There were gaps regarding technical depth and being too ambiguous."

"The process was pretty simple from the early start, but they emphasize a lot on matching Anduril's core values and see if you're a culture fit. I would have better prepared my stories and gaps for the behavioral interview. There were gaps regarding technical depth and being too ambiguous."

"The process was very well structured with no surprises. They will let you know what exactly they are looking for and test you on that which I found nice."

"The technical round was indepth and covered all corner cases and asked a lot of follow up questions on optimization and performance improvement"

"Overall interview process was fairly standard. Coding questions were similar to the previous interview experiences. Make sure to be fluent with file system APIs (reading and writing data within files). System design questions were fairly standard questions."

"Ok! The interview quality was bad, they do not hire much, and their tech stack is not on par with the market."

"The process was fairly simple. I applied online and the recruiter set up an introductory call within a week. While the questions were easy/medium difficulty - they were looking for a candidate with more relevant experience in the travel industry and did not move forward with my application after the second round."

"The process was more rigorous than most interviews I’ve done at other large tech companies. The recruiter was accurate and helpful about what to expect, which made it easier to prepare. The interviews themselves were structured and generally well run. A few questions and follow-ups caught me off guard, and some rounds felt more dependent on navigating ambiguity in the moment than I expected."

"In coding rounds, the questions asked were NOT leetcode based. Both coding rounds had follow ups. Expection is to have working solutions. In one of the system design rounds, there was unusally more focus on the APIs than the actual design."

"I got into the process through a referral and started with a recruiter call that was actually very informative. The process was five rounds for me: recruiter, a 60-minute technical screen with 30 minutes SQL and 30 minutes Python, a 30-minute behavioral, and then three loop rounds. The loop was a little different from other data engineer interviews I have done because each round combined product sense, data modeling, SQL, and Python rather than testing them in isolation. The interviewers were super helpful if I spoke out loud and asked clarifying questions, and the recruiters gave me a lot of prep material up front."

"Recruiter was good at communicating throughout and the interviewers seemed really engaged in the process. Excitable about their space. There is a product design portion where, given a prompt and UX snippet, users are asked to design a solution to the prompt. You are given about 30 min and then are grilled on that. There’s a basic analysis portion ensuring you can read basic data and infer decisions."