Earlier quoted context omitted.
You are right about hiring not being that much different but your prognostications are way off IMO. > - people are probably going to have to fly out for interviews, again. Fly where? Many companies don't have offices anymore. > - awkward and/or neurodivergent people are going to have to learn social skills again. Ahh... the age old, "just do better" position for neurodivergent people. Classic bigotry. > - And yeah, y…
> Classic bigotry. Hiring is all about finding the best candidate. If you find you cannot function sitting in conference room with three other people for an hour, there is a 100% chance there is a better candidate suited for the role, even if his/her technical skills are less than yours. Jobs have soft skill requirements, and there is nothing bigoted about that.
Interviewing a software engineer who prepared with AI
401–410 of 731 posts
Re: Interviewing a software engineer who prepared with AI
#402"Preparing with AI" sounds like an issue here, and it's not. The issue is lying about your experiences, which people have done since the beginning of time. I "prepare with AI" by having it help give me hints when doing leetcode problems, which is very helpful. Interviewing is not a presentation, it's a conversation, and having a simulated other side can be helpful. This shouldn't be surreal at all. A candidate just w…
i totally agree otherwise, there are a ton of other good proper ways to prepare for an interview using AI. for example his resume, im sure he asked for some refinements about how he was wording certain things, and who cares at all that its not word for word grammatically from his mind. getting past the resume screening process is a huge part of the battle, and all the scam attempts and bad candidates will be optimizing their resume as well. The info within it should still be relevant about your ACTUAL technical skills or you are just also falling into the scam/bad candidates category.
Of course your example is a solid one, which ive done myself as well for leetcode stuff and plenty of other stuff.
IF his experiences where actually real and he used AI to simulate an interview based on them, thats a fine use case for AI, so i guess this article likely should have used a more clear way to condone this candidates preparation.
Re: Interviewing a software engineer who prepared with AI
#403Earlier quoted context omitted.
At the company I work for, we are forbidden to ask questions based on resume, as it introduces biases. Reduction of bias means "ask same questions of every candidate".
That’s mental. Why have a resume in the first place then? Any info in the resume introduces “bias”. Well, actually, even wanting to hire the best candidate for a job is already a bias of its own. So why not just have a lottery instead of a hiring process? /s But only slightly.
Re: Interviewing a software engineer who prepared with AI
#404Earlier quoted context omitted.
> Sitting in a conference room under pressure after potentially flying out possibly hundreds of miles doesn't test your soft skills in actual day to day work. I've known many excellent engineers that buckle under that conditional. You're complaining about the hypothetical effectiveness of concrete hiring practices. You are not rejecting the value and importance of soft skills. Also, the ability to work under pressure…
Literally no other industry except for the performing arts interviews like this. No one else expects senior people to perform “work samples” under pressure, they just talk to them and dig into past work. All of the really damaging hires, I’ve seen in the last couple decades have been engineers with high negative productivity who were great at passing high pressure technical interviews. Also in a couple decades workin…
* special demerits to Canonical
Re: Interviewing a software engineer who prepared with AI
#405Re: Interviewing a software engineer who prepared with AI
#406Earlier quoted context omitted.
> Sitting in a conference room under pressure after potentially flying out possibly hundreds of miles doesn't test your soft skills in actual day to day work. I've known many excellent engineers that buckle under that conditional. You're complaining about the hypothetical effectiveness of concrete hiring practices. You are not rejecting the value and importance of soft skills. Also, the ability to work under pressure…
Literally no other industry except for the performing arts interviews like this. No one else expects senior people to perform “work samples” under pressure, they just talk to them and dig into past work. All of the really damaging hires, I’ve seen in the last couple decades have been engineers with high negative productivity who were great at passing high pressure technical interviews. Also in a couple decades workin…
No, not really. Take for example FANGs. Their hiring process is notorious for culminating with an on-site interview, where 4 or more interviewers grill you on all topics they find relevant.
Some FANGs are also very clear that their hiring process focuses particularly on soft-skills.
Where in the world do hope to find an engineering job where you are not evaluated on soft skills and cultural fit?
Re: Interviewing a software engineer who prepared with AI
#407Earlier quoted context omitted.
>a string of meh employers What's a meh employer?
A lot of people look down on companies that solve 'boring' problems with 'boring' technologies. I guess it's an open question if having been writing in-house CRUD apps using a 10 year old tech stack for several years is a proxy for lack of competence.
Not in an interview where maybe they're flustered, this was just an ordinary day on the job. They'd been in strange little enterprise vendor-silo programming environments their entire career. This was accompanied by exactly the sort of lack of understanding of lots of other stuff that you'd expect.
The flip side of this is programmers pushing companies to let them use k8s and Rust and shit when there's not a good business case for it, for fear of having a résumé that eventually starts to look like it could belong to that guy. Not wanting to look like him is a big part of the whole résumé driven development phenomenon.
Re: Interviewing a software engineer who prepared with AI
#408Earlier quoted context omitted.
I’ve always wondered: is there a LeetCode equivalent for doctors? When a hospital interviews a surgeon, do they roll out a cadaver and ask them to remove the gall bladder in 15 minutes while the interviewer scrutinizes how they hold the scalpel?
It’s because medicine, with its residencies and HN-mocked credentialism , is closer to traditional craftsmanship and the progression of apprentice-journeyman-master than the “every hacker for themselves” world of modern tech.
Let's fix the real problem then? Why can't tech be like this?
Re: Interviewing a software engineer who prepared with AI
#409Re: Interviewing a software engineer who prepared with AI
#410Earlier quoted context omitted.
>When an HVAC company hires a new tech HVAC has certifications you can get. We should strongly consider this in our industry. I don't think its an unreasonable compromise, especially now with the advent of LLMs.
We have some certs. The problem is that software development is about thirty different skills in a trench coat, and half of them we don't know how to evaluate (like slicing, or abstraction.) What ends up happening is that our certs end up being a bunch of multiple-choice questions that check people's ability to memorize trivia. It is more like having a Certified Novel Writer or Certified Mural Painter or Certified Gr…
I have interviewed at least one self-described Senior Software Engineer who didn’t know how to write a function that takes an integer parameter and then prints every integer from 0 to the argument passed.