19 ms·
Developers at unicorns: even in the best of times, do you feel more expendable than you've felt at other jobs? We always are amazed at the number of developers
by bdcravens 6y ago
Developers at unicorns: even in the best of times, do you feel more expendable than you've felt at other jobs? We always are amazed at the number of developers at companies like this. (the numbers I've seen are old, but I guess out of 22,000 employees, it was something like 5000 engineers?) While that allows you to build in a more robust way than a smaller company, it seems like there's no shortage of developers working on tooling, R&D projects, and at least partially on open source projects, roles that could presumably go away if a company had to focus strictly on the core product.
- spullara 6y agoAll the big startups hire all the best people mostly to stop them from getting hired anywhere else until they can't sustain it. Having 1000 extra developers is better than having 200, 5 person engineering teams working against them.
- ransom1538 6y ago"Developers at unicorns:" Prato principal crystallized. Look at any big repro or any large company. There is usually about ~5 ish people that know wtf is going on. I think uber could be ran with 10 people.
- pc86 6y ago> Prato principal crystallized You're wrong, and not just about the Pareto principle.
- gdhbcc 6y agoHe is probably Portuguese speaking, and his autocorrect changed the spelling.
- pedrosorio 6y agoCan confirm, I was having a hard time parsing how "main course" in Portuguese made sense in the middle of that sentence.
- deleted 6y ago[deleted]
- CydeWeys 6y agoWorth pointing out that Uber is no longer a unicorn. It is a large publicly traded corporation with a market cap of $58B. I suppose you're asking your question about large tech companies generally, not so much unicorns? Most unicorns are still quite small (revenue and employee count-wise) relative to large publicly traded corporations like Uber and the FANGs.
- bradlys 6y agoAm at a Unicorn. Engineering is 20-30 engineers total. This person is definitely confusing Unicorn with some generic big engineering heavy company. Many companies scale very differently. Some scale with large engineering efforts - mine doesn't. The change in number of engineers has barely moved in the last 2 years. That said - to the question about unicorns: You're always expendable. Same as any job - same politics - same nonsense. No matter how important they make you think you are to a products success - they'll fire you regardless. It's amazing how fake management will be about urgency. "This is the most critical business function! We must have people working on it!11!!1!1!" Fires key employee because they didn't like them - "critical business function" gets shoved into the backlog to never be seen again. People are fake and think they need to show urgency to get the most value out of their employees.
- MattGaiser 6y ago> "critical business function" gets shoved into the backlog to never be seen again. Never worked for a unicorn, but everything from big corp to startup to government. "Urgent" provokes no reaction from me anymore because of this.
- Fauntleroy 6y agoThe only truly urgent thing I've seen is a product being down / a critical bug in production.
- greenyoda 6y agoAnything that can cause your company to lose a lot of money can be truly urgent. For example, your biggest customer needs a new feature, and if they don't get it by the end of the quarter, they'll switch to your competitor. On the other hand, artificial deadlines that are invented by your company's management are usually not urgent.
- tinyhouse 6y agoI worked for small and big. Everyone is expendable. Running lean or efficiency is not something those companies optimize for. That's why they have so many employees. They optimize for growth. Until something bad happens.
- fermienrico 6y agoI don't understand your point, can you please elaborate more? I read it twice and your comment isn't making any sense to me: 1) Are you suggesting that developers should go join a smaller company so they are less expendible? 2) Are you suggesting that developers, now that they are laid off, go work on R&D projects, tooling and open source startups? I am so confused. What is the take away?
- MattGaiser 6y agoI do not think he is suggesting any course of action beyond awareness that their position is less stable than it might be in other jobs.
- CydeWeys 6y agoWorth pointing that your position at a unicorn is probably more secure than at a random small startup.
- fermienrico 6y agoOhh....I get it now. Jeez, I need more coffee. I've always worked in manufacturing so people aren't that easily expendible. Takes a long time to train someone and without them, one of the line shuts down or gets less productive / slow.
- MattGaiser 6y agoHow long do people usually stay at your company?
- fermienrico 6y agoAverage is probably 8 years.
- zankly 6y agoWell regardless of economic boom or bust, the chance that a startup runs out of money is probably higher than the chance that a big company chooses to lay you off.
- simias 6y agoI've never worked for a true unicorn but I've been in companies that got a sudden success and grew way too big way too fast. I think you can tell from the inside when a company loses its way. As you mention, suddenly you have tons of teams working on what seems to be fairly niche aspects of the company's product. You have man-years worth of work going nowhere as projects get scrapped mid-development. You start having a massively more complicated hierarchy of bosses and managers and project leaders and it seems like everybody is chief of something and everybody loses sight of the big picture as they just become focused on a single aspect of a given product. What was once a lean startup with a vision is now struggling to get new products out of the pipeline even though they have ten times (or more) the manpower. Growing is hard and unicorns are expected to grow really, really fast. In the end many companies with a completely viable product end up going under just because investors thought that a million dollar company should be a billion dollar company.
- sandworm101 6y ago>> You have man-years worth of work going nowhere as projects get scrapped mid-development. That's better than seeing man-years go into features that get deployed. I witnessed one successful control system company spin up a team of new hotshot UI engineers, all right out of the best schools. After months of work the team "updated" the product. Withing hours the call center was hit with hundreds of "You changed the g-dam menus!! Put them back NOW!!". The trick is to squeeze your long-term UI project in the same update as some routine security fixes. Then the clients are forced to learn the new system.
- staticassertion 6y agoOr do A/B testing and incremental rollouts?
- brianwawok 6y agoA/B tested products are terrible. Please don’t do that to an actual product people pay money for. “On this page, 12% more users clicked save if the save button was green instead of blue”
- gkoberger 6y agoLet's say you like the Warriors. You and a group of friends get together every game to cheer for them. You're the one everyone looks to for bringing the beer, and you enjoy the group you hang out with. And when the Warriors win (or lose), there's a huge energy you get to be a part of. I think it's the same with big companies. You can be a big part of your individual team, and it doesn't particularly feel much different than working at a startup day-to-day. And as a bonus you get to be a part of the large-scale wins and loses. Much like how it's exciting when the Warriors win, it's exciting when something big comes out of your company. Even if you did nothing but cheer. Everyone is expendable. Travis, the founder and CEO of Uber, was expendable. So are people at large companies or small startups. But within your team, you get to do good work, and it doesn't feel that way.
- bdcravens 6y agoMuch like the Warriors in the last year, it's hard to ignore your team taking losses, especially when success was so easy in the past, and thinking about finding a new team if things don't improve.
- sneak 6y ago> Travis, the founder and CEO of Uber, was expendable. I didn’t like the way he conducted himself or ran his company, but the jury is still out on that. TFA is about how that ball is still currently in play.
- Traster 6y agoIt's a double edged sword, on the one hand you have the freedom to work on interesting projects, new technologies and get well compensated. On the other hand most engineers working at uber should be able to critically think about their job and say "Is what I'm doing contributing to the noticeably to the core business or am I part of a gamble the company can afford to make right now"
- alfalfasprout 6y agoI'm at Airbnb (opinions strictly are my own). The number of engineers working on tooling for us is actually not that large. The vast, vast majority are product engineers and with our most recent layoffs the majority of the cuts were for those types of engineers. My own opinion is that we simply had way too many product engineers for the amount of actual output we got from them. Uber is on another different plane altogether... they have more than double the number of engineers and from talking w/ colleagues that worked for years at Uber it's my impression that even on infra there's a lot of bloat. Plenty of high level ICs that couldn't produce quality IC work to save their lives and plenty of pet projects.
- swyx 6y agoright. this recession is actually giving cover to let go of a lot of bloat that has built up over the years.
- downrightmike 6y agoWell, freeing it up to compete. I expect some of the bloat is just so that someone can't work for a competitor.
- alfalfasprout 6y agoYou'd think so but that's at least not the impression I've gotten. At Google that's certainly going to be the case but at a company like Uber/Lyft/Airbnb the bloat ends up largely arising due to managerial bloat (managers want to grow their org to make themselves seem more important) and low technical standards for higher level ICs (which results in far more resources used to accomplish each project).
- senderista 6y agoAre you saying that technical standards are lowered as one moves up the IC ladder? If so, how and why?
- hintymad 6y agoIt's not about in unicorns or not. It's about the scope and impact of your projects, both of which have more to do with the size than the PR status of a company. When the quantity of people in a company exceeds the quantity of work, you'll be much more expendable. Following this type of logic, joining Uber in 2015 or later is a bad idea. Joining airbnb in 2015 is a bad idea. Joining Google now is likely a bad idea. Joining new orgs in AWS is probably a good idea. A few heuristics that I find useful: 1. Revenue per employee 2. Moving average of number of substantial launches in the past X months 3. Actionable technical blogs that address real challenges directly related to specific business needs. So, no, Uber's why they switched from MySQL to Postgres and then later another article by the same person on why they switched from Postgres to MySQL do not count.
- meditativeape 6y agoThese heuristics are interesting. Do you have concrete numbers for some of the big techs?
- gen220 6y agoI agree this is a great way to think about it. At the end of the day “business impact” per employee is the thing that matters most to your individualized risk. If your expertise is essential to the continued improvement of the company’s core business model, you have nothing to fear. It’s super important to note that business impact is not even close to uniformly distributed throughout a company, even though we sometimes like to pretend that it is. This is all to make a subtle refinement of your point, that it’s worthwhile to join teams that are high value per engineer, even if the company is more bloated. (Ad serving infra at Google, ec2 at AWS, payments processing at Uber). However, because those teams are so essential, they tend to have low turnover, higher bars for entry, and a higher than usual rate of internal transfers (as high performers from less essential teams are shifted into more critical roles). So you’re less likely to be placed into those teams from the outside, unless you have a history of working for those kinds of teams.
- datadem 6y agoUber actually has some of the best technical writing in [datasci/causal inference](https://eng.uber.com/causal-inference-at-uber/ https://eng.uber.com/causal-inference-at-uber/).
- ratww 6y agoDefinitely. The company just felt bloated. Feature teams needed 7 or 8 people working constantly on single screens that would be an afterthought in an MVP, just to keep up with the constant changes in architecture and infrastructure. Lots of over-engineering and NIH from veterans that didn't want work on teams. Lots of rewrites due to performance issues. All that without any noticeable change for the customer (other than the website becoming slower). VCs and middle-management kept asking for more developers, though, so everyone was happy, but the general perception was that we would do just as well (or better) with a half, or a third of the staff.
- monadic2 6y agoWell you don’t get VC money because you want to give people jobs, so yes.
- burnte 6y ago5,000 engineers for Uber. Absurd.
- rachelbythebay 6y agoOh, you might be surprised how many people are not working on anything of consequence. Some of these companies don't even do much in the way of building stuff outside of the product teams, and even then, they frequently fizzle after some point. You know the line "don't mistake motion for progress"? There's a whole lot of motion up in those SoMa offices... but very little progress. Some of these teams are very good at doing a lot of jiggling around while never accomplishing anything. They manage to snow their manager, which snows the next-level up, and if nobody calls BS, it just goes on like this. R&D? When the response to building something new is an _immune system flare-up_ from the people who benefit from things remaining exactly as they are, there can be no R&D. Just like the server situation, the employee situation is bloated beyond belief. You have people making messes and others cleaning it up, instead of just not making the mess in the first place (and then needing neither of those people). If a million monkeys at a million typewriters would eventually produce the works of Shakespeare, some of these companies would likewise boil down to "three monkeys, ten minutes" (not my line but I love it).
- dehrmann 6y agoI see it more as scaling problems that make it look like people aren't actually busy. As the userbase scales, infrastructure scales, and what was once a simple "ALTER TABLE" is now a system with a team managing it because a single Postgres instance didn't scale. As the engineering headcount scales, code changes, builds, even understanding the system become slower. You overcome that with better engineering, but mostly more engineers. As the product matures, there's still a drive for growth, but the low-hanging product fruit has been picked, so you get lots of product teams trying to either optimize their little part because, at scale, it makes a big difference, or product teams working on new, crazy ideas--the startup within a unicorn-startup--that will most likely fail.
- kaydub 6y agoThese companies are beyond being unicorns though. I work at a unicorn and our whole R&D team is only like 100-120 people.
- staysaasy 6y agoAs someone who has hired many engineers and PMs, and runs a hiring budget today, there are some reasons to feel at least fairly secure if you're an engineer at a growing company: - Building a high-quality product is a longterm investment and most technology companies know that. As a result, in my experience companies who expect growth would always prefer to keep engineers and PMs as investments. - Companies generally find it hard to hire Engineers and PMs that meet their standards, especially in competitive markets like the SFBA, NYC, Boulder/Denver, Seattle, Austin etc. (You can argue whether that's caused by overly stringent hiring standards - that's a much more complex question). As a result, companies are somewhat more likely to "hoard" engineers if they expect that they'll need them to grow. - Because engineers in these markets are expensive, it makes economic sense to spend to improve their productivity. If I have 100 engineers on my team and I can make them all just 1% more productive by hiring an additional engineer who focuses solely on internal tools or open source libraries that improve developer QoL, that's arguably money well spent. - Many products at scale are more complex than one might expect from the outside, which demands a lot of ongoing product/engineering effort to maintain. If you're working on something that has a credible path to revenue or clearly makes/saves money now, your job is probably fairly safe. This all assumes that 1) the company wants to keep you, and 2) the company is growing, even modestly. Once the financials go downhill companies will cut directly to the bone in order to survive, and at that point nobody in any industry is safe. (edited for formatting, thanks @mkl)
- mkl 6y agoQuoting for readability: """ - Building a high-quality product is a longterm investment and most technology companies know that. As a result, in my experience companies who expect growth would always prefer to keep engineers and PMs as investments. - Companies generally find it hard to hire Engineers and PMs that meet their standards, especially in competitive markets like the SFBA, NYC, Boulder/Denver, Seattle, Austin etc. (You can argue whether that's caused by overly stringent hiring standards - that's a much more complex question). As a result, companies are somewhat more likely to "hoard" engineers if they expect that they'll need them to grow. - Because engineers in these markets are expensive, it makes economic sense to spend to improve their productivity. If I have 100 engineers on my team and I can make them all just 1% more productive by hiring an additional engineer who focuses solely on internal tools or open source libraries that improve developer QoL, that's arguably money well spent. - Many products at scale are more complex than one might expect from the outside, which demands a lot of ongoing product/engineering effort to maintain. If you're working on something that has a credible path to revenue or clearly makes/saves money now, your job is probably fairly safe. """ Please don't use code formatting for text. If you want bullet points, put a blank line between them to make separate paragraphs: https://news.ycombinator.com/formatdoc https://news.ycombinator.com/formatdoc
- scarface74 6y agoAll developers are expendable. If 5% of all developers at any of FAANGM's got hit by a bus, the company would keep moving. I work at company with less than 100 people, I know where many of the bodies are buried, etc. But if I get hit by a meteor tomorrow, they would send flowers to my wife and open up a req and keep moving.
- danans 6y ago> But if I get hit by a meteor tomorrow, they would send flowers to my wife and open up a req and keep moving. You don't have a group life insurance policy through your company? Sudden unexpected death is exactly what that supposed to cover. If not, that's unfortunate, especially since it's fairly common among white collar jobs at least. If you do, it should cover at least your funeral costs, which should be pretty minimal if your cause of death is meteor strike. It would likely cover a percentage of the income you would have earned for your remaining years of work. But opening a req seems totally reasonable when you are demonstrably not coming back.
- scarface74 6y agoGroup life through most companies are 1x salary. That amount is a pittance to buy on your own. But the point is everyone is expendable. I worked for a company around 2009. They laid a lot of people off that had more seniority than I did. I wondered why they kept me around. Three months later I found out. The founder had written a bespoke development tool chain in C++ using MVC and assembly. The board push him out and the CTO told me that I was now responsible for maintaining the tool chain because I was the only one who knew C++ and assembly.
- danans 6y ago> But the point is everyone is expendable. In the extremum, everyone is expendable, but not everyone is equally expendable, as your own anecdote bears out. When you expend enough people, especially increasingly less expendable people who carry your basic institutional knowledge and skills, you do so by inflicting damage on your company or organization. The economic winds may dictate that, as they did frequently in the 2008 economic crisis, but it's not like there is no institutional cost to expending people. This is the basically why countries like Germany and the UK are paying employers to keep idled people on payroll.
- pyuser583 6y agoEven at Google, how many people work in advertising?
- thejynxed 6y agoArguably everyone from the CEO to the intern pulling gofer duty seeing as how that is the vast, vast majority of their revenue and profit and everything else is just more advertising for Google itself.
- artsyca 6y agoI wish we would take a hard look at corporate culture from a systems perspective, as self-professed systems professionals intent on "solving hard problems" and see how we ourselves contribute to the culture of disenfranchisement through our cumulative individual actions which we often attribute to "that's just how it is" rather than taking extreme ownership and fixing things in our own favour
- yibg 6y agoI think for large companies this is true and by design. Companies don’t like single points of failure so by design should be able to afford to loose x% if engineers (or marketing etc). Of course any large company with staff in the thousands or tens of thousands will have bloat. But I’d guess a lot of the engineering headcount that is not in “core stuff” are adding value. There is a lot of value to be added by making relatively minor tweaks when your revenue and costs are in the billions. Reducing a few percent server load or getting a few basis points of additional revenue / members etc can be worth multiple teams of engineers. The company will survive if those teams are gone, but it’ll probably hurt long term growth trajectories to some extent.
- pwdisswordfish2 6y agohttps://en.wikipedia.org/wiki/Bullshit_Jobs https://en.wikipedia.org/wiki/Bullshit_Jobs Through this pandemic experience, companies that were not previously forced to run more efficiently are now having to learn. Once they have figured this out, and IMO that does not take long, then there are few reasons to again carry the same amount of overhead, including employee compensation and benefits, office space, etc. These BS jobs are not responsible for increasing revenues or decreasing costs. Eliminating them to reduce overhead is a no-brainer.
- rgblambda 6y ago>>Eliminating them to reduce overhead is a no-brainer. Having read David Graeber's original article and his follow up book, I believe he went to some lengths to explain why those jobs are so difficult to remove. Jordon Peterson has also touched on this subject in one of his less controversial lectures. He uses Price's law to explain the proliferation of these jobs, the subsequent demise of the organisation when the handful of useful workers leave, and also that the remaining employees are unable to step up when this happens. I prefer Peterson's interpretation, mainly because Graeber is quite fundamentalist in his view that a job is either bullshit or it isn't. Peterson's view is that large numbers of employees do productive work but that it is minimal in comparison to the few very productive workers.
- pwdisswordfish2 6y agoI think there are more than just those two interpetations. I also think more people than Graeber have been aware of the existence of BS jobs for a long time. What is nice about the Wikipedia page is that it acknowledges that BS jobs "is a thing". Perhaps it facilitates more open discussion of the phenomenon. SARS-CoV-2/Covid-19 may be facilitating the discussion even more as it has forced people to consider what jobs are "essential" versus what logically can be referred to as "non-essential". I have seen one commenter on HN raise the issue of why pay does appear to correlate with whether a job is essential or not. Perhaps this is something more people will start to think about.
- alangibson 6y agoI've noticed that, as projects or entire companies grow, the effort spent on the product decreases relative to the effort spent on things _about_ the product. Effort spent on building specialized libraries, tooling, secondary infrastructure as well as meetings, coordinating with stakeholders, dealing with outside research firms, etc. explodes while effort spent building those things that are clearly on chain delivering value to the customer grows rather more slowly. It's really hard to decide if this is a good or bad thing. Certainly huge amounts of it can be seen as non-value-adding wankery, but it may all be in some way intrinsically necessary in order to scale up.
- mathattack 6y agoThe risk is the same at non-Unicorns. Look at developers at J Crew, hospitals and governments. All will face a squeeze.
- fatnoah 6y agoDevelopers at unicorns: even in the best of times, do you feel more expendable than you've felt at other jobs? I've never been at a unicorn, but I have been at many startups. The story is the same everywhere. Almost no one is irreplaceable. When times get tight, cutting overhead means letting people go.