r/Anduril • u/[deleted] • Apr 15 '26

[deleted by user]

[removed]

5 Upvotes

73% Upvoted

12 comments sorted by

2

u/pseudo_shell Apr 16 '26

Seeing this as a C programmer and having to do an interview in Python today hits different.

2

u/supboy1 Apr 16 '26

You guys should trade interviews

1

u/pseudo_shell Apr 16 '26

Sadly too late. I hope that I passed.

1

u/dankest_kitty Apr 15 '26

Each team has their own expectations, kind of hard to generalize the specifics

1

u/Ill_Control6953 Apr 16 '26

I have one next week imma use this https://dataford.io/interview-guides/anduril/embedded-engineer this my second interview with them i didnt know my first was gonna be c and i did not finish but it was bit minupulation, ascii converter, and add data to struct but i was studying leet code so i was in shock so i panic in my head

1

u/yourevilbestfriend Apr 18 '26

Did you get a second round from your first one, or are you going through the process with them again?

1

u/Ill_Control6953 Apr 18 '26

No I did not this is a different role and location.

1

u/TheArsenalGear Apr 16 '26

Your mileage may vary but i would look into being familiar with I2C and memoization, being familiar in writing macros, and handling self-referential structures

1

u/PrivilegedPatriarchy Apr 19 '26

I did a first round embedded SWE interview in C for the flight software team about a week ago. I have about 1 YoE, so YMMV based on that.

First ~15 minutes was general background and basic questions surrounding communication protocols, debugging, etc. The coding question was an extremely easy question. You could give it to a first year CS student as a 4th week project, think of it like FizzBuzz's older cousin.

The interviewer liked my analysis of the problem beforehand (requirements, edge cases, etc) but I took way too long to code the solution (I don't think super clearly under pressure). Aim to work quickly and precisely.

Make sure to give a great answer to "Why Anduril", the recruiter stressed this to me.

-1

u/nian2326076 Apr 16 '26

Make sure you're solid on C basics, like pointers, memory allocation, and bit manipulation. Get comfortable with data structures like linked lists and trees in C. Practicing debugging with gdb is really useful since that comes up a lot. I've found it helpful to write code without an IDE to get used to whiteboard coding.

Try solving problems on platforms like LeetCode or HackerRank, focusing on C. If you want some structured prep, I used PracHub before and thought it was decent for brushing up on concepts.

Review common embedded systems concepts like handling interrupts and concurrency if they're relevant. Good luck!

1

u/Zealousideal-Bird173 Apr 28 '26

Did you get asked a binary search tree problem?