Live data from Hacker News

Downsides to working at a tech giant

blog.garrytan.com

81–90 of 583 posts

Re: Downsides to working at a tech giant

#81

This is such a weird post. Big fan of Garry, but I don't agree with most of this. 1. Just because it turned out that you would have made $200mm doesn't make it a mistake. If anything, that outsized return proves just how rare this kind of outcome is. If you look at the YC startups graduating every year, maybe 1 will ever generate $20mm for an early employee, let alone $200mm. Joining a new startup for that kind of ou…

I hope that eventually as more and more people realize how much more they could make at big tech (IME a lot of people just straight up don't know, esp. when a lot of the comp comes as equity grants), startups will have to start paying more/offering bigger slices of equity. But seems we're not there yet. I also wonder how much of this is driven by software engineers who couldn't (or, probably more realistically, don't…

Oh I agree— big tech is fantastically lucrative! I wouldn't dissuade people from spending some time there.

Separately I also agree that there's a big problem of credentialism in software engineering. We meet lots of amazing software engineers who didn't go to the right schools— that's a big reason why I funded Triplebyte.

Re: Downsides to working at a tech giant

#82

This is such a weird post. Big fan of Garry, but I don't agree with most of this. 1. Just because it turned out that you would have made $200mm doesn't make it a mistake. If anything, that outsized return proves just how rare this kind of outcome is. If you look at the YC startups graduating every year, maybe 1 will ever generate $20mm for an early employee, let alone $200mm. Joining a new startup for that kind of ou…

Could you recommend good reading from this guy? That article doesn’t reflect well on his judgment- the story, the decision to post this story- the idea that Peter Thiel literally told him to quit his job (after he answered the question of his current salary?!?)- none of it makes any sense to me.

It's pretty bewildering to me too. The point is I said no, and it was the wrong decision. I ended up starting a company and later becoming a VC.

Re: Downsides to working at a tech giant

#83
Why did he value Microsoft over Their? There is something in his character that held in higher regard one decision over the other, there's no exploration of what caused the conflict in the first instance and a likelihood it will happen again. What should he have done with himself at that point and all future similar points where he has opportunity again?

This post seems to be more about signalling than lessons learned. Better luck next time!

Re: Downsides to working at a tech giant

#84

>> He asked, "How much a year do you make at Microsoft?" >> It was $72,000 a year, really the lowest of the low coming right out of college. He got out his checkbook and wrote me that check. >> "Cash this check, quit your job. This is a zero risk opportunity for you." >> I said, "Thank you very much, Mr. Thiel, but I might get promoted to Level 60 next year." Wow. This is probably the most impressive combination of a…

It's the safe and rational choice. I went to work at a startup after college and the company ran out of money in three years and valued my equity at zero. I absolutely would have been better off financially working for Microsoft.

That Palantir worked out is hindsight bias. There's no way he could or should have expected it to succeed at the time.

Re: Downsides to working at a tech giant

#85
post #68

It seems like he has found the problem with companies. "Even though these companies pay a lot of money, in real terms, what software is doing in society is creating a lot more value than what they pay you. Google's pure profit per employee is actually $1.6 million per year, after all costs." "If you're in the engineering, product, design, marketing, sort of the builder's side of that organization, you've got to know…

Huh? Google makes $1.6 Million profit because of the Google Enterprise not because of the Employee.

According to your logic, if the Google Employee quits Google and goes somewhere else, will he create the same $1.6 Million Value? No.

You can determine how much value you are creating by using a very simple formula. Quit Google and see how much less revenue or profit Google made. That's exactly how much value you are providing Google.

Re: Downsides to working at a tech giant

#86
post #31

Earlier quoted context omitted.

It might not be too late for the lottery numbers! I can't find it now, but I remember reading about a guy who was arrested in China for buying winning lottery numbers after they'd already been announced. The semi-surprising thing, to me, was that he did this more than once. Seems like a clear example of when you should take the win, and then leave in dignified haste.

Most criminals get caught because they can’t stop getting bigger. Same with most diseases

You mean the criminals that we catch are the ones who cant help getting too big

Re: Downsides to working at a tech giant

#87

This is more of a humble brag than useful advice

It's also self-serving. There simply doesn't exist $200M for every software engineer out of college. But if this guy, a venture capitalist, can get a thousand more people to think they'll win the lottery, invests in all of them, and 999 go bust, he'll still make money on the one startup that succeeds by being in the right place at the right time.

Re: Downsides to working at a tech giant

#88

I feel a lot of the folks here are focusing on the wrong parts here. The $200M loss was a cheap way of getting user attention, but hey it worked! The core of what he was trying to convey was the sooner you get to understand real user / customer problems the better off you'll be in life as an entrepreneur. He stayed away from this in his early days as he opted for stability and that he seems to regret.

> The core of what he was trying to convey was the sooner you get to understand real user / customer problems the better off you'll be in life as an entrepreneur.

And sometimes you're better off learning this at an actual company that ships products to millions of people than grinding away at a startup that won't exist in a year or two, with options that are worth nothing and a salary much lower than you'd get at a more established company. And there's a good chance the startup never ends up shipping anything of value. Startup vs Big Co isn't always a no brainer, lots of factors to consider.

Re: Downsides to working at a tech giant

#90
The pessimism in this thread really bothers me. I’ve read anecdotes on entrepreneurship being on the decline, but it pains me to read so many negative takes on startups. We’re actively training our young people to avoid taking risks, and it’s going to fuck us — especially if some of those young people have the ambition be early employees at, say, a startup that takes on climate change in a big way.

Look — the fact that Garry knew Peter Thiel when he was 23 is nuts. When I was 23 I was broke and living with my parents in the suburbs outside Toronto. I didn’t even personally know any other software engineers. I think many people here would relate more similarly to that position.

Just because he won the social lottery early, doesn’t mean his lessons are wrong. I got a junior engineering job in Toronto when I was 23, at a startup, making less than Garry. $57.5k CAD. I worked on my open source portfolio and next took a job in another startup in SF for $120k USD the next year.

That startup failed. I took a brief job at a biotech startup after being turned down by Google and Facebook (twice). After three months I quit that startup to run the company I’m still running today, four years later. Today, we’re very fortunate to work with some of the largest companies in SV.

Reflecting on this: I think a better story Garry could’ve told is not that he missed out on $200M, but that startups basically built his network so that — years later — he’d be a prominent VC working with Alexis Ohanian, funding the next round of exciting companies. $200M is an eye-catching clickbait headline, but not the real substance. The real substance is — how the fuck did he meet Peter Thiel at 23, and how can somebody recreate that?

In the story I just told about myself, I got really lucky as a function of working at startups. I didn’t really make any money doing it. But a whole bunch of interesting things happened:

- The first job in SF I worked at introduced me to a product manager who went to school with Aston Motes, employee #1 at Dropbox who would eventually be an investor in the company I run today.

- The founder of that first failed company introduced me to AngelPad, the accelerator that gave me my first $50k in financing. The fact I stuck it out as an engineering lead at a failing startup helped: I gave it my all. (Aside: YC turned me down. Twice.)

- The biotech company I worked at was founded by two early SpaceX employees, one who would also become an investor later on.

Don’t work at startups to make $200M. Work at startups because you’ll work with people who have risk profiles that are much more likely to generate outsized returns as a group. You’ll have the opportunity to join or create a community of high-performing folks that, in aggregate, outperform anything you can do on your own. Maybe you’ll be the CEO one day, maybe not, but no matter what you are very likely to come out ahead if you apply yourself.

And don’t let the comments here dissuade you. Startups are hard, but they kick ass. I’ve cried myself to sleep some nights — as both an employee and CEO — and still wouldn’t change the experience for anything. I’m a better person because of what I’ve been through.

Post reply on HN