3 ms·
The core problem with interviews is that it's basically impossible to tell how well someone's going to perform on the job. It's always possible to grind leetcod
by qweqwe14 3y ago
The core problem with interviews is that it's basically impossible to tell how well someone's going to perform on the job. It's always possible to grind leetcode or whatever and make it look like you know what you're talking about, by using the model people can just skip that part entirely.
Not to mention the fact that some interviewers feel obliged to ask useless cliche questions like "why do you think you are a good fit for this position" yada yada.
Not going to be surprised if picking people based on random chance (if they meet basic requirements) is going to actually be better statistically than bombarding them with questions trying to determine if they are good enough. Really feels like we are trying to find a pattern in randomness at that point.
Bottom line is that if ChatGPT is actually a problem for the interview process, then the process is just broken.
- svachalek 3y agoI think the difference is effort. If someone actually bothers to go grind LeetCode for a couple weeks before the interview, then they have demonstrated some form of persistence and work ethic at a minimum. Someone slow rolling questions with ChatGPT is demonstrating pretty much the opposite.
- adamredwoods 3y agoWithout a dedicated bar exam, we have little to vet hires against. Everyone is a senior engineer, until they're not. I think the next evolution of technical interviews will be hands-off, talking through problems where the criteria changes on the fly, to prevent typing while talking.
- maxvt 3y agoOr we'll go back to doing more onsite interviews at a whiteboard.
- michael_mroczka 3y agoI can't imagine many companies going back to this. The savings are too shiny to resist
- abathur 3y agoThere are also some of us who are just not great at demonstrating intelligence by narrating our thought process while under an adversarial spotlight with a timer running. I realize there are time/resource problems on the interviewing side, but I'd be happy to have conversations that are as long and technical as it takes for an interviewer to feel like they've found bedrock. Whether they pass me to the next phase or not, it's frustrating to spend 30 minutes or 3 hours trying to start a fire by rubbing wet twigs together and never get to walk away feeling like I've communicated more than a few percent of what I bring to the table.