Canonical Software Developer interview questions

The process was very long and drawn out, but also very professional. It started with a very long written interview consisting of dozens of questions, my response ended up being around 20 pages. It took a while to hear back after this piece, but eventually they sent me a sort of mental capacity test that consisted of several brain teaser puzzles that were easy to answer, but speed was a big factor so there was a trade off dynamic between answering accurately and quickly. After this I was sent a very simple coding test. The job was specific to the Rust language, and most of the questions on the test were about language semantics, rather than LeetCode style problems. After this I had a round of three interviews, all technical with a different topic focus. The first two were about general software architecture and rust specifics respectively, and they went fairly well. The last was all linux/unix specific questions. I stated in my written interview very clearly that I did not have very much linux experience, but they still decided to interview me on specifics. This interview was all very surface level questions about shallow knowledge that is easy to look up, which I found frustrating. The interviewer laughed at me because I didn't know the minutia of pipe syntax, but they also didn't know anything about io_uring and how it worked, just as an example. I didn't get an offer and I think it was primarily because of how the linux interview went. I completely understand a company that makes a linux distribution wanting to hire people with lots of linux experience, but the fact that I was drawn out all the way to a linux interview after being very clear about my lack of experience, and that the questions were so surface level and not about deep knowledge, was very frustrating to me. The linux interviewer was also very unkind and condescending. The other interviewers were very nice.