I've found this to be decidedly not true, from many recruiter contacts. They have a role in mind they're trying to fill and if you point out that it's far more junior than what you're looking for, the conversation's over.
Think about how must companies hire. The hiring manager fights internally and finally gets a req for a very specific role. They have to fill that role. Having a generally smart person would be great but they have this immediate need and they can only hire one person. And once that req is filled, no more hiring until you get another req.
I'd love to see a company literally just looking to snap up smart people and then have them come in and kind of define their own role, one where they can add the most value. Nobody does this!
I don't know about letting people "define their own role", but a lot of the biggest companies are constantly hiring without a specific role in mind. If you've got thousands of employees then your best strategy is just hire the smartest people you can find, and figure out how to use them effectively - you have enough roles available that you'll find something for anyone to do, and while not every role you need filled is someone's dream job, a combination of internal mobility between teams and great benefits and pay will attract a lot of good candidates.
Google et. al. are hiring generalists because they want people of a mindset such that when the entire special-purpose they hired them for dissolves, they're willing and eager to ramp up on a new project and new challenges instead of saying "Well, the foo project is closing down and foo's pretty much what I wanted to do, so I guess I'm going to quit (and take all the knowledge and skills Google spent time and money to train me up on with me)."
I get that there are people who don't care (much) what kind of code they are working on. If those are the people Google exclusively wants, that's fine. I just won't have a place there. I do not think this is a generally-advisable strategy, though, as the GGP I was responding to indicated. In fact, I'd argue that well-crafted teams of specialists are superior to, but harder to staff than, teams of generalists.
The big tech companies do also build well-crafted teams of specialists where appropriate (for instance, Google's Deep Mind team is all AI specialists). I don't know what sort of hiring process they use for those roles, but I would wager the process is a little more personalized, and also substantially more selective.
The recruiter may start out with a role that they are trying to fill, but they have plenty of other roles that they could be happy to put you in. And furthermore for the right candidate, they don't have to figure out the role up front.
When I was hired by Google, SRE poached me out of a pipeline to a different group. (Accepting that offer was a mistake on both sides, but it was a learning experience.) When I was hired by Amazon, I was contacted for a job in Seattle, then got hired in Orange County.
That said, plenty of candidates start the process by being too arrogant about what they can demand. Recruiters know to look for that and stop wasting their own time taking these people seriously. That's why pointing out that a proposed role is too junior for you is likely to result in being dropped.
> That said, plenty of candidates start the process by being too arrogant about what they can demand. Recruiters know to look for that and stop wasting their own time taking these people seriously.
Maybe, but I think it saves both sides time. If I'm shopping for a new sports car and a salesman approaches me with a great deal on a 10 year old pick-up truck, it's helpful for both of us if I make my expectations clear right away.
Most Recruiters: "I have this role you'll be great for! Let's see if it's a great match!"
Better Recruiter: "What are you looking for? I work with a lot of companies and probably have a great match!"
These things are generally a mess if you start out that way. Waste of time and money on both sides.
I am a programmer. I tend to dive into things in depth and context switching is unusually hard for me. A sysadmin needs to be able to operate on relatively limited knowledge and rapid context switching is par for the course. I was therefore a poor fit in that role.
After I left I was shocked at how many people I met who had known someone else whose story matched mine pretty closely. I would hope that Google has solved this organizational problem since. But rumor from those I know that are still there indicate that things have gotten worse over time, not better, so I don't think that it has.
However it was quite educational. I wish things had worked out differently but I definitely learned a lot that has served me well since.
You're looking for the sort of person that could setup a startup from the data center up. On top of that, they need to be good coders so they can automate everything, and also understand the applications running on the things they build. It's generally a much more in-the-trenches job - relying on limited information, and much harder to test things in isolation since there are so many moving parts, and things you can't change or automate easily (network vendor appliances, and so on).
The only place hiring generic warm bodies at random state-U is Starbucks.
> I'd love to see a company literally just looking to snap up smart people and then have them come in and kind of define their own role, one where they can add the most value. Nobody does this!
At least with hiring out of college, a lot of companies do the "Let's snap up smart people, then train them to do the specific job we need done". In my experience, this has been particularly prevalent among the big consulting firms.
I have been through what you describe. A recruiter reaches out and tries to get you in their funnel. For me, it's a no-go because of my college background. (Unsexy school, shitty grades.)
A family member was pursued by them very aggressively after making some presentations at significant conferences and getting praise in a book written by a high level business exec.
This family member was received borderline harassing levels of outreach from recruiters from Google. It's pretty obvious there is some sort of targeted hunting list and KPIs associated with it.
If you interview at Google and they ask how much you make you should probably tell them or you might get a weak non-negotiable offer. Unless what you make is already far less than their "standard offer."
It would be a shame to waste all that effort by sticking to negotiation techniques that maybe don't work on Google for regular candidates.
Also the experience of being caught lying is emotionally and mentally draining for me so I stopped way way back. Like in childhood. I wouldn't say I'm completely fib free, but if you are even remotely entitled to the truth your going to get it. If I get caught lying I have to be OK with it and not care. That is a high bar.
This is a negotiation, they aren't entitled to know how much you make nor do they have a good method of checking up on it.
would you hire a plumber that refuses to name his rate, and then when pushed, tells you a number 5 times higher than normal? why do you think any other employment negotiation is any different?
if you "never name a number", the person on the other end is going to know you're inexperienced and operating on cargo cult mythology, and will simply take advantage of you.
http://www.kalzumeus.com/2012/01/23/salary-negotiation/ https://www.twilio.com/blog/2016/02/patrick-mckenzie-on-sala...
Definitely would be good if someone wrote a counter-response to this prevailing meme
The standard "don't name a number" advice is based on the assumption that most candidates don't have that. They know what they earn right now, but they don't know what they could be earning. In that situation, you want to sweat some information out of the recruiter by getting them to name the number.
There are other ways you can get a bit of edge.
In a previous round of job hunting, i let a recruiter persuade me to apply at Amazon, even though i was 85% sure i didn't want to work there. They made me an offer substantially higher than my salary at the time, because they're desperate to hire, because nobody wants to work there, because they're a shitshow. I could then take that offer to the other companies i applied to, where i actually did want to work, as a starting point in salary discussions.
In my most recent round, one recruiter said to me "Company X want to know how much you currently earn, because they can't offer above 130k for this position and they don't want to waste their time if you're on more than that". 130k may not sound like a lot to you over in the Valley, but it was getting on for twice what i was making at the time here in London. "Well,", i said in the most noncommital voice i could manage, "130k would probably be okay".
I gave express disinterest in doing that, and had no issue with providing salary expectations. But I made it clear that this behavior was completely unprofessional and unbefitting of a recruiter.
I then told them in no uncertain terms that as long as they have this policy on their books, do not call back. If however, they change this, I would consider them again.
They just need as many warm bodies as possible to ram through their test so that a few trickle out the bottom of the funnel to keep the ranks from shrinking. If too many started getting hired, they'd add competitive basket weaving to the skillset if that's what it took to balance it.
(1)http://news.nationalgeographic.com/news/special-features/201...