HACKER Q&A
📣 ZhL

How to improve a whiteboard interview performance?


I have recently started looking for a new job. And I think I have a performance problem when it comes to a whiteboard interview.

I often struggle to come up with any kind of specific solution on the spot even if I can outline the general idea. I don't usually feel particularly nervous, so it is not that. Shortly after an interview ends, on my walk outside, I often have a breakthrough when the solution comes to me in a much greater detail, so that I can articulate it much better at least to myself.

I have also noticed that I can typically only solve Medium problems on LeetCode within an hour when left alone. Hard problems often take me a couple of hours at least.

The observations above make me think that maybe I'm slow and/or ill equipped when it comes to solving problems on the go. And certain types of problems are easier for me to solve in solitude.

Does anyone have any suggestions what I can do improve my onsite performance? I will of course keep on practicing, but certain opportunities are getting away from me.


  👤 subhobroto Accepted Answer ✓
Hey ZhL,

that's not just you.

It's me and everyone else I know.

That's why these are called whiteboard firing squads.

The only way I know to improve on whiteboard interview performance is to do more whiteboard interviews unfortunately.

I know it does not make sense. I know it does not teach your or help you further any actual skill you will actually use day to day, but that's the problem we programmers have painted ourselves into.

The "remote" equivalent to whiteboard interviews are "live coding" sessions where you type code into a site like codebunk.io

Some random person who works at your potential employer will send you a link to a site you can type code into and ask you to solve a "5 minute problem". It's not fizzbuzz, it's not a for loop - it's going to be something slightly tricky like finding the sum of 3 numbers that add up to a specific number.

One thing I can recommend at a whiteboard firing squad is to see whether the firing squad has people in it that want you to win.

If you think out loud, show them you know what you're talking about, they might come out, feel your issue and work with you.

Isn't that the kind of people you want to work with regularly anyways?

I am happy to work out some trial whiteboard interviews with you if you feel that would help.


👤 photawe
I interviewed at FB London about 6-7 years ago, and they also gave me whiteboard interviews. They're one of the stupidest things ever invented.

If you want to master it, I guess you need to buy a whiteboard, and have a programmer friend give you random problems on a timer.

Having said that, do you really wanna work at a company that does this? I would never ever go to FB again, and not just for the pathetic and horrendous things it does, but the interview process just feels like "ooh, i know this crappy thing that was taught in high school, which nobody actually uses/needs, and you don't".


👤 he11ow
It's been a long long time since I've interviewed for a developer job, and unless anything wildly radical happens, unlikely to happen ever again. BUT... At the time I recall that what worked very well was that I'd start with the knucklehead solution. I'd say, "Well, a naive way of doing this would be..." and what this does is buys a bit more time of thinking as you talk through the facile way of doing things. That alone is not going to be enough to pass this kind of interview, but I remember this as a useful trick.

👤 itronitron
I've only experienced one whiteboard interview in six onsites within the past three years, so their popularity may be waning.

Also, there seem to be several different types of whiteboard interview, a) the algorithmic solution, b) the conversation starter, and c) the problem analysis. I mention this so that you don't focus solely on the algorithmic type, the other two really are there to help interviewers know how you approach problems.


👤 dyingkneepad
If I ever get into a position where I will be interviewing like that again, I will definitely buy a white board and solve coding problems on your white board, alone. This should get us a little more familiar with the actual interview situation. It's not 100%, but it's something you can easily start doing today.