Imo, company either allows internal "poaching" or will have larger turnover. People need change once in a while, both psychologically and to learn something a bit new. And it breaks the us vs them mentality because you have friends in other teams.
Ask HN: Have you ever been “poached” internally? Is this even a thing?
21–30 of 62 posts
Re: Ask HN: Have you ever been “poached” internally? Is this even a thing?
#22There’s some politics to it, ie one org is losing a lot of people to another, so we aren’t supposed to actively recruit, but if they ask and are going to leave otherwise /shrug
Re: Ask HN: Have you ever been “poached” internally? Is this even a thing?
#23Re: Ask HN: Have you ever been “poached” internally? Is this even a thing?
#24Re: Ask HN: Have you ever been “poached” internally? Is this even a thing?
#25For talented people this is can easily be a win-win all around.
Obviously for the team hiring the hiring process is tremendously derisked. They've already seen the candidate in action, and like what they see.
This is also great for the candidate because a huge part of the risk when accepting an offer is issues that might come up with the larger organization out side of the people you work/interviewed with.
Not that I'm ever one to cheer for the company, but it's also a win for the BigCo as it keeps talent inside and engaged with the company, without them leaving from getting bored or having someone outside offer better total comp.
The only people that "lose" out in this are the initial hiring managers, but if they're remotely competent they'll understand and continue a positive working relationship... and if they're not competent it's good they're losing staff.
The "would you do it" is no different than any other job offer: do you like the team, the comp, the projects? The biggest difference being the interview process is radically de-risked, and the transition is much smoother.
Re: Ask HN: Have you ever been “poached” internally? Is this even a thing?
#26Switch teams without a 30% pay bump? Why bother, just interview.
Re: Ask HN: Have you ever been “poached” internally? Is this even a thing?
#27Speaking of which, what caught my eye in your post is the problem you identity with how SRE is usually practiced vs. what it was supposed to mean. My mandate in this new role is to update our practices and technology to make our software more reliable, and I'm shooting to accomplish that specifically by tackling that problem. In my opinion, there's a reason why the term "SRE" was coined, and it all centers around shaping the organization, _not_ the technology. In an organization with properly aligned incentives, the technology should follow. (Of course it's not entirely one or the other—tech can feed into incentives and help shape the org as well.)
I'm doing my best to carefully guard the term "SRE" here and educate people about its meaning because the ideas and philosophies it brings to the table are precisely what will allow me to deliver what I was asked. If this resonates with you or anyone reading this, send me a message. We're hiring.
Re: Ask HN: Have you ever been “poached” internally? Is this even a thing?
#28I’ve transferred to another position by applying for a position (as a stunt); a talk with my boss’s boss and a week of vacation, and I was on another team.
The director of engineering even encouraged internal transfers, since it probably solved a problem in his mind.
It helped me that I’d voluntarily reviewed code for all other teams, so less onboarding.
Re: Ask HN: Have you ever been “poached” internally? Is this even a thing?
#29Who-like I-was frustrated with how our company manifested 'Devops', and also-like I-had zero interest in trying to play the 'hearts and minds' game of undergoing a devops transformation This sounds juicy. More details, please.
Sure. I'm a Senior SRE, started off my tech career (21 years ago) on a help desk at a law firm, worked up to where I am now through various startups, roles, promotions. It's been my own personal observation in other tech communities when a Devops practitioner or Site Reliability Engineer is bemoaning some of the more common antipatterns[1] that manifest when companies decide "We're Devops now", the popular responses…
Don't mean to be dismissive, I'm still trying to figure out what it is, actually. In reality, as opposed to the stuff people like to hear themselves say about it.