Memorizing behavioral scenarios and regurgitating them in every behavioral round for every company to convince them that you have the work ethic of Albert Einstein and the affability of Robin Williams.
Code abstraction during coding rounds. Write the code as literal pseudocode and implement each abstraction later, this is especially useful for rounds focusing on OO design, but also applies to leercode rounds.
For example if my solution has bfs, my code would have “bfs” as a subroutine. And in my bfs I would have “add neighbors” and “check invariant” as subroutines. So my code ends up being mostly memorable boilerplate with custom implementations to solve the problem. Makes it easy to explain and easy to understand, and you can sometimes get away with saying “do you want me to implement this?”
I have a habit of talking to my code. It freaks out people when I'm intense coding near them but interviewers love it and I don't have to put extra effort to "communicate" 😂
comments
For example if my solution has bfs, my code would have “bfs” as a subroutine. And in my bfs I would have “add neighbors” and “check invariant” as subroutines.
So my code ends up being mostly memorable boilerplate with custom implementations to solve the problem. Makes it easy to explain and easy to understand, and you can sometimes get away with saying “do you want me to implement this?”