[daveguy]

The important thing is not to ace the final result. The important thing is to communicate your thought process, identify bugs, talk about options in architecture and design, stay calm under pressure and keep a positive attitude even when asked to do something you think is silly.

The interviewers know "this exact problem" is not generally applicable to their work. They are looking at how you interact with the problem.

Projecting a bad attitude toward being asked to code on a whiteboard is the opposite of what you should do and misses the point entirely. Code golf and competition (right answer in min time) is not the point.

[ojr]

you can't communicate your thought process on hackerrank or triplebyte it is a timed online test