2 - I think other technologists don't carry the same prejudices against technologists, so they don't accidentally showcase those prejudices. I guess there's a
3 - Spot on.
4 - I think the incentives are against concise initial communication. It's like online dating - from a strictly rational perspective, spamming out a halfway witty message gets better ROI than individual messages. It feels gross, tho. Being reasonably concise would involve some targeting, which would cost timemoney. So you get gross (in both senses) messages. Also, maybe expect an email from me.
5 - That's legit. Maybe my perspective is a little myopic on that point. Oops.
6 - Interesting. My current contract seems to be a fixed percentage, though they won't share the number ("A percentage in the 40s"). I assumed this meant they were lying, but I applied for FTE here and lied about what I make, and HR caught it.
Interesting to hear about it from the other side.
Sometimes we'll negotiate just because the candidate wants to maximize the offer, but negotiation isn't usually as intricate or time-consuming as it's portrayed.
It does benefit me to close a deal quickly, but the easiest way to close quickly isn't by convincing candidates to take low offers - the best way to make a deal happen quickly is to convince the client to pay my candidate at or above market rate.
If candidate tells me $n gets their acceptance, the easiest way for me to close that deal quickly is to get $n+5 from my client - not to convince candidate to accept $n-5. And $n+5 also nets me more than $n-5.
The risk isn't the time spent in negotiations over a small difference to the recruiter's bottom line - the time is minimal. The risk is losing the deal entirely (and getting $0).
2 - I'm guessing you wouldn't just get that from recruiters though, do you? I'd think recruiters aren't any more apt to say something like that than other technologists. That seems like social skills issues, and I don't think recruiters are generally considered poor in that area.
3 - The relationship is often sour on both sides, to some degree, for a variety of reasons. Recruiters would have to be blind not to see the contempt from many technologists. I think part of this is the knowledge that the candidate holds the final say in a transaction that might net the recruiter tens of thousands of dollars. That gives the technologist a feeling of power - "If I turn down this offer, the recruiter 'loses' 25K". Some recruiters make more money than the technologists they represent, which might also cause some issues.
4 - Agreed. Concise makes sense for both sides of the equation. Time is money for recruiters on commission. And if you are a Py dev that knows GIS, we should talk. (sorry, couldn't help myself)
5 - Again, as I've said to others here, we can't even try to read your minds. One candidate doesn't want to hear about benefits, one doesn't want to hear about the office, and you don't want to hear about company growth or stability. The problem here isn't that they are growing, the problem here is that they aren't paying you what you want. They could say whatever they wanted and you probably wouldn't care if they offered you 100/hr.
6 - This is a genuine problem, and I have no problem sharing that with candidates. I actually make a point of sharing it on most occasions, as I want to make sure candidates weigh my advice based on my incentives. If I stand to make 50K off a transaction, you might think I could be less truthful than if I only stood to make 5K. Incentive to lie decreases as the value of your reputation increases.
You mention hourly rate, so I assume you've done contract work. One interesting aspect of recruiting is that a recruiter increases his/her personal income when negotiating higher salaries for permanent hire candidates (where FEE = $SALARY x $FEEPERCENTAGE, but in contracting the recruiter maximizes income by negotiating hourly rate down (where the recruiter earns $BILLRATE - $PAYRATE).
Thanks for sharing your thoughts, interesting perspective.