41–50 of 135 posts
Earlier quoted context omitted.
If you have "not interested in web3", then your profile comes up in keyword searches for web3.
It would naively seem to me that reading profiles is literally the bare minimum to do the job. If a recruiter can't do more than scrape LinkedIn for keyword matches and send spam, I can't think of a good reason why I should respect their time.
Earlier quoted context omitted.
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."
So far this has never failed me. And is far better than ignoring. I only really ignore the crypto companies.
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.
Now have it automatically negotiate a salary range high enough for you to consider interviewing.
I 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?
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.
Now have it automatically negotiate a salary range high enough for you to consider interviewing.
I did the opposite, I just tell them to schedule on my calendar... I'll sit through you salespitch for $100/hr ( https://www.starblazer.pro/#/bk/80jKqZYdBdeBd2J3uTdKIoqVgpk2 ?)