A couple of phone screens, then a ton of on-site interviews in one day. Everyone was friendly, but the questions were hard.

Since then, I've been on the other side of dozens of interviews, as the interviewer. One of the more common pitfalls is just solving the problem, without showing clarity of communication.

As an engineer, maybe 10-20% of your job is writing code to solve a problem; much more of the job is about explaining to other people how you've solved a problem, or why you've solved it that way.

It may seem like the interview is all about writing code to solve a problem, but it's actually about both writing code to solve a problem and communicating clearly about how you're solving the problem.

What happens when you type google.com into your browser and press enter?