Live data from Hacker News

Ask HN: Have you ever been “poached” internally? Is this even a thing?

news.ycombinator.com

21–30 of 62 posts

Re: Ask HN: Have you ever been “poached” internally? Is this even a thing?

#21
Seen it multiple times. But more discussion was involved - I would start ask questions and talk with other team not solve their issues without asking. I don't know how exactly other people went about it.

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.

Re: Ask HN: Have you ever been “poached” internally? Is this even a thing?

#22
I’m on my 3rd team at a bigco at the moment. Putting a lot of emphasis on enabling team transfers is the thing that has kept me there.

There’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?

#23
If the company is comfortable with hiring internally (some aren't) then it's common. If people have good managers, the managers will give their direct reports a heads up when they see a position that they think the employee will like more and suggest they apply internally. You probably don't hear about it often because a selfless manager is the unicorn of the business world.

Re: Ask HN: Have you ever been “poached” internally? Is this even a thing?

#24
At a company where I once worked, there was a development team that started working on an orchestration system for a cloud platform called OpSource[1]. It was sort of a CloudFormation-like system but driven by XML (they were Java developers). The team consulted with some of us who worked on infrastructure. Most of my fellow team mates rejected the project, but I enjoyed attending the meetings and ended up embedded in the development team and delivered most of the code that did the orchestration. The project was successful and I went back to my own team for a while, but they pulled me back in to work on another project. I ended up working with them most of the remaining time I was an employee at that company, even though I wasn't connected to them on the org chart.

1. https://en.wikipedia.org/wiki/OpSource

Re: Ask HN: Have you ever been “poached” internally? Is this even a thing?

#25
This is incredibly common at most BigCos, I would drop the term "poach", as others have mentioned.

For 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?

#27
To answer your question, yes, this happens. The cybersec team tried to "poach" me a while back, and more recently I was asked by the VP of Cloud Operations to leave my technical lead role within engineering and become Sr. Manager of SRE (I accepted).

Speaking 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?

#28
Your friend made a conscious choice to get transferred internally; poaching sounds like the desire came from another team, but it sounds like your friend initiated the process.

I’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?

#29
post #8
post #6

Who-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…

So would you say DevOps is ... more a "brand" than useful proscription for anything? Or what are its useful / redeeming features, in your view?

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.

Post reply on HN