Skip to content

Why interview questions for programming jobs are so difficult?

New Courses Coming Soon

Join the waiting lists

I have to say I hate programming interview questions. Why they are so difficult?

I have to say I hate programming interview questions. Why they are so difficult?

If you ever used a tool like HackerRank or read a coding interview questions book, you’ll probably agree with me. Yes, there’s a whole industry around coding interview and preparation for them.

I hate those. Not everyone agrees with me, on the Internet. Seems that many want to continue this “tradition”.

A couple years ago I decided I had enough with contracting / freelancing and I went through the hiring process of many different companies.

This was before I realized that I am basically unemployable, but this is another story. And by unemployable I mean I just cannot work for anyone else except for me, to build my own products and assets rather than building someone else’s.

About half of the companies I applied to had an initial screening with a practical “take-home” project.

No one asked me to implement FizzBuzz, or other algorithms that are often described as “required knowledge”.

We might get tricked into thinking that every hiring process is like the one you’d experience at Google. I read about people spending one year just to prepare for the Google interview, only to be rejected when they applied. Sad.

There are countless small and medium companies that never hire using a rigorous and sterile technical interview on topics like algorithms and data structures. At a whiteboard. Without Google and (gasp!) Stack Overflow.

Sure, it’s great to know those topics inside out, and I think you really should.

And I get the underlying thinking: the problems are basically all the same, with 10-20 variations. Implement bubble sort. Ok, I can do that. They just want to listen your reasoning on the subject. How you approach it. But in reality, it’s explaining what you remember of a problem you memorized. If the candidate is a fresh graduate, they might even remember it well. If the candidate is a person with 5 years of real work experience, they might not remember that.

FizzBuzz would be more reasonable. It’s not taught in school, the problem can be explained in 3 minutes, and you can reason about it.

But if I was to organize the hiring for my company, perhaps as a CTO, I would never ever put the person in front of a white board, and ask them to implement FizzBuzz. Why? First, it’s completely useless - you will never have to implement that in the real world.

Second, there’s so much stress on the applicant. A lot of people underperform under those conditions. Me included. I could show off perhaps 10% of my value, just because I can’t function well in such an environment alien to me.

DHH (David Heinemeier Hansson, creator of the super popular Ruby on Rails framework) once said: “I would fail to write bubble sort on a whiteboard”

It’s awful and perhaps only good at stress-testing the nerves of an applicant. Which is a completely different thing than testing the abilities to provide value to the company, like programming if I’m hiring a programmer.

No problem you can solve in a traditional whiteboard interview has any correlation with the actual job of a programmer.

I must think about when was the last time I spent some time deciding which algorithms to use, let alone implement a brand new algorithm. So why people are continuously asked about those things?

This is a tweet pointing that also big companies are moving in a better direction:

Practical knowledge. Ask us for this.

I remember one cool question I got at an interview: describe me what happens when you do a Google search. It was open ended, and was the start of a conversation on network protocols and the little things that happen. This was an intelligent question.

There was no whiteboard because it was a remote Zoom call.

Another interview was based off a coding challenge I implemented using React, offline. I had 7 days of time (not that the actual coding took 7 days, 3 hours was enough). The rest of the hiring process was based on the work I did on this code.

So, my answer the question “why interview questions for programming jobs are so difficult?” is probably “because the company hiring process is broken” and you should perhaps think “do I really want to work there?“.

Wouldn’t it be better to skip the interview altogether? The best thing to do would be to have a company contact you to work for them. You can do this in various ways: networking being one of the classic. In person at conferences, on Twitter, on GitHub.. there are many ways. Once you know and stay in touch with one or more employees of a company, the next time there’s an opening you can definitely be on the list for the position. Especially if they know and appreciate your value.

All, as usual, in my humble opinion.

Here is how can I help you: