interview fail: googled answers to questions

daily job: google answers to questions.

Although I think I get the intended humour, the daily job certainly shouldn't be to Google answer to questions.

Google to get to documentation... Sure. Reading documentation.. Sure. Ability to understanding it and how it is used, that's what would be missing, and what is suggested the interview question failed to pick up on.

That's an illusion. Almost all of a coder's daily work is stuff that has been done already about a hundred thousand times. Every time I'm coding on easy mode (eg some sort of personal project where I have all the leeway) I can get through all of it just by googling $language how to $x ... been doing exactly this workflow recreationally during times when I don't feel like exerting myself for years now. It's neither slower nor does it provide worse results than in situations where I'm dealing with technologies I know inside out. With the tougher stuff, you should be consulting your colleagues anyways. If no one knows - then you research together... on google.

> interview fail: googled answers to questions > daily job: google answers to questions.

But you have to cram to make it seem otherwise... seriously one of the most interesting things I have ever seen was a HR person say that they had a stack of CVs but self-selected for those who were able to use 'know how to google when stuck' remarks on their applications.

I think we should just be honest and come clean and state that it is impossible to gatekeep like this while at the same time then expect people to be 'efficient and self-starters' and know how to use stack overflow at the same time. We have built these immense, entirely contradictory, ways of virtue signalling in this Industry that this is the outcome you get and can come to expect from optimizing for this vetting process--in-person interviews only partially elongated the farce of it being a good way to parse through applicants.

Because the truth is you know they are doing this for 2-5 other potential employers and have to do the same there and this is the most 'efficient use' of their time to solve a problem: googling it.

This is why I used to use interview questions that were useful to research by googling and see how effectively resourceful people were with finding relevant information quickly. it’s also a skill and it’s apparent when someone is googling and skimming results way out of their element

I was that thinking of a cool idea, where the conversion was translated in real time and gpt3 was giving you answers to common questions like give me an example of when XYZ

You could also do interview questions.

Or the candidate clearly showed an aptitude for the job!