10 ms·
As a candidate, I've always preferred polite "thanks, but no thanks" responses in a timely manner. The other kind of feedback that I like is things like, "we ne
by gwbas1c 7y ago
As a candidate, I've always preferred polite "thanks, but no thanks" responses in a timely manner. The other kind of feedback that I like is things like, "we need people with a different background / experience than you have."
IMO, judgement feedback (you screwed up how you handle your yak shaving, or I don't think we'll get along with each other) is too subjective to be constructive.
And, I get it. As someone who's interviewed a lot of candidates, my biggest fear is hiring someone who is either incompetent or difficult to get along with. Evaluating a candidate is so subjective that feedback beyond "your experience doesn't match our needs" is just flame bait, or worse.
To paraphrase Joel Spolsky: It's safer to pass on a good candidate than hire a bad employee.
- deleted 7y ago[deleted]
- CapmCrackaWaka 7y agoI feel that most of the time candidates just want to hear something that puts the situation out of their control, and therefore wasn't merit based. It's always easier to hear "I'm breaking up with you because I'm moving for a new job and want to concentrate on my career" than "I'm breaking up with you because you're awkward around my friends and aren't interesting".
- michaelborromeo 7y agoYou really want to go through life thinking you’re competent at something? Honest feedback hurts but it’s how you grow. And if people cared at all about interviewees they’d give some semblance of honest feedback rather than “no thanks.”
- adamredwoods 7y agoI had to dig to get any type of feedback on my interviews, and even then it wasn't clear on what I needed to do to improve.
- Koshkin 7y ago> what It may be not your fault. Or, it might have been your lucky day, not getting that job. In any case, you need to make damn sure that you know your trade.
- gwbas1c 7y ago> And if people cared at all about interviewees they’d give some semblance of honest feedback rather than “no thanks.” A former Apple architect once gave me "honest feedback" about the languages I work with. It was his opinion about industry direction, that 8 years later, was 100% wrong. (Although I don't think I was a good match for his startup.) That's why I consider honest feedback flame bait.
- danaris 7y agoIf you get a piece of feedback from one person, you know what you would need to do differently to get hired by that person. If you get similar pieces of feedback from 3 people, you now likely know what you need to do differently to get hired, period. It’s not about getting specific, individual pieces of feedback. It’s about being able to triangulate toward what you need to do differently. And maybe you get 3 pieces of feedback that are all completely contradictory. That tells you that what you need to do is keep trying.
- zeroonetwothree 7y agoThat assumes there is no systematic bias. Which clearly there is.
- lxglv 7y agoSure, there may be, and you will have proofs that it exists and may find a way, how to handle it.
- gunshai 7y ago>That assumes there is no systematic bias. Which clearly there is. This is a non-helpful statement. Humans are bias machines. We function based on our collective experience or in some cases differed experience. Saying there is systemic bias doesn't really add anything other than saying exploit what ever bias you can find to your advantage.
- mewpmewp2 7y agoAnd receiving that feedback helps you realize if there is any bias and adapt accordingly.
- adamredwoods 7y agoRejection is incredibly difficult to deal with. I suspect some people will say they are immune to it, but (anecdotal example) I've been rejected from hundreds of jobs over the past 3 years and every one hurts a little. I felt it never got easier to deal with rejection, but it got easier to interview and move on. Perhaps it's not the rejection, but the energy in creating the next steps I need to take (more resumes, taking classes, new career, therapy, etc).
- Koshkin 7y ago> rejected from hundreds of jobs Sounds extreme. Were you applying to random jobs?
- deleted 7y ago[deleted]
- adamredwoods 7y agoYou're right, it was probably only around two hundred or so jobs I applied to with 50% response/rejection rate over the past 3 years.
- thayne 7y agoUnfortunately, for many recent college graduates, it's not.
- stakhanov 7y agoIt's not extreme at all. Companies are treating it as a numbers game, which is part of what the article is about. The flipside of the coin is that candidates are forced into treating it as a numbers game too. For example: As a candidate you might submit a resume and get an automated "Thank you, we'll be in touch". There's a large variety of reasons why you might face a very low probability that someone will indeed be in touch that have nothing to do with you. The most common is that you're just too late in the process. They might already have dozens of viable candidates in later stages. They are being economical about their interviewers' time, thinking: Well, the probability that all of those later-stage candidates will end up getting terminated is low, so we're not doing first-round interviews for now. But they are not being economical about expectations created in candidates' minds about the likelihood of getting an offer. They've simply defined the process to say: We pull the advertising after the role has been filled, because there is always the chance that we will have to go back to candidates in earlier rounds. There might be even more extreme cases. Not saying that this is particularly common, but imagine a company has decided they need a diversity hire, say hiring a woman to an all-male tech team. All applications by men may be dead on arrival. They may not want to send out rejection letters so as not to establish the pattern. Or the role may have already been filled and there may simply be clerical error or clerical laziness to blame about why the advertising hasn't been pulled yet. So, from a candidate's point of view: "We will be in touch" means almost nothing. Having come across a job ad means less than nothing. Your calculation is simply going to be: I get one human contact out of every ten times I submit a resume. I get one firm offer out of every ten times I get a human contact. I'm shooting for three firm offers to choose from. So that means I have to submit my resume 300 times. Consequently you can't afford to be all too picky. You just submit to everything that could even remotely be a match. You only start putting real brain power into thinking about whether you actually want to work there in later stages of the process. It's a sad state of affairs, but it's just the world we live in now.
- thayne 7y agoI don't have hard numbers, but anecdotally, I know two people for whom this is simply not true at all. It took them months to find jobs, and they sincerely wanted to know why they were being rejected. If you are told "we didn't hire you, because you don't have skill X", or "you don't have any experience with Y", then you can focus on getting better at that thing. It was extremely frustrating for them to be told "We found a better candidate", or more commonly, getting no response at all.
- Loughla 7y agoThe problem is, often, there isn't a skill or experience that is the reason. I literally just went through this. I interviewed for a position that I am way qualified for. I check every box, in terms of skills and abilities and experience. I'm essentially doing the job right now, just with a different title. And I was passed over for a less qualified, less experienced candidate. The reason I was given, as I dove through the organization (it's where I work now) to ask for feedback to improve myself professionally, was that there wasn't really anything I can get better at, it was just 'fit'. I was able to ask probing questions to get to the root of that, and it turns out that, outside of the folks I work with daily, people outside of my division don't necessarily know my leadership abilities. But tell me, how would you even go about quantifying that for an external candidate, other than saying the, very safe, 'we found a better candidate'?
- croon 7y agoEasier? Yes. Helpful? Not IMHO. I spent my first 20 years on this earth incapable of processing critique, regardless of merit. It was incredibly difficult to get out of that. But once you realize that rejection or critique is just input, you can learn from it. It's obviously not always helpful, but the majority of the time it sure is (YMMV). You can categorize some cases into these: 1) Someone has observed something you do that you're unaware of, and could work on. 2) Someone has misinterpreted something you do, and now you know they have, but can be glad they told you so you know where they stand, and/or clear the confusion by explaining what really happened. 3) Someone doesn't like something you do, but you are already aware of you doing it, but think your way is better, for reasons X, Y and Z, and if you feel like it you can explain that. 4) Someone who has more experience than you recognizes a behavior from their earlier selves, and points this out so that you get a head start at learning their lesson. Regardless of the merit of the feedback, you can't process it and deal (or not deal) with it until you hear it. If you can step away from yourself and just observe and reflect, there are so many things you can learn that I wish I could imprint on a younger me. But at least I'm trying to catch up as a 30-something now.
- cheez 7y agoI love judgemental feedback, because then I can return it in kind.
- sjg007 7y agoThat's probably why they don't offer it and why the interviews that do have become more exam like vs reciprocal. That a big tradeoff to make. I am not sure of the full implications but we do see issues with teaching to the test as well as examination driven cultures in traditional schooling. These test driven processes do not translate into economic success as you'd expect.
- cheez 7y agoMore or less why I refuse to waste my time interviewing. I'd rather spend that time increasing my independent earning potential
- monksy 7y agoAs long as it's not in a phone call. That's a huge waste of time just to be told that they're passing. Google insisted on a call. It's just annoying.
- jeffdavis 7y agoA phone call is considered more respectful than an email. It may waste time, but signs of respect often do.
- solveit 7y agoWasting time is the feature. The fact that it wastes the caller's time as well is the reason that it works as a sign of respect.
- ulfw 7y agoIt's not particularly respectful when it's a rejection. Especially when YOU have to find time on your calendar to make the call (which you already know is a rejection) just to schedule a five minutes "we can't tell you why, but you can apply again in a year" BS
- monksy 7y agoNo way man. Being terminated by phone or in person is respectful compared to email. Being rejected by phone for something that for most times is going to not be successful, that's just twisting the knife. At the moment I don't know how to respond to call requests when it's not successful. I fear that saying: "Hey if this is a rejection, I would prefer to just get an email. I understand."
- jeffdavis 7y agoLike it or not, a phone call is considered more respectful. Respectful doesn't mean easy, pleasant, or efficient. And the standards for respect are not set by any one person; they've evolved over a long time.
- pinewurst 7y ago
- mlthoughts2018 7y ago> “It's safer to pass on a good candidate than hire a bad employee.” After a decade of building teams in machine learning, I regard this as one of those hallowed mythical pieces of wisdom that is just totally wrong. It dramatically over-estimates both the chances and costs of hiring a bad employee, while discounting the huge, huge opportunity cost of not hiring rare, exceptional candidates. I’d much rather spend a year or two managing someone out as a result of actually trying to hire exceptional people than living with mediocre hires who memorized the right fizzbuzz HackerRank crap and said all the right Team Player catch phrases to get hired.
- solveit 7y agoHow large is your company?
- mlthoughts2018 7y agoThe policies in question have worked well for me doing team building in 4 companies, 3 were medium/large ecommerce companies (~1000-8000 employees), one was a 40 person start-up.
- mc32 7y agoA large company can afford bad hires. You can shuffle them around or find something they can do. A small company can not afford that luxury so they have to be more careful in their hiring. A bad hire completely distracts a small team.
- boring_twenties 7y agoWhy is simply letting the bad employee go not mentioned as an option? We had a new hire that didn't work out at a place I used to work at. Fired after 3 months. No hard feelings, he took it well and found a good job a few weeks later. Everyone is happy.
- qes 7y ago> Fired after 3 months. Which means you probably went 6 months or more without a role properly filled. On a small team that's a huge dent. For half a year. Not to mention the time spent in the hiring process itself, which you now get to repeat.
- kmonsen 7y agoInterviewed with two fairly large "startups" in SF recently. Both just ghosted after the interview. I actually don't need the feedback, I realized something I had not prepared well for, but a "No thank you" after taking a day of would have been nice.
- mwilcox 7y agoVC funded companies are often the worst when it comes to hiring because they are overcapitalised yet time sensitive - employees are more like contractors when they're brought on to address a short term issue without any real guarantee over a longer term than 18 months
- burtonator 7y agoMy worst interview was where the interviewer started yelling at me. After the interview the recruiter sent me an email and told me that he wouldn't work with me anymore as I was hostile during the interview. It was insanely bizarre. It was like being found guilty without ever even being given a trial or being told there was a trial.
- xref 7y agoSounds like you had a bad recruiter setting you up with bad interviews. You can throw a pebble and hit five recruiters so no need to stick with a dud anyways.
- fiblye 7y agoI had something similar. I was given an extensive exam to take before the interview, and it consisted of weird things like 200 arithmetic problems in 15 minutes, picking the best synonym for 100 words in 5 minutes, etc. Things not humanly possible without immense preparation for that precise test. The interviewer comes in and starts berating me for not finishing and how I must’ve gone to a bad school, must not be smart, etc. Then he goes on and on about how I’m clearly not suited for the job and his young assistant is sitting beside him laughing. It was a crazy interview. I mentally gave up after a few minutes because the guy was clearly fucking with me and didn’t want me, so I started giving smart ass responses since there was no reason to let myself get beat up. I get a call a few hours later telling me I can start any time. I told the recruiter to tell the company that the interviewer was a dick (in nicer words) and I’d pass. Worse than no feedback is opposite feedback. Don’t play mental games with people.
- leetrout 7y agoI interviewed at twitter for a job working with their infra team. They had an Atlanta data center and they were interviewing me for that role to be remote out of Atlanta. I had to fly to SF to interview via video calls with the team in Atlanta because the manager was in SF. He told me he would prefer someone local in SF over lunch so I knew I was just filler. After lunch interview was with a xoogler and everyone earlier warned me it would be a “google interview”. So he struts in and asks what I know about number theory. I say nothing and he tells me he was a math major and proceeded to ask math proof questions and push on the math side of things the whole time. Weirdly instead of asking how to make a Cartesian product in SQL he had this round about way of describing baseball players and teams and generating a report of games played. So as it went on I gave up. He asked me toward the end how many prime numbers there are... I answered “optimus prime”. He looked at me and asked if I seriously wanted him to write down “optimus prime” for my answer and I swear on my life I looked at him and said “yep. Autobots roll out”.
- mewpmewp2 7y agoI would rather get subjective feedback than none at all. But I understand that some people can not take criticism or feedback so everyone has to lose out on it.
- perlgeek 7y agoThere is another type of feedback that I as a candidate would find helpful, and that I would have liked to give candidates, but didn't due to corporate policy. Something along the lines of: "To pay you as much money as you requested, we'd have to categorize you as a [Senior/Prinicipal] developer, but your skills/experience only put you at [Junior/Professional]". If, as a candidate I had received this kind of feedback from two or three companies in one vertical, I would know that I have the choice between getting payed less and switching to a different vertical that pays better.
- Doxin 7y agoWhat exactly was the policy that caused this? In my (luckily very limited) job searching experience, the salary is something that gets negotiated. I ask for something on the high side, they offer something on the low side. Repeat until you end somewhere reasonable. The only thing I can imagine causing someone to not be hired on salary without them knowing the reason is if there's no negotiation.
- humanrebar 7y agoRight. It's better to offer the candidate what the company is prepared to offer, both in terms of position and compensation. Let the candidate decline. At least some candidates will like the company enough to try working their way back up. Though I'm sure acceptance rate is in some KPI, so there could be some bureaucratic nonsense involved.
- perlgeek 7y agoThat's a cultural thing in the company I work for (or maybe broader in Germany, dunno), where some people think that if they start to negotiate, they might lowball candidates, and then they leave after half a year or so. We try to hire more long term (we aim for 5+ years retention), dunno if that's related, or if there is any evidence to back this procedure. I find it a bit weird myself, which is why as a candidate I'd like to know about it :-)
- precisioncoder 7y ago
- afpx 7y agoI think the idea of only hiring the best is misguided. I’ve hired dozens of people, and I’ve yet to hire a “bad” one. So, either I’m really good at picking the good ones, or there is a low bad candidates per non-bad candidate ratio. Now, not every one became awesome. But, there are places for even the non-best developers to be productive. Good management is putting best employees on critical systems and others in supporting roles.
- gwbas1c 7y ago> Now, not every one became awesome. But, there are places for even the non-best developers to be productive. Good management is putting best employees on critical systems and others in supporting roles. But how many did you reject because your other reports said no?
- goatinaboat 7y agoIt's safer to pass on a good candidate than hire a bad employee. Hence the byzantine process interviewing has become. Like most of what Joel says it’s flattering to the audience but just not true. Pretty much every company in the universe operates a 3-month probationary period. The risk of a bad hire in the real world is well mitigated. Also true in the real world, it is better to do this than waste months of time looking for the perfect candidate when you could easily get someone decent on board in mere weeks.