Live data from Hacker News

Responding to recruiter emails with GPT-3

matthewbilyeu.com

31–40 of 135 posts

Re: Responding to recruiter emails with GPT-3

#31
post #24

I felt like this blog post ended quite abruptly. I was expecting for the author to show how GPT-3 was able to formulate a response back to the recruiter not just parse out the name and company of the recruiter.

Perhaps this was the result of pointing GPT at the title "Responding to recruiter emails with GPT-3" trained on a corpus of tech blog posts.

Re: Responding to recruiter emails with GPT-3

#32
While the title doesn't match the article content, what I really like about this is a notion of semantic regex - learning feature extraction was not a use case for GPT-3 I had imagined, and now my mind is reeling considering other ways this could be leveraged.

Re: Responding to recruiter emails with GPT-3

#33

Someday, the recruiters will also start using GPT-3, and all recruitment conversations will just be transmissions between different GPT-3 instances, creating a massive hive mind of GPT-3s that brings about the singularity.

Ah, yes... The Dead Internet Company Theory...

Re: Responding to recruiter emails with GPT-3

#34
post #24

I felt like this blog post ended quite abruptly. I was expecting for the author to show how GPT-3 was able to formulate a response back to the recruiter not just parse out the name and company of the recruiter.

Can you prompt GPT-3 "as the person who received message {message}, respond to it." and it understands that it is addressing William from BillCheese (aka, "Hi William...")? Perhaps the best you may be able to do with the current model capabilities is something like "response to message {message} by thanking the sender and telling them you are not interested right now but will get in touch if that changes."

Re: Responding to recruiter emails with GPT-3

#36

I explicitly list on my LinkedIn that I'm not interested in "web3" but that doesn't stop the messages. This has me thinking of fun ways to waste a few minutes of these recruiters' time in return for wasting a few (many?) minutes of mine...

Web3 job offers on LinkedIn might literally be phishing scams. It's gotten a lot worse in the last year.

Re: Responding to recruiter emails with GPT-3

#37
post #24

I felt like this blog post ended quite abruptly. I was expecting for the author to show how GPT-3 was able to formulate a response back to the recruiter not just parse out the name and company of the recruiter.

Thanks for the feedback. I just updated the article. Basically I plug those extracted values into a templated response.

Re: Responding to recruiter emails with GPT-3

#38
I spent some time in web scraping, and building extractors that work reliably on websites is damn near impossible. GPT-3 automatically extracting out the right data from text is kinda crazy. Imagine scraping LinkedIn without dealing with selectors that change every other day...

Re: Responding to recruiter emails with GPT-3

#39
post #37
post #24

I felt like this blog post ended quite abruptly. I was expecting for the author to show how GPT-3 was able to formulate a response back to the recruiter not just parse out the name and company of the recruiter.

Thanks for the feedback. I just updated the article. Basically I plug those extracted values into a templated response.

Have you had a chance to experiment with whether GPT-3 prompts can be used to dynamically construct the response? For example, "if the messages describes a frontend role, say I am not interested, and if it is a backend role say I am interested."
Post reply on HN