Agreed, do you know why?
They're looking for yes men. (Ok, maybe not the A later in the alphabet - not sure today)
Now if you meet someone "higher up the chain" outside of a formal setting, this might work.
Agreed, do you know why?
They're looking for yes men. (Ok, maybe not the A later in the alphabet - not sure today)
Now if you meet someone "higher up the chain" outside of a formal setting, this might work.
One of the things you learn pretty fast as an interviewer is that charisma and attempts to pitch yourself tend to correlate poorly with aptitude, and an interview that focuses solely on predefined technical questions is by design impervious to yes men.
Unless you have recruiters (or even engineers) ignoring your answer because it doesn't match exactly to what you were expecting.
And it's not impervious to yes men, you can have a technical savant and a yes man at the same time.
Or maybe they hire thousands each year and want to ensure some consistency in the candidate selection criteria. This could result in hiring more yes-men, but the _intention_ may be different.
I would never know as much as I know about networking, infrastructure, devops, architecture, security, etc. in addition to development if I spent all of my life in a large company.