4 ms·
I've seen the opposite, from close observation on both sides. The recruiter may start out with a role that they are trying to fill, but they have plenty of oth
by btilly 10y ago
I've seen the opposite, from close observation on both sides.
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.
- ryandrake 10y agoInteresting, thanks for the insight. Funny how two people can look at the same recruiting environment in the same industry and have two totally different experiences. > 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!"
- btilly 10y agoYeah, I've seen those recruiters. And they tend to not be honest about who they are actually working for. So, for example, you'll get contacted by someone who is recruiting for a job at a big name company, from someone who isn't from that company and doesn't know what is actually available from there. They only know about the one role that they were told about. These things are generally a mess if you start out that way. Waste of time and money on both sides.
- chris11 10y agoI'm interested in your experience with SRE. What did you like and dislike, and why was it a mistake?
- btilly 10y agoSRE is a difficult role because you need someone with the mindset of a sysadmin and the skills of a programmer. So Google (at least used to) will hire one and hope to find the other half. As a result a large fraction of people hired into the position are not a fit. And Google had no mechanism to identify and rectify this common problem. 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.
- nvarsj 10y agoI think it's tough hiring for an SRE role. Much tougher than a programming role. Although in Google's SRE book, they say the interview bar is lower than for their software engineers. Odd! 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).
- linkregister 10y agoThe coding standard for SRE hiring at Google is lower, but the other requirements are much higher or aren't considered for a generalist SWE role.