5 ms·
> How does a team grow to ~300+ developers ($89M R&D) to figure out how to attach PDFs and videos to tickets, and email people when there's a change in status?
by PragmaticPulp 6y ago
> How does a team grow to ~300+ developers ($89M R&D) to figure out how to attach PDFs and videos to tickets, and email people when there's a change in status?
As with most of these companies, user-facing feature development is only a small part of the engineering workload.
I would assume the majority of those engineers are working on less visible tasks: Devops, build systems, infrastructure monitoring, security, backups and data integrity, internal tooling for customer support, billing and accounts management, and other critical but otherwise invisible tasks.
Duplicating the core 80% of Asana's features as a one-off product wouldn't be extraordinarily difficult. Scaling it into something that can operate as a business with hardened security, reliable data storage, consistent uptime, and reasonable internal tooling for customer service is where things get difficult.
That said, companies often go overboard with hiring in the run-up to IPOs or acquisitions. Excessive R&D spends can be fixed on the road to profitability. Restoring a company's reputation after a major data loss disaster or a security breach is much more difficult, so it's safer to err on the side of throwing too many engineers at polishing everything. If they can't scale revenues to match, expect the engineering workforce to be cut down significantly.
- sheeshkebab 6y agoA lot of internal tools is overengineered bullshit... if that’s what they are spending it on (doubtful though - it’s probably mostly some form of sales).
- dx034 6y agoFor most companies I've seen, enterprise sales is what costs most money. It's worth it in the end but there's nothing you can automate around all the calls, forms and processes you have to go through to get a big enterprise client. Yet many companies invest in it because in the end, the client is happy to pay for all your additional expenses, knowing that they can trust your service.
- dcolkitt 6y agoThis makes a lot of sense. But in some ways it shows the downsides of the modern obsession with SaaS. How many of those jobs would be required if Asana was simply sold in a shrink-wrapped box that you installed on your desktop or the downstairs server run by the corporate IT guy. In some ways SaaS is a big win because it offloads all those tasks to a centrally hosted service. No IT guy or tower server in the corporate mail room required. OTOH not everyone has the same ops requirements. Not every customer needs 99.999% reliabilty. Or ultra-hardened HIPAA-compliant security. Or heck, even remote access outside the office LAN. By delivering Asana as SaaS instead of shrink-wrapped software, it means the Asana hosting team has to deliver to insanely tight operational requirements to every single customer. If one customer requires 5-9s of uptime, then basically every customer requires it. That certainly explodes the cost-of-goods-sold beyond selling shrink-wrapped software.
- sujinge9 6y agoSure, but it's economies of scale. You only have to do the hard stuff once at the source, instead of having every node do it individually. Also if stuff goes wrong in the node model, the customer will blame you even if it's mostly their fault. So it's also important for brand benefits.
- bryanrasmussen 6y agoOn the other hand if stuff goes wrong in the centralized model it goes wrong for everyone everywhere, and it almost certainly is really your fault. I agree trade-offs, but I sometimes feel the gain has not been all that great.
- freehunter 6y agoIf it was shrink wrapped software they would need a bigger sales team, a bigger support team, a bigger professional services team, etc. It’s just trade offs.
- AlphaSite 6y agoAnd honestly its actually even more work in many ways, since you need to be able to work anywhere, not just in a well known environment.
- jmnicolas 6y agoIn the age of VMs and containers I'm not sure it's still true.
- dx034 6y agoI've been involved in debugging a bug in a software that occurred on Kubernetes cluster at the client site but couldn't be reproduced locally. Reproducing that is so much harder than a similar software installation. You have so many moving parts that it's pretty much impossible to create a test cluster with the same properties. Also, with SaaS you can get access to log files, if it's installed on prem that can be heavily restricted by regulation.
- underwater 6y ago> Duplicating the core 80% of Asana's features as a one-off product wouldn't be extraordinarily difficult Not to mention that they didn't have the advantage of duplicating features. Developing an application from scratch requires significant experimentation, false starts, deprecated features, associated tech debt, reinvention, etc. Just because you can drive across the US in four days, it doesn't mean the first explorers to make the journey were lazy.
- tootie 6y agoOps and Infra should be a fraction of feature development though. Not most of your team.
- manquer 6y agoThis is common reason cited . I don’t disagree as such, as my own product grows I see it happening . However I am not sure how much is strictly necessary. I honestly think a small team could achieve lot more . You loose the agility of smaller team at >50 have large company problems without the benefit of sheer manpower 500-1000 typically brings. Scaling devops is not as hard as it sounds . There are plenty of cloud native services which scale pretty well more or less out of the box( you still domain knowledge I.e. need to know that service’s unique limitations) scaling it for cheap is harder, still not as hard as it used to be, plenty of mature tech is available today. Ironically devops engineers with modern cloud skills generally are more expensive than the ones who know how to stand a server in a DC. A lot of startups like WhatsApp , Instagram built great products at scale with less than < 50 so it not impossible to achieve
- aahortwwy 6y agoA major reason why engineering teams at these sorts of companies grow so large is because of how quickly the business operates and the company's rate of growth. These factors put the engineering team in a position where they're constantly having to choose the faster, easier option in the present despite the fact that it will produce a lot more work for the team in future. When the future rolls around they're still under the same constraints so they hire more people to deal with the problems caused by their past decisions while making the same kinds of decisions in the present. Rinse and repeat for several years as the company grows into a behemoth before going public. One interesting thing to note is that as these constraints relax (business stabilizes, growth slows) the engineering teams can make better decisions in the present, clean up the decisions of the past, and reduce their overall need for people. If the company has built a money-printing machine the redundant people are then moved to new lines of business funded by the money-printer. If there's no money-printing happening, margins are super thin, and there's an incentive for the company to cut costs... where do those people go?
- dbtc 6y agoWhat do you think drives the unnecessary growth?
- 6y ago
- cryptica 6y ago>> I would assume the majority of those engineers are working on less visible tasks: Devops, build systems, infrastructure monitoring, security, backups and data integrity, internal tooling for customer support, billing and accounts management, and other critical but otherwise invisible tasks. Most of these other things are absolutely useless.
- eru 6y agoUseless in what sense? And which of those things? Eg backups and data integrity sound rather important. Eg build systems are only useful as an enabler for the other things your company wants to do, true.
- dx034 6y agoCompanies saving money on backups pay for it at some later date. Also, you won't/shouldn't really pass any audit without sound processes in place. Billing is easy until you have to serve 200 countries, each with their own regulation and tax systems. Sure, you can outsource that but it won't be much cheaper once you reach scale (as parts remain manual). And I don't think many would agree that customer support is useless. As a developer, I wouldn't want every customer request to hit my desk. Having customer support that cannot only filter out requests but also respond in a less technical way than most developers is invaluable.
- zaphirplane 6y agoa technology company’s operational work is larger than its development is a bad signal. The reason reminded me of when I get quoted a large price for an hours work like dentist or plumber and they are like i have insurance and car expenses ;)
- rsp1984 6y agoAlso keep in mind the old wisdom that the safest way to delay a project is to throw more engineers at it. Hiring engineers breeds hiring more engineers. To give you an idea how many engineers are actually needed, Instagram hat 13 engineers when they were acquired, WhatsApp had 60. And that was 8 or 6 years ago respectively.
- jariel 6y agoIsn't AWS supposed to handle most of that? Kik messenger had 300M users and a tiny team. Same with WhatsApp - and it's reliable. Asana scales more or less horizontally, meaning that they don't do anything much at the scale of all of Asanas customers. No individual customer repo should be massive (unlike say Facebook, where a user search searches the entire world.)
- waheoo 6y agoMessenger services live or die by network effects. SaaS services with easily replicatable software live or die by building barrier to entry, usually this is done by building up a wall of feature add ons and integrations, in the case of Asana, integrate with all the things and suddenly it's a pain in the arse to replicate it all. I would hazard a guess most the development effort is based around building up that wall of features.
- jariel 6y agoYes I agree. But my point with the Messengers is that it's not really 'scale' so much. Or dev ops. It's more likely the 'wall of features' and perception in business as being the Gartner 'Magic Quadrant' leader etc..