Live data from Hacker News

Why I Don't Prepare for Job Interviews

dev.to

11–20 of 83 posts

Re: Why I Don't Prepare for Job Interviews

#11

Good piece, but misleading title. There is a big difference between "cramming" and preparing. Like the author says: "Preparing by learning about a company and its product makes sense. But preparing for an interview by cramming/studying material that is supposedly needed for the job makes no sense." When I get a candidate who has no sense of the job they are applying for and is not able to ask meaningful questions, it…

The issue is that companies like Google EXPECT you to cram on algorithms before the interview.

They will even give you a study guide!

Being really good at programming on a whiteboard is the name of the game. And studying for this is absolutely useful, and not "cheating" because everyone does it and is expected to do it.

Re: Why I Don't Prepare for Job Interviews

#12
What world does this guy live in where he is being asked relevant questions to the stuff that he would be doing at work?

Sure, if we live in this fantasy world, where the person who passes the interview is by definition going to be good at the job, then his advice makes sense.

Unfortunately, the world we live in is one where you have to program algorithms on a whiteboard to get a job in web dev.

And for THAT world, it absolutely makes sense to study this material that you don't use in your job, but are being judged on.

Re: Why I Don't Prepare for Job Interviews

#13

What world does this guy live in where he is being asked relevant questions to the stuff that he would be doing at work? Sure, if we live in this fantasy world, where the person who passes the interview is by definition going to be good at the job, then his advice makes sense. Unfortunately, the world we live in is one where you have to program algorithms on a whiteboard to get a job in web dev. And for THAT world, i…

I've interviewed for at least 10 web dev jobs in my career and have never been asked to whiteboard anything.

Re: Why I Don't Prepare for Job Interviews

#14
There's a big difference between software development job interviews and job entrance exams that is often not evident on people who aren't deeply immersed in software culture.

Interviews happen in every industry. An interviewer asks about your interest in the company, your background, your leadership skills. Your technical skills may be investigated here, but in a discussion format. You may be asked questions about your knowledge of a database or perhaps a programming language, but you won't be tested specifically on that language.

Then there's the technical "interview" that is really an exam. Google's interview is a good example of this. You go up to a whiteboard, and the interviewer says "write a method to convert an integer to binary. Now add and subtract in binary. How would you square a binary number". You should be writing code on the white board, in either a real language or very tight pseudocode, to do this. Alternatively, the interviewer might ask you to find your way out of a maze, probably through some kind of graph traversal algorithm. Again, you really do need to write code that solves the problem.

This style of interview is indistinguishable from an exam. I think it exists because programmers don't have an actual exam in their field. It might be similar to asking a senior actuary to find the linear span of a vector space. There was almost certainly a time when the actuary could do this, since the actuary took an entrance exam on vector calc and linear algebra, but it isn't something a senior actuary most likely walks around ready to do. It would require re-studying.

As a few others have pointed out on this thread, there's a difference between studying for an exam and prepping for an interview. I've resolved not to do the latter anymore, but I really may simply not have that choice. The practice is deeply entrenched. But the former, of course I'd prep for an interview.

And also, you know, I actually think it's a good thing that lawyers take the bar, that actuaries take math exams. I don't think it's outrageous that people who hire programmers would want to know that these programmers have, at one time, passed an entrance exam on data structures and algorithms, binary operations, and so forth. The problem is that because we don't have such an exam in our field, we have to take a random and often unexpected version of it, under conditions of secrecy, with no feed back, evaluated by people who may not be qualified and who can be captious and arbitrary in their assessments.

Re: Why I Don't Prepare for Job Interviews

#15
The one time I crammed for an interview, it worked, but it was an unusual case. The job was to work with Peter Norvig at the search startup where he was chief scientist, back in the 90s. So the day before, I took his book AI: A Modern Approach and reread the chapters on natural language. An upcoming interview concentrates the mind, and I noticed several mistakes, including a bug in the pseudocode.

(They did offer the job, but for not enough money after I naively answered the salary history question. Oops.)

Re: Why I Don't Prepare for Job Interviews

#16

Good piece, but misleading title. There is a big difference between "cramming" and preparing. Like the author says: "Preparing by learning about a company and its product makes sense. But preparing for an interview by cramming/studying material that is supposedly needed for the job makes no sense." When I get a candidate who has no sense of the job they are applying for and is not able to ask meaningful questions, it…

The issue is that companies like Google EXPECT you to cram on algorithms before the interview. They will even give you a study guide! Being really good at programming on a whiteboard is the name of the game. And studying for this is absolutely useful, and not "cheating" because everyone does it and is expected to do it.

How does one become really good at programming on a whiteboard? Should you rent a conference room and hire a couple of people to play the part of the interviewers and just practice?

Re: Why I Don't Prepare for Job Interviews

#17
I always "prepare" for interviews, I learn about the company, what they do, their stack if it's public, etc. I don't bone up on my knowledge of programming or how to implement an N(x) sort or anything like that. If I don't know it then I don't know it and cramming to try and show off that yes I listened in my CS classes back in college seem disingenuous and misleading. I will succeed or fail on my own merits and I will not pretend I'm something I'm not. I know what I know and if that is not the person they need then it's better for both of us to walk away and look for something that better fits our needs.

Re: Why I Don't Prepare for Job Interviews

#18

Earlier quoted context omitted.

The issue is that companies like Google EXPECT you to cram on algorithms before the interview. They will even give you a study guide! Being really good at programming on a whiteboard is the name of the game. And studying for this is absolutely useful, and not "cheating" because everyone does it and is expected to do it.

How does one become really good at programming on a whiteboard? Should you rent a conference room and hire a couple of people to play the part of the interviewers and just practice?

I don't know about the US, but in India there are coaching institutes where you can pay money to be taught exactly that, how to clear interviews of Google, Amazon etc. They make you practise all sorts of algos on whiteboards.

Re: Why I Don't Prepare for Job Interviews

#19

Earlier quoted context omitted.

The issue is that companies like Google EXPECT you to cram on algorithms before the interview. They will even give you a study guide! Being really good at programming on a whiteboard is the name of the game. And studying for this is absolutely useful, and not "cheating" because everyone does it and is expected to do it.

How does one become really good at programming on a whiteboard? Should you rent a conference room and hire a couple of people to play the part of the interviewers and just practice?

That would work, but you don't have to go THAT far.

When I say "program on a whiteboard", I am mostly talking about the google style algorithms questions.

The way to practice for those is to just do a whole bunch of them, and talk to yourself, like you are in an interview.

It is just CS 201 material. All the material is out there for anybody to study.

The best materials are Cracking the Code interview, as well as the Google University github page.

There are also free resources out there for doing real life practice interviews, and pairing you up with people who do that.

Preparing for the Google Style interview is a whole entire industry.

Re: Why I Don't Prepare for Job Interviews

#20
Cramming for an interview, especially in the early stages of one's career is actually a great advice that helps you grow your technical skills.

If you can learn over the weekend just enough about some technology to pass the interview , then, after you get accepted you'll have another month before you actually join (standard notice period)

After that month of learning and another month of "onboarding" in the new workplace no one would be able to tell the difference between you and someone that has 1 year of actual experience in the given technology.

"Fake it untill you make it" - that's how I got my first 3 or 4 jobs :)

Post reply on HN