Beyond the general idea of incorporating chatGPT into usual work; IMO, chatGPT is highlighting all of the biggest sore spots of the hiring process and instead of finding solutions we're just digging our heads further into the sands.<p>Job descriptions, resumes, cover letters, filling out forms, writing boilerplate for take home projects, etc. All of these are massive problems in the hiring process, and should be addressed before the entire thing turns into a complete nonsensical clown fest of nobody reading anything unless they're face to face with somebody.<p>So much of these things are just leftovers from the old days, we demand a resume not because it's an accurate assessment of history or skill but because "it's tradition". We write job descriptions not based on accurate demands of the job, but to fit in as many keywords as possible in hopes your ideal candidate doesn't miss it. List goes on, but really we can't start addressing these until we admit there's a serious problem - and this time not just relying on Google to maybe come up with something new.
Recently had to hire a new dev, and one of the submissions used chatGPT to generate a solution for our take-home test.<p>The really clever thing was, they did a line by line breakdown of the solution chatGPT came up with, keeping certain parts and throwing out others, giving reasons why each part deserved to stay or be tossed.<p>Then they wrote a second solution incorporating parts of the first and their own original code, which was genius. They put it all in a readme file with the solution. It instantly put them at the top of our candidate pile.<p>Unfortunately, the in person interview didn't go so well so we didn't hire them.<p>Smart approach though. If they'd just used ChatGPT to come up with some bog standard interview questions and solutions they'd probably have walked right into a job with us.
I did a coding test with ChatGPT and supplied the prompt plus a screencast of me doing the coding test with ChatGPT.<p>Didn’t even get a phone interview.<p>I really don’t care though because coding tests are usually a silly waste of time and I’ve had my time completely burned by employers wanting coding tests to which they reply either nothing at all, or some one liner like “we didn’t like it”.<p>If you DO are coding test, agree to it only on condition they supply your their assessment methodology first …. a request to which very few employers would respond.<p>Coding tests are mostly arbitrary, meaningless, unscientific and evaluate nothing real world.<p>I say refuse coding tests and go to another employer.
It does seem somewhat hard to imagine being employed as a SWE in 5 years without being proficient in incorporating some sort of generative AI into your work.<p>Edited to include “in 5 years”