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.
Responding to recruiter emails with GPT-3
31–40 of 135 posts
Re: Responding to recruiter emails with GPT-3
#32Re: Responding to recruiter emails with GPT-3
#33Someday, 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.
Re: Responding to recruiter emails with GPT-3
#34I 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.
Re: Responding to recruiter emails with GPT-3
#35Re: Responding to recruiter emails with GPT-3
#36I 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...
Re: Responding to recruiter emails with GPT-3
#37I 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.
Re: Responding to recruiter emails with GPT-3
#38Re: Responding to recruiter emails with GPT-3
#39I 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.