I was frustrated, because I was never good at explaining my thought process on the technical problems they gave...until it dawned on me that I was overthinking everything and didn't go into the interview with any strategy.
So many Computer Science students skip this part and jump straight into the code, only to wind up at a dead end or confused, which just wastes more precious time.
The advantage to this approach might become more clear with a basic sorting problem.
It is ideal in my mind that you create a few different examples.
Before you even start writing or thinking about any code, take your examples that you created, and solve the problem verbally.