When I interviewed junior devs for my team, I had zero theoretical questions, and only two coding questions which were basically code that had to be debugged, and once it was running, for them to implement some minor things that I asked them to implement. I said I don't mind if they googled, I only wanted them to share their screens while they worked, so that I can see how they worked and how they googled/adapted the answers to their code. I interviewed over a dozen people ranging from freshers to 4 yoe, and you should see how terrible they were at googling. Out of all them, only one fresher came close to being good in the interview. Even '4 yoe' devs who 'spearheaded' various projects sucked at basic python and googling.

[–] Aquila@sh.itjust.works 23 points 3 months ago (2 children)

I would 1000% become dumb as a rock with someone watching me not to mention in a high risk setting such as an interview

[–] MajorHavoc@programming.dev 7 points 3 months ago

Yeah. We do a ton of screen sharing guided mentorship in my role, and everyone can't think straight while sharing their screen.

We get through it, and feedback says it's worth it. But it still sucks in the moment.

[–] fsxylo@sh.itjust.works 2 points 3 months ago

I tend to do the most embarrassing sitcom shit possible when someone is watching me do something I'm an expert in.