Live data from Hacker News

How ChatGPT is changing the job hiring process, from the HR department to coders

cnbc.com

21–26 of 26 posts

Re: How ChatGPT is changing the job hiring process, from the HR department to coders

#21
post #5
post #2

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. Edited to include “in 5 years”

the lawsuit against github/microsoft scraping the entire internet for code wins and kills the practice entirely there, that was easy to imagine

This will linger in the courts for years if not a decade, all the while the tech and industry will move on. Think Oracle vs Google case involving Java on Android. Was finally settled but didn't have any impact.

And if it sinks one model, there will be others. Like has been said, the genie is out of the bottle.

Re: How ChatGPT is changing the job hiring process, from the HR department to coders

#22

Earlier quoted context omitted.

so at what point does your in person interview become the problem? what is the line for you when the day to day doesn't involve unassisted time trials, but instead requires code reviews of assisted work and code reviews of colleagues work

code reviews are not the be-all and end-all of a coding job. in-person interview can give you some insight into what it might be like to work with a person day to day, it has more value than a take-home test in a lot of ways.

does your in-person interview do that?

Re: How ChatGPT is changing the job hiring process, from the HR department to coders

#23
post #8

Earlier quoted context omitted.

if fair use doesn't apply to training... what would it be trained on? Microsoft's code base? who the hell would pay for that?

Right, trashy ads would randomly pop up in your program.

Or heaven for bid the AI decides to add one of Microsoft's famous "please wait while we try to fix the problem" dialogs in your project. Especially since I am pretty sure that code looks something like this at a high level

  double sleep = random time between now and heat death of the universe

 thread.sleep(sleep)

 throw prompt that problem couldn't be solved

Re: How ChatGPT is changing the job hiring process, from the HR department to coders

#24
post #4

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. 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 addres…

As I understand work, an unfilled company job has a

    total normalised workload: w


    c  requirements: r_c(person skill_c, time)

    number of positions to fill: n


    where

        time[now, infinity] integrated:

            sum over i:= 1 to c:

                involvement of person ×

                r_i(person skill_i)

        = w


    (solving for total involvement × requirement = total normalised workload,

    because it's a boundary of inequality (>=100% of w))

That is applicable to set of all living people at the moment L

    finds out about posting: A subset of L

    would accept: B subset of L


    beta(person) := how much of required workload will this person fill after integrating their (involvement x requirement) over their time there


     time: 0 to inf (now until end of the universe)

     involvement(t): -inf to inf (work units)

     requirement_i(t): [0, 1] (in units inverse to work units)


     (a capable and willing person who's not conscious will have involvement=0,

     someone who only would work on weekends for a place that's closed on weekends will have person skill_attendance>0 on weekends, but requirement_attendance>0 only on workdays, a disjoint set)


    a person with beta=1 fills the position until the position ceases to exist

    basically nobody has beta=1, that happens probably only if trade becomes obsolete or position is e.g. to paint a specific room)


    remaining workload after parting ways (company closed, person dead and/or universe ended): 

    w_r = w - beta(w)

    if w_r = 0 then they never have to hire anyone for this position ever again

    otherwise the hiring process repeats with w=w_r


Here, there's a start to formalizing the problem if someone is willing to look into this. It's my half an hour armchair take on this, because I figured it is all I can do. even if it's not anything at all, I tried and enjoyed the process.

I think my main point is, hiring processess seem to be very far from addressing the basic parameters of actual process of working somewhere in my view.

Let's get GPT-4 onto this maybe

Re: How ChatGPT is changing the job hiring process, from the HR department to coders

#25
post #8
post #7

Earlier quoted context omitted.

Another tool will just take it's place. It's too useful

if fair use doesn't apply to training... what would it be trained on? Microsoft's code base? who the hell would pay for that?

There were ads for payed sample code work a while back... so, I guess at least some players are sourcing royalty free stuff.

Re: How ChatGPT is changing the job hiring process, from the HR department to coders

#26
post #13
post #2

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. Edited to include “in 5 years”

It's questionable that there will be many jobs that are very similar at all to SWE of today in five years. There is no reason to believe that the large (language/multimodal) models will stop progressing. In six months the IQ of ChatGPT increased by 30-40 points. If we pretend that these things are linear, (so far they are actually exponential) then that's a 430 IQ in five years. Assuming the acceleration of progress…

> unless the AI is deeply integrated into their brain.

At which point, are they people anymore?

Post reply on HN