Firstly, I got a simple C++ task to solve at HackerRank, which I did well. Afterwards, living in Saint-Petersburg (Russia), I'd been interviewed via Skype and ssh'ing to the server and doing coding tasks in the terminal. I had been scheduled for two interviews. The interviewer for the 1st interview had missed the invitation to the interview (in Russia we have a sort of proverb "The theatre starts with a cloakroom", which means the first impression is right in most cases) and the HR rapidly assigned me another guy who was a C programmer. He asked me to solve 2 simple algorithmic tasks in C which I did well too (1.1 and 1.2). Two days ago I got a response from the HR that we can proceed for the 2nd interview. Also she asked if I prefer C or C++ programming. I said C++ and I had no experience in C programming according to my CV, so she said she'll organize a C++ interview. The 2nd interview was conducted by yet another C programmer as well, whom I didn't expect as I'd prepared for C++ underlying tricky questions. He asked me to write a function to yield a next node (descend traversing) in a binary tree (2.1). I wasn't prepared for that at all! Moreover I had no chance to run/debug the code. So, this task I failed. Then he gave me C code snippet which is allegedly to be used in multithreading environment and find possible issues (2.2). Naturally, there were data races. I suggested using a mutex, but the guy firstly assumed using a self-made spinlock having forgotten to add the volatile keyword. In the contemporary world nobody writes multi-threading code like that! Also he asked me a few questions about compiler optimizations, i.e. how would the compiler amend the code. That's sooo low-level. Use a mutex / std::atomic vars and std::atomic_thread_fence to prevent the compiler to re-order your operations, Luke! Spinlocks are too erratic to use, especially on multi-processor because of CPU caches. This archaic way of designing code (even on an interview) discouraged me from working in the company, so I wasn't disappointed or frustrated by the immediate refusal, though I'm wondering why having said several times that I'm a C++ developer and dislike C, I'd been interviewed as a C programmer. No any questions about C++, no any technical stuff.