Once they hit the on site interview it should be more about how they can work together with a team, how they would design systems, what they would do if they needed help, etc.
Coding up FizzBuzz on-site is a waste of everyone's time.
I should also add that I personally prefer to do coding questions in person on a whiteboard, rather than doing them during a phone screen with some sort of collaboration software.
My technique of explaining the algorithm before asking the interviewee to implement it works way better with both people in front of a whiteboard.
I'm not saying everybody should do it this way. I'm just saying that this is my current approach and it seems like it's working OK.
While I dislike the way most large tech companies handle their interview process this one I don't mind as much.
When I say simple, I mean really simple, like FizzBuzz simple.
There are interesting questions you can ask that are really simple which are not FizzBuzz. I've used the Fisher-Yates shuffle algorithm and more recently Selection Sort. I should stress in both of these cases that I carefully explained the algorithm before asking the interviewee to code it up. Even though these algorithms are quite simple, I do not expect the interviewee to have memorized them.
I do expect someone who is a professional software engineer to understand the algorithms after a decent explanation and then write code which will implement them.
I also don't necessarily expect the interviewee to get the code exactly right. I just expect them to demonstrate that they could write correct code given enough time and access to an actual computer to test the code on.