4 ms·
I believe your error here is "without even going on one interview". There are many developers who have proven their skills and abilities on the job, and also h
by diggernet 9y ago
I believe your error here is "without even going on one interview". There are many developers who have proven their skills and abilities on the job, and also have a proven ability to repeatedly fail interviews. This is precisely why the developer interviewing process is such a hot topic here.
- jack_h 9y agoThere's another aspect that I can speak to personally. My career never really got off the ground. For most companies I'd get through all of the technical phone interviews just fine and after the in-person interviews it was always a rejection. Coupled with my deteriorating financial situation that lead to a lot of depression and massive amounts of self-doubt. To this day I still doubt my abilities quite heavily. Friends and coworkers say I'm smart and talented and whatever, but quite frankly I don't believe them. These interviews can be soul crushing to people with my type of personality.
- monkeywork 9y agoare you suggesting that if you have "proven yourself " you should be able to skip the interview process?
- daveFNbuck 9y agoThe suggestion, which many experienced people also make, is that once you've proven your ability the interview shouldn't focus on that. Spending 5 hours asking about algorithms is a waste of time when you already know someone has the technical chops.
- nsxwolf 9y agoI didn't do a technical interview at all for my last few jobs.
- diggernet 9y agoI am suggesting that "Why not try and go on some interviews?" is a silly, and potentially offensive, thing to say in response to someone describing their difficulties with the interview process. Especially when discussing a field where there is considerable ongoing debate about the usefulness and sensibility of various common interview techniques.