Round 1 : Implement strcpy Basic of exception handling eg divide by zero all edge cases cover what is your weakness and how you handle it new vs malloc copy construtor and destrucor will you recoomend thowring an exception from destructor Inheritance etc Round 2 : It was with onsite people from canada maybe Code was given to optimize it where we have to use references, reduce the loops,naming convention etc - smart pointers, shared pointer, unique pointers Round 3 Managerial round - What activities of developer makes him different from other developer or how do stand yourself out of other developers - Situation where you colleguue given a task but he went on leave so how do you take up his task - How do you learn about the product - Situation where you have interacted with the customer etc

I interviewed for a role of C++ developer in Zurich. First round with HR went well, very responsive and helpful lady. Second round, the techical one, was a nightmare of every developer out there. For some reason post-USSR C++ programmers think that it is necessary for every developer to know C++ internals inside out to be able to write programs in it. But I was not applying for a position of C++ compiler developer nor for a C++ standard committee member. Questions about vtable, backing implementation of a deque or a very smart (deliberately obfuscated) "what happens if birds could swim" questions are meant to confuse and to fail a candidate, not to assess a candidate's ability to write programs in C++. 1.5 hours of grilling on every imaginable detail of C++ internals and tricky and confusing "what will this print?". And OF COURSE classic ghosting in the end.