Live data from Hacker News

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

blog.interviewing.io

641–646 of 646 posts

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

#641

Earlier quoted context omitted.

Nobody is perfect for every job. A phone app is one thing, ERP or accounting is another, avionics is another.

ahahahahahahahahahaha, the arrogance in this comment cracks me up. You have no idea the software I write, don't make assumptions.

The software you write makes you perfect for every job...and you are amused by my arrogance?

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

#642

Earlier quoted context omitted.

"You'd be shocked how many people that write years of relevant programming experience and fail that." Do you find people who did well on a preliminary test where they wrote some code fail this? If not, then why do the whiteboard? If people do fail, do you assume it's because they cheated on the previous test? I think your stated explanation is incoherent, because you are claiming that self-taught developers can "get…

> Do you find people who did well on a preliminary test where they wrote some code fail this? If not, then why do the whiteboard? If people do fail, do you assume it's because they cheated on the previous test? My preliminary test is a phone call if there is more candidates I want to interview than I have time for. No coding. > you're saying they can't do anything and yet somehow they were hired and do stuff at other…

"Again, my goals are people that can work in a team."

Ok, but what does that have to do with writing code on a whiteboard? I'm telling you a fact - there is a whole world out there that doesn't do it, before or after a hire, and yes, of course they work in teams. I'm not out for an argument on how people should do things, so don't make it into one.

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

#643

Earlier quoted context omitted.

> Do you find people who did well on a preliminary test where they wrote some code fail this? If not, then why do the whiteboard? If people do fail, do you assume it's because they cheated on the previous test? My preliminary test is a phone call if there is more candidates I want to interview than I have time for. No coding. > you're saying they can't do anything and yet somehow they were hired and do stuff at other…

"Again, my goals are people that can work in a team." Ok, but what does that have to do with writing code on a whiteboard? I'm telling you a fact - there is a whole world out there that doesn't do it, before or after a hire, and yes, of course they work in teams. I'm not out for an argument on how people should do things, so don't make it into one.

Because we actively put people in the spotlight when discussing solutions or issues. Sometimes it's a whiteboard, sometimes it's a shared coding session, or something else. We use whiteboards extensively, and there is a good reason people do this in teamwork from educations all the way to the very top of engineering teams.

I have had a team that wanted to just chat on Slack and approach the tasks in a divide'n'conquer fashion. It does not work, and introducing a "lead architect" to structure everything is like pulling the reins of a mule - it will move backwards. Everyone needs to participate and feel shared ownership.

So if people cannot code simple shit on a whiteboard, it's my experience that they are a poor fit for this way of working.

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

#644

Earlier quoted context omitted.

If they're dissecting it at that close a level, it's probably not a company you'd want to work for anyway. At least how I judge take home tests (for a simple backend CRUD app spec), I'm definitely not disqualifying based on surface level details like that. I don't even bother running it on my machine most of the time. What I'm looking for that it doesn't have obvious SQL injections (I've seen this a depressing number…

Database migrations? Migrate from what? Most take homes are de novo, so have nothing to migrate from.

Depends on what tech and approach you're using. Some people use migrations to create DB tables, for example. Or seed initial data like, say, what user roles exist.

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

#645

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…

Name and shame since you're on a throwaway.

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

#646

In the UK I've heard it said you can make a subject access request (SAR) for any information a company holds on you. This would include interview notes for example. I assume something similar applies in the rest of europe due to GDPR?

That would clearly have unintended consequences (like all discussion of a candidate happening in person or over the phone).
Post reply on HN