28 ms·
I believe that the article is fundamentally wrong. The bulk of the article is true. But companies are not lying when they say that legal risk is a reason not
by btilly 8y ago
I believe that the article is fundamentally wrong.
The bulk of the article is true. But companies are not lying when they say that legal risk is a reason not to send feedback.
Triplebyte is in the unusual position of being able to say, "Everyone who has enough technical skill gets through the interview." And that fact is sufficient to defuse their risk. But real companies don't have the luxury of ignoring non-technical aspects of the job.
Here are real reasons why I've seen people denied a job. "Nobody could understand his accent." "Accidental personal referenced summed him up as, 'Loves to make things crash and burn in production to see the pretty fireworks.'" "Nobody could believe the argument he got into at lunch."
In my books those are all valid reasons to not want to work with someone. However the first opens you up for an accusation of racism, the second would break a personal confidence, and the third had demonstrated sufficient irrationality that tiptoeing away was a great idea.
And you can't give feedback on technical issues, and not on the rest, because that amounts to a tacit acknowledgement that there was something non-technical. Leave the non-technical to your imagination and guess what happens?
- marcoperaza 8y agoOn the point of legal risk, I’m concerned by the authors naïveté in believing that as long as you’re not actually discriminating based on race/sex/religion, you won’t be accused of it. The more data you put out there, the more likely that someone will crunch it and find some statistical patterns that they will label “racism” or "sexism". Even if you’re innocent, you will get dragged through the mud in the press and maybe even in court. Not worth it. No matter what, you lose. And what’s the upside? You gave some random guy some feedback. This is the world we live in, unfortunately.
- mrkurt 8y agoThe upside is that you've treated a human being with decency. People you treat decently in rejection help you with later hires. If you're going to argue the fantastical downside, you should at least acknowledge the possible upside (which my company, and apparently TripleByt, have both experienced).
- marcoperaza 8y agoThat’s why I said it’s unfortunate. I intended to capture the logic of why things are what they are. And as much as it’s great to help someone out with some feedback, it’s not so great to risk the livelihood of your employees—you know, the people who actually depend on you to provide for their families—and the survival of your company for it. Sometimes doing the right thing requires you to have some perspective and be cold. This is one of those situations.
- mrkurt 8y agoI think you're way overblowing this, but it's possible you know more than I do. What makes you think "either willfully or accidentally mis-interpreting rejection feedback" is a meaningful threat to any company? Have there been cases where companies were wrongfully sued for such a thing that I'm not aware of? And have they gone out of business as a result? I've read an awful lot of employment case coverage and don't remember seeing anything like that. What I do recall seeing are people getting hammered for flippant comments _during_ an interview, but that's an entirely different thing.
- deleted 8y ago[deleted]
- btilly 8y agoGiven how few companies give interview feedback, I would predicted very little in the way of lawsuits involving that. People can't "willfully or accidentally mis-interpret" what you don't say. The real question is, "If people gave interview feedback, would they get sued for it?" I think so. Doubly so if the feedback was at odds with the candidate's self-image or if it is written. (It is a lot easier to file a lawsuit based on what was written to you than your memory of what was said.) More importantly HR departments universally say so. And as long as HR departments say so, managers will follow their advice and not give interview feedback.
- dmurray 8y ago
- slg 8y ago>the more likely that someone will crunch it and find some statistical patterns that they will label “racism” or "sexism". Even if you’re innocent The existence of that pattern by itself might be enough for a company to be guilty of discrimination. If a policy disproportionately harms a specific protected class and they can't show a legitimate business reason for that policy, it is illegal regardless of intent. It is called disparate impact.
- simsla 8y agoNo. Any data exhibits random patterns, especially if you try too hard. If you check for 10 patterns, each at the 95% significance level (p<0.05), there's a 40% chance of getting at least one false positive. Look for 20 patterns and that goes up to 60%. That's why science requires you to formulate a hypothesis before running the experiment. And why finding a pattern through data analysis does not warrant a witch hunt.
- slg 8y agoI don't know what to tell you. It isn't my opinion. It is the law. [1] You can't just saw "No." and be done with it. It also isn't about setting up a witch hunt. It is about protecting people from discriminatory practices even when the discrimination is neither overt or even intentional. [1] - https://en.wikipedia.org/wiki/Disparate_impact https://en.wikipedia.org/wiki/Disparate_impact
- adwn 8y agosimsla is giving a reason why that's a bad law – they're not disagreeing that this law exists. A law can have been well-intentioned by legislators yet get abused in practice.
- heavenlyblue 8y agoAnd here you're forgetting about the significance of the patterns themselves. 95% significance of the fact that no women or ex convicts were hired for the job? Seems significant enough that a newspaper would write about it. 95% significance of not hiring a guy who looking too much of a hipster and has too many tattoos? Not sure, to be honest - I can see how society (and newspaper writers) would easily dismiss that as bs. Don't try to abstract it away as otherwise it just seems you're justifying something absolutely ridiculous.
- will4274 8y agoMy friend works for a large consulting company (you've heard of them). They were hired by a client who needed to reduce their labor costs by 10-15% (read: fire people) because they were hemorrhaging money. The team of consultants asked to NOT be given any performance data - and recommended that the consulting team handle the layoffs and fire randomly - this immunized the client from any discrimination lawsuits and was, according to the senior consultant, the most cost effective way to handle a layoff, once the cost of litigation was factored. The client signed off on the plan and the consultants executed it. The client was a big (>10k employees) tech company. This is the world we live in, unfortunately.
- marcoperaza 8y agoMaybe Shakespeare was onto something...
- gaius 8y agoThe team of consultants asked to NOT be given any performance data I call shenanigans, because people are not made redundant, positions are. Who gets laid off is related to their job not existing anymore, nothing to do with them as an individual person.
- will4274 8y agoI'm not quite sure I understand. Calling "shenanigans" generally means disagreement but your second sentence is entirely consistent with what I wrote - the company had overscaled and needed to eliminate redundant positions, regardless of whether those that held them were high performers or low performers. If you are disbelieving my claim, what evidence could I provide to convince you that it's true?
- BrandoElFollito 8y agoI think this is a misunderstanding. If I understood correctly, you are saying the company needs to reduce its size and therefore randomly eliminate people at some positions (say, need to reduce engineering by 10%), while the other commenter was challenging the fact that the company needs, as a whole and independently of the position to reduce its staff by x%. Both are possible.
- softawre 8y ago>You gave some random guy some feedback I've noticed you've used "guy" 185 times in the past 5 years, but only used "girl" 58 times. This is a statistically significant difference. You will hear from my lawyers.
- deleted 8y ago[deleted]
- jorblumesea 8y agoMost engineering interviewees fail to advance because of cultural/personality/communication issues and not technical competence. The amount of people I've washed out of the interview process because they've gone on some rant about windows vs linux, political ideology or just came off as unable to communicate in general. This is also the hardest to communicate as it is something inherent to the candidate. It's not personal, but it gets personal at this point.
- dunpeal 8y ago> Most engineering interviewees fail to advance because of cultural/personality/communication issues and not technical competence. Not my experience. At least when hiring for programming positions, the typical fatal issue is that the candidate's coding is weak. In my first role as a hiring manager, I didn't stress coding tests for candidates with long work history on their resume. Since then, I learned better. I've seen candidates with anything between 1 and 15 years of full time coding work on their resumes fail to answer basic fizz-buzz level coding questions. At least for the candidates I've seen, the biggest single reason why they get rejected is failure to perform the one main function their job requires: coding.
- mixmastamyk 8y agoThey can't code because you are looking figuratively over their shoulder---the clock is ticking next to a hundred grand in a suitcase. A single question is pulled from subjects vast enough to fill up years of college and there is no time to research, as one would in the real world. Binary pass/fail with your pride/livelyhood/family on the line. Please state your last exam conducted under such conditions? Oh and your questions probably stink. I've gotten plenty of them with recursion that might take ten minutes in seclusion but simply not possible under the gun.
- bsder 8y ago> They can't code because you are looking figuratively over their shoulder---the clock is ticking next to a hundred grand in a suitcase. There is a difference between me asking you how to optimize a graph algorithm (good luck--I probably couldn't do that on the fly with references in front of me) vs giving me a basic FizzBuzz. If I let you pick your language for your FizzBuzz, you need to demonstrate at least some of the following things: I/O of any flavor (I'll even accept Logging if you don't do standard I/O or console I/O) String formatting Modulus Operator Nested-If statements (or equivalent--Matching, case/switch, etc.) I'm not looking for production code. I'm looking for 10-20 lines of "A High School senior with a computer class could pass this." This is not limited to programming, sadly. I used to have to interview VLSI designers with "Draw me an inverter", and 70% of them couldn't pass.
- mrkurt 8y ago"Can't understand their accent" _is_ discriminatory. Please don't ever recommend against a candidate for that. Companies are definitely taking the easy way out. The reality is that most of them don't have a good hiring process, aren't consistent about hiring decisions, and tend to choose based on factors that have nothing to do with the job they're hiring for.
- dsajames 8y agoGood communication is a requirement of the job. If you can't communicate, you aren't likely to be efficient. Take some time to take classes and learn the language better. Try working in a Spanish-only environment as a pure English speaker and see how far you get. This doesn't mean "he has an accent", just that they couldn't understand it.
- tptacek 8y agoWe don't have to litigate this from first principles; this is such a common problem that there is a name for it in EEOC circles: "accent discrimination". You can be civilly liable if you do it.
- biotech 8y agoI wasn't aware of this, but sure enough, "accent discrimination" is addressed by the EEOC. However, in the case that nobody can understand the person due to such a thick accent, the employer may have some argument that it is not discriminatory. Here is the relevant text from the EEOC Enforcement Guidance on National Origin Discrimination: Under Title VII, an employment decision may legitimately be based on an individual's accent if the accent "interferes materially with job performance." To meet this standard, an employer must provide evidence showing that: (1) effective spoken communication in English is required to perform job duties; and (2) the individual's accent materially interferes with his or her ability to communicate in spoken English. [1] [1] https://www.eeoc.gov/laws/guidance/national-origin-guidance.cfm#_Toc451518822 https://www.eeoc.gov/laws/guidance/national-origin-guidance....
- munchbunny 8y agoI think your point that the actual companies have to judge culture fit is critical. TripleByte's interview is about as purely technical as you can get. Their promise to client companies is that the candidates who pass are technically sound to a baseline level. That leaves the companies to judge cultural fit, which is where all of that legal liability seeps in. I've done the TripleByte interview before. Even got an offer through them (though I didn't take it). Their interview is almost entirely about fundamental skills plus a bit about your ability to communicate. There's very little in that interview where you could come up with lawsuit material. All of that said, I think their technical interview is a pretty good one. Their interview feedback was accurate, and it definitely felt both more rigorous and more fair than the vast majority of the first rounds I've done.
- jonny_eh 8y agoI agree 100%. I recommend that anyone who gives engineering interviews, especially phone screens, to go through the Triplebyte process.
- sdegutis 8y agoThis is absolutely correct. Companies can and should discriminate against anyone who wouldn't be a good culture fit for any number of reasons. I don't fault anyone who has ever refused to hire me for personal reasons. At the end of the day, a company is a group of people working together toward a common goal. Company is Latin for those you break bread with, and although companies aren't usually that close-knit (modern business lunches don't have the same level of trust and closeness as an ancient meal) the point is still the same: you're a team.
- Retra 8y agoYou are a team, but you should still attempt to be objective enough in your evaluation to determine whether a new person will allow you to be a functional team. But when you say "culture fit", the implication is that the team would prefer not to change at all, not that it would accept changing into a different-yet-comparably-productive team.
- sdegutis 8y agoMaybe I used culture fit the wrong way. I just meant the ability to get along in non-trivial situations and communicate effectively. I've met people who I have so little in common with that we couldn't even share a joke in either direction, because the recipient just couldn't understand it at all. It was so difficult to accomplish even basic things because our experiences were so different that we didn't have common ground to work from. Not that a similar sense of humor is necessary, but having at least some commonality is necessary if you're going to be able to solve problems together.
- deleted 8y ago[deleted]
- canthonytucci 8y ago> It was so difficult to accomplish even basic things because our experiences were so different that we didn't have common ground to work from. I am curious what kind of work this was, if you can share. I had a lot of difficulty in the past when working in situations where there was "life-experience" context to the problem space that was not shared by the whole team. But we had to get the job done so we worked around it. I think in the end the need to be more explicit, to provide more context and to work towards abstract descriptions of problems was also a positive. When life gives you lemons and all that.
- silverlake 8y agoFacebook gives feedback. I interviewed twice and didn’t pass. They read the feedback report right off their screen to me. So that makes me question the legal liability reason. Facebook is a bigger target than most for lawsuits. I think it’s just uncomfortable to tell people why you didn’t hire them.
- EduardoBautista 8y agoNot all companies can afford to have a legal team review feedback before it’s given.
- smelendez 8y agoYeah, I think that's a big part of the difference. Also, if somebody posts online complaining about their Facebook interview and the feedback they got, it's essentially going to be lost in the noise of other discussion of Facebook. If somebody posts their feedback from RandomStartup and says the interview was biased or otherwise bad, it could end up being in the first page of Google hits for the company, which would be a mess.
- extesy 8y agoNot for everybody, apparently. They didn't respond when I asked for feedback after my interview.
- brandall10 8y agoThe fact that you interviewed twice implies you're a candidate they like, but for some reason or another you weren't strong enough. If a company keeps the door open, it's certainly in their best interest to help you enter it sooner rather than later.
- sametmax 8y agoIf you don't get a paper trail, you can't sue. Oral feedback is pretty hard to use in court.
- jMyles 8y agoI was with you until you said that refraining from hiring someone because his accent was too difficult to understand. That's an insane reason - why pass on a good candidate for this reason? Can your company afford this? If you are working closely with this person, it will be 3 months before his accent is sufficiently adjusted. This is a stupid reason to pass.
- j2kun 8y agoI've seen this a million times teaching students. They raise a shitstorm for two weeks because they can't understand their TA's accent. Then they learn and can understand them just fine. The truth is it's part laziness and part racism. That being said, there is reinforcing incentive to be a bad communicator when the people around you don't make the effort because of your accent.
- reversecs 8y agoI am conflicted about the use of racism in this context. Accent varies by ethnicity and ethnicity is a proxy for race, so they are disadvantaged by their race. But if a student had a ta of the same race but no accent it would be fine. Or if the ta was white but had a bad accent the complaining would continue but it wouldn't be considered racism.
- mgkimsal 8y agoDon't be confused - it's not racist. It's "accentist" perhaps. I'm "white" and there've been plenty of "white" folks who I can't understand due to their accent. In some cases, I would not be able to work with them. It was nothing to do with 'race', everything to do with their ability to communicate in a way I could understand. If there are two people of equal technical ability, and one I (and the team) can understand without hesitation, and one who has trouble communicating, because of an accent, and they're both white, and we choose the one without the accent... are we racist? No.
- jldugger 8y ago
- wst_ 8y agoJust say he's no fit for the organization. Safe and at least partially fair for the candidates.
- gnicholas 8y agoInterestingly, if they give concrete technical reasons why people weren't hired in most cases, then telling some people that they were "not a fit" could actually raise a red flag. Basically, it tells them that there was no technical reason not to hire them, which raises the question of whether it was something illegitimate.
- pmiller2 8y agoIt may raise the question, but it’s not evidence, and it’s not actionable. No lawyer would ever take a case based on a lack of interview feedback, or “not a fit.”
- presscast 8y agoNo, but it might prompt someone to dig deeper. I think companies are starting to treat the hiring process as a security risk and are trying to minimize the attack-surface.
- pmiller2 8y agoTo anyone who’s try “digging deeper” in a situation like this, I say good luck.
- presscast 8y agoFor most of us, dealing with this kind of issue is a hassle, even when there's no actual legal danger. Substitute "bad PR" with "litigation risk" if you prefer. The point is: there exists an incentive to think in terms of information leakage, and it's a very unfortunate state of affairs because everybody loses.
- 8y ago
- hm10 8y agoWell that sucks for the person if they were rejected because of their accent and no feedback was given. All that hard work in preparing for interviews and you don't even know for sure why they didn't pick you.
- marvy 8y agoI partly agree and yet... surely the candidate noticed that communicating was difficult?
- Cthulhu_ 8y agoIf they're never getting the feedback that they're hard to follow, maybe they don't?
- Ntrails 8y agoThere is a point where you realise you don't understand, and are too embarrassed to ask someone to repeat for the fourth time. So you kinda take a guess and move on to something else. It may not be obvious to the other party that you didn't understand depending how well you covered.
- ericdykstra 8y agoThis is a small part of why anti-discrimination laws are harmful. Companies can't be honest because they need to cover for potential discrimination lawsuits. If you go a step further, a truly racist company is never going to hire someone of a race they look down on, but they can't put anything on a job description about it, so they just end up wasting a minority's time.
- carlmr 8y ago>they just end up wasting a minority's time. They also waste their own time, so there's some good coming out of it. But I wouldn't say unintelligible accent is racism. I've met some unintelligible people that were born and raised where I live. An accent is also something you can change (even though it's hard). So it would be really valuable feedback to the person who's not getting it.
- fogetti 8y agoI am wondering why are the technical interviews are put before the personal interviews then? If none of the technical skills matter in light of the soft skills because some candidate has a hair color or accent which bothers a team member, why bother with checking technicality in the first place?
- SmellTheGlove 8y agoDepends on what you want to optimize for. It may be that the technical filter is the finer one, so start there and have fewer in the second round. It could also be that technical is more important, as no amount of soft skills substitute for technical ability in some roles. Also keep in mind that we're usually evaluating soft skills as a single dimension, or sometimes even just a byproduct, in what is actually a broader behavioral interview.
- jefftk 8y agoOther companies effectively outsource the first stage of their hiring to Triplebyte. These companies have much more agreement on the "hard" skills than the "soft" skills, and also have an easier time trusting Triplebyte to evaluate the former. A candidate who passes a general technical interview could be a potential culture fit for many companies.
- austenallred 8y agoBecause most people applying for programming jobs can’t write fizzbuzz and it’s easier to verify than “culture fit”
- dhnsmakala 8y agoHonestly, the fireworks guy seems pretty fun. Curious what the lunch argument was too
- binmanthrowaway 8y agoThe accent thing could be viewed as not hiring someone on the grounds of disability. If you can't understand how someone speaks, you can always communicate via Slack or email. The lunch one - if the argument was not related to work, then I can't see an issue. You don't have to talk personal stuff to the co-workers, so unless the conversation wasn't mandatory and wasn't initiated by the candidate, then no issue here. Only really valid cause is the firework.