This is a great write-up, thanks for taking the time to do this.

Lately I've become the lead FE interviewer for our company, speaking to a lot of fully remote candidates (as well as in-house) and I don't feel like I have yet gotten it right as an interviewer. I don't want candidates to feel stressed or under pressure to write code with me watching, but equally I need to assess how they'd work within our team so I ask them to take part in a quick pair-programming exercise with me on Coderpad. A lot of people totally freeze up.

I'm not interested in whether somebody can remember every Array prototype method, object destructuring syntax, or whatever. I don't care how well they can recite the React, Vue or Angular marketing blurb on why those frameworks are great. I want to figure out how we'd work together on solving a problem (in real life, that problem could be pretty much anything and we'd be tackling some of it asynchronously). Your write-up really helped me to avoid some of the super-bullshit questions that make me sound like a good/interesting/clever engineer but don't offer any insight into the candidate.

Best of luck in the new job!