3 ms·
Good 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, an
by nunez 10y ago
Good 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.
- omegote 10y ago> 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.
- Retric 10y agoConvincing others not to cheat is a useful strategy. Not cheating yourself is less useful.
- user5994461 10y ago> if I'm a Rails developer that wants to become a SRE at Google Of course, you're probably not qualified for the position. Thus it's normal to have troubles in the interview. This sort of transition used to be done by joining a "junior" position and getting trained on the job, without having to pretend to be a wizard. Unfortunately it's hard to accept for one's ego that he has to continue as a not senior when changing fields, and it probably makes no sense on a financial perspective since an experienced ruby dev might earn more in his niche.