| I don't mean to sound rude, but I feel like your response seriously lacks empathy. I am a father to a 2 year old, I have a mortgage and an existing full time job. The time investment required to go through a bunch of algorithms that are almost exclusively used in passing coding interviews does not offer the same ROI as, for example, streamlining a process that you are currently facing on a day to day basis. On top of that, something that I've learned recently about myself is that I have a tremendous fear of failing coding interviews. You see there is an emotional component to the effort you put in to doing one of those things. You go through the work to get accepted into the interview process then you find yourself face to face with "one shot" to impress. Maybe they've even flown you out to their location so you can go through this whole experience on site. At that point the optimistic among us might start thinking about things like what our lives would look like if we worked at "technological mecca" doing really cool shit for silicon valley dollars. So you start allowing yourself to think about watching the ocean on a sunny day eating avacado toast while you watch your now bleach blonde son playing in the surf. Your wife is happy too. You have this beautiful life that you're providing for those that you love. (in your fantasies you don't worry about the cascadia fault-line, the dystopian nature of US healthcare, or the fact that california seems to catch fire for a month every year nowadays) ANYWAYS, you go in, you give it your all. Maybe you think you nailed it, or maybe you can clearly come up with 20 better solutions in the 20 seconds after you leave. Maybe you studied 50 concepts intensely, but missed the one they picked to ask you about. You didn't get the questions in advance or anything. It doesn't matter though, you missed a semicolon on the whiteboard and your code doesn't compile when they type it in. You get a terse reply from your original recruiter "not a good fit at this time" ... there's no insight into what you did wrong or where you could get better. That opens the company up to legal liability. Anything more than "thanks" risks exposure. So you're left with days and weeks of effort for nothing. On top of that you have a real long flight home where you get to grieve the loss of that beautiful life you imagined. Do you work in a place where you can tell your colleagues at work that you were interviewing? If not, you can't even talk to the people in your life who are most likely to understand the pain you're going through. So you get to suffer alone. So. What does it say about someone? Absolutely nothing. |
1. DO NOT get emotionally involved or excited about an opportunity till the time you see an offer letter - those reeeallly sweet people that are so happy and courteous and smiley will switch in an instant, snap! throw you out faster than a used disposable cup and will not so much as give you the courtesy of a reply. They don't give flying f about you no matter how many hours they themselves invested in the process. See for them, this is paid work to talk to you, so they don't give a shit they do it for 10 hours and still drop you without even sending you an email. You are working for free during the interview process and have much more at stake in this process than the person you are talking to. You feel you're having a genuine human interaction with them? no. You think it went well because objectively it went really well? Don't worry you'll get a 2 line generic rejection email.
2. DO NOT ever gauge your self worth as a developer to passing or failing an interview - you will destroy your own morale. Take hints and learn to be better, no doubt, but the decisions people make about you sometimes don't have anything to do with you specifically so don't take it to heart too much.