As one article taught me about over a year ago respond by sending a well formulated email requesting the salary and job offering. Sometimes it leads to you understanding the market. Sometimes it leads to negotiation for higher salary. Sometimes an amazing new job. So far this has never failed me. And is far better than ignoring. I only really ignore the crypto companies.
I really like this advice! Do you have a link to the article? Would like to learn what you mean by "well formulated."
Responding to recruiter emails with GPT-3
61–70 of 135 posts
Re: Responding to recruiter emails with GPT-3
#62I like the plot twist where the GPT-3 use is not to generate the answer, but to query data from the email.
Re: Responding to recruiter emails with GPT-3
#63I like the plot twist where the GPT-3 use is not to generate the answer, but to query data from the email.
I am amazed it can return structured information like this; what happens if the recruiter forgets their name?
Re: Responding to recruiter emails with GPT-3
#64I am curious, what is the success rate with this? Do you get a valid JSON every time? Does it contain the right info every time?
I tried the five most recent messages I received and it worked as expected for all of them. I imagine that I'll encounter some that don't work, and at that point I'll try adding more examples to make the model more robust.
it's incredibly creative that you thought of this
Re: Responding to recruiter emails with GPT-3
#65My response to recruiters (especially on LinkedIn) is always the same; “Please send over all relevant details for the role you had in mind (JD, company and salary)”.
This filters out about 90% of them, and especially those who’re just fishing for clients.
Re: Responding to recruiter emails with GPT-3
#66Someday, 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.
Pretty sure this is happening already. I started to get some messages on linkedin that include some details from my descriptions, but it feels super unnatural, like a template was filled with some data mined content...
Re: Responding to recruiter emails with GPT-3
#67Kinda surprised author uses GPT-3 to generate JSON and then a template to go from JSON to the reply.
Why not have GPT-3 generate the reply?
Re: Responding to recruiter emails with GPT-3
#68I recently turned all the predictive email, the "Nice to see you too! // Yeah it was fun. // See you!" robot shit gmail proposes. I don't want those proposals. The bias they introduce into my human (when it's a human) interaction is impossible to undo, I turned all all that shit off, if I want to write "Nice to see you! Yeah it was good. // See you!" I didn't even read off the screen what I wrote the first time around, I just literally closed my eyes and typed from memory, incorrectly but so be it. I rather actually push the buttons that I supposedly type, do the work I allegedly do, type every character I supposedly type when it's prose. It's not a waste but even if it were there are much worse things than absolute waste.
Re: Responding to recruiter emails with GPT-3
#69Has anyone tried responding to phishing / scams with GPT-3? It seems like a much better use case, scammers are much more annoying and unethical. And you don't have to worry about GPT3 giving a weird response (which idk but the author doesn't seem to realize, machine learning even GPT is unreliable)
I made a habit of never replying to spam. You leak information about your email address being valid if you do. If you don't, the spammer never knows if the email was blackholed or delivered to an actual inbox.
Re: Responding to recruiter emails with GPT-3
#70I 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...
If you have "not interested in web3", then your profile comes up in keyword searches for web3.
"Not interested in СЯYPT0"