> If you work for a company there is some expectation of being able to work while people watch you.

I don't know what kind of company you work for, but, in spite of the fact that every single technical interview I've ever had involved live coding, I've literally never had to write code in front of anyone at work. By "write code" I mean "write code that's expected to compile and run." I've done plenty of whiteboarding at work, but never anything like what happens in a technical interview.

you never had to work through some piece of code together with a team mate? to get help or to explain to them how something works?

That's not in any way comparable to live coding in an interview, for multiple reasons.

ok, you are right.

i brushed over this bit, which makes the critical difference:

write code that's expected to compile and run

for what it's worth, i never had an interview where this was required (except in a coding test, but that was without being watched while i worked on it) and to me it totally does not make sense especially for a whiteboard. making sure every semicolon or brace is in the right place would just be a colossal waste of time.

> You can still be coached through a take-home and follow-up though.

Of course. Anyone who lacks the ability to complete the assignment can submit a solution written by someone else and be told how it works. Where they’ll fail in follow-up questioning is when you dive into their decision making process.

I have only found one person to have cheated in an interview, and they were exceedingly easy to identify as a fraud when questioned in person.