Why I Don't Prepare for Job Interviews
1–10 of 83 posts
Re: Why I Don't Prepare for Job Interviews
#2Good 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 tells me they don't care or don't understand.
If you are completely unqualified for the job, you will be found out, but if the difference in skill/experience is small enough, it's probably best to be honest about the gap. In that case, "studying up" may be a risky investment of your time, but at best it may show your commitment and at worst you will have picked up some new skills :)
Re: Why I Don't Prepare for Job Interviews
#3Good article, but I disagree.
When interviewers ask you all sorts of minutiae that are outside of your experience and also not at all required for your job, and when those companies have extremely lucrative compensation and benefits package with "dream" work cultures (for most), not preparing for that interview puts you at a disadvantage for someone who has.
If you're trying for stretch roles that your experience doesn't cover for whatever reason, not preparing for those interviews will put you at a significant disadvantage.
Most interviews are set up to be an unnatural setting that is, unfortunately, often set to work against you. This is changing slowly, but it is what it is. Not having the skills to navigate that environment isn't bad per se but does worsen your position against someone who has.
An example: if I'm a Rails developer that wants to become a SRE at Google, and my current workplace is too small to give me the experience I need to coast through their notoriously tricky interview, what do I do? Do I take this author's advice and go in blind and wait for the beating that is about to come? Or do I learn what I need to learn to get through it, fail once or twice and iterate?
I would not be where I am today without having prepped for my interviews. I also won't ever ding someone for prepping for an interview. Quite the contrary, prepping shows that they care at least somewhat.
Re: Why I Don't Prepare for Job Interviews
#4His main argument seems to be:
>But preparing for an interview by cramming/studying material that is supposedly needed for the job makes no sense. A candidate should have the experience to do the job well.
I think it is a good ideological stance. However, what about the scenario when you are applying for a junior position and don't have that much experience?
Moreover, as it has been demonstrated time and again, technical hiring is broken. Some folks like to talk about high-level concepts; some folks like to ask trivia and some others like to ask you to whiteboard the algorithms. If a company expects you to use a whiteboard and you are not used to it, you are not going to do well even if it is a topic you are familiar with (We don't realize how much we rely on editor/autocomplete).
I am happy that he was able to find another job without preparing, but this advice will not work for the majority of people.
Re: Why I Don't Prepare for Job Interviews
#5Good article, but I disagree. When interviewers ask you all sorts of minutiae that are outside of your experience and also not at all required for your job, and when those companies have extremely lucrative compensation and benefits package with "dream" work cultures (for most), not preparing for that interview puts you at a disadvantage for someone who has. If you're trying for stretch roles that your experience doe…
> Or do I learn what I need to learn to get through it, fail once or twice and iterate?
There's a difference between trying to _learn_ to get through and cramming as much "knowledge" as possible just to spit it out in the interview, and what usually happens is the second case, specially regarding algorithms.
Re: Why I Don't Prepare for Job Interviews
#6I think most devs would not be doing themselves a favor if they didn't "cram" before a Google / Amazon / Microsoft style interview, even if they are quite senior and very qualified to succeed in those companies. Assuming of course they want such a job.
Re: Why I Don't Prepare for Job Interviews
#7Unfortunately I don't think interviews are a good tool for working out someones suitability.
Interviewers have so many biases and pet interests. If you happen start talking about something technical(Some side project using x technology) you both enjoy, you instantly get on, and its great.
If start talking about a side project the interviewer has no interest or knowledge in, not so great. It becomes hard work.
There is an element of luck about who is interviewing you.
Re: Why I Don't Prepare for Job Interviews
#8Good article, but I disagree. When interviewers ask you all sorts of minutiae that are outside of your experience and also not at all required for your job, and when those companies have extremely lucrative compensation and benefits package with "dream" work cultures (for most), not preparing for that interview puts you at a disadvantage for someone who has. If you're trying for stretch roles that your experience doe…
Convincing others not to cheat is a useful strategy. Not cheating yourself is less useful.
Re: Why I Don't Prepare for Job Interviews
#9For me, preparing for an interview for weeks (or maybe months, I've even heard of interview preparatory courses) by reading exam-like stuff that won't have any effect to your job but are interview preparation only is an insult to my personality. I would never do it and of course I don't want to work on companies that don't respect me. The most important perk for a job (for me) is to feel respected.
Re: Why I Don't Prepare for Job Interviews
#10His main argument seems to be: >But preparing for an interview by cramming/studying material that is supposedly needed for the job makes no sense. A candidate should have the experience to do the job well. I think it is a good ideological stance. However, what about the scenario when you are applying for a junior position and don't have that much experience? Moreover, as it has been demonstrated time and again, techn…
>technical hiring is broken
>this advice will not work for the majority of people
That sums it up, the advice is good but since technical hiring is broken it doesn't work. This is why having a good interviewer is pivotal for a company. Someone who knows the company well and is good at reading people quickly and accurately