Live data from Hacker News

No engineer has ever sued because of constructive post-interview feedback

blog.interviewing.io

251–260 of 646 posts

Re: No engineer has ever sued because of constructive post-interview feedback

#251

I'm so disappointed to read comments on this thread to the effect of "There's nothing in it for the company but risk". I once put in about 8 hours on a take home project at a company (well known in these parts) that I had tremendous respect for, only to get an email back with "sorry, not up to par. We need someone with more experience". I asked them for a couple quick points on what I could have done better. I had ze…

Non paid take home projects... Huge red flag.

Re: No engineer has ever sued because of constructive post-interview feedback

#253

Earlier quoted context omitted.

A company has to hire someone. So they're forced to take the risk. They don't have to provide feedback, so they don't have to take the risk if they don't want to. Don't really think your comparison was fair.

But hopefully they interview more people than they hire.

What's your point? That increases the risk through increased exposure.

Re: No engineer has ever sued because of constructive post-interview feedback

#254
I think the comments that feedback is hard to write are very surprising. Do you not have to write notes about why you are rejecting or approving a candidate? I have never been in a role where interviews are ended with a simple boolean of whether the candidate passed or not. Every company should be keeping detailed notes on the reasons a candidate did well or poorly, even just to be able to compare if the candidate applies again in the future (or makes a claim that they were treated unfairly). Candidates should be rejected or hired for documented, justifiable reasons.

Additionally, in a medium to large org, it's impossible to evaluate the efficacy of interviewers if there are no notes. If the recruiting team can't look at the output of an interview and say "Huh, X keeps rejecting candidates because they use tabs instead of spaces in their Python code," how is the company supposed to maintain any hiring bar?

The effort to write comments in a way that can be shared externally should not be a huge amount of extra effort. Even if feedback is only shared on request, it should not take a monumental effort to distill some high-level bullet points from interview notes.

Re: No engineer has ever sued because of constructive post-interview feedback

#255

One hour coding test. Two one hour phone interviews. 5 hour interview with EA Tiburon. Generic rejection two weeks later. Never again. Are we cool on naming and shaming or should I save that for reddit?

We are cool with it.

Re: No engineer has ever sued because of constructive post-interview feedback

#256

There's no real affordance for engineers to sue or censure the process. I once did some interviewing with a broken wrist that dragged on me two ways: 1) I basically couldn't speed-code at all. Typing was inhibited for sure, but the friction point threw off my whole thought process. 2) Whiteboard coding was easier, but due to swelling, I usually had to have my arm atop my head or hold it in weird positions. So by law…

Yeesh. Sorry you had to experience anything remotely close to that.

The industry is shifting AFAICT. Callousness seems to be in and empathy seems to be out. Unfortunately though I think the same thing happened to pretty much every industry that came before software as well.

Hope you found something good so that you don't have to waste time with shitty people anymore.

Re: No engineer has ever sued because of constructive post-interview feedback

#257
post #121

On the topic of form letter rejections: I WISH I even got those... durring my last job hunt most of the time the company just goes dark and stops contacting me or doesn't respond. I say this and other recruiers tell me they're shocked and yet getting ghosted seemed to be the rule rather than exception durring that time. Maybe I'm such a bad canidae that they don't even want to bother with a form letter. Strangely one…

My experience is similar. I'm currently job hunting again, and this week I spent hours reading through this month's "Who's Hiring" post, making my best effort to write cover letters addressing what each company needs and how my skills and experience can assist them.

I got 2 responses. Both were impressed by my resume so I don't believe that's the issue.

Its really hard not to take it personal when it's such a common experience. If someone sends you an email, you reply. It's basic decency.

Re: No engineer has ever sued because of constructive post-interview feedback

#258
post #84

Earlier quoted context omitted.

They've only disrupted their day to talk to you, in many cases having done these increasingly-prevalent and always-bullshit 4+-hour "exercises", and they have way less time to be allocating than you do. That's all they've done. Their time isn't deserving of respect and it's just downright ridiculous to think that it's the decent thing to do to tell them something that might, just might, not make it a waste for them t…

Interviewing is a business transaction, not social services. They'll min-max their time just like you'll mix-max your compensation. I'll happily give advice, feedback, mock interviews, and other sorts of help on my own time in more appropriate environments. When it's company time, it's just business.

Sure, and as a business transaction, what do you think will happen if you treat potential business partners poorly?

The answer is that they'll leave negative reviews, tell people to avoid your company or decimate any goodwill your company might have. I have in the past left scathing reviews on Glassdoor and was on some occasions the first one to drop my experience. Because after long projects or a company promising to get back in touch, they decided to instead ghost me or make me do ridiculous tricks for the application process.

If you view something as a business transaction, then you should know one of the worst things you can do in business is spurn the person you're working with.

Re: No engineer has ever sued because of constructive post-interview feedback

#259

I'm so disappointed to read comments on this thread to the effect of "There's nothing in it for the company but risk". I once put in about 8 hours on a take home project at a company (well known in these parts) that I had tremendous respect for, only to get an email back with "sorry, not up to par. We need someone with more experience". I asked them for a couple quick points on what I could have done better. I had ze…

I had a guy at Qualcomm Austin tell me to read Advanced Compiler Design and Implementation by Muchnik. I read it and a few months later I was working for Qualcomm San Diego. I've thought about thanking him but I doubt he'd remember me, it was such a small comment.

Re: No engineer has ever sued because of constructive post-interview feedback

#260

I'm so disappointed to read comments on this thread to the effect of "There's nothing in it for the company but risk". I once put in about 8 hours on a take home project at a company (well known in these parts) that I had tremendous respect for, only to get an email back with "sorry, not up to par. We need someone with more experience". I asked them for a couple quick points on what I could have done better. I had ze…

Non paid take home projects... Huge red flag.

I disagree that it's an automatic red flag. 8 hours? Yeah that's too long. But I would rather do a 2 hour take-home project than a 2 hour whiteboard coding interview.

Edit to add: as far as getting paid, nobody expects to get paid for an onsite interview so I wouldn't expect to get paid for a take home project either. As long as it takes the same amount of time that the coding portion of an onsite interview reasonably would, that is.

Post reply on HN