Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I don't know if there are companies that do this (I'm not saying there aren't), but this does not match my ground-level understanding of how and why big tech companies are hiring. The ones I'm talking to are hiring because they are constrained on what they can build by the availability of specific kinds of engineers in their organization.

Zero is the number of companies I've talked to who have ever mentioned competition with other tech companies as a recruiting concern. I'm sure that's A Thing That Happens, particularly in executive hiring, but I don't think most companies are hoovering up developers so they can hoard them.



I think you're right but isn't the second part of your statement ("ever mentioned competition with other tech companies as a recruiting concern") what the following lawsuit was about: https://en.wikipedia.org/wiki/High-Tech_Employee_Antitrust_L... ?

Speaking generally, I don't think startups think about it very much but it seems that the "very top" companies do/did.

Feel free to let me know if I'm wrong. I only have a general understanding of what you mean and the lawsuit.


There's a difference between wanting the keep developer salaries low and wanting to capture all the developers to deprive competitors of them.


Hiring tens of thousands of people is a very high level strategic decision. No one on the ground-level would have any special insight into it. The people on the Android team probably didn't know why Eric Schmidt authorized hiring a bunch more employees after returning from an exciting Apple board meeting, they were just happy to hire help.

A small fraction of Google's employees are responsible for all of its revenue.

They use those profits to help ensure their longevity. One way to do that is to keep people from competing with them, so they liberally hire and attempt to acquire anyone that's a potential threat.

It's not the only reason they hire so many people. Wall Street rewards headcount and tech companies have such great profit margins that it actually makes a lot of sense. What else are they going to do with all those profits?


It can also be a decision that's made from the bottom up. At any large company, as long as there's growth and success, every development team is going to either have more work than they can handle or can think of something they could do if they had more devs. So they're going to ask for more headcount. (Or cynically, some managers view headcount as a metric of their personal career progression and will ask for more headcount regardless.) You don't usually see senior management say, "let's hire 40,000 engineers". Instead, you have maybe 8,000 line managers all saying, "I want five more engineers". If anything, they are all saying, "I want six more engineers" and senior management has to figure out how to cut that down from 48,000 to 40,000.

OK, so what if 20% of Google's engineers generate 80% of the value? As long as either the other 20% of the value breaks even with the cost of the other 80% of engineers, or there's potential for explosive growth somewhere in the 80% of work that's being done outside of the core business, it's a smart decision. Google's not going to stop Microsoft from hiring enough engineers to make Bing just as good of a search engine. And if that's all they wanted to do, they could just go on LinkedIn and offer to double the salary of everyone in the Bing division and it would still cost less.


This is a really important perspective. It comes up in all sorts of fields: If your project is too big to fail, nobody wants to cancel it.

Therefore, everyone tries to make their project too big to fail. It doesn't matter whether the organization as a whole benefits.


The claim that companies hire to prevent competition seems extraordinary. As posited here it's really nothing more than speculation.


> they are constrained on what they can build by the availability of specific kinds of engineers in their organization

Can you give any details/examples of what these 'specific kinds of engineers' are?


"ones that can deliver software" would be the constraint at my organization.


Well, yes, that's pretty much always required, but I'm interested in hearing more specific requirements.


I'm guessing it means just normal requirements. As in, you need a web dev to create web services, EE to design hardware, etc.


I didn't mean to single out a particular specialty, only to call out that there are different kinds of developers, and companies can get constrained on one kind or another.


I was working at Microsoft shortly after 9/11 and one of their main goals was hoovering up talent let go by other companies. Ballmer (or maybe it was the head of HR can't remember her name) mentioned the strategy in a company-wide email.

The largesse worried existing softies so much that someone created the "Mini MSFT" movement, culminating in the blog: http://minimsft.blogspot.com/


Thanks for the downvotes! Are you denying that this happened? It most definitely happened.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: