My interview questions for a C++ job were all C instead of C++, so l asked why I was given C questions for a C++ job. The interviewer accused me of having a bad attitude and ended the interview early. The job was described (by the interviewer) as 70% C++, 20% Python, and 10% other languages that aren't C. Literally no C use was required in the role I was interviewing for. I guess he really likes C. Company will waste your time making you jump through arbitrary hoops. Don't waste your time.

Pros: Great initial approach – the recruiter thoroughly checked my GitHub profile and projects before the interview, which is very uncommon and shows they do their homework. Cons: A major mismatch between the job description ("Software Engineer C++") and the actual interview reality. The technical stage on CoderPad strictly tests bare-metal C98 skills: raw pointers, manual bitwise operations, and packing bytes into 64-bit integers. If you are accustomed to modern C++ (RAII, templates, safe memory management), this will feel like a massive step backward. Additionally, the time expectations for live low-level bit-shifting were unrealistic, to the point where the interviewer started solving the task themselves. Interview was kind and not stressful, just minor mismatch of naming