News for hackers. Stuff that matters.
Re: by vonnik on Tuesday May 16, 2023 @07:45PM (#35969345)
A major problem with data in the job market is that there are bad actors on both sides, employer and employee, with incentives to lie about themselves; ie companies with toxic cultures won't reveal that, nor will malicious or incompetent job candidates. Many readers of HN know that companies can be bad, but don't recognize that, say, competent software engineers are not the median candidate applying for most roles. The other side has a filtering problem, too.

A second major problem with data is that it's often hard to know why something didn't work out. Yeah, not everybody's a good fit for a role. But where would you get an objective source of truth about an individual's performance. Or ... transpose it to dating: would you trust a group of ex-girlfriends' or ex-boyfriends' to give an accurate assessment of someone as a partner? Might they have incentives to distort the record? Where does good data come from?

So it's not just that AI lacks the data. It's that there are structural problems with ever gathering the data. It's not like the data's out there and we just don't have access. If it even exists, it's poisoned at the source.

Re: by SoftTalker on Tuesday May 16, 2023 @08:05PM (#35969526)
The best hires I've seen in my life have come through word of mouth referrals. No data, no recruiters, no leetcode, no HR screenings. Good people know other good people. They trust one another, they are motivated to discuss opportunities of mutual benefit.

Of course that doesn't scale when you're trying to fill in a large team quickly, but at that point you have to realize that "average" is about the best you can hope to get.

Re: by artsytrashcan on Tuesday May 16, 2023 @08:47PM (#35969899)
Some of the worst hires come through word-of-mouth referrals, too. That's how you get unqualified nepotism hires. In fact, networking can be thought of as a form of nepotism or cronyism (depending on how touchy a given person is about "nepotism" being applied to the manner in which they got their position). I know I'm likely alone in viewing such hiring practices - feelings over process - as signal of an impending collapse. I think it's a sound heuristic, though, at least for previously-established companies. If you're not connected to eminently-qualified potential hires (and you're probably overestimating the quality of your network), "hire my friends" is a sure way to end up with an increasingly incompetent workforce.
Re: by alfalfasprout on Tuesday May 16, 2023 @08:54PM (#35969951)
I've gone back and forth on this and now am firmly in the feelings > process camp if you have competent folks making the hiring decisions and you train everyone well in avoiding unconscious bias.

The reality is that strong soft-skills are crucial to hiring the best talent and those skills cannot be "objectively" tested. Even software engineering to a large degree requires a lot of design-related traits that require subjectivity in assessment.

Re: by mrkurt on Wednesday May 17, 2023 @12:19AM (#35971202)
You can test soft skills. Evaluations don't need to be objective, they just need to be consistent.
Re: by cwalv on Wednesday May 17, 2023 @12:39AM (#35971310)
Doesn't 'subjective' imply 'inconsistent' unless you have one subject doing all the evaluations?
Re: by hughesjj on Wednesday May 17, 2023 @02:55AM (#35972063)
In that case, wouldn't that select for generally likable people? Idk sounds like evolution to me.

Of course, though, that's going to encode some existing biases in the data, but we could keep adding them to protected classes if society thinks they're worthy of inclusion.

That last part is pretty flawed today and changes slowly, I admit, but overall this system sure as heck solves more problems than I could come up with. At least, I think it converges over time.

Re: by blitzar on Wednesday May 17, 2023 @05:32AM (#35973028)
An often overlooked job requirement is that you have to sit next to this person for 8 hours a day 5 days a week. There are no leetcode tests for that.
Re: by mikrl on Tuesday May 16, 2023 @10:07PM (#35970464)
Speaking of nepotism: on LinkedIn via my network, I saw a senior manager in a Bay Area company asking publicly for internships for his university age daughter.

I shook my head in amazement, then felt absolutely mortified on behalf of that poor woman. At best, she is living in her father’s shadow. At worst, she is being denied valuable life lessons of the feeling of being allowed to fail and get back up.

Re: by beckingz on Tuesday May 16, 2023 @10:28PM (#35970594)
That's how networks work. Ask and you might receive.
Re: by throw9away6 on Tuesday May 16, 2023 @10:44PM (#35970687)
Nah that’s what you do to get your kid in the door. It works and it helps.
Re: by mikrl on Wednesday May 17, 2023 @03:14PM (#35979869)
It’s stunting independence and setting a nepotistic precedent is what it is.
Re: by sumedh on Wednesday May 17, 2023 @07:32PM (#35982561)
> setting a nepotistic precedent is what it is

That is how the world works.

Re: by NegativeLatency on Tuesday May 16, 2023 @11:17PM (#35970870)
Personally I’d be fine with someone doing this for me. It was hard and scary to land my first job out of school
Re: by godelski on Tuesday May 16, 2023 @11:32PM (#35970949)
Honest question, how is this meaningfully different from a recruiter?

Sounds like a recruiter with intimate knowledge of the candidate and a strong network. A biased recruiter, but aren't all? I mean a recruiter doesn't get paid unless they get someone a job (and they get more money for a hire paying).

Re: by mikrl on Wednesday May 17, 2023 @03:20PM (#35979946)
No recruiter I have ever worked with has done something for me because I was related to them.

Come on man, are we really that cynical towards meritocracy that we are accepting nepotism as normal?

Re: by godelski on Wednesday May 17, 2023 @07:32PM (#35982553)
> No recruiter I have ever worked with has done something for me because I was related to them.

This is missing the point of my question. I'm assuming that the daughter has more to her merit than just her father's connections. If she is getting a job she isn't qualified for, different story, and I think everyone agrees with your point. If she is qualified and the dad is simply helping extend her network (like a recruiter) then what is the difference?

If you only look at the surface then you've missed everything important.

> Come on man, are we really that cynical towards meritocracy that we are accepting nepotism as normal?

1) Meritocracy doesn't exist and can't exist. I have several arguments laying this out. It's worth mentioning that the article is also arguing this. The problem is that the system is noisy. Even considering perfect resumes and perfect hiring managers the problem is that merit is so convoluted that evaluation is near impossible. How do you evaluate a software engineer perfectly? Do lines of code matter? Speed in which they work? Ability to get along with the team? Does pedigree matter? Lines of code from others that utilize their lines of code? Ditto but weighted by net profit corresponding to said lines? Can that even be measured?

2) How do you even measure a potential hire where you don't have any of the above metrics? Does pedigree strongly correlate with productivity? (most people argue no. I argue correlate yes causal no) Does it correlate strongly with LeetCode/Whiteboard problems? If yes, then explain the cheater threads that are so common. So what metrics should be used to evaluate? Again, the article argues (in depth) that the process is extremely noisy, nuanced, and complicated.

3) Which nepotism are we discussing? We'll say that a candidate has 2 attributes: merit and nepo. If merit dominates, then nepo is a means to reduce noise as you get information from a trusted source about information that cannot be gathered through resumes or interviewing (this is not different from calling a previous employer, except that there's higher risk in contacting their previous employers (which is why this doesn't happen) and previous employers are not a trusted source). On the other hand, if nepo dominates then no one disagrees with you and we've all been explicitly clear about this. Nepotism is only useful as a means of filtering through already (statistically) equally qualified candidates.

> are accepting nepotism as normal?

Accepting that it is normal doesn't mean you have to like it, it just means that you are recognizing that this is fairly status quo. Should we put in efforts to reduce nepotism and increase our ability to judge a candidate (and current employee) based on their merits? Hell yeah. But it is a fool who believes we have such tools today. And even a bigger fool who perpetuates the system of noisy evaluations. I'd personally love to have a system that is purely meritocratic. But the truth is that Goodhart always wins and if we don't recognize such flaws we are only creating a worse system that is masking as meritocracy. Few people even ask themselves why Goodhart always wins, and doing so also perpetuates this tomfoolery. I've even answered why Goodhart wins, and let's be honest, how many people caught it?

Re: by jamilton on Wednesday May 17, 2023 @12:07AM (#35971138)
At best she gets a great internship and then a great job. At worst she didn't want him to do that and won't accept a position she could have gained that way.
Re: by wiseowise on Wednesday May 17, 2023 @03:10AM (#35972149)
> At worst, she is being denied valuable life lessons of the feeling of being allowed to fail and get back up.

I’ll never not get amazed by conclusions of survivorship biased.

Re: by blitzar on Wednesday May 17, 2023 @03:21AM (#35972222)
> I shook my head in amazement, then felt absolutely mortified on behalf of that poor woman

I am shaking my head in amazement, and feeling absolutely mortified on behalf of you.

Re: by throw9away6 on Wednesday May 17, 2023 @10:52AM (#35976064)
This ^
Re: by mikrl on Wednesday May 17, 2023 @03:17PM (#35979901)
So tell me, how is it not nepotistic and overbearing AF?

I’d be absolutely affronted, and forever doubting if my achievements were my own or not.

Re: by knewter on Wednesday May 17, 2023 @08:57PM (#35983038)
Being born in America is winning the lottery in many ways. Should Americans pursue jobs in third world countries to avoid failing to succeed on their own merits?

Shoot, you'd really need to pick the worst job in the worst country as your starting point to know you really had what it takes.

Re: by blitzar on Thursday May 18, 2023 @02:30AM (#35984689)
Without suckling on your mothers breast you would be dead. Without that 2nd grade teacher you would be dumb. Without the near infinite external inputs that have gone into each person they would not be the person they are, in the place they are. All that is before we get on to the role of plain old luck.

None of your achievements are entirely your own, we are all standing on the shoulders of giants.

Re: by sumedh on Wednesday May 17, 2023 @07:32PM (#35982557)
> At best, she is living in her father’s shadow.

No, at best she is getting a shortcut which most of the time helps with your career.

Re: by hef19898 on Wednesday May 17, 2023 @03:30AM (#35972278)
I am a big fan of both, word-of-mouthbreferalls and sttict hirijg processes, read Amazon (without leetcode, I am no dev). If youbsomeone good, get them the first invite for the phone screening or even an on-site interview. But then recuse yourself from the hiring process, don't interview, don't participate in the decision making. That way, you are not the only one influencing the hiring, ypu just made it easier for someone to get the first foot in the door.

Of course this isn't perfect, people might be biased to please higher ups or collegues by prefering those referral candidates. Or you might end up indirectly influencing thebhiring decision, intentionally or not. But still better than some AI based CV screening or pure nepotism.

Re: by godelski on Tuesday May 16, 2023 @11:27PM (#35970922)
> The best hires I've seen in my life have come through word of mouth referrals. No data, no recruiters, no leetcode, no HR screenings.

Nepotism. It gets a lot of bad rap but the reason this is effective is because you're essentially comparing hiring via a piece of paper vs via intimate knowledge of a candidate's actual knowledge and work habits. The latter clearly has more information than you could get from any screening process. Of course this doesn't mean you should just hire someone because they're a relative or friend because that's not actually using the information gain. But we should recognize why the process is successful. If we want to make a fair system that doesn't rely on nepotism then we have to also recognize why it works in the first place. I don't see these complicated hiring processes doing this.

Of course, you can also just use a noisy process. But if you're going to use a noisy process maybe don't make it so expensive (for company and candidate; money and time). If this is the method, then the process should be about minimizing the complexity and costs of hiring.

Re: by ipaddr on Tuesday May 16, 2023 @08:02PM (#35969496)
"competent software engineers are not the median candidate applying for most roles"

Most developers with a few years of experience are pretty competent. Most employers are not toxic waste dumps.

Give the worst interview candidates a try and they will do well. Give the best interview candidates a try and they will fail or leave early. Interviewing is a skill, anyone who is extremely good at it most likely practiced more often and that could mean they needed to. The more experienced and poor interview they give the more of an unearthed gem you've discovered

Re: by zdragnar on Tuesday May 16, 2023 @10:13PM (#35970509)
I just interviewed someone who I am certain lied on their resume; they could barely write valid code during their interview, despite supposedly being a senior engineer with nearly 10 years of experience.

Randomly hiring the first people to apply (or "giving them a shot") is a terrible strategy unless you have tons of money to burn and no deadlines to meet.

We have internship positions for people willing to learn, but when we are trying to fill a senior position, we expect people to be at a certain level.

Re: by bodge5000 on Tuesday May 16, 2023 @11:33PM (#35970958)
I'd like to think I'm a competent enough engineer, but I usually don't perform well in those live coding interviews, whereas I tend to do well enough in the "take home" tests. I wouldn't even necessarily say its a problem with live-coding, I've done things like pair programming before and its always gone fine, but an interview is an entirely different setting.
Re: by zdragnar on Thursday May 18, 2023 @09:56PM (#35996867)
There's nothing I hate more than coding exercises in technical interviews, but the team wanted it, so there's a pretty simple one. I try to make as clear as possible in the preamble before we get to that part of the interview that I consider it to be a casual exercise, and have will offer to pair program with candidates who freeze up.

I honestly don't care if they know the answer to some leetcode problem (also something I state in the preamble), I want to see how they break down a problem, and if they get stumped, how they work with other people on it.

In the example I gave before, I had to explain to the candidate what the code they copy / pasted from the internet did. That might be fine for a junior candidate, but for someone with "10 years" of experience with the language, it's a non-starter for a senior programmer.

Re: by ipaddr on Wednesday May 17, 2023 @12:21AM (#35971212)
I would hire that person based on the reasons I gave before. Not being able to perform to your standards in the space you allowed doesn't mean that person is a fraud or that the person couldn't do the job. You were biased by your own test. You thought you were measuring how good a programmer someone was when in reality you were testing how good your test was.
Re: by wiseowise on Wednesday May 17, 2023 @03:14AM (#35972180)
That’s a lot of words to say nothing.
Re: by lisasays on Wednesday May 17, 2023 @01:57AM (#35971731)
It's amazing how fast coding skills can turn to shit (or in more polite terms, atrophy) if they haven't been accessed for, say, a year or so (and you were not super burned in with that language). Take that, add a bit of performance anxiety - that is to say: basic humanness - and there you go.

Doesn't mean you have to hire them. Still, sometimes we just don't have enough data to tell whether someone is lying or not.

Re: by sublinear on Wednesday May 17, 2023 @02:49AM (#35972030)
If the "coding skills" were shallow idioms in a few languages, I agree. This only proves why it's important to get an education and stay curious beyond mere trends.
Re: by wiseowise on Wednesday May 17, 2023 @03:11AM (#35972159)
> Most developers with a few years of experience are pretty competent.

I’ve reviewed hundreds of assignments in last two years. No, that’s not true, chief.

Re: by sublinear on Wednesday May 17, 2023 @02:14AM (#35971824)
> Where does good data come from?

Arbitrary opinions that cannot be decided by mere bias in data aggregated by an AI of any sample size or source. This is the fundamental flaw and why it's all horseshit.

You know artists many years ago already covered all this.

Impressionism: https://en.m.wikipedia.org/wiki/Impressionism