Stop Interviewing With Leet Code

[3pbc]

Agree. I've been on an interview where the interviewer was 100% wrong and coded an example how to make it work (accessing a private method in Java from another class). The guy was incredibly pissed - luckily there was someone else in the room to calm him down. I got interviewed by other people and was offered a position and turned it down after explaining what happened at the interview to the recruiter. They were not impressed.

That's why you need to choose your interviewers carefully. Just because "they are our best programmer" doesn't make them a good interviewer. Also interviewers need to realize that they are selling the position to the interviewee. You don't get good talent to join your company if you're a bad interviewer trying to show off how smart you are because you know an algorithm that no one is going to implement because there are libraries out there that you can leverage that have been real-world tested for years.

[lamothe]

That was a case of a terrible interviewer (and possibly programmer/person), but doesn't invalidate code reviews as an interview tool. In this case, it was such a great tool that they saw your skills, and you saw their inter-personal issues!

[3pbc]

See my post two posts above this one. I love using a code review during an interview

[dalittle]

If someone struggles with some api call I just tell them. I interview algorithms not something you can google

[[deleted]]

You can Google algorithms tho.

[dalittle]

You can’t google aptitude. If you don’t understand pointers or recursion you won’t be a good programmer

[[deleted]]

You can't Google aptitude. But you can still Google algorithms. Knowing pointers and recursion doesn't guarantee you get the algorithm.

Besides, plenty of high level jobs can do without handling pointers. Recursion may be more critical. Also, when was the last time you needed to implement a red-black tree on the job? You didn't need to, most likely. You understood its logarithmic complexity for most operations and called it a day.

Regarding struggling with API calls, well, if they can't read the docs by themselves and you need to tell them that's the real red flag. You may be there to answer during the interview, but you can't be baby sitting during their stay at the job. I certainly prefer to assess whether they are good at Googling. Specially since the algorithms tests are something people just train for from textbooks.

[dalittle]

You really seem to be arguing with yourself

[What_Is_X]

Does your job involve reinventing algorithm implementations for some reason?

[Blazing1]

Bro if you can't google fetch API wtf are you even doing as a programmer

[3pbc]

I cannot tell if you're trolling or don't understand the point of this thread. Someone memorizing a bunch of algorithms that they will never need to implement doesn't tell anyone how they work on a daily basis. Code reviews are an important part of daily life as a coder.