The technical content is the same as in person. The failure mode is different.
Talk the whole time
In a room, an interviewer sees you thinking. Over video they see a frozen face. Narrating — "I am going to check the empty input case first" — is not optional, it is the medium.
Clarify before coding
Two minutes of questions about input size, edge cases and expected output prevents ten minutes solving the wrong problem, and it scores well on its own.
Handle being stuck out loud
"I have ruled out a hash map because of the ordering requirement, so I am considering a sorted structure" is a strong answer even without a finished solution.
Common questions
What if I cannot finish the problem?
Partial solutions with clear reasoning often pass. Silence rarely does.
Can I look things up during a technical interview?
Usually yes for syntax, if you say what you are looking up. Ask at the start.