News for hackers. Stuff that matters.
Re:What software engineers can learn from the rapid collapse... by lmeyerov on Thursday April 07, 2022 @03:04PM (#30948957)
Oof, just one of our customers pays about the same as their full revenue, and we're a cockroach team.

The real thing here is they're not that surprising. A lot of companies with their kind of funding use enterprise sales to force say $5-10M ARR, but there's only so much VC money can force for a leaky funnel, broken product, and overall incorrect market + fit. I didn't appreciate this until maybe a year or two ago. Valuation multiples in 50-100X range are super common (and even wackier numbers in seed/a). Think make believe stories like "well with another 12-18mo of growth this really just a bit over a 30X on some future forward revenue multiple...". The cash almost always leads to overspending, and it's highly unlikely the next 2-3 raises won't blow up and everyone goes home. I'm actually super impressed by the Docker team because they've been one of those rare cases of crawling out of that trap, even if with a lot less of the team.

We get job candidates with high competing offers for companies I know to be rotten inside, yet there's only so much I can say. "Our new hires are getting paid from customer revenue and with equity that doesn't have $50M-$500M of investor thumbs on the scales already cutting you out in 95% of the likely scenarios" generally doesn't punch through the kool aid.

Re:What software engineers can learn from the rapid collapse... by PragmaticPulp on Thursday April 07, 2022 @03:16PM (#30949110)
> We get job candidates with high competing offers for companies I know to be rotten inside,

I fell for this trick once when I was younger, but never again.

As it turns out, when companies are bleeding talent and struggling to hire they suddenly find ways to pay well above market rate. You can have a fancy title, too!

We had a competitor do something similar at a prior company. I would tell candidates that we can't match their compensation numbers but to come back if things don't work out at the other company. I'd often get a message about 3-4 months later asking if the job was still available

Re:What software engineers can learn from the rapid collapse... by meetups323 on Thursday April 07, 2022 @04:01PM (#30949675)
May help explain some Meta offers I've seen... 2 years out of college? Sure, come as a Senior! That's not enough? Principal it is!
Re:What software engineers can learn from the rapid collapse... by naiwenwt on Thursday April 07, 2022 @05:47PM (#30950731)
The problem is sometimes this is done for legitimate reasons and genuinely does lead to stronger outcomes for both employers and employees.

It's hard to tell the difference between "stop the bleeding" title/pay inflation and "aggressively competing for talent" inflation.

Re:What software engineers can learn from the rapid collapse... by lmeyerov on Thursday April 07, 2022 @07:19PM (#30951502)
Sort of. A good question is what is the revenue per employee

Meta is ~$2M/employee. Probably more like $1M once contractors are accounted for? But for a good person, even if the rest of the company has random issues, they can carve out a win.

Fast was like $1K/employee

Consider what that's like for some hypothetical B2B startup BlitzScaler Inc. They're betting on 3x+ growth year-over-year for next 2+ years, 2-3 year sales payback periods, etc, and is probably closer to Fast levels of revenue per employee than Meta's. But hitting $500K is hard, $2M is hard again in different ways, then again to $10M, and again to $20M+ (and increasing range depending if many sales people inflating it). That matters because many aren't there, even unicorns (!). That means, like Uber, they're burning increasing piles of money, except unlike Uber, the revenue is unlikely to be keeping pace. Fundraising buys team, and an artificial sense of fit+growth (kool-aid-drinking team + forced sales that tap out + churn.)

A cockroach team is closer to Amazon style: reinvest ~100% in growth, but don't gamble your employee's stock options.

Re:What software engineers can learn from the rapid collapse... by meetups323 on Thursday April 07, 2022 @06:01PM (#30950858)
Differentiator is what other companies will pay. If GAM all offer X, F offers 3X, and GAM refuse to budge on their X... either F knows some deep dark secrets about your capabilities which no one else can appreciate, or they're bleeding talent.
Re:What software engineers can learn from the rapid collapse... by frankchn on Thursday April 07, 2022 @09:47PM (#30952444)
It is usually not quite that drastic. More often it is like GAM offer X, F offers 1.2X.
Re:What software engineers can learn from the rapid collapse... by nomel on Thursday April 07, 2022 @08:02PM (#30951815)
> this is done for legitimate reasons

What could be a legitimate reason for giving silly titles? If it were a startup, it would be a huge red flag for an auditor.

Re:What software engineers can learn from the rapid collapse... by presentation on Thursday April 07, 2022 @11:30PM (#30953049)
A title is free to give and can motivate people who want them.
Re:What software engineers can learn from the rapid collapse... by mwcampbell on Thursday April 07, 2022 @11:47PM (#30953144)
Mightn't titles motivate the wrong kind of people?
Re:What software engineers can learn from the rapid collapse... by pedrosorio on Thursday April 07, 2022 @11:28PM (#30953031)
> Meta

> Sure, come as a Senior! That's not enough? Principal it is!

Do you mean staff (E6, the level above Senior)? Also, no one is getting E6 offers 2 years out of college.

Re:What software engineers can learn from the rapid collapse... by meetups323 on Friday April 08, 2022 @12:27PM (#30959169)
Not sure the specific title, just whatever was after senior. And I suppose it's more like 3 years at this point. Class of 2019.
Re:What software engineers can learn from the rapid collapse... by pedrosorio on Saturday April 09, 2022 @12:10PM (#30969266)
So, over $500k per year? Not a bad deal for class of 2019
Re:What software engineers can learn from the rapid collapse... by meetups323 on Monday April 11, 2022 @12:27PM (#30991097)
Yep, not bad. But talking in salaries hides the most important number: how many hours are you expected to work for that?

IME, F are the only ones to whip out their laptop at a house party or bar at 10PM on a Friday night because they felt an insatiable to work on some feature request; GMA may do the same when on-call, but I've never seen it otherwise.

I'm personally going the other route: Class of 2019, secured a decently sized FAANG bag (barely worked the whole time while doing it), and now I'm transitioning to a position with even fewer hours of commitment required but also lower salary. Going to focus on things I've come to find more important than money and code.

Re:What software engineers can learn from the rapid collapse... by hackernewds on Thursday April 07, 2022 @07:03PM (#30951373)
They seems to be the narrative I'm seeing for most of matters hiring. they're hiring very, very very aggressively
Re:What software engineers can learn from the rapid collapse... by nomel on Thursday April 07, 2022 @08:00PM (#30951795)
> find ways to pay well above market rate. You can have a fancy title, too!

On my way out of the first startup I worked for, there was an offer to double my pay! Nope!

Re:What software engineers can learn from the rapid collapse... by mwcampbell on Thursday April 07, 2022 @03:08PM (#30949020)
I'm not familiar with the phrase "cockroach team" in this context, and the obvious web search didn't help. Can you please elaborate?
Re:What software engineers can learn from the rapid collapse... by alex_c on Thursday April 07, 2022 @03:58PM (#30949632)
I'm not the op and this is the first time I've seen someone else use the term, but I've used it too. Aspirationally - small and impossible to kill. While a unicorn's goal might be growth at all costs (with associated high chance of failure), our goal is to survive anything that might get thrown our way.
Re:What software engineers can learn from the rapid collapse... by hyperpallium2 on Thursday April 07, 2022 @07:47PM (#30951684)
Look into the early history of Airbnb. They did anything to survive - even selling politician-themed breakfast cereal. Yes. pg exclaimed, you guys are like cockroaches, you just won't die.

Don't know if that's the origin, but hey it could be. Without the story, calling someone "cockroach" has unclear sentiments.

Re:What software engineers can learn from the rapid collapse... by altdataseller on Thursday April 07, 2022 @06:07PM (#30950909)
Cockroaches just care about survival first and foremost. Unlike unicorns that care about growing huge and taking over the world
Re:What software engineers can learn from the rapid collapse... by jollybean on Thursday April 07, 2022 @04:02PM (#30949684)
small, surviving on crumbs.
Re:What software engineers can learn from the rapid collapse... by lmeyerov on Thursday April 07, 2022 @04:35PM (#30950014)
Hard to kill because they're financially independent. We believe enough in the technology we're building (gpu-powered graph ai & visualization) and the missions we're powering (security, fraud, anti-misinfo, healthcare, etc.) that we turned down large initial funding as it would have broken us. So awhile back, being cockroaches meant running as cost-effectively as we could (and still do, in fact, just not as extreme) as we figured it out, and now that things are working, it means prioritizing sustainable growth vs financial games likely to fail.

In contrast, popular models prone to failure and largely fueled by market phenomena like low inflation rates include ad-based social media ("we'll turn on revenue in 5 years, no, really!"), blitzscaling ("we'll eventually figure it out!"), sales-driven growth ("our federal team will make our $ back in 3-5 years, no really!"), acquihires ("with enough AI talent we'll just sell our staff!").

I like venture capital, such as for deep tech and true growth, but the reality is most tech VC funding is more about financial engineering that assumes most of the portfolio fails. They push for commercial scaling too early and wipe out, which is fine for the rich VC who just needs 1-3 bets to win. Fine for them, but sucks for most founders & employees unless they job hop every 2 years. If we take VC $ again, it'd be on our terms and with a clear payback/growth return.

A great way to kill an otherwise great idea & company is putting VC $ in, which puts a company on overdrive and financially implodes before it has a chance to figure things out. They're addicted and likely can't stop relying on VC without layoffs (or less likely, succeeding), at which point many of the A players leave as well and hard to recover. Instead, if a cockroach raises > $2M (so commercialization phase), that should generate enough sales revenue that they can keep organically growing in 18-24mo later even if a follow-on round doesn't happen. You'll hear such cockroach founders saying they don't even touch the money for months. Numbers-wise, most Series A companies fizzle out, which is because of this unicorn-or-bust structure.. and especially whenever the market is not on a bull tear. With a bit more time, they probably could have figured it out... but they blew it.

Some articles: - Paul Graham's article on this: http://www.paulgraham.com/badeconomy.html . - https://medium.com/swlh/how-to-build-a-cockroach-startup-ins... - https://medium.com/the-mission/be-a-cockroach-not-a-unicorn-...

Re:What software engineers can learn from the rapid collapse... by diehunde on Thursday April 07, 2022 @03:49PM (#30949537)
Maybe they work at Cockroach Labs
Re:What software engineers can learn from the rapid collapse... by asadlionpk on Thursday April 07, 2022 @04:08PM (#30949757)
> we're a cockroach team

is this a reference to http://paulgraham.com/guidetoinvestors.html#:~:text=nuclear%...

Re:What software engineers can learn from the rapid collapse... by Jemaclus on Thursday April 07, 2022 @03:10PM (#30949038)
> we're a cockroach team

I think I know what you mean by this, but I'm not sure. Could you elaborate on what this means? Thanks in advance. :)

Re:What software engineers can learn from the rapid collapse... by munificent on Thursday April 07, 2022 @04:18PM (#30949844)
I infer that it means "small and hard to kill".
Re:What software engineers can learn from the rapid collapse... by woah on Thursday April 07, 2022 @07:15PM (#30951474)
> Our new hires are getting paid from customer revenue

Money is fungible

Re:What software engineers can learn from the rapid collapse... by Danieru on Friday April 08, 2022 @12:57AM (#30953453)
Cash flows aren't.
Re:What software engineers can learn from the rapid collapse... by umeshunni on Friday April 08, 2022 @01:52AM (#30953733)
Customer revenue is recurring
Re:What software engineers can learn from the rapid collapse... by pelagicAustral on Thursday April 07, 2022 @03:29PM (#30949273)
I should be a part of a cockroach team, in my estimation.
Re:What software engineers can learn from the rapid collapse... by aidaman on Saturday April 09, 2022 @07:17PM (#30973068)
i feel like even the possibility of a company like docker failing would be among the greatest failures in the history of software