> Why shall I still prove myself?
Because we see candidates claiming that level of experience that cannot construct a simple for loop.
Because we see candidates claiming that level of experience that cannot construct a simple for loop.
Unless they are references from people who those involved with hiring personally know.
It is usually a pretty organic process. If we get into it and question their coding ability, we might ask a few basic questions, like how do you declare an array or vector in C++. Do you use std::algorithm? Then possibly into C++14 territory. It depends on the position. On the other hand, if they breeze through some basic coding questions, it quickly turns into a discussion and feeling the candidate out in terms of fit. But if we get a senior SE come in, and we talk about previous projects and we get "I fixed bugs, reduced memory usage, and saved $X million dollars" that is a big red flag.
Sounds like your expectations are part of the problem.
Why do you expect someone 15 years out of university, working in the now enormously wide software space to have your pet questions memorized? C++ is well known for being too big and needing to be subset(-ed). And, why not realize that such a person could become an expert in those questions in less than an hour of googling and reading?
The bigger problem is that companies are not willing to invest even four hours of training into employees!
These folks with many "senior" level positions on their resume can't manage a task our last hire did in about 6 minutes.