Implement a doubly linked list.

"I went straight to a recruiter screen with no OA, then did a 60-minute engineer phone screen, and after that the final was three separate 60-minute rounds. The biggest theme was ambiguity: the phone screen HackerRank was intentionally confusing, the other technicals kept expanding the problem, and I had to ask a lot of clarifying questions instead of expecting a neat prompt. The behavioral with a senior leader was also tougher than usual because he went deep on every line of my resume and kept circling back to why Anduril and why defense. The turnaround was fast and I usually heard back the next day, and I honestly thought I had failed the phone screen but still got moved forward. I ended up not getting the offer, but the process made it pretty clear they care about fundamentals, clean code, and whether you actually align with what the company does."

"I had a first product design screening round, then went into the full loop, which included coding, another product design, a project retro, and a people management round. The process felt very self-led, especially in the technical rounds, where they gave me a board or editor and expected me to drive the discussion without much prompting. I was told that many engineering manager candidates tend to score higher on the technical side and lower on the management side, but in my case, it was the opposite. I failed the coding round and the full-loop product design round, which really surprised me, since I felt I had answered the product design interview more comprehensively than the screening one. I actually came out of the interviews feeling quite confident I would get an offer, but did not."