Hacker News new | past | comments | ask | show | jobs | submit login
Ask HN: Pros and cons of working at a startup in 2018?
1139 points by snowmaker on June 11, 2018 | hide | past | favorite | 939 comments
I’m Jared, one of the partners at YC. When I joined YC, one of the things that I most wanted to do was to help make hiring and getting hired suck less. I have a business reason and a personal reason for this. The business reason is that YC's job is to help the startups we fund, and helping with hiring is one of the biggest things we can do. The personal reason is that before I joined YC, I did a lot of hiring for my startup, Scribd, and for me it was the most rewarding part of starting a company. Some of the people who joined us had life-changing experiences - they moved across the world, jump-started a new career, grew with the company and became leaders, or used their experience to start their own successful companies. I wanted to help more people have those experiences and not feel stuck in jobs where they don't have much impact.

So, a few of us at YC have been building Work at a Startup (https://www.workatastartup.com/), with the goal of making it easier for startups to hire, and engineers to get hired, at a YC company. We started with the same insight that everyone else has: the hiring process is broken and inefficient, and decided to look for ways we could make it better for everyone, at least within the YC ecosystem. For example, we could get rid of the burden for applicants of having to send a resume and cover letter to every company by creating a simple way to apply to all YC companies at once.

While working on this, though, and talking to engineers and HN users about it, I realized that there's a more fundamental question: why should people want to work (or not!) at a startup in the first place? This question has a history and has gone through several phases. In the early heyday of YC and HN and pg essays there was a ton of enthusiasm about startups, the freedom and creativity and opportunity they offer. In more recent years, when I read HN threads (like https://news.ycombinator.com/item?id=15916350, to pick one close to home), it's common to see people arguing that, for early employees, joining a startup isn't such a good idea. And frankly, some of their points are good ones. There are issues that need to be fixed. One of the big things that YC did in the early days was move the needle in favor of founders. That was an adjustment that badly needed to happen, and it did happen. I think the next phase is to move the needle in favor of early employees. Just how to do this is one question I'm hoping we can discuss in this thread.

So, HN: what are the pros and cons of joining a startup in 2018, particularly as an early employee? And where there are cons, what would fix them? If there are concrete ways we can find to shift the balance, YC is interested in doing that.




I was the first engineer at a TechStars startup that did have a successful exit (I was there about 5 years before the exit). If there is something I want YC to know, it's this:

You helped create the culture of founder empowerment. You have the power to evolve that narrative to those that sacrifice as early employees.

Tell the world that early employees deserve a lot more equity.

Tell the world that early employees contribute to the success of those companies and deserve to have that help their careers.

Because here's what I see are the pros/cons...

Pros:

* I was forced to learn with no one else to help me. Not sure I'd be as good of an engineer without that.

* I got exposure to a lot of things I wouldn't normally be able to control, which propelled my career going forward.

* I built the seed to make connections with people in the startup community which I still leverage today for my own consulting business.

Cons:

* I was paid terribly, and this was 8 years ago, so it was even worse than now.

* Even with the exit, I basically made enough money to recoup the money I should have been making at a bigger company, so it's net neutral.

* No one cares about that as a success for me. I'm surprised no one has brought this up. I was the 1st engineer for a company that had a successful exit for TechStars. Zero recruiters, companies, etc, have ever even asked about that company or my connection to it other than the fact they are reading it down on my resume (and when they do see it, they barely take note of it).

And for the record - I have no beef with the founders. But the culture around how to pay and credit early employees is institutional and was not their fault. They walked off with huge payouts and credit for their success, and I walked away with a catch-up check for missed EV and no one cares that I played an instrumental role in getting them where they are today.

But YC has the power to change that. I reiterate from above: you have the power to tell the greater startup community through your words and your actions that startups should provide better equity to early employees and make it so that the success of a company is shared far greater than that of just the founders.


Maybe engineers are more replaceable than founders? That would explain why founders walk away with a lot more cash and credit. After all, there are a lot of good engineers who probably would do a good job as an early employee. And relatively few people who have the vision, motivation, and skill to create a successful company.

That said, I sometimes feel that being a successful founder has less to do with skill and more with being at the right place at the right time.

Would be interested to see what others think.


This is such a laughably unprovable claim. "Few people who have the vision, motivation, and skill" is equivalent to saying "few startups succeed". It's just a truthism. It's equally likely that few companies are lucky enough to have a talented and motivated team of engineers.

Finding someone who thinks they have it all and will be the next big billionaire is easy. Finding a group of people who know what work needs to be done and can put their nose to the grindstone to match the "vision motivation and skill" is the hard part. Just look to google, the holy grail of tech visionaries. No one doubts that Page and Brin have vision/motivation/skill but they readily admit that their initial team of engineers is what carried them and they rewarded them like it.

What you're advocating probably feels good for the ego though... everyone loves imagining having demi-god-like status. For me it's always interesting to look at what people are fighting for. "The founder deserves 100 million, not 80 million, pay the engineers less!" At the end of the day it's just greed.


As an engineer of middling competence (I don't do poorly, but there are people smarter than me), I think you're wrong. The reason engineers receive less than they're worth by and large is because A. they cannot negotiate very well and B. they do not know their own worth. If you combine these two with some idealism, which is the only real reason you'd work for a startup (high-risk, low-reward work - if it's not for ideals you have no reason to do it), you get a prime exploitative opportunity for any employer.


Suppose getting a good engineer would contribute $2 million / year profit to a company. That company would offer a higher salary than the going market rate, and thus steal engineers from competing employers (in fact, that's exactly what FB, Google, LinkedIn, etc. do: you can ask them to match or beat the other company's offer). Since regardless of how badly engineers negotiate, they would still be attracted by a higher offer. Then other companies would also offer higher salaries, to avoid missing out in hiring. This cycle won't stop until compensation gets to a good fraction of that $2m/year; say, $500-800k/year or so, leaving room for overhead (office rental, benefits, etc.) and profits. The fact that it doesn't happen tells me that me that most engineers probably aren't worth $2m/year to companies.

I do agree with your last point: engineers are often idealists and/or they have very strong preferences about what they want / don't want to work on. So they may often be willing to give up much better comp in order to satisfy such preferences. That's why startups get away with paying maybe half of what large corporations pay. Still that's not nearly enough to explain the gap between engineer and executive compensation.


I get the sense that with the right set of employees all a founder has to do to be successful is not to run in the way. One might argue that in that case they were so brilliant at hiring they deserve the payout. Anyway, who is to say where the line is drawn between founders and employees re: who contributes most? As long as both sides know what they’re getting in to nobody is taken advantage of.


Hear hear all you young uns. This is what happens when you work your ass off for someone at low cost. Never ever work for less than you are worth. Your income minus stock should always be par or above with the market.


I agree, especially on your last point. Even when I think of my own career highs and lows, most of the highs has to do with lucking out with being given a chance or opportunity. By contrast, most of the lows has to with being denied a chance or opportunity. Of course you have to take advantage of any opportunity and work hard for it to pay off. But being lucky enough to be in the RPART is, huge!


Interestingly YC has encouraged startups to offer more equity to early employees and I'm not sure it's had an effect. See pg's recommendation in http://paulgraham.com/equity.html


I vaguely remember reading that article while I was at said company making basically the same salary (with the same company valuation at the time) and realizing my equity was far below that and scratching my head.

If I had PG's recommended equity instead of what I had I would have gone from neutral EV to basically pay-off-my-house money. Like I said, it's things like these that make me never want to work for a startup again and only come in as a founder.


If it had an effect, it would be apparent after 11 years.


The thing to really appreciate is you are one of the ones that got lucky. The majority would not be able to recoup the money they would have made by not working for a start-up.

Essentially a start-up is a school, don't join if you don't intend to learn a lot while getting paid a little so that if one day you want to do a start-up of your own you will at least be a little bit prepared.


THIS.

Its all about the founders. The VCs don't care, the acquirer doesn't care and largely, the industry doesn't care. I have been at 3 startups and they all feel more like "come change my world" instead of "come change the world".

Equity is so lop-sided that its almost laughable.

I earlier thought that a successful startup exit actually carries weight on one's resume but that's only on the founder's resume.

Nobody cares in SV if you were an EE at a non-unicorn startup with a reasonable exit. After an exit happens, founders still get to keep their badge of honor and propel their careers, not the EEs.


I would recommend making a distinction between a startup that manages to get acquired as a small team for building a good product (Instagram is an extreme example... but I know of a few startups that few here have ever heard of where the outcome for employees was substantially better over the same period than if they had worked for Google or Facebook).

There is perhaps a warranted disdain for the behavior of founders on this thread, but I would also like to point out there are founders that genuinely care about the people on their team and would either ensure the equity was sufficient upfront or--if the total size and scale of the startup was miscalculated initially such as assuming the startup needed 100 employees when it really only needed 10--ensuring they receive ample compensation from the acquirer or not taking the deal. These types of founders do exist too, and I think there is an onus on an employee to figure out what kind of boss they have signed up to work for. If I had a few interactions with Steve Jobs, for example, I'm 100% sure I would have quit.


What's an "early employee" for you? (That is, who gets "a lot more equity?")

I ask because I've noticed with some high-dollar acquisitions a lot of times "engineer #50" makes his/her "F-You Money" on the acquisition, but having been "engineer #2" and "#4" and even "#1" (sadly, no big exits) I am skeptical that #50 took on much more risk or contributed more than, say, #200.


Pre-series A. Once Series A comes into play, you can get paid "market" - which is to say, the normal rate outside of FAANG.


"Market" is weird to measure, because you're not really asking what market rate is, you're asking what your baseline is. If you can get a FANG job, the number you care about is effectively the average of what FANG would pay. If you can't, then it's effectively average rate outside of FANG.


AND, arguably, "market rate" in SV is below market rate elsewhere, especially when you factor in cost of living.


So anyone who is good enough to work for a big company you have no interest in?


#2-#9 (roughly) are taking on more financial risk (this corresponds to the startup's market risk).

#50 is probably being hired for very specific skills and experience (to mitigate technical risk) that increases their opportunity cost considerably, and you aren't going to get an engineer with a track record of scaling operations like yours unless they get a decent salary and a shot at a significant upside.

For certain skillsets and track records, when a startup is having severe growing pains, it becomes a sellers' market.


The trick to this is find a company with large upside potential that is either about to IPO or has just recently IPO'd.

The list is small, but there are some obvious choices, even now.

Tangentially, I _really_ lucked out. I had other options that were lead engineer, or engineer #2-4, but this was unequivocally the best choice. The work is more interesting here too.


I had an extremely similar experience, but I do have a beef with the founders for not compensating me fairly with respect to the work I did in helping them create something they could eventually sell to a large company. [Before anybody throws shade, the site was developed by a Flash dev, a Java team for webdev, and me building the backend and running things as a solo sysadmin.]

None of these people are your friends, get as much as you can.


That doesn't have to be true, there are many decent and honorable people that decide to start companies. But I do certainly think you need to walk away as soon as you feel a founder doesn't recognize or value you or your contributions


My experience does have to be true, but sure, not everybody has to be like this. They often are, though.


I agree. There is a culture that founders are special but everyone else is replaceable which makes it self-fulfilling. If a founder leaves, it's bad and VCs won't invest in the startup - However, if a top engineer leaves, no big deal, they're only an engineer...

For me personally, I have a really bad perception of incubators, venture capitalists and big tech corporations. It's all a zero sum game to increase concentration of wealth in the hands of the few but there is little meritocracy behind it.

In a high traction startup, founders are often the dumbest people in the company but they get treated like they're genius visionaries. I've even heard really smart colleagues/engineers say stuff like "A good CEO needs to be enthusiastic and shouldn't be too smart" - For me this sentence means that we've accepted that the system is not a meritocracy but we've found a way to rationalize it.


Working at a startup and I feel you a 100%. Won’t name the startup but it seems we’re doing better after CEO-founder left.


Thank you for your comment. I am a founder currently deciding how much equity to give to our beloved first engineer. Any tips are welcome!


A baseline would be making up for the employee's salary reduction with equity. If you're taking VC money then you have some dollar value per share to work from, otherwise base it on 3-5x annual revenue linearly projected from historical monthly revenue.

Formula: (Fair total dollar compensation - agreed salary) / (dollars / share) * 4 yr vesting

A sliding scale for salary : equity is built in and you can compensate based on hire desirability or local market conditions by weighting dollars per share appropriately. This system is fair as long as both the employer and employee agree upon the share value (some information asymmetry there benefiting employers that decent companies will try to correct for).

Saying this as startup first engineer ;)


PGs comments on equity resonate with me, and actually align with what I would have wanted. One of the replies to my original comment actually has the article.


I think the amounts should flow from the right attitude: that they are joining the team to help it succeed, rather than they are being hired to perform a task.


Not everybody that is an early employee adds to the company value! Some people are not so bad they get fired but they are living off of other people's input. Before you start giving away more equity to early employees, you need to seriously think about how you are going to make the employee earn that e.g. if they leave before 3 years, they lose it, if they fail appraisals, they lose it etc. Many companies go bad because they do give away too much equity then there's not enough left for subsequent raises.


Many companies go bad because they do give away too much equity then there's not enough left for subsequent raises

Citation please, because this sounds outlandish.


Selling equity to employees for their time is exactly like selling equity to investors for their money. Founders can only dilute their stake to a certain point before they’ll own too little to make fundraising worthwhile.

For a rough example, if the company gives 20% to early employees and 20% to investors, and want to raise $1MM A round at a $5MM valuation, they’d dilute down to 48% already. If they’d given 10% to early employees, they’d dilute down to 56%. That majority control could be significant. You can extrapolate lower numbers if a company needs significant cash and has to raise at a low valuation.

Hopefully the mechanics make sense and yes, there are companies that give too much away on paper and hurt the value of the equity long term because they didn’t have room to raise money or grant shares without giving up personal stakes.


100% correct and I say that as a startup founder that thinks SV startups ripoff their early employees.


As the startup gets traction and more money from VCs, wouldn't it be wise to give raises in cash to early employees?


Most companies don't give 50% raises when you finally raise money (which is to say, most companies won't simply bring you up to market if you came in super early).


No, but if you came in super early, wouldn’t you have (negotiated at the start) more equity anyways? A super early employee with decent equity ought to be treated as a late stage founder - so if the founders don’t take 50% raises, neither should the super early employee with decent equity. It would of course be silly for someone super early to not negotiate significantly more equity than the usual couple of basis points (0.0x % of the company)


> If the founders don’t take 50% raises, neither should the super early employee with decent equity.

You're missing the point of my original post. If a founder owns x100 the equity, why should an early employee be bound to the same salary restrictions?

If anything, since I have 1/100th the equity, that means I should be able to get a multiple of some raise when series A comes through.

Remember, equity is a lottery ticket (especially for an employee). If you're a founder, even if your startup fails, you can get a job as a highly-paid EIR or your founder reputation will allow you to join some other startup in a high level role (VP, Director, etc). This does not apply for engineer/employee #1.


If founder has x100 the equity of employee #1, employee #1 screwed up.


Welcome to this entire conversation on why early employee compensation isn't fair.


My point is Employee #1 should’ve asked for more. 1% isn’t enough. Maybe 5 or 10% is.


Yes, let's blame the person that structurally has less power in the dynamic for having that power imbalance used against them.

Of course you can try to negotiate for more. Enough people want to work at a startup however that if you ask too much, you'll get passed on, and they'll just hire the next candidate who doesn't act so entitled to a meaningful piece of the founders' pie. It's exactly the same phenomenon that lets the big game studios chew up and spit out engineers: there's always someone else willing to take the job for less, or even just put up with the status quo.

That's a massive part of the problem, and telling people to negotiate better doesn't address it — or even acknowledge it.


Well, but then don't look for generic cookie cutter startups that everyone wants to work at :) Go after the startup where you as employee #1 are uniquely positioned to negotiate for. If you're employee #1 and you just graduated from college and this is your first job, and you have no special abilities beyond every other CS graduate across the United States, then yeah, you really don't have much negotiating power... nor do you at any other large company like Google either.


Let them take the worse candidate then. The startup is probably going to fail anyway. Jobs are easier to find than good engineers, especially your first few engineers. That requires taking a leap.


I’m not too sure why you’re being downvoted, but it is probably because you phrased your statement a bit awkwardly.

But you’re right that (if there is only a very small number of co-founders) employee #1 should never be accepting 1/100 the total equity the founders have. Employee #1 screwed up in negotiating at least half way decent deal for themselves.


I was a bit blunt.

However, it is up to potential employees to refuse offers that are not in their best interest.


They aren't treated as founders of any sort. They get paltry equity and then don't get raises.


They do get raises. They just have to be persistent. Most engineers don't speak up and are bad negotiators.


And most of the few that do happen to be arrogant entitled pricks. People on this thread who're saying that the founders should try and be fairer towards engineers might actually have a point, although until recently I’d not have agreed with that sentiment myself, and might in fact have argued against it.


TLDR: 30 years experience, I learned: don’t go work for a SV style startup. Be a founder, even if you have no experience. Don’t take VC money for more than %10 of your equity in total. Better off, right out of school, founding a company and failing than working for a startup, especially if they take VC.

It’s lopsided against the founders too. They might walk away with big checks but the risk is too high.

This is the problem with the SV model. VCs take way too much off the table, founders and employees are not adequately compensated.

This is partly YCs fault because they basically groom startups and usher them into the maw of VCs while glorifying the exploitative VC model. But that model makes YC partners rich st startups expense.

Founders and employees in the SV model sell themselves way short. This is also why so many startups are BS non-innovative companies— they are chasing funding rather than the future.

Better model: - slicing pie with no bonus for money contributions- this rewards people fairly. - crowd funding, consultancy funding, boot strapping, angel money with no liquidation preferences, and no VC termsheet BS.

Having founded and worked for startups for 30 years, I won’t ever take a meeting with a VC again. I have not met any good ones (and people who say theirs is great are generally just kissing ass to keep money flowing.)

Worse- the number one cause of failures of startups in my experience is bad strategic decisions forced on them by VCs. The number two cause is conflict among the founders, and the number one cause of that conflict is VCs trying to force a bad decision in the company (and one of the founders realizing it.)


This is partly YCs fault because they basically groom startups and usher them into the maw of VCs while glorifying the exploitative VC model

I believe this is a part of culture that VCs are creating. I've been interviewing lately and I've noticed certain personality traits among YC founders that I'll call "Business Sheldon." I saw it a bit 5 years ago when I went to Startup School, but it's pretty pervasive now, so much so that I see it as a red flag. If you've seen the latest season of Silicon Valley, the character that Dan Mintz played touches upon this: https://www.youtube.com/watch?v=fzbwLktN60c


> Be a founder, even if you have no experience.

Easier said than done. Lots of people leave school without the faintest clue what they want to do. Getting a job somewhere gives people training and experience and maybe even credibility before they strike it out on their own.


Me and my previous co-founder founded a startup with both of us having no experience. It was a very bad decision for the company, but extremely valuable for our personal growth. It also allowed us to skip the biggest parts of the usual career ladder.

It's certainly not the best route for everyone, but definitely one worth considering.


It's great for you. It's pretty bad for any employees who have to pay for your mistakes as you get your personal growth on and skip career ladders.

I think being a founder is a great option right out of school--if you are working for yourself, responsible for your own mistakes, and not actively harming anyone else in your quest for personal achievement.


FWIW I've worked with "experienced" founders who also had no idea what they were doing (in many but not all ways). There's never a guarantee that you won't be working for people who will make you deal with their mistakes.


Heck, there is no guarantee that you won't be working for someone like that in any type of company, regardless of "maturity" or sector.

Bad managers (and most bad management - from death marches to protoduction - can be boiled down to "makes the people who report to them pay for the manager's mistakes") exist even in supposedly mature companies with good corporate cultures.


Con of startups, these are the people you might end up working for.

What's good for your personal growth was other people trying to make a living at a company being run by people who don't know what they are doing. Maybe it's fine, but that level of uncertainty is definitely a con.


I very much agree with you (as someone who has since worked for such people too).

Luckily we mostly had temporary interns as employees, and I can confidently say that they had a good experience, as we are still in touch.

The biggest problems of the inexperience were that we had to ramp up our skills on the job (for me programming), including the mistakes you make there, which killed a lot of the runway, and the lack of business knowledge which ultimately lead to us running out of money.


> Easier said than done. Lots of people leave school without the faintest clue what they want to do.

The rest of the startup game - building a product, pivoting correctly, building a team, overcoming oowerful rivals - is such a huge challenge, that gaining entry level experience before finishing school is perhaps the most straightforward piece of the puzzle.


  Anyone can start a business, and anyone should.  The things you mentioned - "pivoting" "overcoming powerful rivals" - goodness.  How about simply starting a business that earns more money then it spends. Do that and you will learn most any lesson you need to know about being a "founder."


The economics of internet-scale software businesses make this harder than opening a hardware store and selling nails and rope for more than they cost from the wholesaler. It often does require lots of risk capital. If you don't have it, you need a rich partner who does. If you don't know any rich people that want to go into business with you, you need to employ people who provide this service at a price -- and often that price is that you, in effect, become their employee, rather than their partner. This is the silicon valley VC model.

It's possible to build "boutique" scale internet software businesses, but it's harder than ever, and you still need to be well-off enough to "risk" some time that you would otherwise be working on definitely-getting-a-paycheck type work.

In short "start a profitable business instead working for one" and "start a business that's profitable right away instead of taking VC funding" are both rather useless pieces of advice for somebody who doesn't have the means or background to do either.

There are of course more choices about what to do with your life. You should explore those too. Maybe you'd be happier as an auto mechanic or a nurse. That kind of work is available almost anywhere in the country so you won't have the "three body problem" of having to live away from your or your spouse's family, or both.


I disagree with your entire post. It has never been easier to start q business online or otherwise. It has never been easier to start a business with virtually no investment or financial stake. It has never been easier to learn how to start a business in most any field and never been easier to find customers.

I'm not sure what you are defining as risk or difficulty. I can list a dozen day-one-profitable businesses right here that a person could start before tomorrow morning for less than $100 investment.


You could start them with little investment, but your time is also worth (a lot of) money. That's not coming from anywhere if you work for any startup, including your own. You might make that money back later, you might not. In the end that is part of your investment and it's a gamble. If you do not have the financial cushion required to sustain you for the amount of months it needs to become profitable for you, you cannot do it.


Baloney. Those are excuses. If you have no money the opportunity to make some/plenty is abundant and all around you. Everything else is excuses and procrastination. You dont need other people's money. You need to sell something.


That would be great! What are they?


Buy a WHMCS license and a VPS. Go to YouTube to learn how to use it. Set up a simple brochure site. Join a $0 start fee affiliate program. You are now in the hosting business.

Too tough?

Spend $100 on a Beaver Builder license. YouTube to learn. You are now in the small business website building service.

Too tough?

Call a business and tell them you can help their local SEO for a price greater than $20/month. Once the check clears, get them an Advice local account. Pocket the difference.

Too tough?

Call a local business and tell them (true) that 92% of all visitors will seek out their business in a second source other than their home page. For $100 you will setup their Facebook page. For another 100 you will train them to post to it and reply to reviews.

Too tough?

Call a local company and tell them you can handle their social media strategy. If they have T, FB, LI, and IG then great. If not then charge 100 to build them. Signup for Hootsuite. Post to their accounts for the entire week on a Monday morning.

Too tough?

Call a small business and tell them that the number one way to generate repeat business is through a regular email newsletter to previous customers. Sell for $250/month. Signup for Outbound Engine agency program. Profit.

Too tough? Call a business and tell them that chat tech on the front of their site can increase lead flow by as much as 11x. Signup for Apex Chat account, charge $20 per less. (Apex charges you $10)

On and on. It's never been harder to start Facebook or Amazon or Google because we already have Facebook and Amazon and google. But divest yourself from needing approval and applause and you start to see one big truth: its really really easy to make a lot of money online.


> It's possible to build "boutique" scale internet software businesses, but it's harder than ever,

Can you expand a bit on the "harder than ever" point? I've observed a couple of phase changes since the 90s, but I don't think I've seen that particular needle move very much in the past ten years.


> Don’t take VC money for more than %10 of your equity in total.

Good luck man.


Build things for which there's actual demand and real hard problems are being solved and they won't need it.

Build Uber for X and rightly it'll fail without VC money.


Agreed. Yesterday, I replied back with similar sentiments. I was immediately down voted. I second that theory of yours where all the risk seems rational when you are one of the founders.


Seconded.


Why wouldn't you have beef with the founders? Their decisions left them rich and you with nothing in exchange for years of your life lived with excessive risk and a lower standard of living.


This is such a great area to work on.

The equity side is pretty rough. Founders are very sensitive about disclosing important information about company performance. They are sensitive about disclosing the cap table. Some will share info with investors that they don't share with employees. And they are sometimes trying to pitch optimistically and leaving out items that don't fit the narrative. So you end up with a very vague sense of where the company actually is when you are interviewing. A much better stance is "awesome opportunity, and these are our problems, come help us fix them". Standardization on more disclosure would push hiring toward a higher local maximum.

Something like Geoff's https://blog.ycombinator.com/transparency-in-startup-investi... for hiring companies. For workatastartup.com, you could say "if we make an offer, we'll show you this critical info". It's probably a bit much to expect companies to disclose this in public job postings.

Sam's thoughts on equity at https://blog.samaltman.com/employee-equity are spot on. Especially the 10 year exercise period.

Scenario one. You leave a company after 5 years. You think they will be successful but best case is 5 years before liquidity and 10 years is very possible. It will take most of your savings to buy the stock and pay taxes. You helped with the $20 million to $800 million valuation growth. Now you have no savings, and the money is still at risk because $800 million dollar startups die all the time. You get to bet all your savings that a die rolls 1-2 for 10 times your savings. Roll 3-6 and you lose it all. The expected value is great, but it's a pretty hard bet to take.

Scenario two. Your coworkers realize this and hang on at the company long after they want to move on. Now 20% of your team is just showing up and the company culture is dying. Everyone worries about retention, we should worry about over retention too. It's better for the golden handcuffs be "if I stay, I'll vest these options" rather than "I must stay to preserve the options I vested 4 years ago".

These and 10 other bad scenarios like them are definitely on the con side.

And so easily fixed!


Agreed re: transparency. I've had startups refuse to share what even the current valuation was (edit: even when actually presenting an offer!), let alone who has preferences and convertible notes and such. If I'm taking a substantial cut in liquid comp compared to BigCorp, I can't just treat equity as a happy little upside. I need to understand exactly what terms it is subject to.

As for equity amounts - if I have to assume your startup will grow at least 10X, without any further dilution, in order to break even on comp with a public corp, it's not a very compelling offer.


I've interviewed at places that wouldn't even disclose how long their runway was. I've even gone to work at one company that claimed a six-month runway and then ran out of money after six weeks.


The 10-year exercise is such a no-brainer. Just ask yourself, startup founders & investors: when you issue stock options to your employees, do you want them to exercise them or not?

If not, then what you're really doing is offering something you hope doesn't cost you anything and is therefore worth nothing. Good luck to you.

If so, then do everything you can to help them do it. Holding an employee hostage because in order to leave they have to write a check for a significant part of their life savings won't be productive. They're taking up a salary from someone who will actually be engaged and motivated.

In my experience, this definitely plays into individuals' job offer decisionmaking. At least the most sophisticated ones, which are usually the ones you're most interested in recruiting.


I don't agree with that... I would want all the early employees to be rewarded for taking a chance on that. I would want to go the other direction and give restricted stock (which can be early exercised) when the valuation is low and with less than 10 year vesting (such as the standard 4-year vesting with 1-year cliff), it's in the employees' best interests and costs the company nothing. Of course, down the road after later rounds the common stock valuation becomes prohibitively expensive and then it probably makes sense for stock options. But at least back in my day it seemed the common thing was to give restricted stock to founders and stock options to employees. Not sure if that's still a common thing or not?


Those are two great concrete suggestions. I agree with both of them - a standard of transparency and 10 year exercise periods.


> $800 million dollar startups die all the time

is this the case? i actually don't know that it is.


Oh yes.

Jawbone $2.7 billion valuation -> 0

Beepi $560 million -> 0

Better Place $2.5 billion -> 0

Quixey $600 million -> 0

YikYak $400 million -> $3 million

Fab.com $1.5 billion -> $15 million

Rdio $500 million -> $75 million

Here's 133 of them, most pretty big: https://www.cbinsights.com/research/biggest-startup-failures...

Also got some details from: http://www.businessinsider.com/startups-that-raised-148-bill...


great list, and i even knew someone who worked at Fab. thanks.


(Sample size of one)

I worked at a unicorn startup five years ago in the bay which no longer exists. Anyone who bought the options -- and the company was very cagey on providing cap table info -- was left with nothing.


Worthless, or nearly worthless, options are very, very common. The last options I exercised and did get paid out... but in the end, I didn't even make back enough to make up for the pay cut I took. Financially, I would've been better off taking a different job. At least I "had fun' and "got something" though.


Why the quotes? Did you not have any fun?


The quotes are there because it's basically a cliche. Every startup is "fun", right? Okay, I did actually have fun... at least for the first year or so.


This...

Even if the company is sold at a high value chances are the payout will not be worth the risk. Unless your shares come with a board seat never buy the options in a private company because the shares are worth literally zero unless a secondary market exists.


> in the bay which no longer exists

:)


That happens sometimes -- lava filled a bay in Hawaii just last week :P


No matter how far along the funnel you go a significant portion just fail to raise further funds: https://www.cbinsights.com/research/venture-capital-funnel-2...


I echo the comp aspect. I pretty much had a best case non-unicorn startup exit; wonderful benefits pre-acquisition, actual unlimited PTO, and normal ~40hr/workweek, acquired almost immediately after receiving my shares, golden handcuffs after. My total comp was more or less equivalent to my peers doing the big 4 grind over the same time period. They had zero risk and I had to win the start up lotto.

But if I had to do it all over again, I still might do the startup route. It's just more fun. There's more to life than money.


I think a huge part of whether it is more fun or not is about where you are in life. Startup life was great for me when I was young and single, and enjoyed the startup lifestyle of excitement and risk. Now that I am older and have a wife and kid, I really like the stability, predictability, and salary of a job with a bigger company.


Absolutely. Also, startups are intense, which goes both ways.

Intense can be great if you're looking for that, and the startup is doing well.

Intense can be terrible if the startup isn't doing well and/or the atmosphere has gone acrid. It is now intensely bad.

It's like a polite disagreement with a casual acquaintance versus bitter fight with a close friend.

When startups derail, they really do go far off the rails.


Also who you are in life.

When I was younger I didn't have chances. It's incredibly privileged to be able to take a position somewhere you might not have a job in 2 months because you have enough stashed away or enough family wealth that if you fail, you can pick yourself back up easily.


Yeah, I wasn't trying to imply it is just about stage of your life in terms of age and family status, but more just your stage of your life in terms of financial needs and tolerance for risk. For some people that need for lower risk and financial stability comes when they are older, and for some people they start out needing that financial stability at a young age.


Agreed. It definitely depends on your tolerance to risk. Not everyone wants to be part of frat party that takes up half your days and weekends that could potentially disappear tomorrow without notice.


>But if I had to do it all over again, I still might do the startup route. It's just more fun. There's more to life than money.

Easy to say because you have gotten the money. :-D


Not really. I've applied for a startup, got accepted, the next day received a one in a lifetime opportunity to do something I've been dreaming of (security research at a huge and famous company). Went to do the dream job only to quit after 6 weeks and return to the startup. Best decision ever. I didn't win the lottery ticket, but I am also not coming back to a regular job. Yes, you usually get paid less (or much less), yes my peers climb the corporate ladder, have better cars and houses, but I have a more rewarding job, I get to work remotely and travel often, and I can work from home whenever I want. I also hate the hierarchy that eventually comes as the company grows.


Yeah and it’s one hundred percent true. If the story wasn’t “I won the lottery” but instead was “I missed out big time” that may change things significantly


I'm a case where I don't really expect to ever see the equity pay out, but I might still have gone the startup route for the fun and the learning. But if I were to go back in time and advise myself, I would have taken more cash and less equity. At the time, I took more equity and less cash.

As someone just starting out, the hidden cost of exercising and the tax bill that follows was staggering. It would have eaten up most of my fledgeling liquidity and dug into my rainy day fund.

My advice to my former self would be to take more cash over equity and invest that cash in the public markets. Diversify your investments to reduce the risk of the giant startup bet you're about to make. Compounding is a hell of a thing, even over four years, and people tend to forget to account for investment returns when they value their cash.


Why have I been told to begin your career at a startup, before you work at a big corp in order to "level up" your work environment? I took that advice and it has just left me starving for better compensation and, and am pretty lacking skills-wise. And now I'm still unfit to get an offer at the big tech corps, or even a chance for an interview.


There's only a narrow window in your life where many of the cons of working for a startup don't ruin you. That window happens to overlap with the beginning of your career. If you have the skill to make it into a big corp at the beginning of your career, you can do it again later in your career -- they'll still be there later.

I'm of the opinion that the generalist skill set you typically get from a startup is far more valuable than the specialist (and typically exclusive to the corp) skill set you get from the corp, and I'll even argue that the entry level skill set of the corp is pretty damn useless, but that's only from anecdotal evidence.

What doesn't kill you makes you stronger, startups dance at the edge of survival.


I agree -- to an extent.

Some of the skills learned in big mature organisations tend to be very narrow and specific to the tools that the big organisation uses.

Some ... but not all.

The man-management and general engineering skills are still pretty transferable.


How long did it take you to receive your shares, if you don't mind me asking?


Less than a year. More shares than non-essential employees, but far far far less shares than founders/executives.


Having not worked in the Valley or a startup, I can say the biggest con to me is a lack of stability. You can get a job at BigCo or even MediumSizedButBeenAroundTwoDecadesCo and be reasonably sure you'll still have a job... as long as you want to work there. But with a startup, either they run out of money and you lose your job, they pivot and don't need you and you lose your job, or they get acquired and you very likely lose your job (or it becomes a vastly different job you didn't want). When taken in combination with the insane cost of living in the Bay Area, it seems crazy that someone would even consider this.

Here's a crazy idea from the IT contracting industry: Maybe YC and the like should hire employees and contract them out to startups. I work for a company which contracts me out to another: Even if my position is eliminated with the client, I don't lose my job, I just get reassigned. Perhaps as part of this, YC (or other funding group) gets the investment options an employee would otherwise have had, for example.

- For the startup, they'd be getting employees who weren't worried if they'd have a paycheck in the next six months, and they'd know their VC folks are confident in that employee's ability. For all the other risks startups take, hiring a good developer/designer/business manager would be less of one.

- For the employees, they'd have a stable income they could base real estate and financial decisions on.

- For the fund, they'd have possibly gained more investment, and ideally, having known employees that they've seen the work of before should add confidence to the success of a given business they've funded.

Disclaimer: I have literally no experience or expertise in claiming this would work out financially or otherwise for the startup industry.


For what it is worth, I tried this business model, IE: consulting focused on startups. Problem was, startups by and large are grossly undercapitalized, have huge business swings, and often you are dealing with first-time entrepreneurs who have no idea what things cost or how long they will take, but also aren't willing to be educated (because they are scared and there is a lot of risk). Point being - it's hard to sell services successfully to that kind of customer.

I should point out too that many investors want to see a team of employees, because they are investing in the strength of the personnel. So they didn't like this idea of a startup built using contract / outside talents.


FWIW, I had basically this exact experience and met exactly these difficulties. It can be done, but the market is just a lot smaller than "all startups".


I'm not saying this is a bad idea, but, I'll try to argue the other side for a moment:

BEGIN THEORY

Startups hire in-house devs because, basically, management does not know exactly:

A. what to build

B. what's possible to build

C. how the real world will react to the initial product/service offering and how the company will need to adjust

So, they bring devs in close, as high availability, high dedication employees, people who are in the center of the decision making. These intimately involved, trustworthy, motivated devs will then be more likely to come up with features and products that workaround management's deficits. And the company will benefit from that quickly and the company will own those features and products.

END THEORY

But, if this were contracted out to an outside stable of roaming rockstar developers, all highly talented but still less motivated and more in need of detailed direction from management -- how much insanely great startup flash-magic would really happen?


Is "possible homelessness" a required motivation to ensure you have motivated employees? Note that I don't suggest your entire company would be employed by YC, but that you might fill some roles with people who YC has worked with before and considers of high quality. I would argue in terms of trustworthiness, it is likely "someone YC provides" is more trustworthy than "someone you found on the street". Presumably YC would only retain such employees they found were good at getting fully involved in the companies they put them with, so you'd get the same.

Also, consider that not only could someone be contracted to you in a high availability/all hours arrangement, but that this would potentially also allow YC companies to benefit from roles they couldn't afford to full-time.


This is a very good idea and is something that venture builders and value add accelerators do.

For example (here in the UK) Founders Factory and Forward Partners both maintain large stables of designers, developers and other specialist executors that they assign to their portfolio companies.


This is an interesting idea. We've talked about ways that we could help create more job stability for people joining a YC company.


When I was a consultant, I liked two things about my company. I was paid by the hour, which kept my company honest.

I was paid when I was "on the beach"(bench), but I was expected to train and get tech certifications


Interestingly, I strongly prefer not being paid by the hour.

I find time-clocking incredibly irritating, as I may be inspired to a solution or want to fix something outside of hours, which is pretty common for me. And similarly, I don't want to feel bad about if I am doing something wrong or not the most efficiently, but still charging full price for that time. Possibly the most irritating thing for me in times I was on hourly was arriving at work a few minutes too early to clock in and having to twiddle my thumbs, or having to determine whether or not something I wanted to remote in and do met the official terms for being paid in after hours time.

My personal feeling leans towards paying for "a job well done", and leaving it on the idea that if you're doing your job well, I'd like to believe nobody will question how you spent the hours you were doing it.

Being paid while on the bench makes a lot of sense if they feel you're valuable enough to retain, and time to actually spend training is pretty nice when you can fit it in, and obviously works to their benefit.


I didn't have to clock in I just needed to enter my billable hours.


The occasional lack of efficiency/productivity should be reflected in your billable rate, that is, the rate should reflect your level of (relevant) skill, any specialized knowledge, and mean productivity, not max.

Then there is no problem with just billing the spent hours without any fudging one way or the other.


"And similarly, I don't want to feel bad about if I am doing something wrong or not the most efficiently, but still charging full price for that time."

- A lot of people at the company would feel guilty and put in free hours to the client. (They would usually also get rewarded with excellent customer feedback.)


Might want to rephrase the 2nd bit, if you're trying to conceal which BigConsultingCo you worked for.


YC would be competitive by providing health care and maybe some shares in YC if work at some YC companies. Seems doable.


Super interesting idea. One of the cons could be that having your employees not personally invested in the outcome of your venture could make them less likely to be "fully committed" (i.e. long hours, going above and beyond). You might be worried about higher levels of apathy -- "if this doesn't work I still have a job".

If the business works, I'm thinking the transition from the fund swat team to "real" employees might be difficult as well, probably at a time when you need to be firing on all cylinders.


My thought on the "if the business works" case is that such employees should have a clean path to either transition to the company they helped make a success, or get reassigned by YC. Either one is a win for YC in this scenario: An employee which helped a startup succeed is a hot commodity they'd love to reuse, but they also own a portion of the successful startup, so having it continue to succeed is also a big win.

The idea here would not be for YC to have a constantly growing outsourcing team, but to ensure they didn't lose the good employees because a startup failed. In a given failed startup, there are likely some rockstar employees that definitely weren't why it failed, and it's in YC's best interest, presumably, to hang onto those great employees and get them placed with other investments of theirs, should the opportunity arise.


> "fully committed" (i.e. long hours, going above and beyond).

Regular comp does that if the company can afford it. Startup equity is there so companies that can't, can offer early hires the "maybe money". Pay 200k and you'll get fully committed employees.


This is exactly how overseas outsourcing works. The vast majority of the foreign people I work with are under arrangements just like you describe.

This is also similar to how a lot of small software development firms work; they develop web sites and mobile apps for companies on contract.


There were some US companies that did this as well before the dot bomb. One of the selling points would be you get "bench time," which meant paid in-between assignments. I think large companies that make a lot with consulting fees use this model as well, but I'm not sure which ones.


I know of at least one successful entrepreneur/investor who does exactly this with his incubator: incubator/umbrella company hires FT employees who get contracted to the startups and receive stock in the startups proportional to the time spent on each.


I really like this idea, and I think something similar is done with high-level managers in the private equity world. You build your career across the portfolio of companies, and your interests are aligned to the portfolio itself, not the specific company.

That obviously creates a risk of perverse incentives, but from the PE folks' perspective it seems to work.

IIRC that's also how Berkshire Hathaway does it: builds managers for Berkshire Hathaway companies, and whether they're managing at GEICO[0] or Fruit of the Loom[1] depends on where they're needed and not whom they work for.

I don't know anything about how technical employees benefit (or not) from that setup but I suspect there is some amount of informal sharing of tech talent across portfolios.

It'd be really great to see something like that for tech people. Maybe YC can start and everyone else will follow. :-)

[0]: https://www.geico.com/about/corporate/at-a-glance/

[1]: https://en.wikipedia.org/wiki/Fruit_of_the_Loom


Currently it's not hard for a software developer to find a job, especially those that YC startups would want to hire.

So I don't think stability is much of an issue in the current economy, developers are not afraid to lose their job because they know they'll have dozen of opportunities just by activating their network.


Even with that being the case finding a new job is a hassle and means you have an interruption in pay and insurance. Gives me a lot of incentive to just work at BigCo and not worry about it until -I- want to worry about it.


These positions do exist. The VC maintains an engineering team that gets lent out to the businesses they're invested in.


This is great, because it essentially puts the employee in the same position as a VC with amortized risk. We know that startups succeed and fail according to some known distribution, but the odds that this particular venture will succeed or fail are largely unknowable.


Yes, this works, and there are tons of companies that do it, referred to as "bodyshoppers".


Competing with Wipro and other body shops? Good luck with that.


Presumably the difference between this and a "body shop" is that YC, having significant investment in the success of a business, would be less interested in "supplying bodies" than ensuring the business' success.

Whereas a outsourcing company would benefit by providing as many staff members as possible, if YC or the like were to do it, they'd likely want to zero out the "profit" on supplying employees: To keep it affordable for a startup, and to not break the incentive for YC: To push companies to success via whatever resources they can offer.

Particularly if YC's "cut" was solely in the form of share of the business, they'd have no benefit to over-pushing poor quality labor on their own companies: It'd just doom them.


In terms of how to move the needle for early employees, at my prior (and first) startup, I watched us go from 15-20 employees to >300.

One of the interesting things that struck me was how much advisement/mentor/training/etc investment went into the founders/C-team, and how little went into all the rest of us.

(Totally reasonable that this was a situational thing, but I don't think it is).

There's fame and reputation that comes from being a founder, and there's not much of that that goes into the EEs. For example, at my current startup, one of my founders wanted to sub me in for them at a panel they had a conflict with, but the guy running the panel "didn't want individual contributors".

Being a founder is celebrated; being an EE isn't: https://strongfemaleprotagonist.com/issue-5/page-63-2/ https://strongfemaleprotagonist.com/issue-5/page-63-3/

Note: I'm not talking about how employment is celebrated within any given startup - that's important, but it's going to be situational - I'm talking about the community as a whole celebrates the EEs.


> the guy running the panel "didn't want individual contributors".

That may be a reasonable requirement, depending on the panel topic.

But note: Plenty of EEs aren't individual contributors! An EE can be a "team lead" for example. Basically if you have any responsibility for directing or managing other people, you are already not an IC.


> That may be a reasonable requirement, depending on the panel topic.

Hmm. I really don't see how. That's a bit like saying that because you work in Java, you can't talk about Ruby, or AWS, or Scrum, or skydiving. This really seems like the sort of thing that you "opt in" rather than "opt out" - you're qualified to talk on a panel if you are X, rather than being disqualified if you are Y.

Can you think of any topics where that WOULD be a reasonable requirement? I cannot, but I'm biased.


Also, X and Y in this case are (mostly) mutually exclusive. We just don't have a common catchall term for technical non-ICs to be able to express a positive requirement without also including non-technical managers.


I can't identify the case you're talking about.

Seems like the problem is trying to have a category (as in folder, as in old school email) rather than a label.

"Technically capable", "contributor", and "technical contributor" all sound like ways to positively express "not looking for non-technical managers".

The problem comes back around to "do not restrict people to the categories you assign to them".

(Which is also a way to phrase many social justice issues and IMO where "being a cog in a machine" comes from).


Post-mortems, one-on-ones, dealing with toxic team members, adopting "Continuous X" practices, "Your team just added it's first woman engineer. Now what?", etc.


All the post-mortems I do are as an IC; I (occasionally) lead my own one-on-ones either with other ICs as a fellow IC and/or manager; I've seen "continuous X" practices pushed by both ICs and managers (ICs vastly moreso, actually); and management does not qualify you (and IC does not disqualify you) from being able to teach people how to treat fellow humans like fellow humans.

In short, I completely disagree both by opinion and experience that any of those topics have "not being an IC" as a reasonable requirement.


> One of the interesting things that struck me was how much advisement/mentor/training/etc investment went into the founders/C-team

Can you give a sense of how much that might be?


Offsites, speaking gigs, trainings - but really, time with people (in this case, the investors/advisors) that can really coach (or straight role-model) you into being that much more amazing. I can't quantify thing-over-time both because this was an anecdotal impression, and because it was a decently long time ago.

You invest money in successful ventures, and they snowball; people invest themselves in other successful people, and you also snowball.

PS - Also just getting invited to meet other interesting people. It's suprising-not-suprising how much of an effect that has on yourself.


As a two time early employee starting right out of college, I can think of these points:

Pro: I've seen and learned things I wouldn't have in a big tech company. The rapid growth and constant fight for survival means I've picked up skills my big company peers didn't even have access to, especially leadership skills.

Con: In hindsight, the equity was a joke for the pay cut I took. If I had fully appreciated all of the gotchas of startup stock options, I would not have taken the pay cut relative to what I could have gotten from the big company offers that I had. Chief recommendation there: no 90-day exercise window, and employees should have ongoing access to details like liquidation preferences, revenue, burn rate, etc. I appreciate the need for confidentiality for strategic reasons, but I no longer believe that this need outweighs the principle that employees should know what they're signing up for.

The big issue is that there is not remotely enough institutional/cultural wisdom around what it means to be an early employee, so it feels like startups are often exploiting early employee naivete.


Pro (from my personal perspective, YMMV): You get to work on something that will actually see the light of day. For me, there's nothing worse than being this tiny little cog in the machine that comes into work from 9-5 and produces something so microscopic that you question your importance at all. Working at a startup means you have to pull your weight, wear many hats, and get shit done. This also means you can climb the later and get noticed much easier. It also means you can't slack off and fuck around all day. Most of my friends that work at larger public tech companies — it just feels like they're constantly doing unimportant things, going to conferences just for the sake of it, getting into work late and leaving early. etc. That life, that cushiness is just not for me.

Cons: As others have said, the pay is always going to be lower. The stock options are, in most cases, always going to be worth $0.


Huh, I really had the opposite feeling when I went to work for a big company instead of a startup.

Both startups I worked for never had serious traction and both shut down as failed. We worked so hard to create really cool products, but there just was not the demand for what we made. Cool software with no users.

Now, I work for a huge company. My work gets deployed to tens of thousands of servers, and I know that people use and need what we make (because they pay us a lot of money). I can tell people who I work for and they know who it is, and I can point to things they do in their daily lives that my work touches.

I feel like I have a much bigger real-world impact at my current big company than the startups.


> Both startups I worked for never had serious traction and both shut down as failed

I think this is the big difference. When you're working for a startup that literally can't keep up with demand (such as the one I work for now), it's an entirely different animal.


Right, but in reality more startups are like the ones I worked for than like the one you work for. Most startups fail.

Although, given that both of our stories are just anecdotes, the advice might come down to "Work for a good company that does valuable things that make a difference to people"...


> Most of my friends that work at larger public tech companies — it just feels like they're constantly doing unimportant things, going to conferences just for the sake of it

Working at a BigCorp(tm) right now, this is somewhat of a false statement imo, at least for us. Being in such a standardised place, it is very hard a lot of times to find new inspiration for technologies to adopt and things like conferences or meetups are the perfect opportunity to network and hear about how people make use of new things. Usually, we don't really get much time to explore new technologies as capacity is always planned for our current workloads. That's why I love being able to go to a conference every few months (this year it'll be 4 for me) to be able to bring some things back into my team that might be interesting to us.

We get the time approved for conferences, but not to explore things "while at work".

This obviously differs from company to company but that's my experience at my current one so far.


Yeah, and I didn't mean to slam conferences. I enjoy going to conferences and find the well regarded ones beneficial (especially ones offering workshops and certifications).

My point was more about the token conference goer.

I have an acquaintance that has given the same talk at 13 different conferences over the last 12 months. I don't know how that benefits him or the company. He's also on twitter literally all day. I just don't get it (as I hypocritically type this out on HN).


Are you really saying that you don't get how presenting to multiple conferences benefits the presenter, or the company he works for? Or am I misunderstanding your point?

From my perspective it seems that there's tremendous benefit in becoming known by thousands as an expert in a particular topic and in having the skill to present that material to others.


There’s certainly career value to being a “celebrity programmer” of sorts and it can be a signaling thing for the employer and hiring pipeleine.


> For me, there's nothing worse than being this tiny little cog in the machine that comes into work from 9-5 and produces something so microscopic that you question your importance at all

See, I'm the opposite. I couldn't care less about the importance of my work. I work for one reason and one reason only: to fund my life. I just want to put in my eight hours a day, draw a paycheck, and then go home and have fun.

And I honestly like the idea of being anonymous. I just want to blend into the background and not be noticed, and I couldn't care less about climbing the ladder because my career is the least important thing in my life.

> Most of my friends that work at larger public tech companies — it just feels like they're constantly doing unimportant things, going to conferences just for the sake of it, getting into work late and leaving early.

Honestly, that sounds like paradise to me. I'm pretty satisfied with my current job, but if I wasn't I'd definitely be asking you for the names of some of those companies.


> Most of my friends that work at larger public tech companies — it just feels like they're constantly doing unimportant things

Obviously that is not universally true: All the things that do see the light of day, some small, some big, are done by actual employees of a big corporation. Maybe you will not be working on them all the time, but chances are good that you will at least get the opportunity to have a public, meaningful impact.

Just as an anecdote, when I interned at Google long ago, I got to work on a public feature in Google Maps. It was a great feeling to directly work on something that anyone could potentially use, and see even just a few public reactions.

That experience probably set my path on favoring working at big corporations, because I knew I could do meaningful things there if I position myself correctly, whereas startups seemed much more like a big gamble (which by itself is probably an exaggeration also).

Just yesterday I spoke to someone at another big corporation who proudly proclaimed that people clapped at the mentioning of their own feature, when it was unveiled as part of a bigger announcement. YMMV.


Agreed. I always think of the greek word "arete", which (as I understand it) means roughly achieving excellence and living up to your potential.

I'm currently at a big co (though not really a "tech" one, so can't speak to FAANG) and can relate to many of these. I can def see the attraction in taking less money in order to have a better shot at achieving excellence.


> they're constantly doing unimportant things, going to conferences just for the sake of it, getting into work late and leaving early. etc.

uuuh, do you have any links I can follow to apply for a job like that?



Keep looking, most jobs at BigCorp are designed to make sure everyone is easily replaceable, which means positions can't have too much responsibility, else the person couldn't be easily replaced. It's like the very definition of ITIL.


Here's what I consider the 'sweet spot':

A small company, say 20-50 people or thereabouts, that has a profitable niche and does not require much in the way of investments. Here's why:

* Small is more fun for me - I like knowing everyone I work with, and the chance to see what other people are working on, and maybe move around some in what I'm doing, rather than 'the same thing day in and day out at BigCo'. Your work also feels more valuable and meaningful. Startups are a lot of fun that way, however...

* Investments and not living off what you sell are inherently unstable and stressful. That's ok to take a chance on when you're younger, but as someone with 20 years of experience in the industry, a family, hobbies, an interest in local politics and so on, it's not so much fun any more.

* I have a bias for cash, not equity. It's fine to roll the dice a bit on that when you're younger, and even now for the right thing... you never know, but ceteris paribus, I'd rather just have the money.

Of course actually finding a place like that is easier said than done. You need to avoid things like winner take all markets.


> I have a bias for cash, not equity.

I'm like you. I'd rather take cash and dump it into my 401k or an index fund for retirement.


Any startup worth its salt will pay you a high enough base salary to max your 401k and still have a ton leftover for after tax investments.


> You need to avoid things like winner take all markets.

Another thing that might work is looking at industries with a lot of software needs that are not traditionally considered "tech companies."

A long time ago I worked in Biotech. There's tons of money there, and an awful lot of software made both in-house and by consultancies. (And I bet it's a hotbed of machine learning right now.)

I'm sure there are lots of other industries where their core business makes a lot of money but there's no way for startups to just "disrupt" them out of existence; however if you can move the needle 0.01% that's more than enough to support a very profitable smallish company.


> You need to avoid things like winner take all markets.

i love this idea.

yet, it seems like the whole point of startups nowadays is to become the winner in the winner-take-all market. and VCs seem to be looking for that kind of play mainly. and markets become winner-take-all with alarming frequency.

so, it's like, how do we get to the kind of market with room for multiple long-term, profitable players?


That's basically the thesis of Zero To One, and yet it's responsible for burning how much Venture Capital?

One of the interesting things is how companies like CB Insights seem to have built quite successful mid-sized startups with very little funding (CB Insights are at $11.7m in funding), or Atlassian who didn't raise until they were pretty close to IPO. Compared to Uber at the opposite end - how much capital has been squandered on making very marginal gains in the name of growing market share?

It'd be an interesting research project to compare outcomes against funding raised, over say a 10-15 year period.


Markets that have a high barrier of entry and products that require a certain degree of in-house customization. The trade-off is scalability but the gain is that your space won't get slammed (or is less likely to get slammed) with VC-flash funded 'start up' versions of your start up in the medium run.


Open plan offices and general lack of a quiet, contemplative, professional working environment is the hugest con to me, even huger than the compensation issues pointed out by other commentors.

I would look to start-ups to be leading the effort to improve industry practices for software development ergonomy and human-centric working spaces (i.e. focus on privacy, quiet and individual customizability).

But instead, start-ups often try to conflate “collaborative spirit” with some shallow and false idea that collaboration is equal to being continuously embedded in a real-time stream of preemptible audio and chatter.

Headphones, jabberboxes, telephone rooms, limited freedom to be remote — none of these are useful and none address the underlying privacy and human centric ergonomy points.

Practically the only thing left that can convince me to take the risk of a startup, with its lowered compensation, poor insurance, and the poor risk characteristics of equity, is giving me my own private office, and making sure everyone on the team who wants one also has one, from the summer intern on up to executives.

If a start-up cannot offer a private office, then the start-up has to offer me the same market rate salary, bonuses, insurance and work-life balance that any other company would have to offer me.


I review the Joel Test occasionally, even if some of the items are kinda dated. It's amusing how both big companies and startups consistently fail two of them (and the test says if you're at 10/12 or lower there are serious problems).

    8. Do programmers have quiet working conditions?
    9. Do you use the best tools money can buy?
Startups could out-compete larger companies here by providing both shared working space and private space, but they don't. Similarly for one of the tools, development hardware, if all you're providing is a macbook pro and maybe a monitor... well I'm sure Apple will significantly upgrade it any year now. Meanwhile those of us who like Linux distros (or, god forbid, Windows after disabling all the crap) can have quite a bit of power on the go. My current (big) co gives everyone a desktop and a laptop, it's nice to have both. You might quibble if they fully pass #9, but at least they make an attempt.

"... programmers are easily bribed by giving them the coolest, latest stuff. This is a far cheaper way to get them to work for you than actually paying competitive salaries!"

Salaries are such a hot topic, startups unable to match need to differentiate from what the big players are doing in a better way across many dimensions at once, not solely the nebulous "more control of the product direction".

https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-s...


I was just writing a comment on here the other day about whether there should be a “Paul Graham test” based mostly on the essays “Great Hackers” and “Maker’s Schedule, Manager’s Schedule.”

The unequivocal importance of private offices is mentioned in both (in the latter, it’s focused on how meetings swiss-cheesify the day, but the point is obviously the same as that of private offices vs. open plan interruptions.)

So it remains a mystery why Y Combinator and YC-backed companies, so informed by many of Graham’s viewpoints, aren’t more proactive about this.


"... programmers are easily bribed by giving them the coolest, latest stuff. This is a far cheaper way to get them to work for you than actually paying competitive salaries!"

Past time (20 years ago) programmers yes. Today's programmers? No.

The Math is very simple: if a company throws a lot of money, I can buy the latest coolest stuff for the next 10 years.

I doubt programmer is that gullible (otherwise they're probably a "Yes" man).


Past time (20 years ago) programmers yes. Today's programmers? No.

The economics of hardware are very different now. In the 90s you might have a SPARCstation or an SGI on your desk at work, amazing gear you could never have afforded for yourself. Now you can easily buy a home PC that’s better than any corporate model.

I’m sure it’s still true in some industries, 3D printing maybe, but not in software anymore.


You'd be surprised. Many programmers don't negotiate, don't ask for severance or bonuses or better acceleration/vesting terms etc., feel afraid to be rejected after completing interviews, and a lot of people end up working for far lower pay than they could have otherwise gotten. I've known a lot of people who joined start-ups because they were promised various things (freedom to work on X, guarantee of publishing research, attending conferences, etc.) and then 6 months later they feel miserable that they accepted lower pay and none of the promises turned out to be true (sometimes through no intentional fault of the start-up founders, but sometimes through complete bait and switch shenanigans).

The risk that start-ups won't follow through on ambiguous work promises is super high, yet people keep falling for it year after year.


> Startups could out-compete larger companies here by providing both shared working space and private space, but they don't.

i agree that they should do that. OTOH space isn't cheap. i recall a scrappy startup where 20 people were packed inside a live-work loft. the CEO's office was the master bathroom.


Not every start-up could afford it, sure. But by the time you are well-capitalized, it’s not an excuse, and as Stack Overflow has shown, it’s not that hard to afford even in Manhattan.

When young start-ups are spending millions on the company’s third wave coffee station and opulent roof deck for obligatory alcohol drenched happy hours, you know it’s not cost keeping them from prioritizing ergonomy-focused private & quiet work space.


I think part of that is the high cost of office space in places like SV and Manhattan (the SV startup little brother).

Small companies end up in post War art deco buildings with flimsy elevators that open up to a mess of open plan tables, cables over the floor and pillars in strange places. Some of them have the audacity of handing out laptops and making a group sit in a conference room around a table all day (and days are long in startups).

That's what I've observed in Manhattan at least.

The problem is exacerbated by rapid hiring growth and the inelasticity of physical office building plans.


Private offices are great, sort of. I haven’t had one in the last 15yrs in both big and small companies. I find it surprising that you have had access to this “benefit.”


Between 2008 and 2012 I worked in 3 different places where all developers and researchers had their own offices (interns were paired usually). It wasn’t even a second thought, it was just baked into the culture that obviously the work requires huge blocks of hours spent alone, privately engaged in contemplative work.

One was a defense research lab, one was a boutique company that makes computational fluid dynamics software, and one was an education technology company.

The ed tech company went through a huge remodeling effort to rebrand as more of a straight up tech company, spending bonkers amounts of money to tear down offices in favor of open plan designs, despite outrage, protests and resignations from longterm staff, especially in some of the offices where there was no planned headcount increase and no engineering presence (like the Columbus, Ohio, office).

I ended up leaving the final place to take a more lucrative job in finance in a company with high-walled cubicles, and couldn’t believe how distracting and frustrating the ambient noise and discomfort from headphones was. These days I would give my left arm to have even just high-walled cubicles.

Since then I took jobs in two places with fully open-plan shared desk areas and I flat out will never do it again. It’s just too unhealthy and too counterproductive to even bother with it at all.

Whatever my next job is, it has to give private offices, end of story.


> Whatever my next job is, it has to give private offices, end of story.

Given how incredibly rare private offices seem to be these days I can't imagine what kind of leverage you must have to be able to stick to such a requirement.

Especially since unlike salary and other benefits it's not something that any company can decide to give you.

Either they have private office culture or not. If they are an open office company like most of them are you just have to exclude them, severely limiting the type and number of companies you can work for.


The most important leverage is to just say no if they won’t agree. It doesn’t matter what level or specialization or education or experience you have. The only way to win a negotiation is to just genuinely not want what the other party is offering if it doesn’t meet your criteria, and turn it down.

Obviously, if you are desperate for a job due to other factors, you may be literally unable to turn down a suboptimal offer. It’s unfortunate that companies bank on this, and sometimes even angle their search criteria to specifically find classes of candidates they can exploit with low offers, inadequate workspace, etc. But it’s a fact of life.

When you’re not in that situation and you are free to turn a place down, then you just have to decide what matters to you and ruthlessly stick to it.

To your other points, I think they are not actually big deals. Relative to other costs, building private space on an existing floor is not that bad. Of course, companies are mostly not worried about the cost but are worried about the anger and reaction from existing staff who hate the open plan space they are stuck in.

If a company has a top-down “no office” culture, like “not even our CEO has an office!” then just walk away. Those people are so far gone it’s not worth it. You know from day one that insincere corporate evangelism matters more to them than your actual work. You are more office furniture and less engineer at that point.

It doesn’t matter if this is ~70% of all IT jobs. They are bad jobs. Ok to take them if you’re in a pinch, but why would anyone choose them? They’ll never be forced to reform their habits to recruit adequate staff that way.

Another big option is to ask the company to rent a dedicated office for you from a co-working space. So you’ll be “remote” except working from a single office that they lease for you (or you could lease it yourself and be reimbursed or grossed up for it). This is exceedingly cheap for well-capitalized companies and if they are serious about your productivity and ability to actually collaborate, they’ll do it (as opposed to only being concerned if it superficially looks like people are collaborating because of the open plan layout).

There are plenty of solutions for a motivated company. Existing office build out is not a serious barrier, only cultural unwillingness to be adaptable to people whose jobs require private space to work.


I get it. But what you are describing is quite optimistic/idealistic.

Most companies will say "no thanks" and move on to the next candidate in their list.

There are much smaller things that companies treat as deal breakers, let alone asking for a private office. The dynamics of it just doesn't work if there is a open office plan with 20 people working in it, then there's one lone snowflake demanding their own office. Even if they agreed to that you wouldn't want that nightmare.

Your practical options would be limiting your choice to companies that have private offices baked into their culture or remote jobs.

Most people can't realistically afford to exclude that many job opportunities from their pool.


> "Most companies will say "no thanks" and move on to the next candidate in their list."

I don't see why this makes any part of it idealistic or how it is connected.

I view it as pragmatic.

Consider an employer who feels so entitled to workers that just take whatever unproductive office space they give that they would just say, "no thanks" to a qualified candidate and move on. Never mind the fact that in many domains, it's extremely hard to find good engineers, and 'just moving on to the next candidate' is not really a thing. Beyond that, this employer would be telling me how entitled they believe they are, and inflexible about a top-down mandated open floor plan design.

It's not idealism to want to avoid that sort of employer, it's just pragmatism. Like I mentioned, unless you're in dire straits and you have to compromise to take a job right away, then just say no. In other situations, you can by definition afford to just search longer and longer until an employer meets these standards.

I agree it would require patience for a very long job search, but I don't agree that it is optimistic or idealistic. Rather, it's pragmatic and being patient to reject all the bad employers who won't care about your ergonomic health is important and worthwhile, even at the cost of a slow job search where you turn people down for failing to provide private offices.


I work in a software company in the midwest, we've had private offices for the last 10 years.


One of the “weak” points a startup has is the brand perception.

Some-role at FANG sounds more impressive than same-role at a no-name startup.

Even the startups themselves like to brag that they were started by alumni of brand name employers, rather than alumni of other startups.

So, in what concrete way can you shift this?

There is no easy solution, but you can try and follow the same route you did for startups.

No-name (YC 18) is a better brand then just-no-name.

Allow/encourage employees and encourage/require your startups to brand people as “YC Startup Engineer” rather than “no-name Engineer”.

It may sound a little strange at first but there is a probability bigger than zero that if you promote this correctly, as you did for startups, you may end up at top of the prestige pile.

Just 2 cents from a guy with none ;)


+1 to not dismissing prestige, although I'm not sure I agree with this plan. Prestige is easy for some people to dismiss, but it can be a very big deal to others, especially (in my experience) in Asian cultures. My girlfriend's family still doesn't believe that I quit Google to work at a startup--they assume I got fired--because who would willingly give up that prestige?


I'm not sure if that's an Asian thing, I actually only learnt the importance of prestige after coming to bay area. When you mix with people with prestige and without, sharing job hunting and interviewing experiences quickly lead you to realize the importance of brand name recognition of your school and past employers.


I rose in a sales role to be a non-Founder CEO of a material science startup. We were successful - but after 9 years I was burned out and came to a friendly resignation with my board. The name recognition component is real. I got great offers within the industries we sold to - but outside of that there was a lot of explanation about the business, etc.

Brand perception is a real issue - and it doesn't get covered up by your title or role.


That is a great idea! I agree the brand perception is a big issue for startups, and that is a clever and unique thing that YC could do to help.


    STARTUP X!
  [powered by YC]


So, I work at a startup. But, to echo what literally everyone else has said:

The money is better at big companies.

There are exceptions, but you almost certainly won't work for one of them. You will make more money at Google or Facebook or Netflix than you will at all but the luckiest choice of startup. Note I didn't say "best" choice or "most successful" choice. Gotta get in small, and exit big, which, no matter what anybody tells you, is more luck than skill.

That said, why do I work at a startup? Because the feeling of being able to meaningfully affect its trajectory (both technically and in terms of product) just matters to me. You can't get that at a big company, and for me that more than makes up for the ~50-75 k$/yr I gave up for it.

But I'm in the extremely fortunate position of having very frugal tastes, a significant fallback fund (I could afford to not work and maintain my current lifestyle for several years), and no dependents. Beyond the raw dollar amount, this also means that I'm basically indifferent to the prospect of losing my job, which as the other comments point out, is the other significant drawback of startups.

It's unclear to me that the combination of intangibles and tangibles works out positively for many other people, and I kind of feel that to a first approximation, recommending against being an employee at a start up is the right advice.


What if you were giving up $100-150k a year? Would that move your needle?

Or what if you were actually giving up $200k a year?

Yes, money isn't everything, but that's no reason to let someone take advantage of your excitement.

I am seeing a lot of people doing the devils work here, depressing engineering wages with arguments against higher pay. The VCs dont need your help, why are you helping them?


Your worldview will change when you've dependents. :-)


GP said "I kind of feel that to a first approximation, recommending against being an employee at a start up is the right advice."

Are you saying you think startups are better for people with dependents? That's surprising to me, could you elaborate?


No, it was a response to OP writing he had no dependents so doesn't value job/income stability so much. He seems quite lucid about the fact that this might change the moment he'll have a dependents. I was merely confirming it will. :-)


I strongly agree with all of this. I made the same decisions that you did, and while it worked out well (we rolled between 90 and 95 on https://danluu.com/startup-tradeoffs/), it was clearly a negative EV play. I wouldn't have done it if I didn't have a solid record at an established company (so that I could easily return to a similar job at any point), or if the income reduction would have had a material impact (which basically implies no kids and no plans to have any in the next few years, no mortgage or student loans, and no health issues).

I kind of feel that to a first approximation, recommending against being an employee at a start up is the right advice.

Absolutely.


As a former startup founder, I tend to agree that most startups are low-balling early employees. These employees over-value their stock by imagining what it would be worth if the company reaches $1B valuation. It really is a lottery ticket.

But in my opinion, the answer is more pay, not more equity.

Employees should get market comp, period. Doesn't matter how early-stage the startup is. If a founder can't afford employees at market rate, they shouldn't be hiring yet. They could perhaps offer to take people on as co-founders -- with an appropriately equal share.

People looking to join early-stage startups as employees should be extremely skeptical of equity. Obviously, you want to take some. But if a small chance of getting super-rich is your goal, you should start your own startup. If you are going to make bets, bet on yourself, not on someone else, because you know yourself much better than you know anyone else, and wise bets are all about having information no one else has. Yes, non-founding early-stage employees can have a big impact on a company, but they are still beholden to the founders -- if something goes wrong, they can fire you but you can't fire them. Making a big bet while letting someone else hold the cards is just too risky.

Instead, demand market comp. Do not join a startup that won't offer you market comp. It's not worth it.


I don't quite understand. On the one hand you're saying that early employees should "demand market comp" and on the other you're saying that equity basically doesn't matter (and if you feel this way, it doesn't really make any sense to be joining a startup anyway). Are you conflating "compensation" with "salary"?

"Market comp" for a good engineer with several years of experience in the Bay Area is something like 250k - 350k at a Google or Facebook (with some variation in both directions here). It's not realistic, nor consistent with the market, for an early-stage startup to pay people this much in cash.

Early-stage companies should offer sufficient equity such that their employees should in expectation earn at least the same as they would at a public company. If their expected earnings are less than this, then more equity is absolutely a good solution.


> Early-stage companies should offer sufficient equity such that their employees should in expectation earn at least the same as they would at a public company.

That's the joke! Nobody comes remotely close to offering enough equity that their total comp is equivalent!

Imagine a company that just raised a $1M seed round on convertibles at a $6M valuation cap. Now say they offer an "extremely generous" 2% equity package to their first employee. What is that 2% worth?

Well, the investors think that preferred shares in that quantity would be worth $120k. Of course, equity vests over four years. So your equity comp is... $30k/year. If it were preferred shares. But it's not, it's common shares. So it's worth even less.

You'd need to offer more like 10% to claim you are matching the RSUs people are getting at Google or Facebook. But at that point, you might as well call the person a co-founder. And maybe that's in fact the answer: add co-founders, not employees.

But this isn't what people are doing today. Instead they're convincing employees to take sub-market pay and sub-market equity to take a stressful job with almost no benefits.


Yes, I mostly agree.

There's one nuance that I've been thinking about lately that I haven't seen anyone ever point out before, which is that high volatility will make options worth more than they are on paper.

Here's a thought experiment: imagine that there are two employers on the market. One will always pay 200k/yr guaranteed and you can choose to work for them at any time for this wage. The other pays 100k/yr plus one Coconut per year, and Coconuts are currently worth 100k each. So far these are equivalent monetarily. But now let's add the stipulation that after one year, the price of coconuts has a 50% chance of going to 0 and a 50% chance of going to 200k each. Which would you choose?

The expected value of each of these job offers is still equivalent (after 4 years of working at each, you'll have 800k in expectation). But you should definitely take the second one. Why? Because after one year, if coconuts drop to 0, you can just quit and join the first company. Then you have a 50% chance of 100 + 200 + 200 + 200 (coconuts to 0) and a 50% chance of 300 + 300 + 300 + 300 (coconuts to 200) which comes out to 950k, which is better than sticking with either company alone.

This thought experiment fascinates me because it clearly shows the extra value that up-front stock grants have. The point is that you have some protection from downsides in the form of switching jobs, but no similar cap on the upsides, and the higher the volatility of the stock the more value this provides.

I'm not sure what the numbers look like when you view them through this lens, but it does mean that an equity grant of 2% of a 6M company should trade off for more than 30k/yr.


I think that's a good point, but it's just unlikely to actually happen with startup options because of the typical 90-day exercise clause and limited information.

The 90-day exercise clause and options instead of shares effectively forces you to buy the coconut, meaning that instead of a 50/50 chance of 0/200, if you plan on leaving before the event that resolves 0/200, then if your strike price on a coconut is $50, it's more like 50/50 chance of -50/250 because you expect to have to exercise when you leave. You can play with the exercise cost, but it does change your math quite a bit regardless. Now if startups gave actual stock instead of options or if they don't place a 90-day time limit on exercising vested options, this wouldn't be an issue. But almost all startups do it this way.

The second point is that the company often doesn't look dead until much later. You're just not going to be able to tell one year in, or two years in, or three years in. So you won't be in a good position to capitalize on volatility like you would on the public markets.

Then you have things like liquidation preferences that will skew your EV calculation, except they might happen after you join, but you may or may not ever find out that those gotchas are there.

As it stands, all of this just creates an incredibly inefficient market that requires employees to take badly informed, high risk bets, where they often don't have deep enough pockets to absorb the risk.


Both of these are good points. 90 day exercise windows are both unnecessary and terrible for employees and we should move to eliminate them as quickly as possible. I think the trend is slowly in that direction, but it really should just be a deal breaker for engineers.

The limited information is also a good point. Some level of saviness and understanding of your company and market can help with some parts of this but certainly not all.

If anything this may be a good argument for working at late stage private or smaller more volatile public companies. Then if you get lucky and get, say, Square from two years ago, whose stock has gone up 7x, you capture this upside (and if they do poorly, roll the dice again after a year, perhaps). This is quite mercenary and might not be the route that makes one happiest, though.


Yes!

Funnily enough, the fact that equity grants are "options" to purchase stock at a strike price less than the real share price is much less valuable than the optionality you describe of continuing working to earn the rest of a stock grant after more information is known.

Unfortunately I think it's very hard to pin a value on the optionality to continue working, and I haven't seen anyone mention it when considering joining a startup over a larger company.


But while FAANG equity has a 95% chance of still being worth hundreds per share in 5 years, the startup's equity has more like a 98% chance of being worth $0 in 5 years (based on startup survival rates). The expected value is essentially zero. That's why you can't make up for startup salary with startup equity.


this also requires one exercises the cocounut option at the end of every year. If you don't and they drop to zero in year 4...


For the purposes of this thought experiment we're assuming that there's no price movement after year 1. In the real world this probability of failure in the future should be priced in to the year 2 price and doesn't affect the expected value anyway.


When you offer 10% per employee, how many employees can you actually take on??


I believe it was Sam Altman who had proposed a good solution to this, which is that you start off with a high number like that for employee #1 with decreasing numbers as the employee count goes up. If you are Instagram and become worth $1B with only 6 employees then everyone should benefit massively. On the other hand, if it takes 1000 employees to get to a great outcome, then obviously the founders and first employees will have been diluted by the addition of all the future employees required to achieve scale or an exit.


Yes, that’s a good way to go about it… Any educated opinions of what form it should take (resricted stock, rsu, options, etc.) to be most employee friendly?


That was part of the comment: at that point it's more like a co-founder not an employee. So: very few obviously.

Perhaps more reasonable is 1-2% per for the first 5-10 hires, then 0.5-1% for the next batch, etc.

Also I really think these should be RSUs, not options. Employees are already invested in the startup by paying a premium in the form of reduced salary and opportunity cost.


If you give them Restricted Stock, though, they have to pay tax on whatever the 409(a) value is -- which is what the strike price would have been with options.

You can give them a signing bonus to cover the tax, but at this point it's easier and actually better for the employee to give them the cash separately and say "you can use it to exercise if you like".

Really the difference between options and Restricted Stock is measurable in dollars, so might as well just give people the dollars.

(Note that Restricted Stock is not quite the same thing as Restricted Stock Units (RSUs)... RSUs are for later stage companies. But the principles are similar.)


Sure; point being that employees ought not have to pay for their equity, because then it's not really compensation.


Yup, all the options for granting non-founder equity are absolutely awful from an employee POV.

Maybe YC could lobby for a sane way to grant equity to early employees without penalizing the employee?


250-350k is low for Google and FB. It's more like 400-500k if you are senior, 500-700k if you are staff. This is including RSUs


Indeed, and even well-funded startups can't afford to burn $400k on a single engineer.

They basically have to give out generous equity to compete, but they and the VCs would rather be greedy and dole out fractions of percents under the cynical misleading pitch that these scraps will be worth millions when the startup exits for billions.

To their credit, This scam did work for a while, shortly after a whole lot of early employees really did make millions on generous equity grants at early startups like Google.

Being an "early employee" means nothing now. You get the token 0.01% bottom-preference shares that will net you 0 in almost every imaginable scenario, and somehow this is supposed to cover the 200-300k/yr difference you'd get at a profitable established company.


I'm not really interested in arguing about these numbers, it's not really relevant to my point. I was basing this off of https://www.teamblind.com/article/google-engineer---total-co... where 250-350 includes the majority of L4 and L5 engineers. Based on this your numbers look off by one level or so, at least for Google. But again, I don't think this is very important for my point.


I always feel like every developer on HN is making like $200k-$400K without blinking, maybe that's true. Just for a perspective on these numbers, the top 1% of income in CA is $450K - https://www.reddit.com/r/dataisbeautiful/comments/8qhh3x/ann...



Those are not Google and not Silicon Valley.

Try:

http://www.h1bdata.info/index.php?em=Google&job=Staff+Softwa...

And keep in mind that base salary (what's reported on that page) is usually about half of total compensation. (Bonus and stock being the other half.)

Also this appears to be the H1B database. I'm not sure how H1B salaries compare to the overall average.


> I'm not sure how H1B salaries compare to the overall average.

H1B salaries are typically lower than average. Why do you think companies spend millions lobbying for more H1Bs? To pay them more than average? :-)

Also, keep in mind Google only has to disclose base salaries for these H1Bs. For a staff engineer, most of the total comp would be in bonus pay and especially RSUs. They can easily be making $400k or more through those means.


Do you have evidence that people coming on an H1B visa get paid less than their non-H1B coworkers (at same level / same seniority / same office) at Google?


I would suggest that while new hires of H1B might not get paid less, the market dynamics of not having as many alternatives would invariably lead to less valuable retention efforts by the employer. i.e. fewer raises, fewer promotions, smaller bonuses, etc.

As I understand it, H1Bs aren't too bad (transferability is a thing here), but other forms of visas are brutal in this regard.


https://news.ycombinator.com/item?id=13579226 is one example. In addition to the article, HN is in near-unanimous agreement on this issue from the contribution of many H1B visa holders. I've seen it pop up many times.


> To pay them more than average?

No, to get a bigger talent pool.


H1b data doesn't include rsu or bonus. Many are getting 16-17% bonus and ~50-150k/year in rsu.


For a staff engineer, I'd say even $150k is very low. Even for an H1B, I'd guess $200k/year at least in additional pay beyond the base salary.


I work there and I'm surprised by the numbers you propose, they seem too high to me.


rough numbers on http://levels.fyi


> Early-stage companies should offer sufficient equity such that their employees should in expectation earn at least the same as they would at a public company.

This would still be underpaying people for a few reasons: expectations are not risk-adjusted, it also doesn't take into account the timeline you get paid on, i.e. the ROI you would get investing your Google salary in an index fund and taxes make getting paid a regular amount over time more valuable than getting a large startup check.

Maybe you were taking these factors into account, but most startup equity offers are massive low balls.


> in expectation earn at least the same as they would at a public company

No, it should be multiples. Otherwise why is the employee taking on that risk?


I don't see why this follows. I said "in expectation". So some % of the time it's going to be 0 or thereabouts and some % of the time will be much higher. The best case scenario needs to be multiples in order to make the average work out, but I don't see any reason the average case needs to be.


> If a founder can't afford employees at market rate, they shouldn't be hiring yet.

That's a little bit too strict, and as such is not a position founders are likely to accept. Sometimes they need employees before they can pay market rate, and market rate is pretty steep for a senior engineer in the Bay, for example, and most other areas startups are heavily recruiting.

It's reasonable to offer generous equity for early employees willing to take the risk. What does need to stop is the toxic culture of giving out 0.01% even to earliest employees (engineer number less than 10, often less the 5) with the cynical fake-stardust pitch that "this will be worth tens of millions since we're definitely exiting at $1bn+".

As you mentioned, this culture of deceit has become commonplace and it's poisoning the well of future employees. You can witness its corrosive effect throughout this comment thread.

Give out substantial equity to those early engineers who take risk. Give them a realistic estimate of the risk they're taking, and the value they can get. If they take it, it's their prerogative.


> Sometimes they need employees before they can pay market rate,

But you don't get to have something just because you need it. That's not how it works. You need to raise more money, so that you can afford to pay the employees. It's not fair to make the employees act as unofficial investors in your company, and then give them a deal that the real investors wouldn't accept.

> giving out 0.01% even to earliest employees

I hope that's an exaggeration and no one actually goes that low. (EDIT: Re-reading I think you actually meant 1%, not 0.01%?)

But if you go based on the valuation paid by the investors, then even 1% is a laughably low offer during the seed stage.


> It's not fair to make the employees act as unofficial investors in your company, and then give them a deal that the real investors wouldn't accept.

Which is why I'm saying they should be offered a deal that investors would accept.

Demanding everyone pay market rate is just unrealistic. Never going to happen. I'm proposing a realistic, possible change.

> I hope that's an exaggeration and no one actually goes that low.

First ad I clicked on from Angel List front page:

https://angel.co/everlane/jobs

$130k salary and 0.01% equity. But that's OK, I'm sure their CEO will be happy to tell you about their surefire $Xbn exit.

Last I checked Angel List, 0.01% equity was quite common, even for early engineers at very early stage startups. It almost always goes hand in hand with blatant lies about the certain $Xbn exit.


> Which is why I'm saying they should be offered a deal that investors would accept.

> Demanding everyone pay market rate is just unrealistic.

But they're the same thing! If investors would accept it, then you could just as easily have the investors buy the equity, and then pay the employee with it.

So if it's totally unrealistic that founders would actually pay market, how could it be realistic that they'd offer equivalent equity?

> First ad I clicked on from Angel List front page:

> https://angel.co/everlane/jobs

> $130k salary and 0.01% equity.

That's not an early-stage startup, that's a company with >200 employees and a valuation in the hundreds of millions.


> But they're the same thing! If investors would accept it, then you could just as easily have the investors buy the equity, and then pay the employee with it.

See my [response to inimino](https://news.ycombinator.com/item?id=17291045). It's absolutely not the case that if I have $100m worth of stock according to some valuation, I can just go out and sell any amount of that for what you'd expect based on the valuation.

VCs are the only ones who are generally ready to buy this sort of equity, and raising money from them is a long difficult process, and I can't just decide I'm going to sell 0.5%, get $500k, and pay that to a new employee.

Finding a non-VC to buy your equity is very difficult too.

> That's not an early-stage startup, that's a company with >200 employees and a valuation in the hundreds of millions.

Like I said, it's the first random ad I clicked. Last I looked at Angel List, there were tons of startups offering 0.01-0.05% equity.

Also, notice they're offering this 0.01% with a maximum salary of 130k in SF who is skilled with "Python, Java, Scala, Ruby on Rails, React.js":

https://angel.co/everlane/jobs/306986-software-engineer

That's way below market.

> That's not an early-stage startup, that's a company with >200 employees and a valuation in the hundreds of millions.

Do you have any idea how many startups were worth >100m at one point or another on paper, and ended up with an exit where nobody but the VCs made any money due to stock preference? One down round is enough to effectively wipe out most of the rank-and-file equity in these scenarios.


> See my [response to inimino](https://news.ycombinator.com/item?id=17291045).

Yes I responded there.

> That's way below market.

I agree the salary looks lame but none of this conversation is about companies at that stage.

Equity packages in percentage terms are obviously going to be much smaller for later-stage companies, since there is much less risk baked into them. 0.01% of a company valued at $200m is equivalent to 1% of a company valued at $2m.


>> giving out 0.01% even to earliest employees

>I hope that's an exaggeration and no one actually goes that low. (EDIT: Re-reading I think you actually meant 1%, not 0.01%?)

What I witnessed as guidance from a top-tier VC to its portfolio companies: 1% for employee #1, then ramp downwards for each employee: .07%, .05% etc and very quickly you reach .01%


"You dont get something just because you need it"

Huge applause.

"You need to raise more money"

Crowd falls silent.

How about trying to sell something and generate revenue. I long ago stopped subscribing to Startup Porn but I remain baffled as to how seemingly smart people are so intoxicated by it that the notion of building an actual business is an afterthought.


Well yes. But the premise here was that in order to generate that revenue you need the employee. If you don't need the employee then by all means don't hire the employee (and don't raise money to hire them).


My view is that business owners hire too early. Nothing kills a business faster than hiring people.


ok


> Give them a realistic estimate of the risk they're taking, and the value they can get.

Herein lies the problem. Founders are uniquely well-placed to evaluate the risk, and uniquely psychologically motivated to evaluate optimistically.

Because of that, founders sell equity dear.

If the generous equity offer is reasonable, then would be reasonable to make two offers, one with only cash and one with generous equity, in an "I cut, you choose" scenario. If a company has taken funding and isn't willing to do this, then employees are being asked to take risks that the financial backers are not willing to take themselves.

[Edit: removed something about a typo]


Again, you make it seem very cut and dry. It's not.

Suppose my startup is current worth $100m. According to you, I should be able to sell 0.5% of it for $500k and give that to the employee, or offer them that 0.5% directly, right?

Well, no. I can definitely offer them that 0.5% since I control the equity, but I can't just go to a VC and tell them "hey, here's 0.5% of my shares, now give me their fair value worth of $500k".

Ever been close to a startup raising money from VCs? It simply doesn't work that way. VC investment is a big, complex package deal. They're not just going to accept whatever shares you give them, and pay you. They have their own idea of how much equity they want, how much they're willing to pay for it, how much besides equity they want (control of the company, seats at the board, various forms of preferred stock and other guarantees, etc).

Also, fixed the typo, thanks.


> Suppose my startup is current worth $100m.

Then you're way beyond the stage any of this conversation is about... But let's say you said a smaller number.

> Well, no. I can definitely offer them that 0.5% since I control the equity,

... no you can't. You can grant equity out of the option pool, which you defined in collaboration with your investors. If you want to grow the pool you're going to have to talk to them first. You don't have free reign to dilute the investors away at will.

> but I can't just go to a VC and tell them "hey, here's 0.5% of my shares, now give me their fair value worth of $500k".

Well sure, not on a daily basis. You have to raise a round of funding, obviously. Hopefully you don't do that too often, but when you do, you make sure to raise enough to pay your employees a fair salary until the next round.

If you can't raise a round of funding, then your stock is worth nothing and the employee should consider it to be worth nothing.

> Ever been close to a startup raising money from VCs?

I have raised money from VCs.


> You can grant equity out of the option pool, which you defined in collaboration with your investors.

Obviously I'm simplifying here, but overall yes, it's far easier for a startup to give equity than cash, for the reasons I mentioned.

Especially if I'm an early stage startup, maybe after a small seed round, I will surely have enough options in the pool, or investors lenient enough to let me issue these extra stock in the unlikely case I'll need them.

> I have raised money from VCs.

So you know how unrealistic it is to raise VC rounds just to support salaries for a handful of new engineering hires.


> I will surely have enough options in the pool,

At a $6M seed stage valuation, 1% in equity (vesting over four years) is worth the same as $15k in salary.*

Which is harder for a founder to authorize, 1% in equity or $15k in base salary? Honestly $15k salary sounds a whole lot easier and cheaper to me.

$105k in salary converts to 7% in equity. So if you want to hire than $400k Googler you're going to be paying them $200k salary and 14% equity.

An entire option pool is typically 20% or less.

The only reason giving away equity seems so much easier than cash is because you can trick people into taking far less of it.

* Disregarding the fact that the valuation is based on preferred shares while the equity grant is common shares, which only makes the equity grant even more worthless.

> So you know how unrealistic it is to raise VC rounds just to support salaries for a handful of new engineering hires.

That's literally the entire point of raising a VC round?


Yes, I'm eliding a lot of complexity, in that you can't just take the equity and sell it to the bank or to your VCs. However, you as a founder have some control over how much you raise and at what valuation. So the fact that you can't make that decision at the time of hiring is certainly true, but you are making those decisions when you decide to raise a round (or not).

That's why I restricted my final remark to companies that have taken funding. Of course there are a lot more moving parts than I let on, but if a company has taken funding and would rather keep their funding than their equity, then it makes sense to think carefully about why that is before buying that equity with, potentially, years of your irreplaceable life.


If its worth 100 million it isnt a startup.


Hm? Plenty of startups have current valuation over $100m.

However, I just chose this number because it is nice and round so the math is obvious.


Then I would argue that they aren't startups, they are fully formed businesses.


Frankly, the early employees often build more of the company and its success than the founders do.

They should be rewarded proportionate to the growth they create and catalyze.


> If a founder can't afford employees at market rate, they shouldn't be hiring yet. They could perhaps offer to take people on as co-founders -- with an appropriately equal share.

Brother, I have worked with both startup & MNC's and i can understand what you are trying to say but it is a bit harsh to say that if a founder can't afford employees at market rate, they shouldn't be hiring. Some part of me says you are right but other part says that some employee should have some faith. If I look from employees perspective its safer/more rewarding/less riskier to join as co-founder then getting market rate. I believe somewhere faith also counts :)


I would say the 'market rate' for the big tech cos cannot be applied to the financial analysis of hiring in startups because most startups have cash burn, and big tech is profitable. If you somehow negotiate a startup to pay you a google like salary you probably won't have much fun because you will be viewed as an even riskier hire than you were to begin with. There will be even more pressure to perform than there already was.


Faith is cool. But it needs to flow both ways. If you have faith in the person, make them a co-founder and give correspondingly respectable equity.


Not sure how you're viewing getting paid less as safer and less risky. Also, the parent is saying the issue is when an early employee is not considered a founder and isn't getting paid market rate. That's the downside of each of those points - no/little equity and no/little pay


I was employee 18 at a startup recently acquired by Google. Maybe not super early, but I was able to make big contributions that had a large impact on our eventual acquisition. It was a fun ride but I won't be doing it again for one main reason: startup equity distribution makes zero sense for early employees. Founders get 20+ times the equity. Yes they take more risk and work harder, but they're not taking 20 times the risk or working 20 times as hard.

Also there's a bizarre reluctance to show employees the information they need to value their equity, like number of shares authorized/outstanding/issued, existing liquidation preferences, or the whole cap table. Although it worked out fine for me this time, I will never again take equity compensation in a small company without access to the cap table.


The second part is something I think we can easily fix. Transparency about how much of the company you own needs to be a given with any good startup.


Should be law that to hire someone and pay them equity, you must have the employee sign that they've seen the cap table. Maybe even on a yearly basis.


jwz had to threaten Netscape with a lawsuit to see any share information, and that was in the mid 90's.


I was an early employee.

Lots and lots is said about compensation, I won't repeat it here. (Just treat equity like a tip.)

One pro is that I got to set a lot of architectural direction. Because we were small, I didn't need to put up with a lot of groupthink or bad habits when fixing some very bad problems in the codebase.

Another pro is that I had some of the best working relationships in my life while we were small.

A con is that startups are crawling with bozo managers and people who just can't handle the responsibility that their role entails. I used to spend a lot of time pushing back on people throwing unreasonable amounts of their work onto me.

(QA who wouldn't follow process and wrote incomprehensible tickets; and support people who just wrote "it doesn't work" instead of diagnosing the customer's problem.)

Ultimately, as the company matured, the above problems worked themselves out. I helped define the processes for QA and support. Defining these processes is a big pro, IMO, of working for a startup.

Also: Incompetent people manifest themselves in startups just like in large corporations; it's just that large corporations tend to absorb them better. Startups die quickly if they can't push the incompetent people out.


I just went through the startup job hunting process as a new-grad.

I think many startups have their expectations set too high for the work requirements & compensation they're offering.

Many startups want Senior Engineers with several years of experience, and they want people who live in SF.

This makes it difficult for new-grads and those who don't live in the Bay Area to get into the startup scene. Many people want to work remotely or live in other startup hubs (eg. Seattle) where the cost-of-living is less expensive.

New-grads, you could argue, are the most willing, flexible, and risk-taking to work at startups since the lure is more about experience than $ compensation. However, most startups ignore new-grads because they don't have the processes/ability to mentor them (even if the candidate could already be qualified for the position).

There is room here for:

1. A company which offers services for helping startups foster remote teams

2. A company which offers services for helping startups mentor new-grads

3. A YC apprenticeship program that takes new-grads and places them in a YC startup w/ a mentor (who may or may not be at that company) for a few months to see if there's a match and hopefully transitions that person into a full-time role there

4. YC satellites in other cities or encouragement for some YC companies to relocate out of the Bay Area


I agree with all you've said here, first of all.

> Many startups want Senior Engineers with several years of experience

This is often advertised. It's sometimes listed as a requirement. Those requirements are more flexible than new grads ever realize.

I think, coming from school, it's easy to take those lists of requirements literally. It's quite common, though, to hire people who don't match the requirements exactly.

Something is probably improvable, there - job listings are written in a kind of code that's not obvious at all to new grads. You kind of need a few years of experience hiring people to understand what they even mean.


I agree.

FWIW, my university had a required co-op program, so I already had some internship experience under my belt, and even so, I was getting rejected from entry-level "Software Engineer" startup positions simply on the basis that the companies wanted a minimum # of years of experience.


I've had mostly negative experiences hiring new grads. So far, even though they were all smart with a lot of potential, they've all demanded more time and money than they were worth and left as soon as they felt any dissatisfaction, no mind or loyalty to the company or mentorship we've provided. They're fully within their rights to do that but it's happened to me enough times that I've decided new grads are not worth my effort right now. And I understand where they're coming from. I treated my first job out of school as a "throwaway" company while I earned experience and worked on establishing my personal life. Do that at a big company where you're a small component, not a startup where everyone relies on everyone else.

Another perspective: startups don't have capacity for mentoring, in most cases. Startups are high-throughput environments and bad design by inexperienced coders (i.e. most new grads) will slow a project down significantly. New grads are often treated as cannon fodder because they can't be used for anything else, and that leads to frustration and burnout. Do you want that? Wouldn't you rather establish your career under an experienced mentor, unlimited resources, a low pressure environment, and a high salary? Most new grads will do best by paying off student loans first, building a base of experience for a couple years, then jumping into startups from there. 2 years of enterprise experience at a company with a strong engineering culture (not even the "elite" ones) will make you infinitely more valuable to a startup than trying to break in right out of school.

My two cents. Not all new grads are the same :)


Con: The leadership is typically really, really bad. Either clueless, sociopathic, selfish, or a combination of those three. Many founders become C-level by default without ever having to learn the skills they would need to have if they had to get hired by another organization.

Con: As mentioned by others, compensation and especially equity are ridiculously out of balance. A few years ago, a startup I was at (and had left a few years prior) found a buyer. I spent 5 years there, and I got about $50k. Meanwhile, a C-level employee who was there for less than a year before the company sold got $5M.


The leadership problem is a big issue. I'm currently looking for work in the post startup world, places that are "rapidly growing" and filling up their engineering teams. On Glassdoor I see the same exact comments, and it's something I've personally experienced as well

Pro: the engineering team is great and you'll learn a lot on the job

Con: management is constantly shifting focus so you end up working on features for a while just to throw them away. Or the company pivots 2+ times.


Same here. I'm ready to make a move, and there are some products I would really like to work on, at companies that have openings, but the leadership is so questionable that I would rather just stay away.


I think the biggest problem with being a non-founder in a startup is that in 2018 that doesn't make you a key employee anymore. This leads to a bunch of problems, like worthless equity, relatively low pay, poor benefits, etc, but it essentially originates from a change in the business model.

In the older days when startups were aiming to be profitable by solving a new problem in a way that would attract paying customers, while competing in terms of efficiency, the contribution of an early employee to the bottom line was more noticeable, so the startups had to treat them better.

As of 2018, most startups aren't trying to solve a profit-generating problem that couldn't be solved with the tech from 5 years ago, but can be reliably solved now. Instead the VCs expect to get paid through an acquisition/IPO when either a BigCo, or the public buys into the hockey stick growth without scrutinizing the sustainability of the underlying business model (or being confident that the founder will find a way to pivot). So instead of being a cog in a BigCo machine, you are an extra in a VC-funded movie. And I don't think it's going to change without a major correction in the general public's expectations from tech.


I think the biggest problem is transparency, which leads to wrong expectations.

As a 3-time startup employee, people always told me I should expect a pay cut by going to a startup. But how much? When I received a Series A startup offer and a FANG offer at the same time, I couldn't evaluate them side-by-side because I had no idea how much startup equity was worth. I negotiated hard and got surprising results, which left me wondering: what did I leave on the table? What about my colleagues who didn't negotiate?

As an ex-founder needing to hire a team of 6, I had no idea how to pay. We didn't have money for compensation consultants, and tools like Glassdoor and HiringPlan wasn't around. It wasn't until I joined my current team I realized how the top VCs and startups do it - by setting a compensation philosophy and have access to market data. For example, your early stage startup can pay 30th percentile on salary and 70th percentile on equity, and you consistently apply this no matter the type of role.

This is why we built HiringPlan (https://HiringPlan.io) at LTSE. It's a free visual compensation planning tool, and we believe the first one with built-in market data used by top VCs and startups. Founders use it to figure how much to pay folks in terms of salary and equity, and whether they're treating diversity and inclusion with fair pay. Even employees and candidates come to learn what their roles and levels are worth, and use hard data to discuss compensation with their managers.


HiringPlan is great! Tools like that are not only helpful to companies, but also should lead to fairer compensation for employees.


Sounds cool. Went to your website on Chrome on Android and it is buggy. I get 404s everywhere. More specific, when I click the carousel--showing SF example pay--left or right.

Like I can do a better job than that.


You're absolutely right, this visual quirk should not have happened. Fixing it now. Thanks for your feedback.


Fixed! With a few other improvements as well. Please keep the feedback coming!


I was the first engineer at Crittercism/Apteligent which was acquihired by VMWare. I was there for about 5 years before I moved on to Google.

Pros.

* Lots of fun engineering solutions however I wanted to solve the problem. Moved fast.

* Learned tons. Had to touch every part of stack.

* Great culture initially. Everyone was open to helping out as well as going out.

Cons.

* Low pay.

* Growing pains. Visible shift from devs dictating the product to doing mundane things that customers wanted (necessary evil, but obviously less fun).

* Hiring of execs once you get big enough. I was unhappy that I worked there for 4 years but some guy who came in and did nothing got 4x my salary and 100x my stock.

You should never, ever join a startup if your motivation is money. Most of them fail and you end up with nothing (as I did). Even if you're an amazing engineer and think you can push it over the top, you will probably end up as a staff software eng at google in the same amount of time making 500k a year.

The only reason to work at a startup is for the learning and for the fun. You need to leave if you aren't achieving either of those, unless you're certain you will make bank. Don't bother about loyalty to the company because it certainly isn't loyal to you.


I've seen most of my pros and cons covered by others so I'll list my biggest con.

CON: Too many startups want you to be there in person. YC actively discourages remote employees. This is 2018. Remote work is not only reasonable it's beneficial. As an employer you can get higher caliber employees for less money. As an employee you get far more freedom and don't have to live somewhere you don't like.


One of the prime advantages for me is that I could find a company with women in leadership roles and I could interview everyone at the company before taking the job. I am absolutely willing to give up monetary compensation in exchange for working in an environment without sexual harassment, where I can have a significant cultural impact and with fair compensation & career progression.

The downside is that there isn't a good way to find startups where that is true (and especially not where it is actually true rather than just PR), and it is not what startups in general are known for. I networked my way into this particular spot, but if I were looking for another similar opportunity I'm not sure where I'd look.


There were a couple in the May Who's Hiring posts that probably fit your criteria, not sure about June, though actually reading all the individual posts takes quite a bit of time.


A perspective from India. I was at one of the big 4 when I made the decision to leave for a startup. (The salaries at FAAMG aren't quite so eye popping relative to other companies in Bangalore and are about 1/3th to 1/10th those in the Bay Area.) I tried to look for a founder for whom I could work for, but the conclusion that I came to, was that it made no economic sense working for an early stage startup (pre Series-A) as an employee in India. Equity had no value, particularly as it not only had all the problems that equity has in a Silicon Valley startup, but given the very weak legal system, it would be impossible to enforce contracts. Post Series-B the salaries are quite attractive by Indian standards (still 1/5-1/10 of bay area). So I went the founder route. The irony is that as a founder, this situation now comes to bite me. It is next to impossible for an early stage startup to hire engineers, even at market rates. You have to pay a substantial premium over market to compensate for the risk the employee is taking. This may be one of the reasons, that India will have trouble starting hard-tech companies. The startups that I see getting traction, are typically market focused -- e.g. food delivery, etc. So are not as tech-heavy as as say a SaaS startup might be, as they rely on scaling up a low-skill workforce (delivery men etc...)


A silicon-valley YC startup is mostly cons:

- cult-like obsession with working "hard" that amounts to pressuring people into burning themselves out

- have to be around people who act like everything is great and they're killing it all the time even though in reality running or working for a startup is super stressful and you're usually teetering on the verge of failure

- being compensated in the non-fungible scam that is options instead of equity or shares

- don't know whether you'll still have a job tomorrow

- make less money than you would at a bigger company

Some of those things appeal to some people, and the SV hypetrain tries really hard to act like they're great but mostly they're objectively bad.

I believe that 3/5 of these are avoidable though:

- People who work 60 hrs/week aren't much more productive than people who work 30 hrs/week most of the time. Productivity per hour drops off considerably for jobs that are cognitively intensive. Plus it's unsustainable except for a tiny sliver of the population.

- Unfortunately, my experience in raising money is that it's largely theater, and you have to pretend like everything is great all the time. That act ended up seeping into the rest of my interactions with people because there's a tendency to turn into whatever you pretend to be. I've had to make an effort, but I believe it's possible to stay true to myself and not become a caricature. I'll report back on how that works out for me after a few more years.

- The whole private equity system is fucked for employees and I hope crypto fixes the fungibility issue. In the meantime, anyone who pays their early employees in options should be ashamed of themselves.

Obviously, a startup simply can't compete with a big company on salary or stability, but being honest about the reality of the situation and offering real equity can help.


I don't know if I've been unlucky twice, but I think the biggest problem I see with working at a startup is the lack of transparency on runway and the security of whatever form of compensation I am getting. Twice now (in 2 diff companies) I have been stuck in the position of finding out with only a few days' notice that paychecks are not getting wired and we're hunting an investor to bail us out.

Somehow it has become ingrained that a CEO's job is to build everyone up and paint the vision. Well, that's great but somewhere along the way we forgot about the basics of personnel management. Think a co-founder is taking a chance by going without a salary? How about the dude with options and a family.

Sure, people know what they are getting into when they join a startup - or should - but I yearn for YC's next class on "Startup Ethics 101".


FWIW, we would consider that kind of behavior from founders to be utterly unacceptable - like Theranos-level unacceptable. I'm sorry that happened to you.


It's not even ethics, it's straight out theft. If you agree to pay someone for work, they perform the work, and you fail to pay them, that's theft. Or fraud, if you prefer.

Either way, they are crimes, and company owners who fail to pay their employees should do jail time.


I can’t think of any pros. Most startups I worked at had long hours and shitty pay, with a hefty dose of koolaid. Most lacked any sort of business plan besides “raise more money”.

Stock options at startups are worthless, since there’s no market for them and the terms are terrible.

Why make $90k at a startup with some worthless options, when you can work at an established company for $150k+ and get options that are already worth something.


You actually get to do something meaningful, at least to the company.

vs working at one of the big companies and doing fuck all.


"do something meaningful"

I don't see what about the problems YC18 are tackling are any more meaningful than FANG. Can you enlighten us?


Yeah, I look at Silicon Valley, and all I see are a bunch of webdev businesses. Sure, they dress themselves up as all kinds of different services, but ultimately most of the sweng jobs are webdev jobs. It makes me want to run the other direction, because the idea of doing webdev for a living makes me want to smash my fingers with a hammer.

On the other hand, where I live, in North Texas, the bulk of the tech industry here is telecom. Telecom work is far more interesting to me than webdev, and honestly if I ever move out of town, I'm going to be very sad that there won't be as many telecom jobs. And I sure as hell wouldn't ever move to SV.

On top of the work itself, I also find that I prefer the corporate cultures of enterprise B2B telecoms to webdev-centric startups. Going back to a B2B telecom after spending a few years working at other companies (first an abusive startup, then an academia-centric defense contractor) felt like coming home, and now that I'm home I don't ever want to leave the industry again.


Yeah okay.

You see, after the part your put in quotation marks I added on "at least to the company". This was meant to mean that the work you are doing is meaningful, but perhaps only to the company. Rather than working on a small part of a small part of a small part of the massive machine, you get to work on the entire thing because no one else is around to do it.

I really don't understand why I got downvoted for that. Not sure what part of the HN hivemind I upset with that, seems fairly uncontroversial.


> Not sure what part of the HN hivemind I upset with that

Intentionally or not, you implied that people working at big companies (which is a lot of the people here) are not doing anything meaningful.

Second, there's an immune response to this idea because it is part of the startup mythology that leads to a lot of people making economically suboptimal decisions about where to work, which is basically the whole topic we are discussing here.


You have 650+ responses already, so I accept mine will be in the `/dev/null` of history.

As somebody who has worked at startups, including a Y-Combinator startup.

The I have experienced three primary hiring issues that are so common they are worth noting.

1. People presume startups are inherently less stable than larger corporations. Risk aversion and the presumption that larger organizations are more stable in all cases, causes the candidate pool to drop. Helping people understand that competency is always in demand, would certainly help open up the talent pool.

2. Intentionally conflated salary figures have led to disillusionment with expected income. As many people already mentioned prior; how much are people really making? I have encountered several people who believe they absolutely deserve $250-350k, despite not having any requisite skills. Why? Often because recruiters have told them that is what they deserve... or because companies offering (often intentionally over-evaluated) shares, lie.

3. An unrealistic expectation of the number of hours they must work. Sure, there are some poor companies which believe hours-worked = value-added... but how many good ones? My experience has been that candidates expect they will have 60+ hr/week of work. Really? That's just not the case at companies with non-trivial intellectual property.

Want to convince more skilled developers to join the startup world? Dis-spell these myths.


Actually I'm reading all the replies :).

I agree with you very much that a real issue is myths that simply aren't true, or aren't universally true - working hours in particular.


Also compiling?


Definitely!


-A perspective from Chicago-

Early stage engineer at startups (including a unicorn):

pros: Fun work, you learn a ton, unlimited PTO (if you can actually use it), lavish benefits like free lunch, decent company culture, opportunities to try new things.

cons: Poor work life balance, low chance of a bonus, low equity if any, poor management/leadership, lots of hand wavey bs about being number 1, poor career progression, lots of over selling of what you'll be working on, Chicago isn't big on "cashing out" so most startup equity wont really net you much if anything.

compensation: Average for the market in Chicago, depending on where you land as far as talent and skills you can probably get 100k-200k base.

Big tech companies:

pros: great work life balance, annual bonus from 10-20%, decent career progression, more opportunities to specialize in something if that's your thing.

cons: Lack luster tech, no equity, lots of red tape, lots of mediocre/bad engineers, occasionally have to work with legacy code.

compensation: 100k - 250k base salary based on skills/talent/position.

From my experience in Chicago it really comes down to stability, work life balance, and trust. From what I've seen the big players are usually a lot more upfront about what you will actually be working on day to day and they provide a level of stability that others can not. On the other hand though you can grow a lot more as an engineer at a startup if you put in the effort.


> compensation: Average for the market in Chicago, depending on where you land as far as talent and skills you can probably get 100k-200k base.

Could you name any of these startups that you are talking about? I'm also in the Chicago market and I'm curious. It's hard to tell on Glassdoor or Paysa what salaries are and I definitely don't see many being in the 150-200k range.


Everywhere I've seen/experienced unlimited PTO has been utter BS. Usually there's a culture along with it of 'not taking too much time off' which kind of defeats the point. Would rather have a fixed number of days with a min required per year and maybe some year to year rollover/accrual of extra days for years of service.


Maybe Glassdoor and Angellist are not good sources but nowhere have I found any kind of jobs with that level of compensation. Then again, 100k-250k is a HUGE range and I imagine the distribution is heavily skewed towards the lower end.


200k is not hard to get in the bay if you have more than 4/5 years experience in a similar position or more than 8/9 years experience in the industry. For most unicorns that's the 75% percentile for base compensation in Sr. Software Engineer roles.

Edit for data: base at Google is 191k so I'm not that off with my estimation https://www.paysa.com/salaries/google--senior-software-engin...


There's several good data-points on compensation here: https://goo.gl/iHw7cj

It's also broken down by area of focus (ex. ML / AI pays exorbitantly well right now).


At a FAANG company my total (equity + base) comp is in the 300-400k range but the best offers I get at startups is ~140-160k w/ 0.0010-0.0040 equity.

Telling me that 0.001-0.004 of current equity pool (maybe-worth-something) > 150k cash now isn't usually convincing, especially if you have a lot of college debt and no safety net out of college.

This is just equity+base comp. I don't know how to price / factor in food, caltrain pass, healthcare, 401k matching, life insurance, discounts, performance bonuses, refreshers, and the fact that my job provides growth / would give me level match if I switched to a similar company (for example L5 SWE @ Google -> L5 SWE @ Facebook, vs VP of Eng at some startup -> L3 at Facebook...).

If you're good enough to get into Google/Facebook on a good team, it's scarcely worth it to join a startup as an early employee if you optimize at all for expected value.

That said plenty of FAANG employees feel limited career growth in the roles/teams they end up on, which is the main case a startup would look appealing. But also internal team transfers aren't that hard and you get to keep your nice comp.

One more datapoint: I have a friend who would totally work in startups despite high comp at a great company -- his blocker is US citizenship / worries for his family if the company goes under.


I think there's a bit of confusion around what market comp is. It doesn't matter that Facebook, Apple, etc. are willing to pay top of market at $500k - while they're big firms who employ a lot of people, I'd wager they're still not the majority of the labor market. It is also unrealistic to suggest that the "average" engineer has a high chance of being hired there.

I suspect true "market" rates are between $120-200k, depending on the seniority of the employee and the stage of the firm. A lot lower once you step away from US Pacific.

I think the best reason to be an early employee at a startup is if you plan on founding your own startup one day and want to get some hands-on experience. You won't make the strategic decisions, but you'll have easy access to the founders and will get to learn a lot about how to set up and run a company (both good and bad).

So why not just found your own company? Well, here are a few reasons: (a) you need financing but don't know how fundraising works and don't have a network to tap (b) you don't know how sales works (c) you don't have a good co-founder lined up (d) you're still a junior engineer and don't feel confident you could build a product by yourself (e) you haven't found a problem that excites you enough to feel justified working on.

I also notice a heavy trend in the comments here towards: employees should be rewarded almost as much as founders. I'm sorry, but no. A good founder will likely have spent years researching and understanding the problem space before finally trying to set up a company for it. They may be paying you with their own money. At the very least they had to starve long enough to raise enough money to pay you. They've taken on pain and risk. If you want to get equity comparable to a founder, go work for a pre-seed startup for free. In other words, if you want founder stakes, go be a founder.


Pros:

1) You almost always will own a larger chunk of the core product, and it's easy to point your finger to details that you played a big role in figuring out.

2) At good (small) startups, the transparency is enough so that you have trust in your leadership and understand how big decisions are made. At big companies, it's generally far more convoluted.

3) You gain a skillset outside of proprietary internal tools. This is often overlooked, but if you get used to the internal tools at your company, it means your skills are not nearly as transferrable if you used other industry standards. This makes you more valuable for other jobs.

4) Startups can be a great way to broaden your horizons and jump into a new industry.

5) There are things you will learn building a startup that you really probably won't learn much of at a big tech company. The decision to go to a startup isn't just a compensation risk tradeoff. Examples: you are typically exposed to vastly different parts of the company much more, and you more often learn how to build things from scratch.

Cons:

1) Salary expectations honestly need to be lower, and you need to be excited about the job despite this. There are lots of comments here about this.

2) Benefits and perks are less, but I typically don't consider this as big of a deal as most people. But, it's pretty objectively better at the bigger well-known companies.

3) Company culture can vary tremendously, and there isn't a great way to know much about this without actually working there. OTOH, you can learn a lot more about the culture of the big companies because there's a better chance you know people there =).

4) The stress levels are generally higher at startups. Similarly, achieving a good work/life balance is definitely harder.

I've honestly always felt that human connections play a decent role in helping a person figure out what they want to do. If their social and/or professional bubble isn't into startups, then you already have quite a mountain to climb, even if you think they would love it (and even if they seem to be genuinely considering it).


Some pros:

More ownership/authority/responsibility over the tech stack means more flexibility and opportunity to shift rapidly when necessary (lots of tech debt potential, though).

Smaller teams make communication more efficient.

Cons:

Compensation is generally terrible. We might expect lower base/cash compensation, but total comp (cash, equity, benefits) is also much lower.

The equity portion of compensation is extremely lopsided in favor of the founders and investors. Early employees are taking almost as much risk as founders. It's a different risk, but mainly in kind and less so in degree. There are no good reasons for the parsimonious grant percentages, the terrible vesting schedules, or the lack of protection against dilution.

Startups won't compete on this, and so when they complain about a shortage of willing workers it looks like they don't understand or care about really basic human relationships.

The fix for this is straightforward: pay larger cash salaries and offer more attractive equity (shorter vesting, more RSUs versus options) and better protection against dilution. A 0.5% equity grant should not mean "0.5% (for now)".


> Early employees are taking almost as much risk as founders.

Why do you say almost? I'd say most of them are taking more, as most of them won't have a seat at the board, IOW they have less control over the direction of the company.


Good points! Most of the time, though, employees draw a (slightly) bigger salary than the founders, at least until real funding (Series A or B) is obtained. Then unless the company changes its compensation model the balance definitely and clearly shifts: employees are taking bigger risks.


I bet they mean financial risk, as in personal investment in their own company.


I'd like to recommend something: discourage 1-year cliffs in vesting schedules. I recently joined a BigCo where your stock vests monthly as soon as you start. I felt comfortable accepting that offer because I knew I could quit without leaving money on the table if I hated it.

Before BigCo, I was at a YC startup for 8 months that I disliked working at, but felt that I needed to hit the 1-year mark for the equity. That startup was generous enough to ignore my cliff when I told them how I felt, but I don't think most companies would do this.

I think moving cliffs to 3 or 6 months would make startup opportunities much more interesting to job-seekers.


Sounds like Cap Table hell. If you're only there for 3 months, why should you get rewarded when chances are you didn't contribute anything to the company? I think a 1 year cliff makes even more sense for a startup than an established company because you really should contribute something before hitting the cap table as someone with employee options.


I think you can contribute a meaningful amount to a startup in 3 months. Arguably the top reason to join a startup is to make faster impact. I'm not saying this is possible at all startups, but most startups yes.

Options/equity are a component of your compensation and I'm questioning the reasons we wait a year to get it. I think it would be more employee-friendly to smooth out the vesting schedule.

Startups seem to be having a hard time finding talent (probably why this thread was started). Everyone already thinks you work on more interesting problems and make more impact at a startup, but it seems like those reasons alone aren't attractive enough right now. If startups can't pay $300k/yr cash, then they need to think outside the box to entice people to join.

What burned me working at startups was the 1-year cliff and 3-month exercise window after leaving. I'd consider working for a startup again if those two disadvantages changed. Until then, I'm very happy at BigCorp.


I disagree, I don't think anyone can contribute meaningfully in 3 months. I think a one year cliff is perfectly reasonable for a startup. We will agree to disagree, but I don't think any startup will agree with you, it rewards people who stick around for too short a period of time and makes their cap table much harder to maintain.


That's an interesting proposal that we will discuss. Thanks.


I second eliminating the one year cliff. This is becoming market-standard. And not just for the employee's benefit. It's a lot easier to tell management their heads are up their asses when you're vested. Good for the company.


Good one. This is entirely consistent with the thought behind the 10 year exercise -- don't shackle the employee.


Hi Jared, I'd advise you and your team to take a hard look at GIPS (global investment performance standards) and create a similar model for startup equity packages.

Call it whatever, but the standards would have employee friendly terms so that people joining early stage companies would actually get something if the company liquidates.

Little stuff like recruiters need to not say stuff like "we are already valued at X, so that is great"... wut?

Or...

Big stuff like: 7 year option excersize term instead of 3 months. (Gross).

No one who understands the asymmetry of joining a startup would do it. Only people who dont know any better.

This is your opportunity to use YCs power to get people interested again.


Thanks for the pointer to global investment performance standards - that's a good analogue.

We already agree about 10 year exercise windows (https://blog.samaltman.com/employee-equity) but we need to do more to make it a standard.


The brilliance of the GIPS is that firms cannot be partially compliant and it is 100% optional.

The reason a 10 year excersize window is meaningless on its own is that you cannnot control or know how your share class will be treated after you leave.

You need a set of standards which clearly allows employees to capture value. Otherwise it is all marketing. Smart people will see through that. As they already are.


Per your other comment on CEO ethics - the CFA Institute - GIPS creator, while focused on public equities, has great materials for illiquid alternatives as well.


This is a bit nuanced, but i'll try to be brief:

- housing in the bay area is substantially more expensive now, so you need to already be pretty qualified in your role to justify your cost - this partially goes against Paul Buchheit's old point that startups allow you to do work you'd otherwise be unqualified to do - because startups work on building (rather than maintaining) products, the tech skills that startups want are different from the tech skills engineers in big companies are using - universities aren't really making up the difference

Options: - YC makes its own university for engineers/scientists

This goes along Alan Kay's point about not relying on vendors. If there's a particular skillset that YC cos want early engineers to have and people don't have it (at the scale YC collectively wants), it may make sense to teach it.


San Francisco needs to build some frikken housing if it wants to keep adding jobs. That so much of the city is covered in single family homes is an affront to everyone trying to work here.


The Work at a Startup resource is great. We've found it to be an excellent hiring resource.

As other folks have noted, the pros/cons of working at a startup vs an established Silicon Valley tech company have shifted over the past couple of years. I think of venture-backed tech companies as falling into three broad buckets:

  1. early stage startups
  2. "post-Series B" high growth
  3. large, publicly traded
At a startup, you get to see a lot (both good and bad) that's highly relevant if you want to start a company yourself at some point. You have much more responsibility earlier in your career than you will have anywhere else, and you get an equity lottery ticket.

At a high-growth company, you have the invaluable experience of seeing growing pains first hand, your equity is much more likely to be worth something (statistically) than at a startup, and down the road people in the San Francisco startup ecosystem are likely to look at this experience on your resume as uniquely valuable.

At a big company, you have great work/life balance, great guaranteed (or quasi-guaranteed) comp, and -- sometimes -- you have unique resources available to you.

I wrote a blog post earlier this year about this that goes into more detail: https://medium.com/@kwindla/what-kind-of-silicon-valley-comp...


Employees are more aware now that the startup they work for isn't going to be the next facebook or google so perpetrating that myth and offering below market comp with some equity isn't attractive to top employees anymore. As many have stated, competing on comp and benefits is a tall order so looking for other ways to compete would be useful. Focusing on location, an enjoyable work environment, and quality of life (not fake unlimited time off) would entice those who want to work for a startup but can't justify the tough work hours combined with low pay.

Most startups are located in the Bay Area and the cost of living there combined with lower salaries make it an unattractive proposition for early employees. Encouraging remote work is a great way to attract employees who may not want to live in SF, NY or Seattle and are happy to work for less than those in the major hubs. Or move the startup HQ out of the valley if remote just won't work. Competing for workers in places where the big players aren't will give them an edge and greatly increase the value proposition they offer to early stage employees. This combined with proper quality of life focus and increased autonomy and responsibility that startups offer would change my mind about working for a big firm and make me consider a startup job.


If the comp, stocks, big $ is your primary motivation, look somewhere else.

We go to the startup for a thrill. For doing something you strongly believe. For creating something that didn't exist before. If you think you can do it in a big org, too, you are right, now go and try, get a job at Cisco or AT&T. Innovating there is like driving Kia Rio vs Porsche: it's a car, too. It goes thought the motion. But the thrill is not there.

Many people are happy in big companies. They won't be happy at startups. They're no worse because of this. Different stokes for different folks. There is no objective pro's and con's for startup vs big corp. There are properties, that match personal traits. The key is to know yourself and what are yours. Trouble is, we don't always know what we want, worse yet it changes over time with experience. And once we finally learn it, it's time to retire. Life is fun.

Now, you don't want to be taken advantage, right, so all written here about transparency, cap table, etc are the right things. Do check. Don't take below-market salary for the mirages of future. If you don't do these basics - you failed intelligence test and shouldn't be hired.


There aren't nearly as many people out there who want the thrill of working for a startup more than they want higher comp AND can afford to miss out on big-co comp as there are startups wanting to hire them.

If startups want to be able to fill job openings (the question posed in this Ask HN), they have to be able to offer something besides thrill.


Second paragraph is great. I haven't worked at a startup, but my experience in a big company is that you can definitely innovate, change things, and make things better.

But I wouldn't call it thrilling, I'd be interested to see how many startup employees found it thrilling.


I joined a startup 5 years ago as a CTO for 10% equity.

Fast forward 5 years. We merged with another company and we got 60% out of that merge. So then I moved to 6% equity.

Then we raised $15m in various rounds. My equity is now at about 3%.

In our last round we were valued at $20m. Well, all the investors have preferential pay back rights.

My equity is fully vested. If we sell for $20m today I will make a grand total of $97,000. If we sell for $30m it would be $397,000 and at $40m it would be $697,000. To bring our valuation from where it is today to $40m will take a few more years and be pretty difficult.

So I personally advise you not to join a startup and instead start a small side project and take a large salary at an established company. It's actually easier to make that level of money over 5 years even with a moderately sucessfull side project and large salary.


I had the opposite experience. I also joined a startup 5 years ago, and I was one of the very early employees. I received 0.5% equity as stock options, and my salary was around $120,000.

I stayed for a few years, and now I own around 0.1%. The company is now worth a few billion dollars, so my stock is worth a few million dollars. I have no liquidity yet, but an IPO is certainly on the horizon.

I don't feel like I took a pay cut. It was my first real job as a software engineer, and it gave me some good friendships and connections.

I can't say I learned a lot, and I didn't grow very much. The work was very boring and there weren't any technical challenges or interesting problems. I just got very burned out with the long hours and pressure. But it was nice to live in the Bay Area for a little while and have the "silicon valley" experience. I got very lucky and might be able to retire in a couple of years, so of course I'm going to say that the risk was worth it. But I do realize that I'm an outlier.

My advice: If you can somehow spot a potential unicorn and you'll be one of the first employees, then drop everything and join it.

Look for a YC company with some impressive investors, and try to get 0.5% - 2%. But I've noticed that YC has started funding a lot of companies that seem pretty terrible, so you have to be very careful. Don't think of yourself as a employee. You're a VC who invests their time and energy.

If the first one doesn't work out, then do it a couple more times. Work on your own side projects and see if any of those take off. The connections can be really valuable, and working at a startup is a great way to find future co-founders.


Don't take this the wrong way, but you are living in a world of confirmation bias.

There are 288 companies in the world with a valuation of > $1b [1].

There is most likely over 100 million companies in the world [2].

With these numbers in mind you will have a 0.000288% chance of joining a unicorn.

Except, 50% of all new business fail within five years [3].

So, you will have a 0.000144% chance of joining a unicorn.

My company is doing well (approaching $4m revenue). I have already hugely defied the odds. I am one of the sucessfull ones. My return for a 5 year investment will be $600k at best. My story is a VERY common one. Yours is impossibly uncommon.

> My advice: If you can somehow spot a potential unicorn and you'll be one of the first employees, then drop everything and join it.

The advice you are giving is for people to drop everything for a snowball's chance in hell.

[1] https://www.weforum.org/agenda/2016/06/unicorns-do-exist-and...

[2] https://www.quora.com/How-many-companies-exist-in-the-world

[3] https://www.inc.com/thomas-koulopoulos/5-of-the-most-surpris...


Agree with the points around increasing equity and comp. One thing about option plans is that the devil is in the details. How things play out in a liquidity event or the tax ramifications can be large based upon how the plan was set up years prior. My guess is founders probably don't spend a lot of time sweating these details and the lawyers are concerned about protecting the company. YC could help by pushing for plans that are employee friendly. Publish articles about how to set up plans in a good way. Publish articles about what employees should look for when comparing offers. Possibly publish legal docs that companies can start from similar to other sets of documents you've published.


Those are great suggestions - thanks!


Employment contracts and more equity may be the answer.

Contracts are already a feature of some companies for some employees. It would be very interesting if all good startups started doing this for all employees. It might make them a lot more competitive with the big players.

It could guarantee that employees walk away with some amount of fully vested stock and cash regardless of why they leave. It could promise a minimum of raises/bonuses/equity on a schedule. It could also formalize things like remote work, equipment, schedule, vacation, insurance, etc.

The idea would be to formalize in legalese the exact nature of the business relationship. Treating the employee with the respect they really deserve, and not like a disposable "at will" cogs. It puts more of the onus for an employee's success on the company. Any good startup should be happy to do this. The bad ones would likely resist it.


Contracts are tough when the employer isn't able to honor them. That forces the employee to vet the fairness of the offer and the employers ability to pay it out if needed.


Hard to contribute any more to this. Most of the pros and cons have been given, and are well known anyway.

The problem space should probably be constrained to, pros and cons of joining a startup in 2018, in SV, now vs 3-5 years ago. Otherwise this isn't going anywhere interesting.

My take on it is, founders should be encouraged to only take 3x equity of early employees, not 10x or 20x. This risk is the same, and the founder's contribution is generally small relative to their equity. Ideas are plentiful. Execution is hard and matters the most. A founder cannot get it done by themselves, the entire early team really, really, really matters. And the typical founder is so inexperienced as to really lack what it takes to execute. The point of only taking 3x is not to penalize founders, it's to recognize the early people. It will help equalize the financial problem of joining a startup.

The second major problem is that there are too many startups. I'd suggest YC should halve (at least) the size of each class. Y'all (incubators, angel funds, etc in general) are throwing too many darts for your own benefit, to the detriment of the actual employees. By over-stretching the talent pool for startup employees, it discourages top talent from joining because they know it's that much harder to recruit the best.

I'd suggest also that YC fund/subsidize shared housing situation.

I hope that my comments address specifically problems of SV and problems of 2018.


A long overdue recession will solve many of these problems


I have worked at several Fortune 1000 companies and several startups.

One of the cons I see in even very small startups is trying to be like Fortune 1000 companies. There is an understandable reason for red tape when working at a F1000 company. But why very small startups overly burden themselves with red tape, convoluted procedure etc. is a mystery to me. Anything getting in the way of shipping on the way to product/market fit should be cast overboard.

Another con - the advice here and in related milieu (Eric Ries etc.) is to make a minimally viable product, ship as quickly as possible (within months), then iterate on that MVP. This is very sensible for most startups. But even in very small startups - the founder gets hung up on some feature details, or wants too many features. They want too high of a quality in their first release. Ironically this can become self-sustaining - the longer you wait to ship, the higher the quality bar becomes and thus the more time you need before shipping. You get into this mindset and soon you're starting development of Duke Nukem Forever in 1997 and wind up shipping it 14 years later to a giant thud.

Then there are the various financial cons which people here already talk about. Even with a good team and all of that, odds are 100 to 1 against you making anything more than you would working for Alphabet/Amazon/Apple/Google.

The pros are you can get a larger chunk of equity than at other places (though as others will say, there are many caveats to that). You can have an outsized impact on the company. It is more informal and less rigid. And if you get into a company with good people on an upward trajectory, it can be very, very good.


> They want too high of a quality in their first release.

I've actually have seen the opposite. Usually it's a very crappy early product and then when the company grows they get bogged down. (They'll never address testing, tech debt, etc)


I was one of the first employees at a fairly large dotcom 18 years ago and via a circuitous route through industry and academia I find myself back at a startup now.

One mistake I see early-stage startups make over and over again is low-balling key positions with the consequence that good engineers/designers are not retained but less-able engineers/designers are. As the company ages and the remaining OK-ish employees gain more power, a culture-of-mediocrity-death-spiral sets in which is hard if not impossible to escape from: products don't ship, sales suffer.

There are lots of good reasons NOT to work at a startup: Outside of startupland it is now easier to land a well paid gig at a big tech company than at any time in the last 15 years. In the public/state sector technology workers have experienced steep pay increases due to the intense pressure to digitalise. Consultancy and contracting remain lucrative, with established players constantly on the lookout for new hires, and individuals often able to multiply their pay by switching to contract employment.

I feel like the opportunities to influence and be promoted within a startup are in some ways overstated. In my own experience this has been just as easy in larger and more established organisations. Startups often lean pretty heavily on this argument and I am not sure if it is actually true for anybody outside of the founder's circle.

Startups often tie themselves up in knots trying to find out how to attract early employees, when really it just comes down to pay and conditions. Treat your early employees like functioning adults by offering decent pay, pension, holidays and benefits and great applicants will come flocking.


The biggest pro IMO is that you get to see how a startup is built without having to take all the risk as a founder. Not everyone is in a position to jump in to a risk taking venture on their own, or have the ideas that lead them there. This includes not just the technology, but also a wide exposure to product, marketing, sales, finance and the investment ecosystem.


I consulted for a certain 'unicorn startup' based in India during their stealth stage. I joined another (now defunct) startup as employee #2. Worked my @$$ off for 3 years before I called it quits. From my own experience:

Pros: - No layers of management BS

- Startups seem to be more flexible about work hours and remote work

- More wiggle room to experiment; open to embracing new tech

Cons:

- Inexperienced leads, managers, CXOs. I can't stress this enough.

- Uncertainty. You gotta have a bag packed, ready to hit the streets at short notice

- Slog it out as an 'early employee' for years and watch the company go down the drain. That is the story of most startups. The chances of making it big are astronomically low.


While I absolutely agree with the comp aspect and think that's probably the biggest point, I want to add that management skill is also a huge factor. I've seen a lot of startups (YC and otherwise) fail to grow the team well because the founders are good hackers but not good managers. In a large company your manager has a manager who will help guide and review them, and you can switch teams without risking your current compensation and benefits or your vesting table.

At a startup there simply isn't room to move around without taking on more significant risks and at least waiting for your first equity cliff, and honestly many startup founders I've met don't have great managements skills, or the drive to learn them. There's also simply a matter of personalities, sometimes people just don't get along with their managers and/or teammates, but the fact that you have to switch companies and re-interview again vs being able to apply to your skip-level to switch teams is a significant difference.

Some ideas of concrete options to fix these:

* Shorter cliffs, even Google has a 2 month rsu cliff now, and I think Facebook is similar

* Maybe a hiring pool, again, similar to Facebook or Google where you pick your team after you "pass" your interviews, allow you to really work with different startups and feel out what it's like. I could see YC setting up a similar program where companies can choose to share an interview pipeline and let candidates talk to different startups after passing an agreed-upon bar for the pool. This is similar to https://www.workatastartup.com/, but to not have to formally do a technical interview for every single startup would be a huge help.

* Some way to try out/transfer between startups who allow it would be awesome. Similar to Facebook's bootcamp, if there was a way to still get paid, maybe a simplified consulting agreement that YC can help broker among a few startups for a month or so while a candidate explores what it's really like to work with each startup would be really helpful.

* Management training for founders, and a standardized way to review founder's management skills. If founder's were held accountable for their management skills and rated across one of these shared pools where their ratings were available to prospective employees, they would be much more incentive to improve their skills.


Those are all excellent suggestions, thank you.

I'm intrigued by the idea of a "way to try out/transfer between startups who allow it". Would anyone else be interested in that, if we could broker it between a set of companies?


Along the lines of other comments: Consider creating “YC Engineering, Inc.” Good engineers are concerned with their career path more than comp packages.

One function of YCE could be to enable engineers to swiftly choose projects rather than companies. An ML expert may work on optimizing income for AirBnB hosts for 6 months and then switch to working on a project at Coinbase Prime. Maybe they like Coinbase Prime and migrate to that full time or maybe they want to explore more with ML and switch to optimizing Cruise routes.

This would also be useful for startups since “fire fast” is a challenge for some. It would seem easier for founders just to tell you “this person isn’t working out: they may be better suited for a more mature YC company.” At that point you could pull that employee and have them placed at a better suited company.

Lastly I think it is a good opportunity for educating engineers. If a good engineer is proficient in Python but YC needs a lot of blockchain/financial engineers (e.g. Coinbase’s ridiculous hiring growth) then there could be opportunity to guide that engineer to such a path if they’re interested.


> Some way to try out/transfer between startups who allow it would be awesome.

This is a fantastic idea that I really think we should explore within the YC ecosystem!


In addition to the risk and opportunity cost and work-life balance issues that everyone's already mentioned: immature organizations. Both in the sense that the organization itself hasn't yet matured and that the people running the show are often immature.

This is particularly prohibitive for underrepresented groups - a combination of colleagues too inexperienced to know what professional behavior actually looks like, nobody more experienced to model better behavior, and nobody to turn to when things go horribly, toxically wrong.

The superfund site cases are thankfully rare, tho we've seen a few of them discussed here. Even some of the big names (Uber and GitHub come to mind) have hit the news with significant issues that have made employees feel marginalized. And that's just the ones that have made the news. Even if the problems are relegated to only 5% of the startups out there, that's a risk for a job seeker.

Moreover, the weird kool-ade assumption that the team has to all bond and be best friends and voluntarily go out for beers twice a week as long as the company is <25 people is off-putting. Especially for those of us who are more than 3 years out of college and already have friend networks and in many cases families we want to spend time with instead.

I would also mention that there are some things startups are great for in terms of learning, especially as a junior. You get exposure to a lot of things, the chance to wear different hats, challenges that in a larger company you'd be sheltered from by the presence of seniors.

But a very small company isn't always great for mentorship, especially in management. (My experience with management at early stage startups has been awful.) Even when management is excellent, startups are typically too small to have layers of management and opportunity to learn leadership and management skills.

Further, startups tend to be devoid of opportunity for advancement or promotion within the company unless they manage to grow very quickly - which is rare.

And when they do grow quickly, they typically grow too quickly to grow well. Hiring too quickly to preserve culture. Outgrowing processes and then taking 18 months to realize it. Hiring incompetents or toxic personalities because they can't find enough bodies to fill the seats at the at-best-median salaries offered.

And then there's the inevitable 18 month long "we'll be out of runway" death march. Never again.


Pro: how much you learn.

My first engineering job was at a startup. I learned an enormous amount in a year because there were never more than 3 engineers in that period.

I had to learn the basics - git etiquette, how changes are managed, how work is planned. But I also had to learn almost every technical layer. One day you're setting up DNS records for a new subdomain, the next you're choosing a JavaScript test framework, the next you're working with the CTO on designing an offline job-processor. It's a great breadth of experience that's hard to get at big companies, where projects typically have much longer timelines. People stay on one team, on one project, for years.

At a startup, you do it all in a mad dash, probably absorbing technical debt, which is also important. "Shit, the database migration didn't work, I just took down the site, shit shit shit" is a really important lesson that you can be hard to get at a big company.

I've worked at companies ranging from 3 employees up to 50,000+. Definitely learned the most at the smallest scales.

I see this when hiring, too. It seems from my experience that an engineer with 1 year of experience at a startup is typically much better-prepared than an engineer with 1 year of experience at Google (sample size < 10, I am likely biased by my experience and expectations, many exceptions possible of course).


I've been a repeat startup employee, and have now become a founder. The reasons I chose to live this path haven't changed.

If you have a comp.-driven mindset (i.e. you'd like to become a millionaire in X years), then I think there are far faster, better, easier ways to achieve that. Join a top-tier firm in the valley / NYC and do a decent job at getting promotions and you'll be well within your way by your mid-late thirties.

The best part of being part of a startup is your ability to be in fast-paced multifaceted problem-solving environment.

You can play quiet a few roles at a small company. As an early employee (engineer or otherwise), you can look at any part of the company, product or its internal operations and decide that it's something you care enough about to fix and improve upon.

I joined my first startup as an engineer, became a product manager, did sales, built employee on-boarding flows and training manuals, re-branded the company and learnt how to manage a sizable team as I moved on to marketing. All within less than 2 years.

You can get most of those experiences elsewhere, but not within that timeframe or the depth of autonomy you would receive to get it done is not attainable in a Big Corp.

This is exceptionally great if you're early in your career, are generally good at getting tasks done, but have no idea what your calling is. You can work at a startup (or a series of them) for a few years and walk away with understanding what you'd like to focus your time and money on for the next few decades of your life.

Only caveat that I would add is that if you'd like to achieve any of that, then it's paramount that you look for the right founders. Founders that are willing to give away autonomy and let you flourish. They tend to be the best ones and produce great companies with incredibly rich cultures as a result.


A lot of comments are complaining about the comp and the cons of a startup, I think when you join a startup you are basically making a decision that is risky and challenging in the first place especially if its a no name startup and the comp is really just part of the risk you acknowledge.

The real pro of joining an early stage startup (note: not a famous one with billions in the bank) is really I would say the satisfaction of being in a life-changing startup and grinding with a team, ultimately its really the developer experience you're going for. (Otherwise if its a unicorn, you're probably going for brand recognition, flexibility and comp)


Pro: You get to build things from scratch, I like this one most.

Con: You find yourself at the end of the work-life balance, which might not be comfortable for everyone.

It's a great initiative, today itself I was thinking if there can a common test to get a job, but then I realized companies do not just test the engineering or field knowledge.

PS: I thought refreshing the page will show an early day picture of dropbox/reddit/stripe/instacart and so on.


> Pro: You get to build things from scratch, I like this one most.

That hits the nail in the head! Having exprience in building things from scratch has to be invaluable down the road in your career.


I work at a startup (Reforge) and I own a startup (Casting Call Club).

I turned down a Google offer to do these startups.

Here's why:

1. I have full control over building things from start to finish without politics.

2. I work remotely, setting my own hours. All of us have been doing what we do for 10+ years. We care little about the hours put in and care a lot about the impact made. I can do this from SF (used to live), or Boston (where I live now), or Bulgaria (to visit family).

3. I learn so much about the whole picture, rather than a niche.

I love Google (and my previous employer Eventbrite), and might return to them one day. For now, startups match me.


I was a lawyer for a big SV law firm for 2.5 years doing company options, VC funding rounds and M&A. Then I was an early employee and engineer for a startup 5 years. I've seen this from multiple angles and the folks with a lot of startup experience will tell you that it's not worth the money - you're doing it mostly for non-monetary rewards. Engineers deciding between FAANG or a startup should not kid themselves with founder hype.

What can YC do to help? - Provide transparency in the form of data, particularly into outcomes. For a typical YC graduating startup, what % of them have an exit within 4 or 6 years? What is the distribution of outcomes for a 1% common stock holder? Only then can engineers properly value their options. Founders will typically multiply the equity by the last funding valuation or $1 billion and claim that is how the employee's options should be valued. Only someone like YC has the access to do this type of analysis. - There's a lot of incompetence and bad behavior by founders that investors and outside board members don't see. If you really want to understand what is going on, always have an inside channel. You should also provide these inside channels to all interested board members and investors. Not everyone is willing to do talk but someone usually is and ex-employees are usually willing to. You don't have to always do something about it but failing to talk to employees and only relying on founders to tell you what's going on is just sticking your heads in the sand. - Options are broken. No employee should be required to fork out $50k to buy something that (1) they already worked very hard for, (2) potentially has no value, (3) will completely forfeit if they can't come up with the cash in a month, and (4) may even have to pay additional taxes to acquire. There are a few ways YC can help: (a) Establish a standard among new YC companies docs, stating that employees should have up to 12 months after termination to purchase the shares. Better yet, establish a standard such that employees should be allowed to keep vested options and not exercise until a liquidity event, no matter when that might be. If you guys set that standard, then maybe other companies may follow suit. (b) Advocate a change to tax laws so that exercising options does not have such negative AMT tax consequences, except when there is a liquidity event.


I like the idea to use YC's dataset to calculate expected outcomes based on actual historicals a lot. That's a great idea!

Options have been mentioned before - we 100% agree we need to fix this and are going to work on it. https://blog.samaltman.com/employee-equity


And again, remember, the important thing here isn't only the upside for the founders, but also for the early employees.


One giant risk is spending your formative career and life years being subject to the psychologies of young under developed founder(s), artificially granted empowerment to hire and manage employees by VC speculation.

This inexperience is a helpful pre-rec for ideating concepts and building innovative products that create massive value for the markets, but it's a crap shoot with low odds for being an effective manager: These are not people who rose through the ranks in management by demonstrating finesse in motivating groups of people into effectiveness. These types of people don't come into the company until Series B, C if ever.

Furthermore, founders are typically in hiring mode after they have secured financing - which means you only get to know them while they are not under as much pressure. Dealing with founders while they are under the additional pressure of fundraising is when the more vivid colors of personality (and harsher interactions) come out.


I worked at a YC startup with a pretty good exit.

I was employee #40. I made about $100,000. The co-founders made about $100 million each. If I joined a FANG, I would have been granted $500,000 in RSUs, and they would have tripled in price during the time I was at the YC startup. Unless you turn into another Uber, the vast majority of wealth goes to founders.


30 here with a lesson for younger guys. Ask for more compensation not stock options. If you’re offered stock options ask if they can swap it for an increase in compensation.

You vest slow, you may be fired before they vest, hell, the company may go under before they are even worth something.

Take the money.

Or take stock a few times and learn the lesson the hard way.


No startup is going to offer meaningful salary increases in lieu of stock options. You might eek out 10% more, you're still going to come out far below an established company offering liquid stock compensation.


I've been working at startups -- small and medium -- exclusively since I got in the field. I don't know if I'd have it any other way. When I visit my friends at the big companies, something about the rigidness and massiveness feels cold and out of touch. I like being able to see my CEO on a daily basis and have a relationship with him.

I think that's worth it to me, because unlike a lot of people, I'm not in this field for the money as much as it's just something I love doing. I spend my free time writing code whether or not I'm getting paid. At a big company, I suppose I can accomplish the same, but the difference is that I am afraid I will not know to what end my software is being used, while working at a startup I know exactly how everything fits together.


I worked as an engineer at a startup early in my career (looong time ago). Company went under, stock => $0.

However, I am extremely grateful for that time. It taught me a wide range of non-technical skills that have proved invaluable throughout my career.

Most of those non-technical skills revolved around leadership opportunities, being given huge responsibilities vs. my skill/age (and having to figure it all out on my own), and getting to participate in many aspects of the business.

It ingrained in me ownership; and I've never been able to shake bringing that startup mentality to everything I do at a larger company.

Just my experience. Much of this perhaps is achievable while at larger companies, depending on the situation.


I definitely echo the feelings about compensation at startups. They massively over-value their equity because there is no risk adjustment, they just assume that the face value price of the shares is how you should be valuing the equity, which is obviously total nonsense.

One surprising thing I encountered when leaving a startup was that non-startup companies would value my startup equity at zero when presenting offers, making that deal even worse.

I definitely felt like the founders were being completely disproportionately rewarded to everyone else, which drove some amount of resentment on my part.

One of the pet ideas I have is that founder/employee shares should have some sub-linear returns with the value of the company, with the gap being redistributed to people down the value chain. E.g. once the founders have gotten a few million from their shares, part of the returns should start going to early employees, and once they have some amount of money it starts going to later people, etc.

Another idea could be for employees to be paid with options for an entire YC batch, rather than a single startup to reduce the risk associated with being paid in equity for a single startup. This is tricky for various reasons, but tries to reduce the risk without meaningfully changing how much capital is needed.

When I lived in the Bay Area I was pretty surprised by the amount of startups in the South Bay, living in SF and then Oakland, I basically refused to commute down there because of the shitty transit situation.

There are "pros" for startups, but most of them depend a lot on what the alternative is, if your alternative is a high performing team at a well paying company, there aren't a lot of things in the pros column, but if your corporate job doesn't pay great or is sucking the life out of you, then startups could be great in comparison. So maybe the right way to frame this is more of an "is this right for you" question, than is it objectively good.

[EDIT]: Providing ways for employees to cash out their equity would do a lot to de-risk things too. Particularly for employees who have are leaving and there is little reason to keep them aligned and are willing to make space in the cap table.


Background: Mostly startups (10 person, 30 person, 3 person accelerated at Imagine K12) but also large companies (Amazon, Bosch, Oracle)

Pros: 1. Depending on your own personality and the size of the company, regardless of your role you have the opportunity to actually drive direction across the company. 2. While titles aren't important in my opinion, startups do allow you climb the proverbial ladder faster. I became head of engineering 5 years in, that opened doors to skills I didn't think I'd pick up and opportunities I didn't think I'd have until I was 10 years in. 3. It is mighty fun to work in a small team and see results of your work everyday. You care a lot more about customers, product, your team. You learn empathy.

Cons: 1. The stock option sell - lets call it what it is, it is nothing but a justification for a pay cut with the sell of riches in the future. Every time I hear the stock spiel (shpeel?), I nod my head but I forget about it and always try and negotiate a salary that works for me in that I'd be happy to give a lot of my time for that amount of money. 2. If you start your career and remain in a startup for a long time, it is very very difficult to transition to a large company if you want to {political klout, diplomacy, all skills you pick up at a large company are harder to pick up at a small startup}. I found this very hard when I transitioned from startup head of engineering to management at Amazon and quit within a few months


Maximize for learning and personal growth. Startups provide the best place for this. If you have any dreams of being a founder your self, you need to spend time in trenches.

If you are a "career" man or woman, I still say spend 4-10 years at startups, then go grind with the usual suspects. By spending time at a startup you acquire a diverse/well rounded set of skills that make you an exceptional team member at big companies down the road. Forget an MBA at anything but a top tier university, do startup(s).


I used to think your first point was correct, but it's actually not. If you look at the founders of startups, very few of them have worked in other startups. Usually they ladder up as the founder of progressively larger ventures.

The other pathway is a prestigious college / MBA program or working their way up through one of the big tech companies and then leaving to start their own thing.

I've seen very few "former lead engineer at X startup founded their own company" stories, and that was literally what I was trying to do with my career for probably 5-7 years.


Note: this is my perspective, one as a software engineer who has mostly worked at startups and now currently at a FAANG

Pros:

- Often easier to make lots of impact/move up quicker

- (Potentially) less bureaucracy around decisions

- (Potentially) lots of vacation

Cons: - Typically not as smart coworkers

- Often can get into more dysfunctional situations, whether by process or individuals involved

  - Not good managers/engineers also have outside impact. One company I have worked for had half of engineering leave or be laid off in the span of half a year, and most of them were above average engineers (and on the upper half of competence in the company as well).

  - Poor management structures and managers really decimate engineering.

  - Bad/toxic engineers also wreck havoc.
- Compensation is significantly lower

  - Senior engineers can easily make over $300k at a FAANG if they are good. Stock options at startups do not come close to keeping up to pace with top performers, and are pretty much regarded as having no value given a lot of the shenanigans/risks engineers have to put up with to maybe get an exit. Startup compensation would have to change drastically to get many to even think about taking that risk, and as a result, the risk of a startup failing increases due to less competent engineers being hired, which decreases the startup's velocity and increases the startup's likelihood of acquiring damaging technical debt. The worst part about this is that startups try to be demanding over all sorts of random small things in the hiring process, yet don't hold themselves to the same standard when it comes to compensation.

  - The big tech companies have special benefits as well, such as employee stock purchasing programs, or paid sabbaticals. They do a better job of compensating for loyalty than startups do.

  - Dilution of stock value and the stock value opaqueness in VC-funded companies make engineers skeptical of their value. In addition, the preferential treatment of investors over employees for stock selling/allocation gives a lot of people distaste over the sweat capital dichotomy.
- Increased likelihood of stress from not being allowed to address crippling technical debt or make things better so the company could operate smoother.

Just some things from my top of mind that I've observed/experienced. After spending about 4 years at startups, I'm not sure I'll ever go back - I was not a low performer either at any company I have worked at. At my last employer, one employee remarked that they would need to hire 3 senior engineers and a manager to replace my technical & managerial output & make up for the decreased output/morale of the team.


As a pro, methinks "everything needs to get done" is the main one. It's a trait shared with all small companies, and can be petty things like buying the coffee to coming up with a plan to do X and overseeing it because nobody else has time. If you're able to take initiatives the startup/SME world is for you.

The main con in my personal experience is the grueling entitlement of some founders. Not saying this applies to any or all YC startups (never worked for one) but there are founders out there who expect an arm and a leg and then some, fully expecting their employees will work long hours for peanuts. I'm assuming this is less of a problem at YC companies since they seem reasonably well funded and able to actually pay employees properly (if not you're doing a good job at PR but shame on you), but it's worth raising if only in passing.

Another big con IMO is lack of experience of quite a few founders. The best way to frame this might be a lack of insights in the industry they're targeting. Rewarding turning a business model into something that can work with a pittance of cash and equity is not very enticing to say the least. I've seen this play out from within and without and it's just plain ugly to see whoever came up with the bright idea being thrown a bone as means of thanks while the founders and their VCs laugh on their way to the bank. With respect to this, methinks try to teach humility to founders you work with: if an employee or a consultant shows a much better way then by all means invite that person to the team as a cofounder or nearly so. It doesn't matter if there has been 3 or 5 years of work poured into a hopeless idea before that. I've seen more than a few startups where someone put a brilliant improvement forward only to be shown a bone as a reward, finding a new job as a result, and the startup eventually going nowhere or failing from lack of execution.


Pro of startups:

- Get responsibilities you couldn't get at a big company. Don't have a graduate degree in underwater basketweaving? Wearing many hats at a start up means you might get to do some basketweaving anyways. A few years of experience and wins to demonstrate with that and now you can get good basketweaving jobs everywhere.

- Learn about lots of things. Learn a little about a lot. Learn what niche work you like. Learn learn learn. (caveats below).

Cons of startups:

- Terrible comp. Enough said elsewhere in this. Also, handcuffs are weird, and the current tax system means that if your company does well, then the IRS might handcuff you even harder than the company does.

- Environment that encourages overoptimism/kool-aid. This is true everywhere, but startups seem worse. That lottery ticket? Going to be worth millions for sure! Our competitors? They're idiots! Our employees? The best!

- Terrible work life balance. Everything is on fire always, and you're running out of runway and "passion" is so important.

- Fewer experts to learn from. Startups have fewer people, tending younger and greener. 30 years experience at OldMoneyCorp? That's an old stagnant legacy company, so that experience doesn't count. Oh, and they have kids so won't work here anyways. This means you'll do more things wrong and spend time learn things you didn't need to. Self guided learning is hard and has lots of backtracking.


Im now a founder having previously worked in a startup as an early employee and in a senior role as it expanded.

As with many people here I had little faith in options. And now having more visibility as to how share structures evolve this has lessened even further. Despite best intentions as things progress the value of options and non-founder, non-VC held shares frequently take a whack. There is also a whole host of problems including liquidity and tax issues.

Ive have however seen some traditional companies structure early employee incentive in a completely different manor. They leave the cap table for investors and founders and instead arrange either a bonus or a profit sharing scheme that does well for these employees.

This typically works on trust, but Im sure there is a way to formalise it. Either through employee contracts which have a defined profit sharing goals (in a similar manor to a sales persons targets). Or even perhaps through contracts which ensure cash bonuses based on acquisition value are full-filled.

There must be ways to orchestrate it without effecting the finance of the company or complicating acquisition too much. For example, creating a pool of "tickets" associated with future revenue/profit/exit sharing commitments that can then be vested in a manor similar to options.


To hire better you have to look at the past source code. I got hired once in a startup in France and what the CEO did is that he looked at all or so of my personnal projects. He could figured out I was a good programmer because I was able to run most of my programs and talk about them in depth. If you want to work in innovation, you have to have side projects. Has anybody tried that? Sounds quite like a silly question but I'm curious.


I think this is a real advantage that startups can have in hiring over big companies. At most big companies, the first screen is from a non-technical recruiter, and they won't be able to do this.


Comp is a big one, discussed elsewhere.

The other professional problem that well-run startups have is that it's easy for early employees to feel like they're held to a different set of standards than the founders for professional growth. Essentially, founders are given chances to succeed in roles they never could otherwise, and early employees miss all the coaching and context that might help them succeed in similar roles.

Let's imagine I was a 26-year-old developer interested in startups. I have two paths:

- I found a company. I have the chops to hack something together with my cofounder, and maybe we make something of it raise a seed. We hire another couple engineers, and with a couple big logos in a good market, we raise an A. At this point, I've learned a ton about what makes a business work from other founders and I see (far too clearly) the gaps in my own knowledge. I hire some marketers / salespeople to work for me, and we keep making things work. At some point, maybe I choose to hire a professional CEO, and I stay on as CTO. I still have a lot of leverage in the company. I still go to board meetings.

- I join a company as the first employee, after they've raised a seed. I have good conversations with the other 26-year old founders over beer after work. I jump on the occasional phone call with customers and crank out features that they like based on that insight. We raise our A, though I'm still a software engineer since we only have 10 employees that all report to one of the founders. I quit seeing customers, because we hired a sales rep. We decide to hire management, and I'm considered for a line manager job, but we ended up hiring somebody externally. (She was awesome, glad we hired her, but I'm bummed I'm not reporting to the CEO anymore.) By the time we're 40 people, I don't talk to the founders much anymore, and I don't really understand what our bigger customers want. I don't have the influence I once did, and the codebase is too big for me to brute force that leverage through productivity. I start to look for another job.

There's nothing wrong with either story, but in the founder case, I was given a ton of chances and support. As an employee, I was given, at best, the support of a single manager while the company grew around me. This is fair, in some sense, but compared to the opportunities offered to the founders, it's far behind.


I just finished a job search 6 months ago and it came down to comp. The earlier-stage companies I talked to seemed much more fun, but my life has some problems that money solves, and comp was very important.

The base comp was lower at the early-stage companies, but not critically so. The problem is that ~half of an engineer's comp these days is equity, and startup equity offers were far, far, far lower. My best startup equity offer implied ~2M for a 100M exit. If it takes 5 years to pull that off, I'm better off not just at FAANG, but any number of established companies.

> I think the next phase is to move the needle in favor of early employees.

I would love to see this happen. I like my new gig but I'm not scratching the entrepreneurial itch like I could if I were employee # less than 50. My life can handle the chaos of something failing in 24 months; FAANG will always be there if it doesn't work out. But I'm not in a position to be a founder, and I can't roll the dice for 5 years for the chance at 1/100th of the payday of a founder. But maybe 1/10th the payday?...


I worked at startups back in the day and am now at a MediumCo and pretty happy with the situation, though missing out on the SV gold rush. I do think sometimes about returning to that world but I would need at a minimum:

* At least equal total compensation and benefits beyond the stock options.

* Reasonable compensation for the loss of job security.

* Support for my work-life balance, i.e. for my nonstandard schedule and geography requirements.

Given those things, what would motivate me to go to a startup?

* Solving a problem I care about, i.e. not selling ads or throwing elections or increasing device addiction.

* Serious, grown-up founders and leaders: no Boy Wonders, no Tech Bros, etc.

* Using technologies I respect.

I don't know how helpful that is to your overall goal, but it might be interesting as an "older" guy's perspective (mid-40's). I sort of doubt I'll get involved in startups again but if I do, I strongly suspect it'll be either as a technical founder or as the technical founder's VP of E.

For people like me, the "YC Consulting" model proposed in another comment could be pretty attractive. I guess it might already exist at e.g. Google (Ventures).


Summarizing the most popular startup con here: if I'm a relatively senior engineer, joining some late-stage startup for 180-250K cash comp and 50-100K options, then the payout in case of good M&A or IPO could be $20-100 per share (if I don't wait years, cash out at the end of the hold period and move on). So let's say in 4 years I can make $720K-1M cash and $1-10M in stock. Which is roughly comparable to the big guys.

Make it possible at the little guys too. More risk - more equity. What I see now in the Valley is that the series-A guys are offering the same stock (roughly) as the series-D. Just the strike price is an order of magnitude lower. I ever saw pre-IPO startup offering _more_ stock than seed-stage one. This just doesn't make any sense. ISOs are not dollars, their value is multiplied by the risk coefficient. And I feel that founders are somehow lured into thinking that their ISOs are even worth the strike price. Change that and you'll see more people coming to work for startups.


Very interesting comment. May I ask a quick clarifying question?

When you say "the series-A guys are offering the same stock (roughly) as the series-D", what units are you comparing them in? Number of shares? Percentage of the company? Estimated $ value of the shares (and if so, how calculated)?


The number of shares. One can argue that early startup shares are less diluted and thus comprise a bigger piece of the company, but the risk is disproportional to dilution.

When evaluating an offer, you just multiply this number to the projected IPO price given the comparable (same industry, company size, etc) IPOs recently.


FWIW, I wouldn't recommend using the number of shares as the benchmark for comparing offers (across any two companies, startups or otherwise).

Actual share counts are quite arbitrary. It's common for startups that are going public to do a 10 to 1 stock split shortly beforehand. Using your algorithm, an offer from that company would 10x more valuable the day after the split!

Much better would be to compare the expected value, by multiplying the ownership percentage by some estimate of the value of the company.


True. This metric is as good (or bad) as any else, a percentage of the company included. You can't predict dilution or stock split (the only startup I joined early enough to have the strike price of 11 cents which went IPO, did a _reverse_ stock split). But somehow the number of shares granted in a company of 20 ppl with stage-A money and 0 revenues is within 10% of the company with 3000 ppl and doing 300M in revenues. And also within 10% from the company with 200 ppl and 30M in _profits_. Go figure.


Cons:

If you're an engineer in demand, and your startup exits nicely, your equity is still less than the market rate you would've gotten over the years. Less than your 3rd-best offer, for that matter.

Often you can't even know anything whatsoever about your upside and have to take it on faith. Faith! It is increasingly common that, as an employee, you are intentionally given too little information about the equity to know what you would be getting even if you had a crystal ball telling you the price for which the company was eventually going to be sold.

In 2018, because both the salary and the upside are low, working at a startup is in the same bucket as working pro bono, except that it's pro bono founders instead of pro bono publico. But you'll still get a pitch that the upside is big in the event of a nice exit (you just can't be trusted with specifics), and you'll hear a lot of rhetoric about how being scrappy is better than having 18 cafes and 23 massage rooms.

In 2018, unfortunately, it is, in short, a bit of a scam.

Pros:

Lack of bureaucracy.


I see a lot of talk about comp, and that is 100% an issue (particularly considering the time-value of money, that every year that you're earning more money you can earn ~10% long-term on that in your IRA/401k).

But, considering there is only so much money that startups have access to, and most early employees are not primarily motivated by money (I would hope, or else they are likely quite naive), the biggest let-down I've experienced as an early employee, that would have made up for the lower comp, would be actual access to the founders' networks and learning opportunities.

If being an early employee meant getting to meet with investors and help the founder raise money (and make an impression on those investors), if it meant being actively involved in the struggles of the founders involved in running a startup, then I suspect those of us who wish to start our own startup some day would consider that a reasonably attractive opportunity to really learn those skills and build their network.


The other thing that I think would be great if YCombinator threw their weight behind would be lobbying for universal healthcare.

I (and many others, I presume) would be much less risk-averse and more likely to start a startup or work at a startup if healthcare wasn't so expensive. One of the biggest benefits of working at a big company is their good health insurance, which many startups are lacking. So not only do you get paid less at startups, but your costs are higher if you or anyone in your family gets sick.


I like this. I'd be more open to lower compensation if it meant that I would have opportunities to open my own shop.


The single biggest con for me is asking me to move to the bay area on a sub $200k salary. I have 4 kids, I live in SoCal. The difference in mortgage alone means that I will be either losing money compared to my current job at a medium sized company or having an absurd commute.

I looked at bay-area job opportunities and FAANG would be break-even to small-raise, while all startups would be a minimum of $20k less money in my pocket for any sub 30 minute commute. My current commute is 15 minutes.

On top of this, from my sphere of people I know non-founder equity is a joke. One quote from a friend "You're more likely to get rich taking a job with no equity and sinking the difference in salary in powerball tickets." The largest exit from my social circle netted the (#3 employee) $60k, or about the difference in salary over the time working there. The best financial outcome for him was actually the massive raise he got by working at the payscales of the company that acquired the startup.


One major con, as far as I'm concerned, is the increasing ageism that exists in the industry in general, but especially at startups. My father-in-law is 68 and can barely get an interview, much less an offer. He is very technically competent. Any company of any size would be lucky to have him. Now, you might argue that he's too expensive, especially for a startup, but the fact is he just wants to work and is willing to take less money to do what he loves to do.

You could also argue that they won't hire him because he might retire at any point. Sure, buy why would he? He wants to work. Some at his age and experience even need to work still. And besides all that, even if he retires in two years, the startup would get a tremendous mount of value from someone with his experience over that two year period.

Given how badly companies need technical talent these days, its a shame that they leave that segment of the working population out.


On the compensation point...

If you are a smart, quantitative person looking to maximize your income, you should go into investment banking, not software engineering. Partners at an investment bank can make $5M a year. You won't make that as an engineer at Google.

Since you're reading this, I'll assume you didn't go into investment banking, but went into engineering, likely because you found it more rewarding. Good job! Life isn't about money.

Now if you're a software engineer looking to maximize your income, go be a senior engineer at Google. You'll make $400k a year (supposedly). But you may find working in a smaller organization to be more rewarding / engaging / exciting. If that's the case, work at a startup.

You won't maximize your earnings potential at a startup. But you'll likely work in a nimble environment, solving interesting problems, and get a lottery ticket (options) to boot.


Aside from the probability distribution issues with investment banker income, it's actually a much harder thing to simply "go do".

Going straight into investment banking right out of undergrad is a privilege largely reserved for students of "elite" schools [1]. The other way in is post-MBA, but an MBA is quite expensive.

The hourly rate also looks very bad [2]; junior/entry-level research analysts routinely put in 80+ hour weeks, regardless of the reforms that were put in to attempt to curb that sort of abuse after multiple deaths.

[1] https://news.efinancialcareers.com/uk-en/199099/top-50-unive...

[2] https://corporatefinanceinstitute.com/resources/careers/comp...

(Edited to add a couple of pertinent links.)


I would argue that making $400k as an engineer at an elite school also requires some element of academic pedigree.


"Maximize income" is not helpful without probabilities attached to the outcomes. What percentage of people who start in banking end up as partners making $5m? And what does the income distribution for the rest of the bankers look like?

I suspect the long term payoff distribution for engineers is fatter, meaning if you end up around the 25th to 75th percentile, which you should expect to do, you will earn more as an engineer.


By "Maximize income" I mean Expected Value. The Expected Value of a lifetime of investment banking is certainly higher than that of a software engineer. While not every investment banker ends up making $5M, very few make less than $200k.


I think the incentive structure for first 10 employees is completely broken right now. Adjusted for risk and dilution, the risk reward ratio for top 10 needs to be closer to the founders since they are taking almost identical levels of risk. I wish companies would value the stock part of their offer with respect to the valuation that investors have put money in. I never understand the huge disparity between the valuation of companies as understood by investors (in terms of their investing decisions) and as explained to prospective employees. From my point of view it would be good if the Startup clarified what they intend to pay me, put a hard cap on how much of that they can pay me in cash, and then allow me to use the remaining to "buy" stock grants at a valuation that closely resembles what investors have recently invested at.


Pros:

  * More choice in terms of technologies you get to work with
  * Less bureaucracy 
  * Once you've launched, typically a very fast life-cycle in terms of conception to production
  * Early on, you can fit the entire company in your brain
  * Investors are less likely to bring in stodgy "babysitters" and just let the founders do their thing
With the exception of the last point, the "Pros" really haven't changed much in the last few decades.

Cons:

  * Limited transparency from founders
  * Weak technical leadership in many "technical cofounders" or CTOs
  * Widening compensation gap versus established companies
  * Equity offers are often poor (related to above point)
For "Cons", the first two have been with us a while. The last two are a recent phenomena as our industry has matured.


Of course, now that start ups are starting out side the bay area, that is the biggest appeal. There's a lot of people who want to get out of the Bay area. From the perspective of someone with a family: With the astronomical housing costs on the penninsula, working anywhere outside the bay area/penninsula is like getting a 1 to 2 million dollar signing bonus. Even with less than half the pay, you'd be much better off (assuming someplace reasonable: Albequerkee NM, Austin, Dallas, Chicago, Nashville, etc).

Nearly 50% of bay areans want to leave: http://www.foxnews.com/us/2018/06/04/bay-area-exodus-nearly-...


People are forgetting that a start-up is inherently an unnatural place for employment. Given a choice, a rational decision will always be to work with the big companies, specially if those big companies are among the FAANGMU (or whatever abbreviation it is). And it's not only the money. The money is good no doubt, but it's the brand recognition. I know several folks who went to work at Amazon on a pay cut for a couple of years, and jumped way ahead on their next gig with a badge of honor of being an ex-amazon employee.

Now, the question is will you leave that job for a start-up. It really depends on your situation. Have you already been an employee of the big co? Then, sure go for it. Your employment at FANGMU has pretty much guaranteed you employment at middle tier companies with a good salary. No start-up has that kind of clout.


Well it depends. Some startups actually prefer you to have startup experience...which makes sense. They might like it if the startup is well known but I don't think that's a requirement. And definitely a lot of the experience gained in a huge corp will not be good for a startup.


Here is the very basic equation we are all looking for:

M(faang) <= M(su) + (CV * ES * CS)

where M(faang) is the money/salary over the expected timeline earned from a FAANG-ish company (many many of them), M(su) is the money/salary earned while in a start-up, CV is the Company Value when the Start-Up lotto is cashed in, ES are the Employee's Shares as a proportion of the company that the employee can sell for money, FR is the Fail Ratio of Start-Ups that get to the point that they can sell the company and don't just flame out.

Lets run some numbers to get a feel for the equation:

Say M(faang) is $125k/year and the timeline we are looking at is 7 years; that's $875k total. Say that potential start-up employee is making only $60k per year for those 7 years; that's $420k total. So, the expected paycheck at the end of the 7 years needs to be at least $455k.

So, CV * ES * FR must be $455k. FR is typically said to be 90%, as in 90% of start-ups fail, we'll take that as dogma too and set it to 0.1. ES is likely to be very small, even for very early stage employees, so without nearly any consensus via googling, let's set it at 0.001. CV is the company valuation when the start-up lotto is won, these days it's tough to find this out (it's mostly a power distribution), but let's be a bit conservative and set it at $500M. These numbers give us $50k.

That number is about 10x less than what is needed at a minimum. The start-up fail ratio is really never going to change. So, either the CV must become about $5B, not $500M, or the ES must go upwards from a thousandth to a hundredth (honestly, either situation isn't unreasonable) to meet the minimum pay requirements.

You can play with the numbers yourself and add conditions too (stock mechanics, value of medical benefits, rent issues, taxes, etc), but the math isn't calculus, just nested algebra. Hopefully this will help others out when thinking of trying to join a start-up as an employee.


Pro: Remote friendly (sometimes). Startups can't pay the big $$ for good talent, so they're more open to remote employees. I've worked for a few startups where I never met anyone else on the team face-to-face, worked from our corners of the world, and we built cool shit.


Con: Startups almost always screw the remote workers on stock and legal terms. I have yet to see a positive story. Illegal worldwide industry-wide non-competes, forward-dated options (if any), remote expensive jurisdictions, wrong financial info, etc.

So yes, remote is a sweat deal if you are getting paid cash, but keep in mind most of these founders were laughed out of the room in their own HQ city's startup community.


One thought experiment is to take your hypothetical market rate, and calculate the opportunity cost of working at the startup. Then think if you had that cost over say 5 years, in hard cash, would you take it and invest in the equity of that startup over other options?


Great way to think about it. It is a concentrated, illiquid equity investment.


As an experienced engineer it’s too late for me. I’m being paid 500k/yr working for a small successful hedge fund with flexible hours and remote work. There is no way I can gamble this away for an expected maximum upside of $10m with a 10year horizon...


Pros:

- More autonomy

- Less administrative overhead

- More executive interaction

- Higher percentage of superstar colleagues

- Work is more fun

- More breadth of opportunity and interaction

Cons that YC can help with:

- Less formal training

- Less formal mentoring

- When things go South, the cuts are worse and you have less notice

(The above can be mitigated by offering training and mentoring for the entire community, and proactive in-community job placement when companies fold)

Cons that YC can’t help with:

- Higher volatility in financial outcomes

- Less predictable schedule and work-life balance

- Less brand awareness for your parents to brag about


One idea to reduce volatility in financial outcomes: offer equity in the YC fund itself in addition to the equity in individual companies. That would also give employees an incentive to support other employees in the cohort.


Other options include pooling of benefits, and active job placement when things don’t work out.

Pooled equity would have to come from the startups rather than YC. Instead of “for 6% you get 200K” it could be “for 10% you get 200K and an equal share in the pool of your class. Divide it amongst your employees as you want, though we suggest....”

(Note: numbers are made up)


We've looked into that. It's hard to make the math work - when you slice up YC's equity into that many pieces, each piece becomes very small.


Well, presumably you'd have to take (at least some of) the companies' option pools as well, but I'd believe that the math still doesn't work: that just reflects that the equity for employees is not a valuable deal in general.


I'd like a portion of my equity to be shares of a Y-combinator fund. I can spread my comp risk across a batch of startups, just like a VC.


Health insurance and housing instability is a huge risk. Not to mention the weaker pay and corporate structure.

If company explodes within 4 years (like most startups), I'm off interviewing again, and my family relies on my health insurance for substantial coverage, as well as paying housing costs. Obamacare is getting gutted as we speak, so it might as well not exist.

if you want to change the game, set up a standard small company health insurance group and offer entrance to all employees and their families, regardless of pre-ex condition or whattever. So long as you find work for a company signed up with that group within, say 12 months from company collapse/being fired/whatever, you keep coverage. Effectively decouple employment from health insurance. Give me the ability to lose employment for whatever reason (remember, Fire Fast is a popular creed) without putting my family at risk of bankruptcy or losing our house, and I'll be far more interested in working for a startup.

Similarly, YC needs to contemplate pushing remote work hard on its companies. The amount of money I would have to ask for to live in the SFBA with, again, hedging the risk of company collapse or being fired is absolutely absurd.

There's extremely little upside for me to take the enormous risk of being poorly managed, company doing wrong decisions, market not being there, etc. The liklihood is that I lose money, my bosses are very inexperienced, and the business doesn't fly. Maybe I am a reasonably early stage employee and walk out with a $0.5m check (this is a reasonable ballpark for an IC). That's cute... RSUs from major employers equal that for reasonably senior ICs. Without the risk.

For comp, you will need to jack up equity substantially - probably some kind of preferred share not subject to clawbacks (I remember well how Skype took advantage of ICs) - as well as meeting the cash salary of the big players. This hedges the risk of the company exploding.

These days, I generally only talk to startups who are past their A round, have paying customers, and reasonably experienced engineering management. And I expect market comp as well as a well seasoned benefits plan.


As a startup employee, I'd say a big con is not necessarily the amount of equity, but the type of equity, and difficulty of evaluating it. Common stock really only provides exposure to the tail end of good exit outcomes, since other entities on the cap table get liquidation preference, participation, and so on. To make it worse, it's not standard to share information about capitalization with employees, so we have no real shot at valuing the equity portion of an offer. It would be nice to be able to know what our equity is worth, and get some benefit from a decent but not great exit.


Pros:

- accelerated responsibility, especially early in career

- making something new

- little bureaucracy

- credentials matter less

- can be more fun

Cons:

- typically inexperienced, inept management

- longer hours, higher instability, and lower comp even if the startup pays off. Not quite the worst of all worlds but it's getting there.

- lack of transparency about cap table and what options are worth. 90% of my colleagues don’t even know about liquidation preferences. We expect early employees to make investor-level decisions with employee-level information

- exits are rare or perpetually delayed. even acquisitions may mean nothing if you aren’t a good fit at the acquiring bigco and are let go before vesting (and if you were a fit, why were you at a startup?)

- chaos, stress

- typically hostile environment for URMs, monthly HR disasters

- distorting effects of investor prejudices, expectations

- SFBA-centricity; locks out the vast majority of founders and potential employees, and very high costs for early startup employees

You asked for solutions but I doubt many of these are easily fixable. Maybe we have to accept that startups just aren't a rational career path to maximize wealth. And especially for Americans, it's incredibly risky to try a startup, unless you come from a very privileged background.

The fact that startups are chaotic and run by inexperienced people seems to be a given. Unless you go to a "studio" model where you have a stable team of professionals spinning out startup-like projects all the time. Some people are trying that but IDK if it's ever worked.

Transparency about how funding and options work would be trivial to solve. But the founders, board, and investors all have the incentive to keep it hard to understand. But maybe YC could set new norms here, somehow.

It might help if YC's alumni network included more URMs. I know you're trying to fix that.

And maybe this is harder but at least at the startups I've worked at, there's been a lot of wasted effort simply in order to satisfy what various investors want this month. But I've never worked for a YC company so maybe it's better there.

One possible mitigating factor to all of the above would be for the whole startup ecosystem to be more remote-friendly. The compensation starts to make sense if you have nationalized healthcare and don't have to pay SFBA rent and aren't in the running for other SFBA jobs anyway.


It sounds like a lot of the criticism is that employees don't get enough compensation or don't get it quickly enough. With options, the variance is too high, since even companies that raise a lot may fail, and liquidity takes a long time. Plus, if the shares are voting, founders have to give up some control. I guess the variance will always be higher than many employees would prefer (at least not considering schemes that share risk among multiple startups), but how about something like the following for mitigating the concerns people are raising?

The company commits that some percentage of each month's revenue will be immediately set aside for existing employees (to a first approximation, split equally between them). Crucially, any investment should be counted as revenue for this purpose, since early-stage startups often get major investment before major revenue. Ideally the percentage should be something big, like ten.

To encourage employees to stay, the revenue will be paid out to them over a period of years, similarly to how options take time to vest. A detail to be worked out is what to do with any money that isn't paid out because the employee leaves. (Maybe just return it to the company, though that could give companies an incentive to get rid of employees after a major funding.)

The company should be able to revise this commitment but not without a warning period of, say, half the period over which compensation is paid out to employees.


Wow, when did we all lose our souls? So many pro "FAANG" comments. Working at a big tech company totally sucks. Its soul sucking.

Personally speaking, I made about 300k at a FANG adjacent company - and I hated every moment of it. I quit to make less money at a startup. And I'd do it again.

Today, especially today, what is there to be proud of in working for a FANNG company? Google is working with the Pentagon on war technologies and new ways to abuse their users privacy with Internet spyware and spam; Facebook is a master of fake news and Donald Trump; Amazon is an anticompetitive monopoly.

If its only about money, check out mikekij's comment:

> "If you are a smart, quantitative person looking to maximize your income, you should go into investment banking, not software engineering. Partners at an investment bank can make $5M a year. You won't make that as an engineer at Google."

Hacker news is the place to be positive about startups, the future, and technology.


I'd like to update this response. Even though I'm positive about the quality of work benefits startups have over FANNG companies - its still important to negotiate a fair equity deal for yourself.

Equity is one of the factors that really should differentiate working at a startup vs an established player. So fight hard for it, and never settle for a bad deal.


It can feel like these startups aren't all that independent from those companies. Most are hosted by Google or Amazon and many depend upon Google or Apple to approve their mobile apps for distribution. Some get acquired by them.


Good point. These are big monopolies and its pretty tough to avoid them.


It's easier to be positive if you don't feel exploited, underpaid and disposable. It's important to push startups to do better, so they deserve our positivity and can create that better future.


One of the real cons of joining a startup that doesn't grow fast is that the founders of the startup will structure the acquisition so that the early employees get nothing. I'm talking about the "well the company has no value after paying back the investors, but the founders and their friends got sweet hiring deals at newco that otherwise they would have had to share with the other employees" sort of quasi-acquihires.

I've been through two of those (and successfully forced the acquiring company to give me $ in one of them because of how venally obvious the deal was.) I hear of these sorts of things happening relatively frequently. It's a real reason that I probably wouldn't participate in another startup.

For me personally, it isn't the risk of failure that keeps me from joining another startup as an early engineer. It's the risk that the founders will cut a deal in an acquisition that cuts out the early employees.

This would also be good for the acquiring company, they have a large risk in cutting a deal just for the founders. In one of the cases that I know of, the acquihire was a disaster because the founders represented to the company that they had the expertise that rested within the early employees and it ended with a great deal of waste.

So, fix this issue and I think you'll see better results overall.


Pros:

* Access to new tech/growth opportunities

* Culture is often far superior to the big players

* Make an impact, you can have an outsized impact simply because of company size

* Nimbler/move faster due to less bureaucracy/overhead

Cons:

* Huge risk/feast or famine situation, working for a startup could mean retiring 15 years later or 15 years earlier

* Stress levels/health risks

* Complete chaos at times

* Mediocre / nonexistent benefits

* Sold as "do interesting things" but not always true. Startups have just as boring things that need to be done as any company.

* Career growth is largely based on the growth of the company


Ha, most startups use crap tech because the founders might not be highly technical and hire the first tech person they come across or they outsource and can't vet whatever cheap contractor they found.


I worked at a startup of a semiconductor fab early in my life, which was not quite the same as what you mean but I think the reason still applies. I wanted to see how these messes get made. After working in old organizations with lots of legacy problems, I wanted to see first-hand what the process was that led to these situations. It did.

Having worked as a contract programmer at software startups, I can say that the main reason would be, to have more power to direct how the software develops, instead of just having to accept so much of it as a problem on top of which too much as been built, and which cannot be fixed.

However, I worked at a software startup only as a paid-by-the-hour contractor, because frankly the attitude towards early employees time is appalling, and I have seen this in how many, many other people got treated at other startups. There really isn't enough of a potential payoff for early employees to justify the hours that they are made to work, and in many cases it is done mostly because it is so easy to demand that and no justification is required. Founders are by nature egomaniacs with ruthless focus on their business, and that can turn even very good people into the sort of person you don't want to work for (unless you're charging by the hour).


More than 'pros' and 'cons' I see working at a startup as requiring a certain kind of personality.

Working at a startup: Ideally you'd have a high risk tolerance, be self-motivated, be interested in learning new things -- being a do-whatever-it-takes kind of person. The kind of person who wants to throw themselves into their work. You want the kind of person who just can't sleep unless they get their product into peoples' hands. Everything may well be on fire -- all the time -- and it's up to you to fix it.

What you get being that kind of person at an early startup is a breadth of experience, often in things you weren't qualified for initially. You get oversize impact. You build your reputation -- fast. You get to build an amazing network of similar-minded people who you can leverage whether the startup goes well or poorly.

The cons, of course, are that it may not go your way. Either because of you, or because of reasons totally beyond your control. At any moment. You may make a ton of money, or no money, or anything in between. It's not the kind of workplace that's a good fit for everyone, or even for every life stage. Big companies offer effectively a 'guaranteed' way to make a 90th percentile salary, startups definitely don't.


I worked at a few startups over ten years ago. As a SW engineer I had unique value to the company back then - me being able to hand optimize code better was what set the company apart from the competition.

But SW has grown up a lot since then. Now you need more commodity, reliable engineering. Most of the low hanging fruit in SW have been picked.

Today's startup key employees are the designers, copy writers, sales people, and marketers. HW might still be where SW was 10 years ago.


Pros:

* Technical skills sink or swim very quickly - you'll learn vastly more in the same period of time at a startup than you will at a big company. Or you'll fail.

* You learn to accept that failure isn't as bad as high school / college would have you believe - as long as you learn from it.

* Invaluable leadership experience very early on.

* A lot more responsibility early on - if you like to take charge and see things through it's a wonderful experience.

* Startups are usually founded by intelligent, successful, driven people - based on head count you usually work closely with them and have the opportunity to soak in that knowledge and experience.

* Connections. When you're young / early in your career a startup puts you in situations to meet people you wouldn't normally be in the same room with at a large company.

Cons:

* Equity is a joke. Liquidation preferences are always against the employee no matter how early. I'm at my second startup and anytime I hear a coworker talk about taking a pay cut because they got equity I cringe.

* The pay CAN suck, it doesn't have to. It took two tries but at my second startup (current job) I'm paid fairly. Maybe slightly less than I would be making in the same role at a large company but coming here included a promotion I was 6-12 months away from at the previous large company.

Neutral:

* Transparency. Some startups keep everyone in the dark about cash on hand, burn rates, fundrasiing, etc. Do not work for one of those startups.


There is no average startup. Everything depends on the competence of the founders, and whether the project sincerely excites you. There is a world of difference between a badly run startup focused on a boring market, versus a well run startup focused on an exciting possibility that might honestly make the world a better place.

Sturgeon's Law says that 90% of everything is crud, and that applies to startups. The good ones are rare. If you get a chance to work at one of the good ones, you should go for it. But can you be sure? Sometimes the founders are talented at selling a false image of what the project will entail.

Startups are a chance to build something entirely original with brilliant and ambitious people. But startups are also dangerous. Limited money means there is little room for mistakes. One bad decision can mean bankruptcy. The potential payoff attracts capital, which in turn attracts scam artists. The unscrupulous often lack the skills needed to succeed, but sometimes they are smart enough to trick investors. Even entrepreneurs who start with a strong moral compass can find that the threat of failure unmoors their ethics from their ambition. Emotions matter. We might hope that those in leadership positions possess strength and resilience, but vanity and fragile egos have sabotaged many of the businesses that I’ve worked with. Defeat is always a possibility, and not everyone finds healthy ways to deal with the stress.

As an example of what can go wrong, see here:

https://www.amazon.com/Destroy-Tech-Startup-Easy-Steps/dp/09...


The main reason I consult to startups over taking a gig with a FAANG type is location. Silicon Valley, SFO, SEA, PDX are all lovely places to visit, but I don't want to live there, pay the mortgage there, or sit in a commute there. Yes I make a lot less than I'd like, but I also have total control over my schedule, get to work on green-field type projects, and get to work from my laptop in my garden.


I've thought about the comp issue for a while and came up with a kernel of an idea for a possible solution. Most companies are going to fail which means that most engineers will see their options go to ~$0. The reason VCs make money regardless of this low success rate is that they have a better Beta due to the many concurrent bets they're taking.

It occurs to me that some kind of Startup PEO could be created to help give engineers a favorable Beta too. Startups would hire the PEO by granting them equity and paying the salaries of their team each month. In exchange the PEO would pool the costs for good healthcare and other benefits. They'd also provide placement services to help engineers in their program switch companies whenever they wanted.

Do damn good work and the shared fund will give you upside. You won't be rewarded for picking the winning horse anymore, but instead the quality of your work over years and across several organizations. I'm not going to pretend I have all the incentive management figured out, but I think there's something in there and an ORG like YC might be able to pull it off.


I would add that there is some added risk (impossible to quantify) to being an early employee in 2018 as it seems that we are coming to the end of a macro cycle. Therefore the likelihood of a positive outcome (or surviving follow-on rounds) for a start-up in a down environment is lower than if it was earlier in a cycle. The obvious caveat being that if this bull market continues - this point is moot.


I think the talent pool is getting smarter about how much their equity will likely be worth (hint, it's $0). Those who are joining startups now, are either naive to that fact (not good once they discover the data), or they care more about working on the problem than they do the compensation (which is the perfect employee if you can find it - but the cost of living in SF has made that nearly impossible).

So when the company you are going to work for is going to pay you less in cash, likely require you to work harder, and not offer any guarantee that they will be in existence in two years, you are taking a ton more risk for less reward. Financially it does not make sense, so you better be in it because you enjoy the work that much more than a big company.

Bottom line is that startups are going to need to pay more money to attract talent. The secret is out on common shares and what happens with liquidation preferences.

As for how YC could solve this, perhaps they offer an unemployment supplement to those who are laid off. Help talented folks reduce their risk and you will find it easier to recruit.


Just another thought, but perhaps YC can explore more options for building startups in secondary markets where the cost of living is more manageable. I know the shop is famously SV-centric, but certain companies may have a better chance at success in markets like Salt Lake City, Austin, Des Moines, Nashville, etc.

Maybe an HQ2 process for YC.


Financially I don't think it makes sense to join a startup after the first two dozen employees or so ... unless you get a very special compensation package. The risk-adjusted rate of return on your labor can't compare to the compensation packages at places like Google and Facebook.

Having said that ... your chance at working on an interesting project is higher at a startup if you are the kind of person that can land a spot at Google/Facebook. What I mean is, you'll be a big fish in a small pond. The kind of person that gets buried in some obscure ad-tech team at Google, for example, can pick and choose the projects he works on if he shops around at a lot of startups. Want to work on an open source database? I bet you can find a place that will pay you 100K to do that ... but your stock might be worth nothing in four years ... and if you worked at Google your compensation would be around 160 and your stock would be worth around 750K.

So you really genuinely have to love what you do. And if you want a family you have to be prepared to move out of the Bay Area when you fail ... because you won't have enough money to buy a house the way your peers at Google and Facebook will.

So being at a startup you need to make peace with a lot of very probable outcomes ... moving away from California, possibly starting a family later, etc.

On the positive side, you can choose the area of technology you want to work on. And if you chose well, there's a chance you can parlay that for future returns.

I haven't even touched on the role of purpose and lifestyle ... mainly because I think its simplistic to assume a startup will give you purpose and a big company won't. I think purpose is something you'll have to shop for ... just like you shop for the right project.


I think startup is best way to boost your career. This is aimed mostly at junior level roles - it's the fastest way to gain meaningful experience. What a dev experience in one year in a startup is like 5 years in a big corp. For highly experienced/highly paid/execs - I don't see the value in joining a startup unless you're the founder or you need that for motivation.


I advise fresh grads or new entrants in the tech job market to avoid startups as their first gig. Instead, starting at a mature company with a strong team team is much more suitable. Learn from the industry experts in your field in a real world setting, develop your chops, and establish yourself as a professional. After that go do whatever feels exciting, which startups certainly are.


Pros: - some startups have a really high concentration of awesome and smart people to work with - it’s exciting to work on something new with a big vision - you can quickly get experience building a feature (or a whole product) from concept to launch. As an engineer building a feature you can feel more ownership over more aspects of it including the business/marketing/pricing etc. - I’ve found at early stage startups it’s easier to make friends with your coworkers than a larger company. You tend to do more together, from dinners to socials, and you become a tight group. It’s especially nice for people who are from out of the area or recently graduated etc. - you can work on really cutting edge and innovative things. You might get that at a larger company on a team like Google X but it’s not guaranteed - potential for big upside if your startup does well

Negatives: - you are subject to the whims of the founders. There is much less oversight over firing, demoting, and general behavior of a founder than the oversight a manager would get in a larger company. - If you’re a woman, you are likely one of the few in the engineering team. There’s often bad behavior and it’s very difficult to speak up about it without retaliation. I know multiple women who have been fired by YC founders and it’s been a tough environment for them to succeed in for multiple reasons. It’s also easy for women to end up doing a lot of office housework in addition to engineering in a startup where roles are not as well defined. I think it has gotten easier to at least have some recourse now in the era of me too - Lower compensation once you factor in public company stock, bonuses, 401ks etc. Base salary might not be too different but larger companies offer a much fuller package of compensation

I could do a deeper dive on the additional factors that deter female engineers out of early stage startups but that would be a topic of its own!


Con: half the money. Pro: work remotely and create a lifestyle you enjoy.

Startups that don’t allow remote are really missing out on a great differentiator.


Working for a early stage startup depends on the stage of life, your financial freedom and your ability to hustle.

Early stage startup requires that you work a lot more than 40 hours of week with a big pay cut compared to what you would get at an established company. This usually is not a problem for individual or couple who don't have kids but very difficult for people with school kids. You have less time and less money -- both have direct impact on how your kids grow up. Is it worth taking the risk? This depends on your values and how you define success in life.

Your roles and responsibilities are not well defined. Even for a software engineer, you have to split your time helping sales, customer support and marketing. I personally find this aspect super exciting but I know a lot of people who don't like and wont thrive in this kind of environment.

Most startups fail. Founders and VCs can screw you -- intentionally or unintentionally. Odds are just stacked against you if you define success by financial gains.


I think with most startups, even if they're successful, they don't deliver on the ownership and ROI you would expect for the time you invest.

Several years ago, I joined a Midwestern startup just before the Series A as one of the first ten employees and the first mobile FT dev. I took a pay cut to join and was explicitly promised ownership and real "skin in the game." Nine months later, when they finally devised an options pool, I found I had been granted 0.065% and left immediately. It was like they'd stolen months of my work. Today, they have over two hundred employees and are probably headed to a large equity event.

Another startup I joined raised a lot of money and paid almost market rates to some of the best developers in town. Their tech was some of the best in the city, but they pivoted and lost most of their developers when they didn't achieve product-market fit. They will probably only ever reach a tiny multiple compared to what their investors desired.


Have founded a startup, worked at a startup and worked at several fortune 500s and I can say the most interesting thing on my resume for the fortune 500 interviewers is by far the startup experience.

Showing that I can pull my weight, have a sense of leadership, drive, ambition, etc are traits that every employer wants to see but not many employees get to flex.


I've heard this from multiple Fortune 500 hiring managers, too. And of course it's doubly true for founders and hiring managers at startup and growth-stage tech companies! Just about every experienced person I know in startup-land thinks that resumés that show only big company experience are a negative hiring filter.


Early employees get to decide on a gamble: Do I want equity in return for probably less salary and do I want to get load of influence on the technology in return for a higher expectation that I can deliver it?

A more general difficulty is that a good employee might not want to work for you because they don't know that they are a good fit and plenty of poor employees might say anything they can to convince you to hire them because they like the sound of a startup even though they cannot deliver what's needed.

The missing part of recruitment (from personal experience!) is how to quantify what skills are needed in a startup (multiple hats, big picture, time commitment, understanding of the whole business, not just the tech, pragmatism in spades and the idea that growth is assumed and will need to be managed - ideally with early employees being the Managers) and how can the applicant 'prove' they can meet these?


As an H1B visa holder, my number 1 concern when responding to startups is the uncertainty it creates in terms of future H1B extensions, green card application etc. Big cos have large lawyer squads to push me through the paperwork.

Besides that, can YC create some sort of insurance fund to pay employees at early stage startups at market rates? This fund would mostly be fueled by equity that the founders and investors were planning to give the employees. If a startup succeeds, the payout should be able to sustain a few more startups at roughly market pay. Of course, what this would mean is that the employees who opt in given up their chance to "make it big", but also reduce their risk while getting to work at something they are more passionate about and more rewarding compared to whatever they are doing at bigger companies.


It seems like net share settlement for employee option exercise would benefit early employees considerably without really costing the issuing company much. For example, if I have options to purchase 100 shares at $1 each and current market value is $2, instead of me having to pay $100 to exercise I can pay in shares, so I instead end up with 50 shares of stock ($200 current value minus $100 to exercise, so I get net $100 in value, $100 / $2 = 50 shares).

This is pretty common in the convertible bond world. When I first learned that employees had to write a check to exercise that sounded crazy to me. I’m curious why net share settlement doesn’t seem to really exist in the startup world. Maybe due to the difficulty in determining current market price?


This is a big topic with plenty to be said but to synthesize some concrete ways YC can eliminate the cons:

- Raise equity ownership if possible.

- Raise the 90 day option exercise period.

- Be pro-actively transparent about the financial math.

There is a counter argument here that more transparency could lead to morale issues but most mature EEs know that they are rolling a dice and upfront honesty works wonders. The worse thing for the eco-system is the feeling of getting duped.

- Ruthlessly support EEs in growing their careers.

If your hands are tied w.r.t giving financial upside, at least be a champion for personal growth for EEs. As a founder, you get tons of opportunity to receive mentorship. Send that elevator down, every time you get a chance to. YC can easily provide mentorship for EE cohort, if it can do it for Founders.


The biggest irritation I have is that some things are outside of my control. I can make technology better, optimize things and add features, but I can't magically wave a wand and make other areas of our company better. In specific it's hard to learn how to market a product, especially if it's a disruptive technology. Also frustrating is that I have been here before and seen scenarios where 3 years later someone else is able to bring your passion project to market after you've given up after being told "that would never work" by people who are now using said product.

I truly believe there are tons of already built products out there that get turned offline because they never were marketed correctly.


When I hear startup, I think 80+ hour weeks with low pay and a very very small chance of being compensated for that. If there is any way to compensate ruining your health financially.

Basically, it's all cons. Unless you like playing the lottery and have no life.


Startups offer pretty good compensation for folks who lack the ability to pass a FAANG interview. Folks lacking traditional CS backgrounds but with an actually high level of skill for writing software, specifically web software, tend to be over-represented in this group.

A lot of the downsides of startups people mentioned here are 100% true. If you didn't study CS in college though, consider the hours of reading Cracking the Coding Interview you'd have to do and divide those hours by your FAANG comp, and you might come out with an equal or slightly higher hourly rate going the startup route. And your interview process might be a lot less stressful.


I've worked at multiple startups and feel it isn't worth the effort. The execs always make out and everyone else doesn't make it worth their effort. The compensation will be better when working at established companies.


Startups pay pennies in both cash and equities and are usually run by morons working on dumb “problems” they sold to even dumber investors. Good luck solving this. (If you’re really interested check out Andrew Mason’s work on equity.)


Pros: Work with cutting-edge tools and languages. Work with people who basically know their shit. You're given much more responsibility, hence control, upfront. Process isn't ossified. Flexible hours.

Cons: Hope you like your coworkers because you'll be working cheek-by-jowl with them in someone's coworking space or crammed in a garage or something. They will try to pay you partially or entirely in Bison dollars (equity). You are assumed to have flexible hours so I hope your evenings and weekends are free. A company without solid footing can go tits up once the VC funding dries up, sending you on an early job search.


I have a https://www.workatastartup.com/ question:

What happens, if you work for a YC company and want to work at another one? Do they still see your looking?


At the moment, yes - and we know this is a huge issue. I don't recommend using it if you are working at a YC company at the moment. We're fixing this in the next week.


>> Ask HN: Pros and cons of working at a startup in 2018?

i dont see how they are different from 2017, 2016 ... etc.

There is nothing special about start ups its just another business so consider it like one.

I'll distill it down to simple level. Working for a startup or any company is like working for a pizza joint. Consider there are 3 pizza joints in town and you know how to make pizza sauce. Which pizza joint would you choose? Why?

- The one that pays more - The one that has better hours - The one that has better work environment/culture - The one with the owner that is not an asshole - The one that has a better potential for personal growth

plus whatever else you think is important.


There is a lot of talk in the comments about amount/value of startup equity vs FAANG companies, but having founded and worked with numerous startups, there seems to be an overall lack of transparency when it comes to equity. It's not just how much (percentage), but how are you even measuring that percentage? Fully-diluted shares or current outstanding? What are the liquidity preferences of the VCs? 1x, 2x, 3x? Beyond the rare chance of the company even exiting, there are so many terms that most engineers are completely oblivious to, and the startups are usually not there to inform you.


Joining a startup in 2018 is probably one of the most stupid things one can do. The market is certainly oversatisfied at this point, so the risks increase, as well as the average bullshit from founders and investors one has to bear with (e.g. see Theranos). Sure, YC will continue as long as you can. I understand, you also just want to make money. But for an engineer it is much smarter now to join the biggest possible company, take all the benefits, build a small nest egg, and be active about switiching jobs every 2-5 years.


The only reason to join a startup is if you know the founders and you think working with them would be fun enough that you're willing to give up hundreds of thousands of dollars to do it.


Currently a dev at a pre-Series A startup.

Pros:

- both the freedom AND responsibility to build things that'll directly translate into increased growth/profits, or the opposite in the case of failure

- close-knit dev team, and in general everyone is chill, i.e company culture is great so far

Cons:

- my salary compensation is pretty average so I am hoping for an eventual big pay-out, but it's hard to gauge what the payout amount of my shares will be.. maybe this is just due to my ignorance/lack-of-experience (are there tools/calculations to figure this kind of stuff out?)


Here are a couple of articles that might help with regards to calculating your equity payout: https://codingvc.com/valuing-employee-options https://medium.com/@jamesseely/eshares-option-value-calculat...

I'd also really encourage you to talk to the founders of the company about this and ask them to walk you through their model for how much you should value your equity.

Our advice to founders is to walk every employee through a model that estimates the value of their options under different scenarios.


Really appreciate the links and feedback, thank you.


  > I am hoping for an eventual big pay-out
Please, please, make sure you have a plan for when this does not happen, your company evaporates overnight (because leadership didn't tell you) and you find yourself out of a job.


:thumbs-up:


https://tldroptions.io is all about estimating the approximate upside under a wide variety of exit scenarios. Even the basic answer ends up being “it depends...”


There might be potential bias here - people who work at intense startups probably don't have the work-life balance to browse HN and comment on here right now. /semi-sarcasm


I would distill this as follows. Limiting to 1 pro and con to respect your and my time.

Pros - You develop the skill of approaching things more holistically as you are forced to see things from end to end perspective.

Cons: - As an early employee (#1 to 5) You are taking the SAME amount of risk as the founders but being compensated quite differently. The exception to this is where founders have invested their own money into the startup. But thats rare in SV style startups.


Con: Aggressive copy+pasting of giant tech companies. I get the sense that start ups are now just market-fit validators who assume all the risk without the ability to reap all of the benefits.

Snapchat + Spotify comes to mind. Unless your company has to make heavy investments in operations infrastructure (think Airbnb/Uber) go in with the mindset that you will definitely be competing against FAA(N)G (not so much Netflix), as soon as your product gets some market-fit.


So much good input here, and as a person outside of SV I am sad for those that chase the brass ring without realizing it is on someone else's finger. I agree that if you are hiring early employees at below market rate because you cant pay market rate then you shouldn't be hiring employees. But that's worthless input because there will always be a person willing to take the low paying job thinking it will pay off. For shame and oh well.


Depends on your age, here is why: I've been in startup most of my 20s and early 30s. The amount of learning, growth, potential and responsibility is amazing. you simply will not have it elsewhere. you will have tons of impact. when i got married and had kids i couldn't take these risks anymore, i needed a stable working place with good WLB. now i'm making more money, using the experience i had in startups working for a FAANG company.


All this comp talk is a little silly imho. I literally just quit a job (today) at a big boring company where I brought home north of 300k / year to join a startup making less.

Why? Because doing something interesting is more important than making a ton of money. Because creating something is better than tending someone else's garden.

Seriously though, do what you want to. Go make some money. It may get old though, and then you'll be back. Impact has value


I've worked at a couple of the top tech companies and have been co-founder of a startup with a successful exit.

Pros:

* Low stress. I find the most stressful thing at work is trying to figure out what my boss wants. (Small) Startups are easy -- just stay alive and find product market fit.

* Power/control. Things are small, so it's easy to know a large part of the codebase/product. This allows one to quickly make changes to support the business.

Cons:

* Pay. This has been well documented in this thread.


Here's one that may have been mentioned, but wow, there are a lot of comments.

Founders: get over yourselves. I understand that you have to have a lot of faith in yourself to do what you're doing.

At the very least, try to have some humility, and maybe understand that what you're doing may not be world-changing after all.

How many good employees were passed over just because they didn't appreciate your "vision"? Furthermore, why should anyone care?


This may well get buried, but I think it's worth pointing out that all the big employers consistently mentioned in this thread once started out as, well, startups. Yes, getting there is a near improbability, and most companies never get there, but the ones that did got there by virtue of people believing in the mission (whatever and however you want that to mean) being important enough to make tradeoffs for.


I dunno how possible this is legally, but one thing YC could do is create a pool of equity of all the startups in a batch which employees could be granted options in.

Investors diversify, and founders own a disproportionate share of their companies (because they take the largest risks, but even so), but early employees are locked in for years with no chance to diversify.

So a shared pool would let early employees diversify their (time) investment.


Speaking about a few cons from an H1B perspective from countries like India.

1. The nature of H1B Visa makes it inherent for people to not take the risk of working at a startup. Part of the problem is the short time between layoffs and finding another job. H1b's may have very little time[1] to search for a job after a layoff. A startup could make it easier for them. Short of a layoffs due to financial reasons, startups could have a decent protocol for making the transition smoother. If the engineer is not a good fit, unless he is terrible, he can work a few months more until he finds another position. A few weeks notice as a standard is very little and keeps good engineers away from startups.

2. Some startups process Green Cards(GC) only 1 year into employment as a part of their "policy". This is partly understandable as GC processing is a bit costly. But the cost is not that much(<10,000 based on my experience)[2, 3]. So this 1 year hard stop is non-sensical from a monetary standpoint(especially with developer salaries running in 80-150K over many years)[4]. It also creates a sense that GC is being used as a carrot and stick approach to make people stay, this is morally questionable because for the H1B's have a lot at stake (pack bag and go to india if you don't find a job fast enough, disrupting family and personal lives). A better idea would be to process it immediately as Google/FB etc do. This gives a lot of people confidence to work and even if it does not work out its not that big a deal.

PS I can vouch that a GC is more important than 10K$ here or there in the long run.

[1]At the moment a one time 90 days grace is provided thanks to a 2017 USCIS rule(which is plenty), but it can be only used once per H1b VISA. i.e. if you use that up once you can't use it again.

[2] http://www.immi-usa.com/eb2-green-card-cost/ [3] http://www.immi-usa.com/immigration-attorney-fees/ [4] https://stackoverflow.com/jobs/salary/results?l=San+Francisc...


That's an excellent point about the terrible H1B grace period policy. A lot of good companies have an informal policy about that, but I agree it needs to be more widespread. Do you know if any companies offer that policy publicly?


There are entire categories at work you can't do at a startup. And since you might die tomorrow, a lot of what you build is a fairly throwaway.


What is a startup anyway? It can be anything between a 2 people business without a cent to a company with 500 employees that raised 300 million dollars. Even Airbnb is considered a startup in the media. When talking about these things it's very important to distinguish what stage the startup is in because the experience varies wildly. A pre-seed startup is not the same as a round-X startup.


I don't think working for a big, well funded startup will be that much different than a big corp in terms of work life balance, stability etc. You have mass firings in Microsoft too.


One reason I would never again join a smaller startup: Most of them refuse to offer equity refreshers. Even after a significant funding raise, I've been at startups who simply do not offer any more equity beyond the initial grant.

Compare that to any competitive Big Co or startup, such as Facebook, Google, and Airbnb. All of them offer annual equity refreshers, and that equity is significant.


One thing I think most startups can do well to remember is that engineers are not the only hires a company needs to make and that modern tech companies very rarely fail due to technology factors. I'm curious why there isn't a greater emphasis placed on non-technical roles? My only conjecture is inherent bias, but I could well be biased myself in throwing that out there.


Having worked at both a Fortune 500 software company, and a small valley startup with good funding, I can speak to this issue.

On the matter of working at a startup:

PROS:

- You have a much larger impact on the product. Often times you may be working solo on a very significant part of the product. If you enjoy this feeling of autonomy, this is a major plus.

I list this as a major PLUS because at the large company I worked for, I felt like a "cog in the wheel". I could easily be replaced. Despite doing good work, I was just one of many who could do the same work. I could only "own" a small portion of the application.

- You have a chance to make money on the exit. Assuming you got stock options as part of your hiring agreement.

CONS:

- Jack of all trades, master of none.

You will be asked to wear multiple hats. In my case that has meant I was hired to do one X, but actually ended up doing Y, and Z in addition to some X. Specifically, that meant learning new programming languages, new domains, etc.

I list this as a major CON. While it can be very good to learn new languages / domains, I think you should do this on your own "track". Learning a new programing language on the job, especially at a startup, can be quite stressful when you're expected to also PRODUCE.

On the other hand, learning it on the job can give you some of the most practical experience in the shortest amount of time. So this one can be a double edged sword. In general, if you are YOUNG in your career, this is GOOD. If you are middle, to late in your career, avoid a startup for this reason. (Don't stop learning. Rather, find a mastery of one domain, and make that your day job while keeping up your abilities in other areas).

- On all the time. Your coworkers will be working weekends. That can mean that when you aren't working, you feel like you should be.

- You'll never feel like you can take a vacation. Take them anyways. But you will feel guilty, and like you're asking a lot to take a week here or there. At a big company, this is "PTO" and you either have the days available, or you don't. Take the time if you have it, because you have a large team that can cover for you.

- You'll never feel like you can leave, as the business hugely depends on you.


I did a PhD, so by the end of my 20's, my net worth was approximately zero. If I rolled the dice on a startup, there's a very good chance I'd hit my mid-30's and be in the same place I was financially at 20. Instead, I opted for FANG where I could accumulate as much in a few years as my parents did over their careers.


My two cents is that all the low hanging fruit is gone and start ups are now 'mainstream', 10 years ago you could make a nice looking TODO list and as long as it had shareable lists and deadlines you could flip it for a few million.

I think the kind of work that is required to build something is much harder. I'm probably wrong though.


To me, the cons of working at a startup in SV are these:

- lower salary than bigger cos

- mostly smaller/less challenging projects

- low chances of ever liquidating RSUs and if you do, the value will more likely be low with some very rare exceptions

- it's harder (or impossible) to achieve a decent lifestyle living in SF/Bay area with a startup salary

- lack of diversity in most small startup teams


Here's some problems YC might be able to fix.

Equity Liquidity -- I can't wait 10 years to get liquidity on options. YC could offer to purchase some employee equity when the company raises additional rounds.

Employee Branding -- FANG on a resume looks better than working at a startup. That really helps when it is time to look for a new job.


It is strange nobody here mentioned the crypto (public blockchains) space. As a pro early employees have liquidity and much more money in average than with a typical startup. Not saying the space is not full of scammers and void promises but good projects pay well and have more incentives attached.


Just a quick aside: I'm in biotech/medtech and hardware engineering. A lot of the comments here are about software engineering in SV. Here in biotech-land the average salary, even in the Bay, is about $80k.

Granted, we don't have as many start-ups as the FDA puts a hell of a damper on things.


The only reason that makes sense is to break into an industry without experience, or to move up the career ladder faster. Startups are hungry and will take folks who couldn’t even get interviews at big tech. And if you make your bones, boom, you’re in.


One nice thing about startups / small companies is they can be flexible with work hours.


Hey Jared. I think the most noticeable appeal a startup has is equity. The rules of equity are skirted, obscure and the level of trust is low.

Stratups cant compete on compensation to big-co but can compete on equity compensation and its just not competitive.


And where there are cons, what would fix them?

My understanding is insurance and benefits are a weak area. The internet ate my really long comment. Suffice it to say, if you haven't already, I will suggest you (YC) talk with an Aflac agent.


Do you have any specifics on what issues you have seen?


Things I've seen: * No 401ks (which means I'm paying extra in taxes). * Crappy health benefits (prescriptions costing 4x what they do under other plans or high deductible plans). * No commuter benefits/pre-tax Clipper cards. * No tuition reimbursement or education budget, the assumption being that just working is supposed to be the whole of the employee's career advancement. * No parental leave. * No childcare support (why this isn't rolled into coworking spaces I have no idea.) * No HR in case of harassment, politics or personal vendettas.


I don't have any experience with working at a startup. What I do have is 5+ years experience working at Aflac some years back. I no longer work there.

They sell supplemental insurance, not major medical. They don't do co-insurance. They pay cash directly to the policyholder.

Not long before I left, they came out with a disability policy that could be purchased with as few as 4 employees and working as little as 30 hours per week. My recollection is this was groundbreaking.

They can provide access to benefits at no cost to the company.


There seem to be two sides in this thread - "Fix it for early stage employees" from the OP, feels like a long term map towards less reward for capital and more for labour.

The grassroots side seems to be "give us more comp or we go work for Google" - which is roughly the same map as above but from a different direction.

However I suspect the chances of landing a gig like that are similar to landing early employee at a 50Mil exit. Or perhaps I need to go work in SF, or charge more in London...

What seems to be missing here is not a path to a new socialism (not a bad thing TBH) but that the risk / reward ratio has shifted - usually to justify large rewards there needs to be concomitant risk. But it seems to me that product market fit is being found earlier with less capital cost. And then the sheer scale of the market when you do find a fit is returning a reward out of all proportion to the investment at risk. From Whatsapp to Trello, a small team can find product market fit and go global.

In which case the reward for capital should come down in a sane market. The risk is not as big as it used to be, so the price must come down.

That seems a good thing ?


Pros: More Freedom More Earnings Potential Express Way Up the Corporate Ladder More Say in Business Decisions More Say in Work Culture

Cons: More Pressure More Work Less Job Security Possibly Little or No Starting Pay


Startup only as a contractor otherwise you'll get squeezed dry.


It really depends on the startup. There are some crazy awesome situations, and some crazy not awesome situations. It is hard to generalize across all startups.


As someone who has started and worked as an early employee at several startups in the bay area and has spent a large amount of time interviewing and evaluating offers:

Con 1: Compensation

Equity is not worth it. Early employees bare the same risk as founders, work just as hard, and have an order of magnitude (or two) less upside. The chances are that even a series A funded startup will go bankrupt and the equity is useless. Seed funded startups are even worse in the sense that the risk is way higher for just slightly more equity.

Base compensation is too low. Salaries at usually barely livable in the bay area and leave no room for savings. This has two major problems:

- First, its hard to support mortgages or families. This creates a biased hiring process that favors those already well-off or very young (and likely inexperienced).

- Secondly if the startup fails (the likely scenario), the chances are the employee's savings are non-existent. They'd more likely opt for a cushier job instead of building on their experience at another startup.

SOLUTIONS:

1) Early employees need a higher salary. No living wages. No forcing people on a ramen diet. I'm talking $130-$180k for engineers at the seed stage (in Silicon Valley), PLUS healthcare. Other roles should be proportionately similar based on market rates. This means either seed rounds need to be larger, or bridge rounds become much more common. I think the latter makes more sense; if the startup has some traction, but not enough to go for a series A, then the founders can raise a little more. If the startup doesn't have traction and burned through its seed, it should fizzle out sooner and liberate the team to do other things.

2) WAY more equity for early employees.

* 25% - founding team (first 5-10 employees)

* 25% - all future employees

* 50% - founders

* Investors eat from everyone's shares proportionately.

A win for the founders should be a win for the early team. There should be no scenario where the early team doesn't benefit from an exit but the founders do. The founders succeeded because of the team.

3) No bullshit vesting schedules. At worst, stick with the standard 4 years, 25% a year, 1 year cliff. No 10-10-20-30-30 5-year split nonsense that only favors employers and force people to stick around longer than is healthy. And add refreshers that vest. 10-20% of their annual comp. Salary bumps can also work as a substitute. Incremental rewards are important.

4) Not 100% on this, but common stock for everyone. No class A shares -- win votes by convincing the team you're right and not being a douchebag.


Con: Lack of mentorship because everyone is so busy and manpower is low.

Pro: Have to chance to decide what to do if the hierarchy hasn't been built up yet.


Startups should allow employees to take RSUs with them when they leave the company. Otherwise it is deceitful to refer to it as compensation.


Should we expect the balance to shift back in a few years where salaries+RSUs go down and startup compensations become competitive again?


I am working at Udacity right now, it feels good.


Seems to me like today's engineer #1 of a startup valued at < $10M should be getting 5% equity, not the 1% of yesteryear.


If you're young: yes try

If you can be a cofounder: yes go on

Everything else: no they are bad employers


I guess as long as you don't care about the $ might be fun


What are some well paying non-startups that are not FAANG?


How does this differ from triplebyte?


Here is an earlier sub-thread on that: https://news.ycombinator.com/item?id=15917671


Pros: - Level of responsibility and opportunity you can get at an early stage startup WAY outstrips what an established company can typically offer you, especially if you are early career. You might be able to get more money at FAANGM, but your career will not grow as fast. - Because of the above you get to learn skills that generalize (eg. how to deliver value with a product, how to negotiate a partnership, how to make an impact on a P&L). I've seen many folks come in from Big Co. who only know things that are specific to that company. The reason for this is that Big Co. has already figured out how work needs to get done to achieve their business objectives, and everyone who works there gets handed that API. I've seen folks come out of large companies and realize that they hadn't learned fundamental skills around how to generate value. That they had mostly built experience in how to operate in the environment they were in, but didn't translate outside. In startups you have to learn to generate value or the company dies. - You get to make an asymmetric bet. If you're early career your opportunity cost is low but your capture could be high if it works out. - The experience of working on an early stage team really trying to DO something is unparalleled. You won't find anything like it at Big Co. (unless you're lucky enough to get involved in a new product launch, which does happen).

Cons: - You only get one bet at a time. This is as opposed to investors who get a portfolio. But your stake is usually smaller than theirs. So it's REALLY hard to hedge your risk. This is not a worry in your early career, since your alternatives are not great. But it becomes a problem later on. If you don't have personal liquidity, you really can't afford this by your mid-thirties. - Returns are really skewed right now towards founders and investors (who dominate the cap table), and then the first "adult" executives brought in (who may not get the largest equity stakes but tend to be bonused out in cash even in the case of a fire sale, when most employees get nothing). IMO this is why startup recruiting is so hard right now. It's clear to anyone looking closely that the returns are so heavily founder/investor skewed that it makes no sense to join a company at an early stage if you have any other options.

IMO the biggest problem to fix is the lopsided cap tables. Without this it's really hard to attract talent. For most people who are startup focused, the competition is not a high paying job at FAANGM, but them starting their own thing. Here's a possible solution: Companies could start at their inception with 3 classes of shares instead of 2- preferred (for investors), 10x voting common (for founders), and 1x voting common (for employees). You could then allocate a MUCH flatter cap table so that you can make meaningful equity offers to attract folks to the early team who would otherwise have chosen to found a company themselves, but you don't run into the control issues you would otherwise run into due to diluting the founders stakes. There are certainly other solutions, but solving this problem is what I would advocate for- ie. make it more rational for someone to choose to work for your company as opposed to starting their own.


Just a few cons....

The big players have drastically pushed up developer comp. The "maybe" money that might come from a best-case startup exit isn't holding up well against the RSUs of the big players. I have friends pushing total comp north of 400K / year at the usual suspect companies. Over a five-year-span-till-liquidity your "maybe" money is competing against a near-guaranteed $2M in comp.

Equity grants for early hires haven't kept up well with both the afore mentioned industry comp pressure and the drastically increased time till liquidity. An early hire employee will be in the soup nearly as long as the founders but with significantly less upside.

That said, working at a startup can be great fun. It's also a fine opportunity to learn on somebody else's dime.


Entirely accurate. At a startup, I expect to make ~$100k/year, have mediocre insurance and work life balance, and underwhelming equity (<1%). At my enterprise job (southeast US), I’m making double the salary, 20% annual bonus, five weeks/vacation a year, great work life balance, and much better health insurance for a family of four than any startup can offer.

Unless you’re a founder, I actively steer colleagues away from working at a startup. The sense of accomplishment, impact, or whatever the feel good term is, isn’t worth shorting yourself on significant comp for years (while founders and funds are getting almost all the upside).

Edit: If you want to compete, pay more and provide more equity with less risk. Throw “hire fast, fire fast” out the door; anyone who isn’t single and in their 20s can’t rely on a job like that. Maybe consider giving preferred shares to early employees as well, so they share in early liquidity events during pre-IPO/acquisition offerings.


US healthcare is clearly a huge barrier to older employees joining startups.

At my company we have a great selection of healthcare that's fairly affordable both for employees and the company. I think it's as good or better than any packages I've seen from big brand-name enterprises. However, as a European founder, I was shocked by the complexity and effort that went into the comparison shopping necessary to get anything other than expensive, poor coverage. The quality of what's out there from JustWorks, Gusto, Zenefits et al was frankly shocking - and they are feted as "making it all easy and affordable". (We use Trinet which although in many ways antediluvian has very, very good health options at least for NY).


> US healthcare is clearly a huge barrier to older employees joining startups.

It's a barrier to anyone with nearly any disability, chronic illness, or precondition (or with family members who may have them).

A friend's wife has to take medication that is classed as Tier 4 in California (least coverage). He has had to turn down many offers as he would then have to put the family on their own insurance, potentially costing upwards of $1200/mo. just for the one set of medications. As is, the meds are <$10/mo. on the insurance via their current employer.

US Healthcare is a giant hurdle for small businesses. We need UHC in the US.


This is true but the logical implication then is why are there not more startups in Europe/Canada where healthcare is "free"..


Other barriers to entry than healthcare - labor laws, cultural issues, venture availability, and more.


None of this, the market is too small. No European country is comparable to the USA and its 300 million customers.


On the other hand, Shopify is a Canadian company with most of its business outside of Canada...


Just to state the obvious, there are things to optimize for other than compensation (like happiness); ~$100k/year provides a comfortable life and saving opportunity in many (most?) parts of the country.


Happiness doesn’t provide good health care to my wife and kids, or help me retire years earlier (I get to save >$100k/year because we live in a low cost of living area). I suggest a hobby if you want to be happy, as well as time with your family and loved ones.

Be careful about those who offer you emotional fulfillment or purpose in your job. There’s always a cost.


So much truth in here... Specially for the "just funded" startups : they loose their souls fast when the investors start to get impatient. It's a trap in so many cases.


So do you work remote to live in a low cost of living area? Just curious how many big salary opportunities are in low cost of living areas.


I work remote because I demand flexibility. I live within 20 minutes of one of my org's offices, but prefer the ability to work from where ever I want. I just happen to enjoy the low cost of living locale I live in.


Very few YC startups allow remote work and a large percentage are in expensive areas like the bay.


This is such a massive point right here ... there is so much talent, either already in "far flung" parts of the country; or currently in a place like SF, but who long to move "back home" for any number of reasons.

Having startups be more remote-friendly by default would be a huge boon for everyone involved.


This might be the one and only competitive advantage startups can offer over the big (and even mid sized) tech companies now. As previously mentioned, the compensation is so large at the established tech companies, and the (mostly) false promises of startup wealth are largely debunked, that allowing all workers the ability to move to lower cost areas or back home but still work in a dynamic industry is very appealing.

One of the risks of remote work is the next opportunity. What happens if you land a great remote job, move your family across the country, and then realize the new job/boss/company is not a great fit? Right now, it can be a challenge to find a comparable position offering full time remote flexibility. But if all startups offered full time remote, then the network effect occurs, leading more candidates to want this option and opening up a larger pool of qualified applicants for startup companies to work with.

If YC could facilitate this industry trend, you could be helping startups with talent acquisition, helping workers establish better lives in lower cost locales, helping to spread tech talent and opportunities around the country, and helping the Bay Area (and other highly impacted tech hubs) ease some of the housing and transportation issues. If this is a successful startup trend, I guarantee the big tech companies will follow.


Agreed that this is a big competitive advantage that smart founders should take advantage of. Doesn't mean you need to go 100% remote, but by being flexible on location you offer a pretty compelling alternative to a big tech co salary.


Ah, but here is the rub. If you want to work remote, who would you rather work for? An employer as established as possible (with less risk of going under) or a startup which might not even be around next year? Being remote, new opportunities might not be easy to come by, especially if the startup folds due to an economic downturn which is affecting other startups as well.

While hiring remote makes sense for startups, working for a startup might not be the best option for remote workers.


Sounds like you should found a remote friendly startup!

Plenty of money floating around. Find another remote friendly guy and go to town!

Seems how most remote friendly places have started...


I found a loophole to all this madness. I joined a company that was not remote-friendly, moved a couple hours away after about a year, and told them I'd be happy to continue working for them remotely. They obliged :)


Having been on both sides of this, this is usually career suicide.

Not to say you get fired, but you miss too much. You miss watercooler talk. You miss the invite to a new project. You get sent maintenance and bug work.

If you want to work a 9-3 and coast, sure. If you want to do cool stuff and move up the chain? Being remote in a local company is totally suicide.


Pick me!


This is true! However, there are still many quality startups elsewhere.

I’ll admit I would not choose to join one if they were to force me to live in SF and not give me a competitive salary.


yes, but startups aren't really very good at optimizing for other things. The stressful nature of startups are usually bad for happiness.

Startups are really good at providing two things - a sense of being able to affect change and working on something novel/new (assuming you actually go with a startup that does something new)


I’ve been reliably surprised with how many startup employees enjoy some level of stressful problem solving. Maybe it overlaps with being a workaholic to some degree?


Those other optimizations select for financially independent individuals and young, single individuals coming from an affluent background. It's an oblique way to maintain an "old boys'" network and discriminate by age.


I basically agree.

Unless you are a founder, go with the money.

Better Estimated Value.


How many years of experience do you have and what industry? Just trying to get a picture of your profile.


18 years in tech, last 6 have been focused on Infra/DevOps.


Take that view with a huge grain of salt. Nobody is denying that someone, somewhere is making $400k as a software engineer, but we are talking outlier employees at outlier companies. You’re not getting this as a medium level rank and file engineer, or at a non-FAANG company. This whole “software engineers make $400k” trope seems to have taken on a life of its own. Every time salary comes up here, these guys come out of the woodwork to tell you that their brother’s girlfriend’s roommate makes $400k at Facebook, therefore it is an average compensation in Silicon Valley. That is far from accurate.

Most startups are not competing for talent that would otherwise be making $400k.


FAANG + Microsoft + Uber + Airbnb hire thousands and thousands of engineers in the Valley and Seattle every year. 400K is L5-L6 salary (senior engineer, first level manager). There are a TON of engineers making that money. They are not really outliers, and FAANGMUA is also not really outlier considering Google itself has 80K employees and Amazon and MSFT have over 200K employees.


I work at Google, used to work at Amazon, and had an offer from Microsoft.

From my experience, Google/FB pay much more than Amazon and Microsoft if we're talking about total compensation so I think it's a little more rare than what you're saying.

I don't think it's that easy to hit L5 either. My teammate is amazing and had like 8+ years at Microsoft before joining Google but was hired as an L4.

For most SWEs, L5 would be the last level they ever reach in their entire career..


One thing to consider is the runaway stock market. It has a huge effect on total comp. Yes, Amazon has lower base salaries than FB/GOOG, but they've always been pretty generous with RSUs and their stock is damn high right now. There are no doubt many engineers there making those $400k figures by virtue of having been granted RSUs when they were half as valuable as they are today. It may take a true outlier to get hired today and immediately be making that kind of salary, but it doesn't take much of an outlier for someone with a few years of grants to get that high.


> Yes, Amazon has lower base salaries than FB/GOOG, but they've always been pretty generous with RSUs and their stock is damn high right now.

Actually my salary was very similar at Amazon when compared with Google and my friends have similar salaries. The problem with Amazon is that their vesting schedule is very heavily weighted towards the 3rd and fourth year.

It's true that if you stay the entire time, that might work to your benefit since by that time the stock value may have increased greatly, but I'm not sure how much that should count since you could in theory just sell your RSUs and buy Amazon stocks if you wanted to.

My experience is that total comp at Google is much higher than Amazon but again this may be anecdotal?


I keep hearing about the FAANG companies and I have to wonder what can I do to make my proactiveness pay off in getting into the running for job interviews? I feel like it's easier to get their attention as a CS student seeking internships than as a self-taught mid-level developer (which I am).

I have interviewed on two separate occasions by Amazon, and only contacted by Microsoft (submitted some forms, but they never called me back). Both times, it was from an internal recruiter making first contact with me. But when I try to reach out to them first (applications or LinkedIn), nobody answers.

Are these FAANG companies usually recruiting candidates on the basis of "don't contact us, we'll decide if we want to contact you"? Other than knowing an acquaintance that works in the company I see no other way to get into an interview more quickly.


The signal to noise ratio in the hiring process is horrible. I work at one of the FAANG companies and do a lot in the hiring process. I can tell you that getting a phone screen off of a resume that you submit is a crap-shoot. There are people applying to positions they aren’t qualified for, people applying to positions they have no idea what the role is (blast a bunch of resumes out and see what sticks), and genuinely qualified people who suck at writing a resume (and probably go unnoticed as a result). As a result, there are probably a lot of good candidates that don’t even get looked at because they are lost among the noise.

My best advice is find someone who can submit your resume as an internal referral. Those carry a lot more weight (at least where I work). However, make sure that person is someone you know and is comfortable “vouching” for you. These referrals are looked at more favorably since the thinking is that it’s somewhat of a known quantity.


I can only speak from my experience with Amazon. I sent a resume in for a job at Lab126 since I'm an embedded guy with an EE background, no CS except 21 years doing embedded software. I never heard from Lab126, but the AWS team got back to me. After failing to pass all the test vectors of the coding test, they gave me a phone interview. I did OK at best. They flew me up for an interview and proceeded to ask me CS algorithm questions on a whiteboard for 6 hours. I didn't get the job(and probably would have turned it down otherwise, since it involved being on-call), but it surprised me that their screening process was so bad. Nowhere on my resume did I indicate having any knowledge of CS algorithms, yet it was seemingly vital for the role. Strangely enough, I did study up on virtualization implementations(KVM/Xen), but no one asked me a single question about that(despite it being listed as vital on the job description).


No, they're voracious recruiting machines. It is certainly possible to get hired by writing into a webform; it's not a particularly effective way relative to others, but it works enough to justify them sending those leads to recruiters.

Other than knowing an acquaintance that works in the company I see no other way to get into an interview more quickly. You should certainly cultivate an internal advocate. In no circumstance will that be worse than applying cold; it will often be better.


The Foobar coding challenge seems to work really for Google, for whatever reason.

Go to Google and search "python list comprehension" in a bunch of different tabs. Make sure it's exactly that. If you have an extra 's', or if you do "list comprehension python", it's not gonna work.

If you go through the first 3 levels, then they'll ask you to send in a resume.

Admittedly, I only know results from the perspective of students, but I know several people who were initially rejected that got callbacks after finishing Foobar.


In 2018, this is kind of sad, judicious combinations of generator expressions and list comprehensions is so much more interesting (use lazy and eager evaluation where it matters)!

Anyway, I did that search in 20 tabs and didn't get anything.


Start closing them pretty fast and this will pop up.

https://imgur.com/a/XMt7PAq


ISTR that only works from the USA.


That explains it.


Unless you make a name for yourself somehow, the best way to get recruited to FAANG's is to get hired for a summer internship, perform well, and then get hired. Another way is to attend the job fairs at your Uni and see if you can score an interview.

I wouldn't worry too much about getting into them though. SE's are in high demand across the Valley; expand your horizons and interview with some of the late stage startups and other SE companies as well (e.g. Atlassian). They will provide amazing compensation as well as being a smaller company where you can have a bigger impact. Once you build a few years of experience delivering products, your problem will be rejecting 99% of the recruiters that reach out to you lol.

Seriously as a CS student, you really just have to get a job where you can learn and write actual code and watch your career soar.


FAANGs receive massive volume of applications, so it can be very difficult to receive a call back from a recruiter. I had a Facebook recruiter tell me that their acceptance rate is "way lower than Stanford", which, if you think about it is not that surprising. Anyways, the best way to get a call from Google or Facebooks is to find someone to refer you.


A startup is a good place to accelerate yourself to an L5 somewhere else.

If you are on a team of n<10 responsible for keeping a company/product alive you tend to learn a lot more than if you're on a team of n>1000.


True in some regards, but it’s also incredibly easy to learn how to do things the wrong way, if you have no one to learn from.


>but it’s also incredibly easy to learn how to do things the wrong way, if you have no one to learn from

Yep, say hello to startups who go cheap by outsourcing to developers who are not as good in their craft or don't care about learning more.


These startups also don't stay in business for very long ;)


I guess I might phrase it something like, if you're going to make L5 it is probably the result of excessive competence. If that is you, you will get their faster cutting your teeth in at least a few different startups. Develop judgement and a variety of experiences.


Excuse me but the median senior software engineer at Microsoft does not make $400k/yr in TC. Same goes for AMZN. There are only a handful of companies that pay $400k/yr for senior software engineers and MSFT ain't one of them (facebook, and google do however). Go checkout Blind if you don't believe. Or ask your friend at MSFT.

And like someone else said, first level managers are more like 250-350k range, not 400k, yes even at G and FB.

Uber and Airbnb don't pay that much either. Sorry I don't count paper money as real money.


> There are only a handful of companies that pay $400k/yr for senior software engineers and MSFT ain't one of them (facebook, and google do however).

None of the companies in top tier tech can afford to pay substantially less than any of its competitors. That's why they're "top tech".

If what you said was true, and FB or Google paid a lot more than say MSFT or AMZN, then all the best senior engineers would eventually leave the latter for the former, and only the bottom talent will retain. Then the latter won't be top tech in any meaningful sense.

In reality, FAANG are grouped together because they pay about the same and can compete with each other for the same level of talent. Other companies are in this category, just not as famous.


It's quite a well known fact in the Valley that FB/Google pay much better than MSFT/AMZN...and yes the best (or lets say a lot of them) engineers eventually do leave for FB/Google...AMZN has huge turnover. MSFT on the other hand is more of a rest and vest type of place with nice work life balance so not as many people are leaving.


No, he’s correct. MSFT pays a lot more in the Bay Area than Seattle because the cost of living is so much lower in Seattle (no state income tax, housing, etc) that they can get away with paying a lot less.

My total compensation went up by ~80% going from MSFT to FB (but my housing costs 3x in the Bay Area vs what I had in Boston so it’s not as large an increase as it sounds).


What you're saying is that the difference isn't between companies - MSFT vs FB - but between areas: Seattle vs Bay.

I'm mostly aware of pay in the Bay and a few similar areas, and it is largely equivalent at the levels posted here.


I'm not sure why you are trying to dispute my facts when it's clear you have never worked at any of the above companies based on your comments.

Even in Seattle it's well known that FB pays more than MSFT. So your theory about top tech needing to pay top dollar etc, doesn't hold.


You made the following claim:

> There are only a handful of companies that pay $400k/yr for senior software engineers and MSFT ain't one of them

This claim is false.

There are a lot more than "a handful" of companies paying $400k for senior engineers. MSFT will also pay you this amount in the Bay.

Overall, top tech pay about the same. You say FB pays better than MS in Seattle, and perhaps that is the case (as I stated above, I'm mostly familiar with the Bay, not so much with Seattle). In the Bay, the pay is very similar. There could be many reasons why FB would pay more than MSFT in the Seattle: for example, MSFT has a huge office there, and FB probably only a small one. So it's a pretty wise strategy for FB to offer larger pay for the small amount of positions they have there, and in this manner poach some of the best talent in Seattle, while for MSFT it would be prohibitively expensive to raise salaries across the board at Redmond.

That still doesn't change the big picture, which is that top tech pay is largely equivalent, outside of a few anomalies here and there.


"Overall, top tech pay about the same."

No, they do not. Again, obviously you have never worked at a FANG company otherwise you would probably realize this. It's quite a well known fact in the Valley that FB/Google pay much better than MSFT/AMZN.


You seem bitter for some reason. I wish you well.

FYI, I got offers from FANG companies, specifically the ones you mentioned. There used to be a gap, but on the last round the AMZN numbers were effectively the same as Google's. My guess is that over the last few years they faced the necessity to pay equally.

I have friends working at MSFT in the Bay and their current pay also falls in line with the numbers mentioned in this thread. Of course, they're senior engineers.


Your sample size of 1 or a couple does not refute my statement about not all top tech pay the same.

I think you are quite the bitter one trying to refute every single one of my comments.


Google pays the same pre-tax in Seattle as in the Bay Area, at Bay Area rates in each case. So it's also between companies even within the Seattle context.

(Or at least that's the official line. I haven't examined any de facto pre-tax pay disparities between the two locations. But at least they don't adjust comp when one transfers between those locations, or between either of them and NYC; whereas they do for relos those areas and significantly cheaper areas.)

Source: personal memories of policies from 3-5 years ago, which could have changed but probably haven't.


I didn't say median. I said it is L5-L6 comp, which doesn't make it a median as I assume most engineers will be in L1-L4 band. That said, it is not an outlier either. And won't be surprised is 20-30% of engineering and PM orgs are making that money.

Also, Uber and Airbnb gives RSUs which are not paper money. I am confident that an IPO for both these companies are inevitable.


RSU's in a company that hasn't gone public are not very liquid... not paper money, but definitely not worth face value. Take that value and cut it in half or 1/4.


You picked .5 or .25 as the multiplier. If it's still 2-5 years until a public offering, it's also quite possible for the multiplier to be closer to 1.5 or 2.

Everybody has a different assessment of how likely each outcome is, so everybody has a different expected value.


Still a lot better than stock options in a startup that isn't even close to liquidity.


Anecdotally, I know plenty of 66s and 67s at Microsoft that are pulling $300-500k in TC. Microsoft’s stock rise has also made this decade extremely nice for grants.

Course, with the average house going for $1 million in Kirkland, they have to spend it.


If you’re making $300k-$500k a year, a $1M house is extremely attainable.


Yes, but they need to spend the money of course.


Most of the employees are certainly making less, becomes pretty obvious with the http://levels.fyi salaries per level (only starts going above 400K after L6 @ Google & FB)


Most people who think of 400K (or even 200K in some previous discussions) as "outlier pay" are probably just not familiar with big tech pay and how much revenue they earn per engineer.


> how much revenue they earn per engineer

That does not necessarily correlate with salary. At least it doesn't outside of SV.


It correlates with how much a business will be ultimately willing to pay a developer, if they have to.

If I'm making a $1M profit on you, I'll be willing to pay you up to a high fraction of this amount if I have to. Financially, even if I pay you $950K, I'm still making money. Assuming my business scales, I'd hire as many engineers like you as possible, and pay them the same. Why not? I'm making a profit for each one. Great deal for me.

Of course, if you're willing to work for $100k, I'd rather pay you that instead. Hell, I'd rather you worked for me for free!


If I'm making a $1M profit on you, I'll be willing to pay you up to a high fraction of this amount if I have to. Financially, even if I pay you $950K, I'm still making money.

Where does the money come for dividends, taxes, and overhead?

If there is enough supply of engineers at the same quality, no one will pay more.


Obviously, I'm keeping it simple. My point is, profit per engineer does have a lot to do with how much I'm willing to pay that engineer. I'd rather pay as little as possible, but if necessary, I'll pay almost as much as I make in profit, because I'd still be making money.


Agreed. SV is different from the rest of the markets, and it is the main reason why it attracts so many engineers from all over the country (hell, from the world).

Although I don't regret the time I spent outside of SV, from a financial perspective as a single young engineer, it absolutely, 100% makes financial sense to consider opportunities in SF that compensate you so well.


>Agreed. SV is different from the rest of the markets, and it is the main reason why it attracts so many engineers from all over the country (hell, from the world).

In my case, SV is so different that it actually made me want to leave. Personally, I can't recommend SV to anyone if monetary wealth isn't the only goal.


"Thousands and thousands" is an exaggeration, particularly considering the portion that is churn between them. There are over 3.87 million software developers in the US[1]. I would be shocked if even 10% of them are employed by the companies you mention Nationwide, let alone just in SV and Seattle. Of that, a minority pull down the massive TC you cite. I think that certainly qualifies as an outlier.

Furthermore, the headcounts of the really big companies, particularly Amazon and Microsoft, are inflated by non-engineers. Citing them doesn't really say much.

[1] https://en.m.wikipedia.org/wiki/Software_engineering_demogra...


The other thing that people seem to forget is that a lot of people calculate their FAANG Total Comp with the value of the stock today, not on the day they were given to them. This simply because you could have yourself bought those stocks at the same price back in the days. You cannot include the increase as part of your total comp

This in some case makes a huge difference, especially now, where all the tech stocks have gone to the moon.

I believe that a lot of 400k$ packages would actually be no more than 250k$ if calculated correctly


FAANGS give you RSUs, which are cash equivalent. When I am referring to 400K, I am referring to "total cash in hand" at the end of the year. Generally the comp you get quoted when you get hired is $200K base + $200K in RSUs based on hire date's stock price. So in today's frothy stock market, you would at least earn $400K and possibly more.


that's what I'm saying. I'm clarifying that the value of the RSU is when you got them at the time of the offer. Not at the time you sell it or vest it.


The value of an unvested RSU is a very tricky thing. I had to try to value my potential RSU benefits when I got divorced. It's not the same as a stock option where even if you leave, you have an asset that you can still purchase at the contract price. RSUs are little more than a promise that at point in time X, company promises to release Y stocks to you. I'm pretty sure you could argue that RSUs have zero value until released to you.


RSUs are guaranteed money at big tech companies. I have never heard of any MAFANGs rescinding their RSUs. In fact, when shopping for a house in SV, my mortgage lender also took unvested RSUs in account when deciding how much to pre-approve me for.


I see. But for most people, when they look at their W-2 they will see the total cash they earned. So it is fair that people call that their salary.


I see. But for most people, when they look at their W-2 they will see the total cash they earned.


The stock could have gone down also. Total comp cannot take the upside of the stock.

You could have invested in the same stock and receive the same upside also. This is part of the luck in being in the right company or pick the right stock. That's why Total comp should be the number you got with the information you got at the time of the offer


Yes it can. I don't say my total comp in a given year was my salary and the target performance bonus. I say it was my salary and my actual bonus. Stock comp is much the same.


I'm at Google and I think only L7+ are getting that much, and that's not many people. I'm an L5 and my RSUs are less than 1/4 that.


200K in RSU's per year or over 4 years?


If their base is 200k? Then it's 200k per year RSUs (800k 4-year grant)


400k is an outlier for sr engineer or 1st level manager. Most all of them fall into 200-300/yr in the valley or Seattle at those companies.


400k is not unusual for a senior engineer working at big tech for several years in the Bay, Seattle, NYC, or even a city like LA.

Base salary will be around 200K, and bonus would be another 200K. Can easily be 50-100K more than that on some years.

Outlier would be 750K or more, which means the engineer is one of the most valuable members of the team.


The median T5 Google eng does not have 200k base. (It's less than that) and lol bonus is not 200k. Bonus is 15% of base. Not sure where you are pulling your numbers from but Facebook is very similar. Most senior devs at big tech are not making 200k base (more like 150-190k). It is more like top 20% making that base. But base doesn't matter. The money is in the RSUs anyway.


I'm obviously including RSU in the "bonus" portion, in addition to cash. There are also companies who pay these kind of total bonus figures in cash, but in big tech it's typically paid in stocks.

I'm pulling these numbers from direct contact with recruiters in these companies, and in some cases job offers.

Incidentally, there's an anonymous reply from a Facebook engineer under one of my other comments in this thread. His total compensation last year was $450k.


So? That's one engineer. I said top 20%. You act like the median engineer is pulling 400k at FB. They aren't.


The median employee at FB is making $240k. We can safely assume the median engineer is making more than that.

I never claimed that median engineer is making $400k. This entire thread is about the senior engineers and their payout after 4-5 of working at a company like FB vs at a startup.

If you could do good work as an engineer at a startup for 4-5 years, pulling $400k at FB is very realistic for you. With the median being $240k, it's not going to be a whole lot less.

I'm not sure why you're trying to prove me wrong, but let's face facts: even that absolute median of $240k that includes non-engineers is better than what most engineers would pull at a startup.

Bottom line: if you can stick it out as a senior engineer at a startup for the 4-5 years it takes your options to vest, then you can realistically pull $400k/yr at FB. Except at the startup, you'd make maybe $180k base, and your "bonus" would be your bottom-preference 0.01% equity that would almost certainly be worth 0.


> I'm not sure why you're trying to prove me wrong, but let's face facts: even that absolute median of $240k that includes non-engineers is better than what most engineers would pull at a startup.

I think there has been a common disbelief among many commenters on this forum about engineers making that high compensation. There really isn't any upside to trying to convince others of this reality. Its easier to mock you here than to face the facts that many are losing quite a lot in opportunity cost by not working in SV. So its natural you will face a lot of animosity here.


No one doubts that some developers are paid that much. What they doubt is that that compensation is normal. To me, the argument implicitly seems to be over the definition of what's "normal" rather than the actual existence or non-existence of highly paid developers. Of course highly paid developers exist.


That's really just a distinction without a difference. The point is that for reasonable definitions of normal, this is true. Some people don't believe that. Sure not every engineer takes home that much, but its also not only the top 5 or 10%, its significantly more than that.


What evidence do you have that significantly more than 10% of engineers earn more than $400K?

Are you talking software engineers? Software engineers in the Bay Area? Software engineers in the Bay Area working for a subset of companies?

I suspect the reason this 'debate' exists is that we are not specific enough with our language to make our meanings clear to one another. :)

To me it's difficult to tell whether the commenters here are disagreeing over the objective reality of compensation distributions or the subjective reality of what counts as 'normal'.


>Software engineers in the Bay Area working for a subset of companies?

Yes, to be clear that's what this argument was predicated on. Someone said "A significant percentage of SWEs at FANG style companies take home more than 400K per year" and other people said "I don't believe you.

No one ever said "A significant portion of all swes everywhere make more than 400K." That would indeed be a silly statement.

Specifically, this was the statement that started this thread:

>400k is not unusual for a senior engineer working at big tech for several years in the Bay, Seattle, NYC, or even a city like LA

That statement is objectively true for practically any reasonable definitions of "not unusual".


> What evidence do you have that significantly more than 10% of engineers earn more than $400K?

What evidence do you have to the contrary?

Compensation data isn't typically shared openly. Well-paid engineers have no reason to share their pay figures and create animosity or worse problems.


I have no strong evidence to the contrary.

I'm trying to learn the truth. The previous commenter made claims about the distribution of comp. No doubt they had reasons for believing that claim. I want to know their reasons so I can update my own beliefs.

I have made no claims so I don't understand why you are asking me for the answer. I'm trying to learn the answer! :)


Beyond "I work at one", there's not much I'm willing to share, but suffice to say that when the majority of the people who work at these companies are saying something, perhaps they have reason to believe it is true.

There are also past threads on reddit and hacker news which include anecdata that points to such compensation being reasonably common, but again that requires believing anonymous internet people.


You're probably right, it's just my first time encountering this.


Yes I know the median is making $240k. The median eng is probably doing 250-360k. You do not work at a startup for 5 years straight out of college and then goto FB making 400k a year. A few do, but the median engineer does not.


200-300/yr still doesn't get you less than winning the startup lottery as an early employee. So it's better to get that than risking getting only half.


$400k salary is decidedly not average for non-principle engineer salary at Amazon, Google, or Facebook.

The thing is, part of my job lets me see some outlier salary data for AI jobs and uh, I see the extreme right end of the salaried with-benefits spectrum hit a base cash comp around $300 with bonuses to $400.

Now, if we're talking, "With stock, benefits and maximum bonus included" then yes, $400k is high end but not absurd. And if you're talking a lot of work as a contractor I'd expect more.


400K is average L5-L6 total comp including salary, bonus, and RSUs. (A lot of folks in this thread seem to be confusing base salary with total comp.)


Just to add another data point. I'm a Google L5, and make nowhere near $400K. My RSUs would have to quadruple in order to even get close to that. I think your idea of a normal L5-6 salary here is a vast overestimate.


Are you in an eng ladder and in the bay area?

Because if not you're RSU grant is grossly low (since I'm an L3 who isn't fully refreshed and if my grant quadrupled, I'd be nearing 400K, and my grant isn't exceptionally high).


Or you’re getting underpaid relative to your peers.


I think you guys are agreeing with each other, right? L5-L6 isn't "average", is it? Most FAANGMUA employees are not managers/senior engineers.


I think 20-30% of Googlers are L5. If you're able to be hired at Google, you're able to make L5 within 2-4 years.


This. L5-L6 is not really that hard to get into if you have a few years of experience.


I'm looking at a Google internal self reported income form. Large majority make less than 400k.

There's more l3 & l4 employees that. L5. And way less l6/l7 than l5.

Also Uber and Airbnb don't offer liquid rsu. Nobody knows their ipo price and ipo valuation.


FAANGMUA. The acronyms just keep getting better.


The best one I've seen yet is GAANDU (Google, Amazon, AirBnb, Netflix, Dropbox and Uber). Apparently it means asshole in Hindi.

https://www.teamblind.com/article/Breakdown-of-compensation-...


Can we go with FAANGAMU? It's like a Kangaroo, but with FAANGs.


http://levels.fyi is a good tool for shedding light on some of these numbers


Make a reasonable estimate - what do you think is the total number of people earning in the range of 400K at FAANGMUA? How about in terms of percentage of engineering staff?

Do bear in mind that it takes almost 10 years of steady relevant experience to get to that level (L5+). As another commenter points out, 8 years of solid experince only made an L4.


Here's how I've seen it work, and this is specifically relevant to Bay Area compensation (although it prob works the same in other markets, just scaled down). You come into either one of:

- top tech company (i.e. FAANG)

- high growth, public, mid-sized tech company (e.g. top enterprise cloud companies)

Your base salary will be between maybe $130K - $160K. And not just for engineers, technical product/program/project managers make this as well. Your bonus will be 15-20% of your base, so another $20-30K, bringing your total comp minus RSUs to $150-200K. Your first RSU grant will prob be worth $100K per year once you start vesting. If you are a top 20% performer, you will get another grant within the next year or two.

After you've been at the company for three or so years, you will have multiple RSU grants starting to vest. Once you stack these RSU grants on top of each other, your total comp can easily reach $400K for some period of time.

A couple of caveats/risks with this comp structure

- it seems companies are much more willing to throw more RSU's at you than a significant base salary increase.

- as long as the markets are rewarding growth vs profitability, the RSU's will continue to flow

- if the market crashes, the whole comp structure may crumble.


If you're hired into the role directly.

Someone coming in straight from college can realistically expect L5 in 6-8 years. Back in the day, you used to get basically kicked out if it took longer than that.

Even coming in as an L4, you can plausibly expect L5 in 2-3 years.


> Most startups are not competing for talent that would otherwise be making $400k.

But why not?

Obviously you shouldn't only hire $400k-TC engineers. But if you're going to hire a team of 5-10, wouldn't it make sense to hire at least one more-senior engineer to help lead and mentor the more-junior ones?

When I was an early-stage startup founder, I was told by various advisers* that $150k should be the absolute upper limit on engineer salaries, and that I should try to talk engineers down to $110k or even sub-$100k by selling them on the "vision". I was told I should make up the difference in equity, but also that I shouldn't give an employee more than 1% in equity or maybe 2% for a "rockstar".

Do the math here. A company raises a typical seed round at $6M valuation cap, and is offering 2% over four years (considered VERY generous!). Even if we pretended that was preferred stock rather than common, it's worth $30k/yr. So you're trying to hire senior engineers while offering less than half their previous total compensation.

What ends up happening is you hire people straight out of college or away from other startups. But you cannot hire a senior Google engineer.

In my opinion, a tech-oriented startup should plan that exactly one of their first 5-10 engineers should be a senior engineer for whom they offer a salary of $200k-$250k and equity of 3-5%. Aim to poach an L6 from Google with this offer. (But only hire one such engineer early on. A team with too many senior engineers can be even worse than a team with none.)

Or alternatively, make sure one of your co-founders is such an engineer and is able to focus their time entirely on engineering, not other founder duties.

* Advisers all say different things, often contradictory. It's probably best not to listen to them, TBH. Yes, that advice applies to this comment as well, and even this footnote. Have fun.


Startups require crazy hours and solid dedication. If you put that into a career at a big software company, even with average talent, you will reach the level which yields that kind of money.


No you absolutely won't, unless you luck out and end up on a good team. Big companies are notoriously bad about rewarding hard working and talented engineers. That is in fact one of the main reasons people leave them (including yours truly).


If startups don't reward engineers and neither do big companies, then what does?


Nothing. In all my years ( 13 ) software engineering, the people who made the most were the ones who could sell. And I don't mean like "sales engineer", but rather who could sell their projects to team members, bosses, etc. Making money really comes down to being able to sell

A) actual, i.e. what you've built or

B) potential, i.e. what will you build

And then to get rich you need a multiplier on those things. But just being a good engineer, in general, does not get richly rewarded. If you show me a pure engineer who makes 1 million, I can show you a founder who made 100x from his work.


I'm just pointing out that its not absolute. So in general I recommend being open to switching jobs/companies until you find and environment that you personally find enriching, both professionally and financially.


Selling own labor in capitalism won't generally get you very rich.


Fine, leave those FAANG "outliers" out. Startup comp is still wildly below market.


Some of my most mediocre acquaintances have jobs at FAANG/Big N. You don't have to be exceptional to land a high comp job there, you just have to be exceptionally tolerant to BS and mindnumbingly boring work and be willing to grind interview prep.

If anything, landing a job at an unicorn is much harder cause they care about things like culture fit, enthusiasm, esoteric FotM frameworks, and entrepreneurial spirit.


Trading one anecdote for another: I've met plenty of mediocre engineers at unicorns. Every company has its own flavor of BS and "mindnumbingly boring work."


I have a friend that I consider borderline incompetent. He works for an unicorn. He claims he makes up for it in spirit in charisma.

Point is, compensation and skill don't correlate as strongly as people think.


There's a group (Dropbox, Airbnb, LinkedIN, Splunk, etc) between FAANG and Startups and this group pay really well too.

I heard Oracle OCI also pays in the 300-400k range (even for Seattle).


Yep, and that's my point: startup compensation is below market even for average, not well known companies.


Linkedin Oracle etc. are not well known companies :)?


My company isn't well known and the 200 or so engineers who work here have an average all-inclusive compensation north of $200k (many see above $225k).


You literally have no idea what you're talking about. Every one of my friends who is a senior software engineer, including myself, at a decent-sized company has a total compensation between $300-400k per year. One of my good friends has a total comp of $650k, with almost $300k base salary. I have friends at Facebook, Google, Uber, Airbnb, Apple, etc. We all share compensation information with each other.

My friend at a startup is ready to quit because he's only paid $170k for the last 5 years and he regrets not staying at Apple because the shares he left on the table were worth over $1M now. He is now 0/2 in startups, both of which you have heard of, and he's very frustrated.


Where does your friend with $650k TC work and what is their role/level?


FANG, L6-equivalent level.


400 is starting to push into standard deviation territory but 300 (total comp) is absolutely right in the center of the bell curve for a mid-level engineer (not a rock star), from everything I've seen and heard both first and second hand. In the valley, anyway.


That's where I am. I'm pushing $300k total comp at Twitter as a senior SWE out in Colorado.

Before this I was first employee of a startup that eventually sold to Google. Even if I'd stuck around for the acquisition I'd have gotten $0 from my stock options—employee options were wiped out completely. Why put up with that bullshit when a big publicly-traded company will reliably deposit large sums of money into my bank account every quarter and I don't have to work crazy hours?


Speaking as someone that has stock options... how did your employee options get wiped out?


The usual way is that all the investors, who hold preferred stock, get paid before all the employees, who hold common stock. If there's not any money left over after the preferred holders get paid, the value of employee equity is 0.


how did you get that much? Hired as senior with a lot of rsu? is it mostly rsu after the jump the last few weeks? If I got to senior I wouldn't be making that much based off what Im being told about comp increases. I must have gotten a shit deal when I joined lol


I worked here during the years when the stock was in the toilet and managed to get some retention grants that have turned into a tidy sum.

Plus I joined as a SWE1 so there are two promos in there.


After your startup and Google experience, you were hired as an SWE1? Also, curious if the experience of the startup or subsequent integration was perhaps more valuable than the opportunity cost.


I never went to Google, I left the startup a year before that happened. That startup was pretty much my first job out of college and I was there for about two years.

In that specific case, I believe the startup was worth the opportunity cost. I was coming from San Antonio, not exactly a tech hotbed, and from a small liberal arts school nobody's heard of. I'd interviewed at a bunch of companies out the Bay and was rejected by all of them. A friend was an investor in TechStars' seed fund for their San Antonio program and he put me in touch with the founders of one of their companies. Those guys took a chance on me and hired me on a contract to solve some scaling issues while they were still in the program.

Once they graduated and raised a series A, they brought me on full-time. I worked remote for another six months after they moved the company up to Boulder, eventually following myself. They let me go after about two years but during that time I gained a ton of StackOverflow reputation for Scala and Akka, which led me to one of Twitter's open source advocates who made the intro for Twitter's Boulder office. That was back in 2015. About a year later the company sort-of sold to Google, who then fired almost everyone and re-sold the IP (or something, it was weird and I wasn't there, but my investor friend gave me some of the details).

So, in my specific case, the startup was worth the opportunity cost because my opportunity cost wasn't that high. I didn't have a six-figure SV job as a backup, but I was able to leverage the risk I took into that sort of job.


Maybe I'm in a bubble but everyone around me is making at least 400k total comp. Doesn't seem that uncommon in California.


But if you work at Uber/Airbnb/Whatever out of that 400k total comp 250k is just paper money.


Not really... If you have 250k / yr equity, your salary (plus bonus) is usually north of 200k at those companies.


naw, the people I know work at netflix, apple, amazon, google, spacex, microsoft, tesla, etc


From what I’ve heard, SpaceX pays pretty poorly. Extremely long hours for below-average aerospace salary. Surprised to see you mention them, but maybe they’ve improved lately.


But successful exit of a startup is also outlier. It is only fair if we compare outliers to outliers.


> these guys come out of the woodwork to tell you that their brother’s girlfriend’s roommate makes $400k at Facebook

Reminds me of grade school, when "my uncle who works at Sega" always had let their loving nephew/niece play that game that wasn't out yet.


It's not that amazing. I work at a startup, 300k cash comp, plus probably worthless options :-0.


depends on level / YoE most of the time, theres breakdown for FAANG companies at http://levels.fyi


This. I joined a moderately successful startup (good acquisition where founders made > $1 m) and the rewards were not worth the risks as an early employee. Also, the RSUs are low risk, high rewards at the "usual suspects". Unless you love working on a small team with more autonomy, but without comfortable resources and losing sleep over whether your company will be there next week, I just don't see the attraction of joining a startup as an early employee. You can learn a whole lot from a "usual suspect", where the world's experts reside, and a whole team of competent and hard-working people are also.

With that said, I'm super interested in how we can make it better for early employers, and the obvious solution is to give them more equity. Why do founders get over 10x early employees ? Just doesn't seem fair.


Just be warned, a startup often has the promise of more autonomy, but there are plenty of startups run by ego-centric micromanaging wanna-be engineers. Be careful equating, 'being able to talk to the CEO' as autonomy, you may find yourself having to explain your decisions/code to people who's engineering skills are 'being able to convince a VC to give them money'. You'll also probably not tackle 'large problems' but hack and slash a Node/Django/React app into meeting an MVP.

Choose wisely.

That being said, I'd go for a startup if you want to eventually run your own. There's so much you'll learn from seeing things actually occur that you'll never learn from anywhere else.


My experiences from startups have been underwhelming for reasons similar to yours. I haven't been part of an autocratic ego-centric management, but I still felt like I didn't deliver any real impact. I was just told to fix bugs, close tickets, etc. Same cog in a machine feel but without the benefit of working closely with people to mentor you.

In the last startup I was in, even though we're in a team of only 3 engineers, implementing design changes was an uphill battle. The senior engineer lives in Eastern Europe so communication time was difficult, and he had a very impractical way of doing things (preferred his own hand-made JavaScript framework over third parties, no modules, no integrated testing). These things lead to making myself a harder sell for companies that follow less unorthodox software development practices.

Yeah, they can often be more freeform, but also by giving you the illusion that you can flip things around, or be a big fish in a small pond. Being that big fish is not good if the pond itself stinks.


That's absolutely true. The assumption "that you will always get more autonomy at startups" is fanciful.

In reality, many if not most startups are run by inexperienced and often immature managers and engineers who are substantially less qualified and skilled at running a team than their equivalents in more mature tech companies.


I have seen this too. Particularly when the first round of early employees don't have a lot of experience, but have a significant amount of influence and sway simply by nature of being an early employee. It can be very frustrating being someone with experience that has to sit back and watch big mistakes be made despite warnings from people who have done it before.

There's an attitude I've noticed also of, "we're not Xyz." Hate to break it, but most problems aren't really that unique. If you resist learning the lessons from other companies, you will repeat their mistakes.


> Particularly when the first round of early employees don't have a lot of experience, but have a significant amount of influence and sway simply by nature of being an early employee.

As is often the case...

Very often the first generation of employees at a startup will consist mostly or solely of folks with 0-3 years experience at most. Then if that startup survives, all these people are "naturally" promoted to senior / team lead / tech lead levels...

> It can be very frustrating being someone with experience that has to sit back and watch big mistakes be made despite warnings from people who have done it before.

I feel you, brother. I've been there too.

> There's an attitude I've noticed also of, "we're not Xyz."

It's called "young arrogance".

"Hey, we're a bunch of straight-out-of-school engineers, but clearly we can do better than Google because we're awesome!".


> but there are plenty of startups run by ego-centric micromanaging wanna-be engineers.

This times 1000. Too many stories to tell, especially in SV.


Also,

> you may find yourself having to explain your decisions/code to people who's engineering skills are 'being able to convince a VC to give them money'

> you'll also probably not tackle 'large problems' but hack and slash a Node/Django/React app into meeting an MVP

Those hit way too close to home for me. I made the mistake of joining such a business when I was fresh from college and broke. The only good thing that happened is that I got some savings out of it. Issues included broken spaghetti code, hacking together MVPs with enough fancy graphics to impress clients (faking it all the way), and having to explain to my tech illiterate boss why I couldn't "just fix it" on the harder problems.

Oh, and the micromanaging is real too. It can wreck your mind to the point of needing professional help.

The real kicker was that it was all on an indefinite "contract" (1099 but you sit in the office like a regular worker - I already filed the IRS contest forms) with low pay and zero benefits. Never working at an early startup again.


I think we may have had the same first job out of college.


> Why do founders get over 10x early employees?

Because founders take at least 100x the risk of an early employee, and 100x the personal risk and commitment.

Founders generally aren't getting paid (at least until revenue or significant funding comes through) and they have 100x the impact that an early employee does on the success of the company. If an early employee doesn't work out, the founders just replace that person. If the founders aren't working out, the company fails. If an early employee isn't working out and the founders don't replace that person, and the company fails, that is again the founder's fault.

Early startup employees have higher risk and generally more stress than at established companies, and if the market was rational, they would be compensated more, in cash, to offset this risk and stress.

Equity is not the solution, for many reasons. The biggest reason is that the founders will always value the equity higher than early employees. If not, they should not have founded the company.

It sometimes makes sense for founders to sell some of that early equity to VCs (anyone who has buckets of cash and wants more risk/reward exposure) who can afford to hedge by investing in lots of early stage companies, only one of which needs to be a winner. Once the VCs put the money in, it makes sense for founders to hire people at market rates.

VCs should be people who are swimming in cash, and therefore looking for a high rate of return, and with a high tolerance for risk in the amounts that they are going to invest. Early employees in general do not meet any of these criteria.

For early employees to accept equity in place of a market-clearing salary is then just a mistake. We see engineers settling for half the salary they could have at an established company, plus lottery tickets. This is absolutely crazy. Early engineers in the vast majority of cases should not be going anywhere near the kinds of crazy risk that pouring half your salary into a long-shot investment represents. Especially when the salary that you are left with is tied up in that same risky venture.

The reasonable position for early employees is to insist on not also being early investors. Raising money is the founders' responsibility, they should go out and do that, and early employees should demand the same salary they could get at an established company.

The argument that equity compensation aligns incentives makes sense for co-founders and for executives. It almost never makes sense for early technical hires who can easily be replaced.


At the end of the day, when your company gets sold, and your founder worked on the company for 1-2 years before you did, but they walk away with millions and you walk away with the equivalent of a Camry - I question whether equity is not the solution.

In terms of market rate salary, the startup will never match FAANG. Seriously. I'm talking about Sign-on bonus, annual bonus, re-ups, benefits (like a heart-transplant $100k operation for your kids), gym membership, rent subsidies, etc...

So it has to be equity since that's all the startup can offer. It's income inequality 101, what we're living in.

Anyways, at some point, I'm complaining, because the system is the way it is and we have to live with reality. And I understand that if founders didn't make it out big enough, they wouldn't start one in the first place. But I have a feeling that if enough people were educated on how much a bad deal being an early employee was, we could tip the scale a bit.


> "In terms of market rate salary, the startup will never match FAANG."

> "if enough people were educated on how much a bad deal being an early employee was, we could tip the scale a bit."

Yes. The reason why startup compensation is much lower are because of perception (people aren't rational) and only a shift in perception will shift the balance.

The reason why equity is not the solution is that the default outcome is not the Camry, it's giving up some multiple of your salary in exchange for nothing. People overvalue lottery tickets. We're not rational.

If a funded company (series A, say) is offering you equity as a large part of comp, you have to ask yourself why the VCs don't buy back that equity for the cost of paying market rates for talent. If it makes sense for you, it should make even more sense for them. Unless you think you have a higher appetite for risk than early-stage investors, something doesn't add up.


> If a funded company (series A, say) is offering you equity as a large part of comp, you have to ask yourself why the VCs don't buy back that equity for the cost of paying market rates for talent.

Because the company wants to align your incentives with its own success, of course. That's the original reason why equity was offered to employees in SV, back in the good old chip-making days.

According to your argument, equity never made sense as a compensation factor. Obviously that's not the case, it has been an important factor in the past, and if enough people wisen up, will probably be so again in the future.

Look, either startups sell equity and pay developers market rate, or they give them more equity to compensate for under-market pay. Otherwise, these startups are underpaying developers, plain and simple, and these developers will prefer to work in companies that compensate them fairly, which this thread's commentary suggests is already happening.

Incidentally, I agree that paying market rate in cash isn't the solution, because startups need harder, more dedicated workers than the average company in the market.

That's exactly why equity is crucial.

Tellingly, startup founders agree when they pitch their startup as "definitely a unicorn, stick around and your options will be worth millions of dollars" to every single candidate. It's just that the equity factor is now only empty promises, because even early employees only get tiny amounts of bottom-preference options.


It makes 0 economic sense for developers the alignment thing is marketing BS. Go to the best VC in the field and offer him/her to bet all of the funds money on a single deal see how hard he/she laughs at you. If you exclude top 5 VC firms the whole VC field is net losers and that people who's full time job is to pick winners


> startups need harder, more dedicated workers than the average company in the market.

I agree. So hire harder and more dedicated people. This is not impossible.

The idea that people will work harder for equity than they would for EV-equivalent cash is where we disagree.

If you have 5% of the company, and your direct contribution makes 5% of the difference in whether the company meets its objectives, setting aside whatever external market factors that are totally beyond your control--how motivating is this really? How motivating would it be to a more economically rational actor? Maybe this is the real reason why startup employees tend to skew younger...


Thanks for the interesting discussion. The only reason why I'm still advocating more equity for early employees is because founders get so much of it. So if an exit were to happen, which could make the founders very rich, the early employee gets nothing. In your case of the default outcome, both get nothing, and that is OK. But if something were to happen, the early employee still gets nothing.


> if an exit were to happen, which could make the founders very rich, the early employee gets nothing

Depends what you mean by "early". The first engineers should be getting 1% or a bit more and getting diluted along the way. This can still be $400k-1M for 4 years of work with a base that is more than enough to "pay the bills".

Not quite nothing ...


You're assuming that VCs can evaluate the prospects of a company better than potential employees. The reverse is often true, especially for startups where the main risks are technical.


The main risks are never technical, except in hindsight.


Respectfully, if you don’t like the split, the clear answer is to be a founder.

The option is available to all, but very few take it. For really good reasons.


The point is that startups are not competitive in recruiting good talent, and they go to the large companies.


I disagree- I’m really good. They just have a very large hammer they swing. Anybody can get good results with the resources they bring to bear. Getting good results with jack shit takes talent, haha.

The answer is not and will never be writing bigger checks with money you don’t have. It’s getting real up close and personal with your team and figuring out a way for everybody to win. If folks want to ride my ride, that’s super, but most cats don’t really have a taste for my risk and work profile. Where I excel is professional development and lifestyle. I can move the needle for people there.


True, but you don't have anything a big company doesn't have, or can't have. Therefore, to differentiate yourself from your talent going to FAANG, you need to provide more equity to early employees than what is the status quo. They joined your startup for risk, and your rewards need to match up with that risk. A large company has professional development, a great lifestyle, and mentorship. What they don't have is huge upside if there is a huge exit, and the early employee at a startup needs to capture that.


People think they want the equity but they absolutely do not. They may want something for nothing, certainly plenty of folks are interested in that, but you don’t really understand the devils bargain until you’ve made it.

I know what I’m doing. Been at it for years. It works for everybody. There are so many people who deserve a shot but will never get one, if you’re willing to dig and develop there is no shortage.


"Because founders take at least 100x the risk of an early employee, and 100x the personal risk and commitment."

The risk part of this isn't remotely true in many cases,or rather it's offset by so many other benefits accruing to them. Founders generally are drawing at least a small salary and, in this context (YC/VC funded) they are not necessarily risking much if any of their own capital. Moreover they are benefitting in ways early employees don't (e.g. social/network connections).


Be careful about assuming that how the company looks when the early employees are hired is how the company always looked.

It usually takes 2-3 years before a typical founder can get seed funding and even think about hiring employees. During that time period, they are funding the company themselves, and doing all the work themselves. Yes, they usually draw a small salary once the company is VC-funded. By that point, ~95% of founders have been flushed out of the market and failed.

There are a small minority of people who can raise VC on just an idea because they're white, wealthy, and went to Stanford or because they're roommates with a VC's daughter or because they're an unusually slick salesman who can swindle lots of people. I would highly recommend not working for these people - or really, any founding team who did not build and sell the initial version of the product themself - because they generally do not know what they're doing, and these startups become a miserable experience for the employees. But they are, I'll reiterate, a very small minority of founders. They are a somewhat larger minority of the founders who can hire employees, because getting VC investment automatically puts you in the pool of startups that is looking to hire. That's an information distortion between the viewpoint of employees (who only see the startups who have gotten at least to the first funding round) and founders (who see all startups, including the ones that struggle for years to get their first revenue).


> There are a small minority of people who can raise VC on just an idea because they're white, wealthy, and went to Stanford

Really? Does white people baiting have to become totally normalised? It’s not like East and South Asians aren’t over represented in VC land.


I say "white, wealthy and went to Stanford" because that is the reality of it. The "Hi, I'm going to raise money on nothing but an idea because trust me" strategy does not generally work if you are Indian, Chinese, or any other minority ethnicity, unless you previously had an exit (in which case you know just how hard actually building a business is, and my comment doesn't apply to you). It largely also does not work even if you are white, if you happen to lack the cultural capital that comes with growing up wealthy and going to Stanford. I know a number of East and South Asian founders (I'm one of them) who have taken VC (I'm not one of them), and they all got to that point the old-fashioned way: they built a product and sold it, themselves, before any VCs invested. These are all folks who have plenty of credentials, including working at major successful Silicon Valley companies (Sun, Google, Microsoft) or graduating from Stanford.

(Exception: if you are Chinese and your investor is Chinese and you have a personal connection to that investor you can sometimes raise money on "Hi I have an idea and trust me." This is a recent development and comes from the massive amount of Chinese capital floating around these days, and is sometimes not actually the best move for your startup.)


Do you think (a) White applicants are more likely to get into YC? (b) Founding teams with no white people that get to demo day are less likely to get funded than those who do?

I know YC is a relatively small part of the VC ecosystem but it’s pretty influential. If the VC ecosystem is as racist as you say there should be plenty of opportunity to make better returns out there for some enterprising VC.


I think YC is pretty unrepresentative of the VC industry in this regard, simply because the VC industry is as racist as I say and YC is hoping to be that enterprising VC that seizes this opportunity for better returns. The YC partners have been pretty open about this - racism creates a market opportunity, and so they've put in a significant amount of working in retraining their own unconscious biases so that they don't miss the market openings that are left behind by other firms. (I should probably also say that they're not doing this just for better returns - it's also the right thing to do, but it has the side-effect of being economically rational.)

There are a few other VC firms that similarly work hard to avoid missing promising founders of minority backgrounds, but they are still the exception rather than the rule. Over time, the "rich, dumb, and prejudiced" folks will get flushed out of the market, but that's over a lot of time. Besides, they'll probably just get replaced by a different set of prejudices - nobody can be 100% unbiased, you can only hope to replace biases that are useless and arbitrary with ones that are somewhat more useful.


You have a very narrow view of startups if you think that's how they all operate. Many many companies never raise money. Many founders are unpaid, or just paid the bare minimum legally allowed. And numbers alone do not tell of the significant social and psychological pressures while employees can always quit and go work somewhere elsewhere. Even successful acquisitions don't guarantee riches to founders and that's completely overlooking the fact that many don't find success and are left with nothing.


"while employees can always quit and go work somewhere elsewhere."

This is an exaggeration at best. For the vast majority of employees there is a lead time to begin employment at most places. Typically this will be a minimum of one month (interviews + decision + org readiness to onboard).

By the way, it applies equally to founders as you describe (anecdotally I've seen a number of founders get regular jobs while they wound down a business).

"Left with nothing" except social connections and, exactly like the employees they had to fire when the business failed, a need to generate income from another source.

Founder lionization is absurd.


How is that an exaggeration? I talked about the ability for them to go to another company. Founders cannot just leave and have a much greater lead time if they lose it all.

What social connections do you think founders get that employees somehow dont? And what is this worth? So founding a company and losing everything is fine because you make some friends? If you talk to any entrepreneurs, you'll quickly realize you'll lose more friends and connections than you gain, precisely because of lack of time and ability to relate. It's a very lonely road, not some glamorous jet-setting adventure.

What's absurd is thinking that starting a company is just some hobby that is no different than any normal job. Until you actually do it, it's easy to overlook the incredible personal investment and stress it takes to put something together from nothing. Most companies fail, and many do not raise capital or have some quick meteoric rise but rather suffer through years of trying to make it work. The upside for founders is incredibly rare while the downsides are very common. Employees get paid either way.


It's only a lonely road because of decisions they made themselves.

Maybe if they stopped treating themselves like some anointed class and shared the equity with their employees instead of viewing them like lower-class citizens it wouldn't be so hard to find comrades.


Employees aren't friends and really shouldn't be. Maybe you've had a bad experience with some founders, they certainly are just as varied as people, but the role itself is anything but easy.


> Employees aren't friends and really shouldn't be.

That's a fine view to take! But don't come rattling the cup around going "but poor founders, so lonely, nobody to talk to" when they've made that choice.


You seem to be missing the point, as the prior comments are talking about "social connections" that founders get as a significant benefit, and which I'm saying isn't true.

Nobody is complaining really, certainly not the founders who chose what they do. In fact it seems like people who aren't founders that are complaining about the supposed benefits and lack of work without actually understanding what it entails.


When the founder starts with a million bucks in his personal bank account, and is pretty confident that even if the thing fails _someone else_ is still gonna pay him six figures for _something_... yeah.


> Because founders take at least 100x the risk of an early employee, and 100x the personal risk and commitment.

Simply untrue.

Many early startup employees work intense 12-14 hour days. Are you saying founders work 1,200-1,400 hour days?

Early startup employees also risk about the same as founders. Maybe a little less, financially.

> Founders generally aren't getting paid (at least until revenue or significant funding comes through)

That often happens fast, particularly in markets with well-established, well-oiled VC machines like SV.

Founders usually start out with under market pay, but it's maybe x3-5 under market, not x100 as you imply.

> Early startup employees have higher risk and generally more stress than at established companies, and if the market was rational, they would be compensated more, in cash, to offset this risk and stress.

You're talking about it as if it's some sort of impossibility. There's no natural law that says that early employees must get a fraction of 1% non-preferred shares and almost never make any money from it.

Early employees can and should get a bigger piece of the pie. If they don't, then it's not just something to be wistful about ("if only the market was rational!"), but there will be very real consequences, which we are already seeing: startups won't be able to hire top talent, because the top talent will go to companies that pay it better.

> Equity is not the solution, for many reasons. The biggest reason is that the founders will always value the equity higher than early employees. If not, they should not have founded the company.

So you're telling early employees working 12-14 hour days that they don't value the startup? Irrelevant, unsubstantiated nonsense. "You shouldn't get more equity, you probably don't want it anyway!". If they don't want it, or don't believe in the startup, what are they doing there?!


> Many early startup employees work intense 12-14 hour days. Are you saying founders work 1,200-1,400 hour days

Hours and days don’t capture the value. I have risked my house, every minute of spare time, I have put Heroku bills on my personal credit card, paid contractors out of my pocket and had to create something out of nothing within a difficult market vertical. Comparing that to a “long day at the office” doesn’t even compute.

Early employees also get paid. In my little company, I am the last person to get paid. My employees are the first even when it’s coming out of my own pocket.

It’s asinine to equate an early employee with a founder. As far as 12-16 hour days for employees — if that’s the case then you are doing it wrong. Nothing good comes from those sorts of hours — it isn’t sustainable even for a little bit.


Just to bring some perspective...when I was starting out, I was a teacher. I put in 12-16 hour days, got paid the inflation adjusted equivalent of 23k/yr, and put school supplies on my CC while facing the significant opportunity cost of spending my most energetic years empowering others.

I finally burned out and “retired” to 10x the salary at half the time and energy cost.

My point is that people will do things that are not in their financial interests because they are believers. Early employees are believers. I think you are underestimating the amount that early employees are putting on the line, including things like out of pocket costs for services for those businesses. People ARE doing it wrong, if rationally self-interested is your metric.


I loved your response. Just to add to it: early startup employees aren't working hard just because they selflessly want to contribute. They often hold the belief (typically mistaken nowadays) that their equity will be worth tens of millions of dollars, because that's what the founders told them. So they pour their heart and soul into this venture that will surely make them rich.


> Hours and days don’t capture the value. I have risked my house, every minute of spare time, I have put Heroku bills on my personal credit card, paid contractors out of my pocket and had to create something out of nothing within a difficult market vertical. Comparing that to a “long day at the office” doesn’t even compute.

First of all, kudos to you for being so dedicated and courageous.

Most startup founders that I know aren't like you at all.

Often they have seed funding very early. Not only do they pay nothing out of pocket, but typically they can draw a modest salary pretty early on.

The other thing is that nobody is claiming you shouldn't get more equity, that is fair. My argument is against ridiculous assessments that "founders always work x100 harder than any employee".

Most founders I've seen weren't like you, and I've seen early employees working harder than founders in some cases.


Fair point. I haven’t been lucky enough to raise a $750k seed round because I went to Stanford and play tennis with a Sequoia partner. So my perspective is based on my experience of actually suffering to build something while, you are correct, many decently funded startups could do a better job of sharing the reward with early employees — especially when founders are essentially spending other people’s money.


Founders don't work many more hours per day than early employees at x100 less than early employees. They work many more months/years before earning an income at all.

By the time the employees start to get hired, a large part of the risk and work that a founder does to earn their hopeful future fat stacks has already been done.

Now, are startup compensation packages a little low and relying on the money making reputation of past decades? Sure. That doesnt mean there isn't a world of difference between working hard on something that has a decent amount of vetting for below market rate, and working hard on working that's almost certainly not going to pan out for zero dollars.


> Founders don't work many more hours per day than early employees at x100 less than early employees. They work many more months/years before earning an income at all. > > By the time the employees start to get hired, a large part of the risk and work that a founder does to earn their hopeful future fat stacks has already been done.

What you describe isn't the case for most tech startups I know.

These startups need a lot of highly involved technical work done, and often need to hire a small team early on. They typically get seed money quickly. It's not unusual to see seed money right from the start.

> Now, are startup compensation packages a little low and relying on the money making reputation of past decades? Sure.

The point in this thread is not that it's "a little low".

The numbers quoted is that if you're a good engineer at a top tech company, you can almost guarantee about $2m over 4-5 years. In a startup, you'd make less than half of that in cash, with the only compensation being some stock options, that people are rapidly realizing are worth nothing in most cases.

That's a big difference, especially over many years. And we didn't even mention the large gaps in benefits, healthcare, work-life balance, job stability...

The bottom line is that the startups were so good at squeezing the real value out of their job offers, that now only irrational developers will choose them over bigger already successful companies.


If good means experienced/senior, which is what the people pulling those numbers in are, then yeah I certainly don't think startups are anywhere near competitive with big companies for talent. I don't think they really need to be, or should try to be.

If you're 15 years in at Google then yeah, no shit you shouldnt take a job at some hinky dink no name company. You're severely demoting yourself. You wouldn't go wait tables at a restaurant and expect the compensation to be competitive with your software engineer salary. Your skills aren't that useful to the restaurant, they wouldn't make anywhere near enough money from you for it to make sense.

Senior level big software company employee vs startup employee is like that but on a less extreme scale. You're more useful to them than you are to a restaurant, but you still have a lot of skills and experience that it doesn't make sense for them to pay for that it does for a big company.

Its on me for not specifying and making assumptions, but imo when talking startup competitiveness it should be focused on fresh grads or those with a couple years experience in industry but not necessarily at big tech. That's where startups are going to find their cost effective generalists, and its where I think the compensation is "a little low and relying on past reputation".

Also, with good devs making $400-500k/year at bigco, I think it needs to be kept in mind that those numbers are with a lot of their compensation being in stock and big tech stock having risen a lot in the last decade. Someone whose compensation at Facebook happened to turn out to be $400k/year would have been getting signed each year for far less.

Using those numbers would be like evaluating startup packages as if theyre guaranteed a large ipo.

As for startups getting funding right from the start, that means they're being funded based on founder credentials rather than the qualities of the business. If you have those kind of credentials and use them to start a company then your opportunity cost is likely huge. That's the founders additional risk there.


> If they don't want it, or don't believe in the startup, what are they doing there?!

It's a job. Early employees working 12-14 hour days are not doing themselves or the startup any favors.

If the market were rational, compensation would be more in cash and less in kool-aid, the importance of work-life balance would be understood even at the early stages, and the idea that a startup has some special kind of magic--where people sleep under their desks and believe in the dream--would be replaced by professionalism and the sober assessment of probable outcomes.

The reasons that startups have yet to learn lessons that other industries learned decades and centuries ago are easy to see in the startup culture if you look for them.


> It's a job. Early employees working 12-14 hour days are not doing themselves or the startup any favors.

I worked in early stage startups. There is absolutely a strong sense of a small, intimate team working hard for a common goal.

Nobody is claiming or treating it as "a job". When the founders were asking the whole team to regularly work entire weekends before launch, nobody said it was "a job".

> If the market were rational [...]

You keep repeating that, but it is a sort of truism that doesn't stand up to even cursory scrutiny.

High-acceleration startups are, by definition, trying to reach ambitious goals quickly. They're not about providing a nice work-life balance to their members.

If a startup founder pitched a VC with "we all have great work-life balance, and it's our goal to stay this way!" she wouldn't get a dime.

Startups are intense, and have intense expectations.

The reality is that startups need people to work harder, sacrifice more of their lives, for a few years, in a hope of a big payout, which is where the equity component comes in.

This formula worked well in SV for decades, but recently the VCs and founders got greedy, and said "hey, why should we reserve millions of dollars for our early employees, if they'll work just as hard for empty promises of such amounts instead"?

That's the current situation, as reflected in this thread.


take 14hours/day multiply by avg. going rate for contract work in SV and it stops making sense even for very avg devs.


> The reality is that startups need people to work harder, sacrifice more of their lives

There's probably two areas where we might disagree here.

One is that "sacrificing more of their lives" leads to better outcomes. Reasonable people can disagree on whether, or under what circumstances, 80-hour weeks and weekends at the office actually do help the company.

When you are a founder, it is hard not to work all day every day, and you have to actually force yourself to take time off or you're likely to become less effective without even realizing it. Often this same intensity and drive filters down, but in a distorted way, by the "nobody wants to leave the office first" effect. Hard work "theater" is just as common in startups as it is anywhere else, but the hours are longer and it is even more destructive in the long run. Where the correct balance should be between "real artists ship" and professionalism and having a life outside of work--that's a big issue.

Setting that aside, the other area where we might disagree is that if you decide long hours are where it's at (and I'm not going to disagree with how you run a company if it's yours) then how do you motivate people to do that?

> When the founders were asking the whole team to regularly work entire weekends before launch, nobody said it was "a job".

Is that because nobody would do that for just "a job"? Or is that because nobody would rationally do that unless they were being fairly compensated? Finance and petroleum are very different industries but in both of them people put in long hours, risk their health, and are (sometimes) well compensated.

Leaving aside pep talks, let's say you can motivate people to work long hours by giving them either equity or cash. Even if the expected value of the equity is higher, the higher variance makes the cash a far better choice for most employees. The question is, if employees were compensated wholly in cash at whatever rate the market would set, but had the option to buy the equity they are getting for the salary they are giving up, as a totally unrelated and optional transaction, how many of them would take it?

> This formula worked well in SV for decades

How do you avoid survivorship bias here?

Regardless, we can agree that the situation has gotten worse, in the sense of people taking compensation packages that you need a finance degree to understand, but I wouldn't say it was rational for most employees taking early equity even before it got worse.


For early engineers, dealing with the beginnings of software and corporate systems and seeing how they can shape them up, the temptation to work long hours is at least as bad.

Don't act like founders are unique in this affliction.


Valuing a startup and being in a position to receive a meaningful amount of compensation from said startup if/when it IPOs are two very different things.

I am not an expert, but between dilution of stock, the high risk involved with any startup, the timeline to payoff on equity and accompanying opportunity cost for non-founding engineers, and the overall lack of control which even early employees have relative to founders, it’s not unreasonable for an early employee to say “I do value the company but do not want to bet the farm on it for the next five years of my life. I will, however, as an employee, give it my all.”

Especially if said employee is > 24 years of age.


I agree with what you wrote, but the reality is that startups can't pay market rate in most cases. So they should at least offer more equity.

Or, you know, they can try to keep getting away with offering 0.01% non-preferred stock, and telling every employee that the startup will sell for $1BN at least, and they will become millionaires.


Founders are being paid passed seed. So their risk economy spans "garage to seed". Following that, they certainly do have x10 commitment, and non-existing "work-life balance".


This.

It's really only obvious why founders deserve a much larger exit than employees after you've tried to start and run a company.

There's plenty of edge cases where it doesn't feel fair, but in general, starting and running a successful startup is nothing like being an engineer. And it deserves a very different level of comp.

Also - there's plenty of engineers at startups that wouldn't get a job at a large tech companies.


My issue is that just because something was hard before you came, but you're just as talented, why do they get 10x in compensation ? It's kind of like saying because Steph Curry came to the Warriors 3 years before when they weren't a Championship-contending team, he deserves 10x Durant's salary. Curry was drafted by the Warriors and started the culture and created small-ball, but could you imagine his salary being so high ? That would be absurd, with Curry making $250 million per year.


Your example isn’t that accurate. Imagine being a talented sailor coming into an already sea worthy vessel. That’s for sure worth something.

Now imagine having to create convince people to invest in your crazy boat idea, build the darn ship, prove it won’t sink, and then finally do some sailing.

In no alternate universe is sailing a ship the same as all the other steps. Maybe you’re just as talented as the main dude/owner of the ship. But you sure as heck don’t have the experience or skill in building a sea worthy ship.


Good point. Let's say you do have that experience or skill in building a sea-worthy ship. Let's say you are more valuable than your founder given where the company currently is. Maybe the company is in the growth stage, and your skills matter more to the company's survival than the founder. Why, oh why, does the founder make out like a bandit, and you make out like a chump.


I mean...so go do it ? That’s the point. You might be a better version of Steve Jobs and Elon Musk, but if you’re not striking out on your own you will never get the rewards of the person who actually did do it. At this point all you’re saying is what the bitter/jealous little boy says “oh I could do that” while watching from the sidelines.


I'm not disagreeing that one should become a founder if they don't like the early employee packages. I'm saying we should make early employee packages suck less.


That narrative is completely false.

Initially there is definitely a bit more work//risk, but don't forget that they also get all the benefits associated to it, even early in the life of the startup:

Social//network connection with other entrepreneur that will always give them a fallback job in case the startup fails. They are also seen as brilliant individuals and market themselves so much more then normal employees.


A bit more? You vastly underestimate the effort involved.

And who's guaranteeing all these fallback jobs? Other founders just hire failed entrepreneurs so they can stick together? That's a great way to lose money. You must be reading about the 0.01% of founders who get all the attention and the fluffy feel-good startup posts because this is definitely not how it works.

And yes, more risk deserves more reward, why is that even controversial?


> And yes, more risk deserves more reward, why is that even controversial?

I think the argument is that the current reward to an early employee is a joke compared to the risk their taking, given the other job options available to them.

So its not that the founder shouldn't be rewarded fairly for their risk, but that early employees are not. Thus the answer to this thread is just that being an EE isn't worth it.

I think that makes sense, an EE should end up making more money then a non EE for the same effort/time. Otherwise, why would you risk ending up making less in case the startup fails?

So say a startup has 10% chance of success. On failure, the EE loses 200K compared to non EE jobs. That's a 9 in 10 chance of making 200k less, so maybe the 1 in 10 chance should give at least a 9 time payout, where the EE would end up making 1800k in case startup succeeds.

Otherwise, you'd be crazy to accept an EE job, unless you just can't find any other non EE work.


Sure, but that's up to the employee to decide. Forget startups, why does anyone work for any of the other thousands of companies out there then? It's just not as simple as some money metric, and either way the market will correct for it, as this entire thread shows.


Well, the thread was about if it was a good deal to work for a startup. And its not, so its about a potential employee asking for advice to make that choice. If another person asks about another type of employment they might get different or similar answers.

That said, I think its obvious for a tech worker currently that unless you're located somewhere which only has startup jobs, and you don't want to relocate, then you're better of going with an established business with more guaranteed pay and equity.


Having a constant ratio of risk without looking at the company is absurd.


Because founders take at least 100x the risk of an early employee, and 100x the personal risk and commitment.

Absolute rubbish. Considering the opportunity cost, lost benefits and so on compared to a BigCo an early stage employee is easily going to be 6-figures in, and probably working 80+ hours a week. All so the founders can toss them a few scraps from the feast.

Meaningful equity participation or big-company pay and benefits. Anything else is pure exploitation and the founders and VCs know it.


What's rubbish is thinking that people don't have personal responsibility. If someone who can "easily" get 6-figures and the luxurious benefits of a BigCo decide to work for a startup instead, then that's their choice and there's no moral judgement needed.


Partial agree. Folks also shoulder responsibility for knowingly scamming young folk that don’t know any better yet.


It's not a scam...

This isn't an elaborate con involving lies and deceit, it's a pretty clear setup and is offered in writing before you start which you have to accept. There are 1000s of articles now about working in startups and how equity works, along with fair ratios. The research is minutes away and is no different than checking the paperwork for any other part of your employment.


that's their choice and there's no moral judgement needed

Sure. And when you hear VC backed companies whining that hiring is soooooo hard, now you know why.


Could you please stop posting low-substance, high-acid comments to Hacker News? You've done it a ton, it damages the site, and we've asked you repeatedly not to. Plenty of people are arguing civilly and substantively for views similar to yours in this thread. It's not hard!

https://news.ycombinator.com/newsguidelines.html


> I just don't see the attraction of joining a startup as an early employee. You can learn a whole lot from a "usual suspect", where the world's experts reside, and a whole team of competent and hard-working people are also.

I’ve noticed people tend to specialize at larger places, and not everyone wants to go deep rather than wide. Startups are a super easy way to optimize for a wider skill base, albeit at a sharp cost of depth.

YMMV, but it depends on the type of education you value.


I can't speak for other because people choose different walk of life but I thought I share what I felt about specialization vs generalization w.r.t to large companies and startups.

Generalization will limit career and compensation eventually. There will be a point where the market will have a glut for general skillset.

Specialization, on the other hand, usually leads to higher compensation and valuable skillset.

This does not mean that Specialist can't be Generalist. It could be that Specialist was once Generalist and get bored :).

By 2012-2014, the landscape of web development has not changed drastically so if a Generalist stops doing what he/she did and chose to be a Specialist from 2014-2018 (say, in Storage design, Distributed Systems, Machine Learning, or AI), that doesn't mean he/she can't go down to the product/web layer and contribute: it's still MVC doing CRUD backed by MySQL/PostgreSQL and with a touch of some client-side stuff.


I see your point, and I agree. I'd also say that even though people are "deeper" at larger places, there are so many different "deep" people that you tend to get "wide" if you need to. Just ask a different person.


> I joined a startup and the rewards were not worth the risks as an early employee.

Which risks did you take?


Risk of not being employed by big-paying corp + risk of not having that big-corp on my resume which consequence with the risk of being unemployed for 3-5 months once startup is gone + risk of working nights and w-ends because of reasons + risk of having a tiny network for my next job hunt + risk of pivot every N months + ... maybe I should really quit my startup and apply to Bezosland.


> maybe I should really quit my startup and apply to Bezosland

You should. They're constantly impressed with the quantity of their applicants that they will only reply to you if they want to hire you at all. Otherwise, you'll spend another six months waiting for an email that will never come.


Opportunity cost being the main one, and living uncomfortably. Benefits were not that great. Resources were small, which limited potential for expert help.


Risk of not earning similar to what FAANG offer.


It's not simply compensation, but the variety and flexibility of learning or working in different things, and from others.

Try doing that with a startup whose bulk of development is done overseas. No personal work connection, lack of meaningful discussion (due to time zones and cultural/philosophy barrier), no concern for your growth as an individual. You are more likely to be distant from your workers due to startups' smaller budgets discouraging the use of in-house developers.


I wish I could say otherwise, but all my startup experiences have been kind of like that. Wouldn't change it for the world, though.


>The big players have drastically pushed up developer comp. The "maybe" money that might come from a best-case startup exit isn't holding up well against the RSUs of the big players. I have friends pushing total comp north of 400K / year at the usual suspect companies. Over a five-year-span-till-liquidity your "maybe" money is competing against a near-guaranteed $2M in comp.

I can second this. But it's not just the money though. One big thing for me is lack of actual vacation/sick time accrual in favor of this "unlimited PTO" nonsense. It leads to a culture where no one ever feels comfortable taking vacation or sick time (the obvious goal of the policy), and work life balance is a nightmare as a result.


A saner equivalent to 'unlimited' is 'minimum required'. That way, folks know for sure you're supposed to take at least 3 weeks (or 2 or 4 or whatever) and can do so without worry.

In fact, to call it unlimited and not have a minimum is probably always a scam - its so easy to post a minimum, to not do so must be deliberate.


Ditto - I prefer a flexible and generous actual paid time off policy over unlimited PTO. One big benefit to a defined policy is accruing time off you'll be paid out for if you leave. That can be a non-insignificant amount of money for some people.


"Unlimited PTO" is a policy ripe for employer exploitation. In practice at my workplace, this means a) Cannot take more than 2 weeks of PTO at a time (even if you want to go unpaid). Automatic manager rejection. b) Cannot be combined with other forms of time off. I had a kid recently and was told that PTO cannot be combined with FMLA. c) When I told them that I wanted to take FMLA, I was told by the Dir. of Engg that I could not take any further PTO for the rest of the year even with the "Unlimited PTO" option and said policy was unrelated to FMLA. He went so far as to state that when he worked at Twitter, there were folks who would alternate working 2 weeks with 2-week PTOs cause of the Twitter's "Unlimited PTO" policy. I found that extremely insulting and de-motivating.

Of course, I am sure a lot of this has to do with management culture /values. Another colleague in a different department is being discouraged from taking FMLA (which is borderline illegal). However, he feels stuck as the company is doing his Green card application and has him by the balls.

All that to say, I took my FMLA and handed in my notice as soon as I returned.


I work for a tech company that's public now, but has had an unlimited vacation policy since before IPO. I take 5-6 weeks of vacation per year (in addition to the 10 fixed holidays we get). Who cares if you don't "feel comfortable"? Do it anyway! Trust me, you'll start feeling comfortable real fast once you have a reasonable work-life balance.


I work for a non-startup/non-tech company with unlimited PTO and people here take advantage of that all the time.

Unlimited PTO doesn't lead to work-balance nightmares; it's the result of management discouraging employees from taking breaks.


I've worked at two companies with "unlimited PTO" and it also worked as stated.


The other goal of "unlimited vacation" is that companies don't have to pay out banked vacation days upon end of employment.


I guess that depends on the jurisdiction. I worked at a company with unlimited vacations and they had to pay. It got quite complicated to estimate due days when employees started leaving in droves and there was no record of any holiday taken.


> "unlimited PTO" nonsense

Absolutely. I've seen multiple startups with this ridiculous policy. The net effect of it is that people hardly ever take any time off, and certainly less than employees with more sensible policies, since taking any time off directly reflects on your moral character.


I worked at a large Seattle startup (~300 people post Series A), with "unlimited PTO" and only had 5 days approved the entire year.


I've had unlimited PTO at a place with double digit employees, and one with four-figure employees.

These issues around having vacation days "approved" seems like a function of your bosses, not your PTO plan. If you have to get your time approved, it doesn't matter the size of the bucket you're pulling from.

My experience is much more "hey I've got a couple weeks off coming up, by the way, I'm thinking of [x, y, z] for making sure everyone's up to speed while i'm out" and no pushback.


I agree with this, but I think that there is something to be said for the cadence at which others take vacation. I think it's more accepted at megacorp that you'll use most of your earned vacation and that's fine. As a result, everyone does it.

At a lot of places that have unlimited vacation, I'd bet that people take less vacation overall, and part of that is the status quo/what is currently acceptable.


The last experience I have with unlimited PTO is it being unlimited PTO until people actually try to take PTO. Then that all goes to shit.


Duo, where I work, has an unlimited PTO policy. If you take less than 15 days a year, they try hard to encourage you to take more time. It's common to take more than that.

I think this policy really depends on the culture where you work.


Those issues are because of leadership and culture. Unlimited PTO is perfectly fine. It's much more flexible for both sides, and limiting time off is definitely not the goal.

Plenty of companies do a great job with it and have no questions asked up to a certain amount or minimum time off to encourage usage.


+1 to this. 10 years ago you couldn't make 400K at Google, Facebook, Microsoft, etc. Now you can.

Startups made a lot more sense when your opportunity cost was 50-150K per year.


Basically, startups started taking more funding, and VCs realized there was more money to be made, so they're squeezing the little guy with terms.

A small startup taking less (or no) funding can 'afford' to give more equity to employees, who are effectively providing the capital (in the form of labor) to the business. Today's startups taking huge amounts of funding AND cheap labor are trying to have it both ways.


Yup, they just realized "hey, why should we pay random engineers millions of dollars on successful exists?".

They never stopped promising them, they just stopped putting any terms in the equity plans that would lead to them.


Honest question since I'm not familiar with the area - who is making 400k at Microsoft or Facebook? Not the typical mid-level software engineer, I'd assume. Are these product leads or head engineers making the 400k?


400k is reasonable for total comp after a few years of experience. Note that total comp includes a bunch of stuff that's technically discretionary, like your annual bonus, and a bunch of stuff that's paid out but not really cashable, like meals and health insurance. Your pre-tax cash, sans benefits, is probably closer to $200k.


People don't usually include health insurance and free meals when they think about their total comp.


If it goes on my taxes, it's part of comp.


Nobody counts free meals as part of their total comp.


These numbers are realistic for any senior engineer working there for over 3-4 years.


Are these engineers at Facebook/Google/etc. working the typical 40 hour work week or more like 60-80?


Obviously a throwaway account, but I work at Facebook, on an infrastructure team. I average ~45 hours/week, except for the week I'm oncall, which is about every three months. I probably work 60 hours that week. I get in early (7:30am) and leave early (3 or 3:30), and sometimes I'll review diffs at night, but normally my laptop stays in my trunk when I'm at home.

I work hard when I'm at work, and really focus. I don't do a lot of the extra-curricular stuff that you can easily spend your time on. I'm an L6 and last year earned just north $450K with decent performance reviews. I have damn near a million dollars in unvested $FB RSUs, too, so there's almost no chance I'm going to leave for anywhere that won't match that with equally liquid public shares.

¯\_(ツ)_/¯


Thanks for the response. Sometimes I get the impression that engineers are killing themselves doing nothing but work with occasional sleep, so it's good to hear you're around 45 hours.


Would you mind sharing how long you've been working there and your level of seniority? Would be super interesting to know for at least my reference.


My guess 6 to 10 years


Depends whether you count the half of their workday that is spent on a bus.


That's optional, for folks who WANT to commute (eg, either want a big house in BFE, or want to live the city life, or whatever). If you want a short commute, it's yours -- if you live in the city, work for one of the many tech companies up there. If you want to work at FB, come be my neighbor and walk to work, I live in a great walkable neighborhood <2mi from FBHQ.


There's some data about this on Blind for Google that seems pretty solid: https://www.teamblind.com/article/google-engineer---total-co...

For Google, it looks like 90% of L6 engineers and a single-digit percentage of L5 engineers are at this number. So yes, not your typical mid-level engineer (many/most engineers plateau at L5).


I wonder how sustainable this is.

Its 400k while their stock price is crazy high. But If we really are in a tech bubble, that money is back to the typically 80-120k of most tech jobs.


Disagree. You get 400k at FAANG when your base is 150k plus 20% bonus. Sure that bonus will go down to 10% but the rest of the 100k+ stock grant per year is not going to become 0. You would still end up with 225k which is still more than startups.


A burst bubble will kill pretty much every startup that can't get to profit with what they have in the bank right now. Raising will be next to impossible. You do not want to be at a startup if that happens.

I'm old enough to have seen the dot-com bubble and it's aftermath, and it wasn't pretty.


Facebook and Google and others make their money globally. They don't actually make a lot of money from Silicon Valley that's just where their workers are. I can't think of a more diversified, protected stream of income than one of the FANGs right now, even if the US has a recession, there are still countries around the world that will be doing better.


>I can't think of a more diversified, protected stream of income than one of the FANGs

Arent they 100% tech and nearly 0 physical products?

That is not what I learned 'diversification' is.


Your definition of diversification is flawed.

Their customers are diversified not only across product sectors, but across the globe. Unless internet traffic or engagement drops, which it hasn't yet and probably won't until a new technology replaces it, they don't need physical products to make the billions upon billions that they do.


But the startups will suffer in the same way.


It seems to me these high compensations started appearing right after Apple, Google et al got their hands slapped for colluding to hold down engineer salaries.

https://www.theguardian.com/technology/2014/apr/24/apple-goo...


If there is a bubble + a burst, I'd rather be at a big company flush with cash. (Note: I'm currently at a startup!)


You can make that much. You can also win the lottery. Your opportunity cost should not be measured against your best case alternative, it should be measured against a most likely case.


If you want to look the average comp at FAANG or any well-paying public company it's "only" 250k. That versus the average case at a startup being closer to 150k (average options are worth 0).


I agree with this too. There is a tier of engineers that are good, but for whatever reason, can't get into the big 5. They're bad at white-boarding or maybe they don't live in an area where the big 5 have offices.

In those cases, maybe a startup makes more sense.


Often I find a number of great engineers that the big 5 disqualify for two main reasons: Location or Education. The big 5 tend to not allow remote work and if you don't have a college degree it's often hella hard to get an interview.


But the Big5 have tons of locations. Amazon in particular has tech centers in places like Phoenix and Detroit, while Google is in Chicago. Microsoft is even in Fargo!

Unless you want to be a digital nomad I guess. Then it’s probably not ideal, but I do know some fully remote positions exist at the L6 level at Amazon.


Google has an office in Chicago, but from what I hear it's almost entirely sales jobs.

I live in Chicago and periodically have Google recruiters contacting me, and it's never been for a position in Chicago, it's only ever been for Mountain View.


That is not true anymore. They have engineers now, and they're rapidly expanding.

They do have a low base though, $98.5k vs. like $110k or something in MTV (and of course most people negotiate that way, way up).


I'm pretty sure they all pay less outside of their HQ location. At least in London, salaries are significantly less for the equivalent role.


In America, they generally don't. It's a mild adjustment at worst. Chicago is the biggest I've seen - $98.5k base vs. $110k base for L3 SWE - but FB doesn't change their comp, Amazon and Microsoft only increase it in the SFBA and NYC (IIRC).

In fact, for new grads Amazon pays the exact same TC in Seattle and in Detroit.


Oh cool, didn't realize that. Hopefully London will catch up.


Historically, the money in London has always been in the finance sector. Both large banks and hedge funds.


I think even in finance you'll be unlikely to touch 400USD (~300 GBP) for a similar level. Sure there are outliers, but of the senior people I know in this area total comp is around 200GBP after many years. It's much easier to just contract (if you don't mind the mercenary role), you'll make similar due to the tax savings.


That seems about right. 100-200k GBP in London, 200k-400k USD in the USA. Standard packages for people with a few years of experience.


> But the Big5 have tons of locations

Name one Big5 job in the entire U.S. south. Or at least one that pays as well as them.

There aren’t any.


Facebook is in Austin; Amazon is in Dallas


Austin isn’t the south.

Raleigh / Durham probably is the best tech scene in the south. No mega companies but a good number of second tier, ie. Redhat, Sas, Epic, and so on


Last I checked, Austin is south of the Mason-Dixie line and has plenty of small towns around it that will be glad to remind you that you’re in the South.

RDU definitely has an enterprise tech scene. So does DFW!


Ok, so Texas is technically in the South... you got me.

I suppose I should have clarified: major southeastern cities (Atlanta, Charlotte, Raleigh, D.C., Nashville, Miami)


AWS has several thousand engineers in the Virginia suburbs of DC, with a bunch of local VP-level management

(and that's not including anyone who works on the us-east-1 region)


Apple and Amazon could end up choosing Raleigh for their HQ2. So maybe that'll soon change.


I've only ever lived in Raleigh and I'm very skeptical they'll pick Raleigh for HQ2.

I'll be very excited if Apple ends up deciding on Raleigh though, it could easily push up salaries significantly.


Then don't live in the south. You'll get paid more, the weather will be nicer, and you'll meet less numbskulls with confederate flags painted on the hood of their trucks. Win/win/win.


Google's Skia team* is in Chapel Hill, Microsoft has a team in Raleigh working on VSTS. I know a few folks that have interned there.


Yeah, I doubt I'll even bother to apply to the big 5, maybe even the big 20. I'm coming out of a yearlong software intensive in October with a liberal art major from a marketing background. I know a few people at those companies but there is also the question of leetcode. I think my chances are much higher with other types of companies, startups included.


As someone without a degree, getting an interview at the Big 5 was quite easy. Passing those interviews is another thing entirely but having the right experiences in your resume has been more important in my case.


That's the thing, right now, I don't really have the "right experiences" that's why startups do seem appealing.

I have the skills people are looking for but not the resume validation with internships, the right degree, or school. I got an internship at the start of my intensive where I got to work on some fun problems and used my marketing skills too.

I think the only other track would be through open source contributions. If we circled back in December or January, I wouldn't be surprised if I ended up at a non-tech SMB, small consultancy, or startup because of my prior experiences in marketing paired with my new SWE skills.

Something I was wondering, in your experience or anyone reading, do I have to always focus all the technology stacks for each role and project or can I focus more on the problem I solved?

For example, in my internship, for one problem that made a big difference was setting up all their email automation and tieing it into their website. That project wasn't a ton of programming but my work; but by the end got them about $150k in revenue with my other work on their Black Friday sale, as an intern. Most of the SWE projects I got started but wasn't able to finish in the 3 months (priorities kept changing) like a tool that converted audio from videos into searchable indexes for their youtube videos (granular text searchable video basically). I'm hoping to redo that project on my own. I did get their website to speed up though (an older WordPress website).


Absolutely focus on the problems you've solved, and also the problems you failed to solve after getting deeply involved in them.

They know that you'll have to learn their proprietary technology stacks, which are always both ahead and behind the public stacks they inspired. At some companies they won't ask anything about your resume keywords after the phone screens.

Most Big 5 companies use what's called "Behavioral Interviewing" or "S.T.A.R." to formally assess how you get stuff done, and the technical questions can be answered in almost any language you like. Hell I've given successful answers to Big 5 "tell me about a time when you had to…" questions based on experiences in bicycle manufacturing and nonprofit administration, but it really has to involve ownership if you're straying from the norms.


I'm good at "S.T.A.R.", most of my effort in the past is using CAR and PAR but it's not a hard shift. I'm glad to hear they don't limit it to just technology problems.

>"the problems you failed to solve after getting deeply involved in them". I have done it before in interviews when asked about weaknesses or failures; I've never done it on a resume though. How would you go about representing that on a resume?


You don't put the failures on the resume as failures :)


I think this might be true if your lucky I was up for a FANG position in London but I have an atypical education I I suspect my lack of a degree counted against me.

With the best will in the world some low level recruiter working out of Spain is not going to be able to read between the lines and work out that actually working for a world leading RnD org on campus at one of the elite UK universities might actually mean I was a good candidate.


I'm like you, I've got some really niche experiences. I went to a #1 program at an arguably #1 school for undergrad for the industry I was planning on going into. I also have a unique personal background (extensive life-long travel) which has been helpful in more than one way but it's hard to see that on my resume.


For what it is worth, we LOVE people with your background for both technical and non-technical roles. If you're ever interested in at least exploring a startup in the marketing technology space, feel free to reach out!


Thanks! What’s a way I can contact you? I’d love to learn about what’s out there. If you don’t want to post here then you can email me at “lassitergregg” at gmail.


In the bio :)


I checked there initially but it was empty and still is: https://www.dropbox.com/s/g8uodwa450lw0lh/Screen%20Shot%2020...

:(


In those cases the big 20 make sense.

Stsrtups are great but you are always held hostage waiting to cashin


> 10 years ago you couldn't make 400K at Google, Facebook, Microsoft, etc. Now you can.

> when your opportunity cost was 50-150K per year.

That's why Google, Facebook, Microsoft, Amazon, etc are not attractive at all in Europe.


Can you elaborate? My impression was that they still pay very well, while the startup scene is much less hot than in Silicon Valley.


I can't echo this enough, I have been going from startup to startup most of my career and I am about burned out and have almost nothing to show for it financially. I am ready to work with a big player from now on. I wish someone would have told me steer clear of startups unless I was a founder.


The problem is that since we are drawn to startups, we tend to read material about startup by startups. And startups would never say joining one is bad, since they need employees. And they would never make it easily known that founders get most of the benefits here. They throw things around like "great culture" and "office perks" but at the end of the day, they walk away with millions and you walk away wiser. Saying you're the next Google is like saying you're the next Buffett - the numbers make it too unrealistic for an early employee to do well.


I'm a startup founder and will happily say that if you are an engineer, in Silicon Valley, in 2018, and you are maximizing for income, then you should not work at an early-stage startup.

I did some hand-wavy math, here: https://medium.com/@kwindla/what-kind-of-silicon-valley-comp...

Dan Luu did some, too, here: https://danluu.com/startup-tradeoffs/


I’m sorry but I don’t buy it. Startups employees are squeezed out by vc dilution and lack of big exits. Those $1m total equity cash out from startups I fear are fairly rare.

Whereas working for faang type companies, a l5 is more or less guaranteed to make $300k a year. $500-750k is doable without being a “brand name”. Timing and luck, but the spread is much smaller.

Startup founders have made a devils deal with vcs to underpay employees. You know it. Unless you issued preferred stock to all employees?


Maybe a devil's deal, but not with the goal of under-paying employees.

I know very few founders who have the highest salary at their own company, which is as it should be. Founders of VC-backed companies are making an explicity equity-vs-salary trade-off.

And every founder I know would love to pay employees more.

The challenge is that taking VC money is a commitment to try to figure out how to grow relatively quickly. There are never enough resources to try all the things you wish you could, on the way to product-market fit.

It's perfectly reasonable to criticize this model, but it's not a model that is intended to negatively impact early stage employees. Hence the discussion in this thread, much of which is about how the economic context in the SF Bay Area employee market has changed, and how to adapt.

Look at this another way: employees at early stage boot-strapping tech startups generally make less money than employees of early stage VC-backed startups.


It's marketing BS of selling dreams to both Entrepreneurs and in turn to employees that keeps the boll rolling for VCs. If you are honest you will realize that it's def. designed to take advantage of employees.


It looks like you both agree, they said you should not work at an early stage startup.


Unfortunately Im in the midwest and Im interested in something very niche (operationalizing data science using hadoop, spark, etc) so i would have to move to SV to work at a non startup company and honestly I just dont want to.


I'm happy you say this, and I wish it was more well known, even if obvious. People join early-stage startups for the potential bucks. I'm not saying that's a good reason, but I'm saying most graduates, who are not as educated about the world, will join a startup for the money upside. Being honest like you are is not the same as admitting there is some degree of deception in the culture about how well off you'll be as an early employee in the startup world.


I mean, just look at the tagline on the website being advertised by OP:

https://www.workatastartup.com

"Join the next Airbnb, Dropbox, Reddit, Stripe, or Instacart". Reminds me of Ben Affleck in Boiler Room.


Yeah my first company out here in the Bay Area was a startup. After that experience, not really looking for another startup position at the moment. All my friends I used to work with have moved on to other non startup companies and are all making minimum 50% more in terms of total compensation.

Yes, yes, there is always things more important than money and they have all that too as well. They can afford good leadership, good management, talented ICs. I can go on and on.


Not that 400K isn't believable, I don't think it's the norm, but being outside of the Bay Area or the US for that matter, I'll buy it.

However there's one other area where startups have failed to evolve, doing a worse job than big companies actually and that's accepting remote employees.

Big companies have been doing better because at the very least they are opening offices in multiple countries, whereas most of the startups I'm seeing are staying in the technological centers, a majority being in Silicon Valley and hiring locally. Which is nuts.

For somebody living outside of San Francisco's bubble or other expensive and overrated cities like New York or London, 150K is actually better than 400K. In many of Europe's cities, minus the expensive ones (e.g. Zurich, London, Paris), you can have a great life with 150K.

It doesn't happen though. And for the very few startups I've seen accepting remote employees, many times they are hired as contractors, without any perks or stock options and an extreme expectation for low hourly rates.

Well, you know what they say, most startups die and this is one reason why.


> For somebody living outside of San Francisco's bubble or other expensive and overrated cities like New York or London, 150K is actually better than 400K.

There's no way that's true. You can easily save six figures per year on 400k total comp, no matter where you live. Saving 100k per year on 150k is much more of a challenge, especially when health insurance and taxes are accounted for.

Point being, you need to measure net savings. And you don't want to adjust that by cost of living.


I disagree. There is nothing worse than teams scattered around the world in "Tech Hubs". Big companies have no idea how to run remote teams, they only know how to outsource.

A startup needs to deliver fast and have access to capital. SV, in particular, have most important ingredients - money and talent.


Being remote is one of the few things startups can compete on for really talented employees who for whatever reason don't want to live in a tech hub.


I live in the bay area. 2 incomes. My rent is ~30k/yr. If I rented a house and had a family it might be ~60k/yr. Are you seriously claiming that 150k after tax income doesn't cover the difference in COL in the bay area?


You can have a great life with 150k in London or Paris. Very very great.


The math on this is even more direct, as you can take the differential in salary and invest directly into early stage companies that interest you, trading technical advising for access to seed rounds. You often end up with more equity (on better terms) than you would have had as an early employee, with less risk.


I am interested in this. Where does one find these opportunities for early stage investment?


Hang around startup accelerators, and if you have some special expertise you can offer, and you have an interest in early-stage investment, people will seek you out.


> It's also a fine opportunity to learn on somebody else's dime.

If you're getting paid less to work at a startup, it's not on "someone else's dime", though. It might be the most affordable way to (re)train yourself, but opportunity costs are still costs.


The money aspect is interesting from a want-to-be founder's perspective.

Suppose you know you want to do a startup, but want to gain some "experience".

You could

  A) Work at FANG for 4 years, put away 200-300k, blow most of it in the first year learning how to run a startup.

  B) Work at a startup for 4 years, put away 50k, raise 200k seed and find yourself in roughly the same place, minus 10% equity.
For someone who doesn't intend to go on as a founder, my current conclusion is go to whoever will pay the most without completely compromising your morals.

The expected value of your options is not 400k, and even if you get lucky it wont be available for 8+ years. Dear 22 year old self, would you like to put a down payment on a house when your 30? If so, go get a job that aligns with your goals.

As others have mentioned here, as long as a founder isn't blatantly fraudulent, things tend to work out quite well for them. Founders learn the most and are often in the position to try again, either in the form of another startup or as a product manager within an established company. FAANG companies are also hungry for aquihires, so its possible that founders holding preferred stock may even walk away with something.

As an employee, the butt end of the bimodal distribution is probably negative. It's easiest to get through the FAANG hiring process as a new-grad, and not having one on your resume makes it even harder to break back in later.

My experiences only. I interned at and ultimately turned down a FAANG for startups 5 years ago. In the process of starting my own now.


Well... If you can get 400k per year semi-guaranteed... that puts you in a certain category. I don't think that's average though, even in sv. Anyone making this kind of money (regardless of industry) usually has limited options for employers that can match it.

I do agree there's a problem with early employee comp. They don't have anywhere near the upside founder's do, but may be taking more risk on their equity than later employees. Personally, I think the best solution would be to create some liquidity for employees. 5-10 years, if you're still around is just too long.


What also comes into the picture here is the extremely high cost of living in the Bay Area. Even startups have to offer $200k in non-"maybe" compensation to make sure people can afford living here. Even a relatively small size startup with 50 people now already has $10 million in salary costs per year (not even counting taxes, benefits, etc.).

So overall the balance is tilted very much in favor of the big companies that can afford paying people that much. I'm wondering how that changes where startups get started. Is the Bay Area still the dominant place for this?


Which raises the ancient Quan - why are startups so reluctant, as a species, to establish remote teams? How come VCs are even allowing their investees to pay bubbly rents and wages?


Go read Ronald Coase's "The nature of the firm". And if your work _can_ be structured to minimize the transaction costs, you might as well go to a low-wage country rather than mess with a remote, medium-wage team. I worked with one company that had all of their engineering team in Pakistan. The SV-based VP engineering never saw his team face-to-face. They had a huge cost advantage.


It reads as if you equate the term "remote" with "remote (US)". The term "remote team" most obviously implies your pool of developers includes the entire earth (bar some language/timezone difficulties).


Follow the money?

Who owns the apartments? The VCs?


VCs are landlords in Silicon Valley. They money startup employees pay in rent often goes back to them so I guess they don't mind high wages that much as they are benefiting from sky high rent by renting out their real estate.


Or how about in person but not in SF?

Benefits of in person. But not SF salary.

Has been my route, no complaints.


Yes.. well China might be cheaper.


This gets even more exacerbated as you become more experienced. Most startups I find seem to be quite averse to having Senior or above titles, which is fine (desirable for some, even), but then offer comp that doesn't really scale with experience in any meaningful way. It makes little-to-no sense to work for a startup when they only offer you 50% of the total comp of FAANG, being a non-founder.


Unless you are working in a country where compensation is not that great. Not everyone is working at Silicon Valley or even in States so compensation between working in a well-funded start-up and big Co. is not that different. This is at least the case in Finland. Average developer in Helsinki from what I've learned might get paid 4-6k € per month equal to 48-72k year. Underpaid? Maybe. But this is how things are at the moment.

It's easy to lose perspective looking at the world from Valley/States but the salaries are generally much lower elsewhere.


Agree. Paysa is off their rocker for ranking the comp from a private company like Uber vs the comp from a public company like Google. (https://www.paysa.com/company-rank)

RSU grants from big public companies are the new/old way to get ahead in tech.


Also, it's Uber - Brand isn't comparable.


Related question but not directly to OP:

I'm a 6 years experience SWE making $200K TC (all "paper money") in Orange County (CA) right now -- is it realistic to ask for this much paper money if I wanted to attempt a spot at a FAANG(MUA)? I'm still young and flexible and have no trouble moving around so I wouldn't mind at least trying.


I agree with this from experience. I worked at a startup for about 2 years and when they exited, it was a horrible exit for me. I made $30k in the sale. I got a $15k bonus my first year with the next company, plus I had so many other benefits of being at a larger company.

Work-life balance is not great at most startups and you're expected to not ask questions about it.

Larger companies, it's always touted that they're better about work-life balance, and after being in larger companies for the past 2-3 years, it's been apparent my stress has gone down while still being productive!


Stock markets have fared quite well in the past 5 years which explains why compensation is so good. But what if there is a market crash?


Three quick thoughts:

* The base compensation and benefits alone, even if RSUs became worthless, are still serious money.

* I would expect startups founded and running in today's boom market to fair worse than established firms. Short runways, limited revenue, and a sudden contraction in funding availability is not a great mix.

* If the lucrative comp packages of the big companies collapses, the world of startups will still be there for you. You'll have the added advantage of a very healthy bank balance going in.


I believe those tend to hurt startups worse because even more of those startups go bankrupt thus causing you to lose your job at the worst possible time.


I guess a lot of startups would shutter


So well put. Startups in 2018 make economic sense iff you're not CS-ish enough for the big apes, or live in a location they have no presence in.


is the compensation really like this for a mid level engineer at a FAANG? I'm still fairly new into my career and I can't believe that the enterprise money is sooo much better than the startup world. I'm currently earning around 120k a year with health insurance and no equity. Should I really be designing on trading up into a nice big enterprise job?


I just started a job as a data scientist at a FAANG company. PhD + 2 years of experience for $200k total compensation (plus another $50k in one time bonuses/relo). It’s almost double what my previous (non-tech) employer paid. Although I’m starting to wonder if I should have gone the software engineering route instead. SWEs get double the RSUs as data scientists for the same experience level (so ~250k for my level) and they also didn’t spend 4 years working on a PhD to get there. Oh well... I can’t complain. Very happy with my current situation.


I'm in a somewhat similar boat and have seen DS positions at FAANG not pay as well as SWE. Why is that?


I’m not sure. At average companies, I think SWEs and data scientists make about the same. But the top companies have a much larger software engineering population to choose from, so they can afford to be picky, and the pay correspondingly reflects that. There’s about 20x as many software engineers as there are data scientists in the world.

I think this is changing though, and I think “data scientist” will soon be split into sub-roles. Some companies like Lyft have already changed their title scheme. Business analysts are now data scientists, and those who were data scientists are now research scientists.

The company I work for has an internal job role that isn’t public and an external title that is. So a “data scientist” may have an internal role of “business analyst” or an internal role of “applied scientist”, and there’s a big difference in pay despite the same outward-facing title.

I think the pay scale goes:

Data scientist (business analyst) < data scientist (non-CS PhD) < software engineer = core data scientist (CS PhD) < AI researcher (ML PhD + great publications)

I have a non-CS PhD so I think that’s why I don’t make as much as a software engineer or a core data scientist.

Base salary and bonus is generally the same for all roles for a given experience level; the difference in comp. comes from the RSUs granted.


Or you negotiated poorly for your first and second jobs. Do better next time. There is a wide variance both within and across companies.


On the other hand, top PhDs in machine learning are earning 2 million a year: https://www.nytimes.com/2018/04/19/technology/artificial-int...

If you have a PhD in CS and are being paid less than someone with an undergrad, something is wrong.


Facebook's median compensation across all employees is $240k. Median of engineer compensation would be significantly higher. Also note that Facebook's median age is 29.


If you are in FAANG, and in bay area, then your numbers look too low. I know mid-level engineers in bay area, can make ~300k. All this assuming a good engineer who has been performing consistently, and is among the top 10% in his/her team.


Mid-level and in the top 10%?


I can only speak for the bay area, but the compensation numbers your parent quotes is not too wild.

Your number, IMO, seems low if you're in the bay area.


It won't be anything like that for a mid level.

The friends I'm talking about are deeply experienced and knowledgeable (10 years minimum, mostly more), phenomenally talented, and incredibly effective at delivering results.

The pay spread between startup and big-co exists at all tiers, but it's particularly huge once you start hitting the top talent.


That is mid level engineer in Atlanta where housing is significantly cheaper.


I find it quite amusing that it is normal to find non-junior engineers getting paid 40K / year here in japan.


Now the VCs that made lots of money selling their Google, etc., would now have to spend much more on giving a new startup runway. That's also a reason why many US startups and corporations hire dev teams in Eastern Europe and make it much harder to hire for local startups.


I think the core of a "fix" is here.

If I were building an engineering org today I'd either go remote-only or build it somewhere which is not SFO/SEA/NYC and friends. An underwhelming bay area compensation package puts you at absolute top-of-market in most European cities.

So Y-Combinator can help companies get out of dodge immediately after raising a seed round. For recruiting, warm up a pipeline of talented engineering managers outside the tiny handful of overheated areas in the US. Provide legal, hr, and accounting assistance with setting up shop elsewhere.

You can always still keep sales, account managers, and fully customer facing-roles in SFO.


YC could do that, but it goes against YC's mantra of the importance of having a team working in the same office of a startup and it being located only in SV.

https://blog.samaltman.com/how-to-hire

Thats not to say that it is the right policy, but if I were founding a startup I would definitely be looking for remote workers in other locations.


How long before YC companies are at a disadvantage for not allowing remote work?


> If I were building an engineering org today I'd either go remote-only

There's a reason why so few startups go the remote-only route. How many remote-only startups ended up a success? I can't recall a single remote-only unicorn, for example.

> For recruiting, warm up a pipeline of talented engineering managers outside the tiny handful of overheated areas in the US.

Finding good engineering talent anywhere is hard. You're supposing you can find them in various foreign, remote countries you don't know. It's not that simple.


There's Automattic (creator of wordpress):

http://time.com/88025/wordpress-parent-automattic-joins-the-...

There's also companies like Craigslist who has ~50 employees, but is another billion dollar company:

https://www.forbes.com/sites/ryanmac/2017/05/03/how-does-cra...

Even if it's not remote, it's small enough to basically be fine in the bay area because finding 50 engineers to manage html webpages is relatively cheap.


The sample size isn't even close to big enough to draw meaningful conclusions. The number of VC backed startups that succeed is tiny even in the general population. It helps that there are now examples like Gitlab, but ultimately the default option is still hiring local with butts-in-seats. As with most things, there are many followers and very few leaders.

However, I think economics will increasingly drive the adoption. The price of both devs and real estate is overwhelming in the major US startup hubs.

And while finding great talent is always hard, the difficulty still varies drastically by region. Eight years ago Seattle was a sweet spot with an abundance of great talent priced significantly below the bay area. Seattle's upside has since diminished as everyone and their grandmother set up engineering centers in the area, creating strong competition for talent. Two years ago, I found hiring a solid team in Tel Aviv to be significantly easier than Seattle of the same time period.

One of the nasty barriers to going remote-only is legal. Even if you limit scope to the US, each state you hire in potentially establishes a legal nexus, exposing you to yet another set of tax and employment laws. One way companies attempt to work around this is through contractor relationships, but at both the IRS and state level that doesn't always hold up to scrutiny.

If you go overseas, you also get the accounting headaches of apportioning cost-transfers to the subsidiaries and HR headaches of getting benefits and payroll setup.

But the legal, accounting, HR, and even key-hire pipelines are all things YC can help with given their scale and personal networks.


> How many remote-only startups ended up a success? I can't recall a single remote-only unicorn, for example.

What's the ratio of remote only companies to not remote? A fraction of a tiny number will be tiny.


There's the problem with the sample size, but Twitter for example outsourced some early development to Eastern Europe.


What this suggests, capitalistically-speaking, is that there is insufficient supply of developers and the supply that does exist can be most effectively employed by large companies. Is the problem that startups are not an efficient way to use scarce developer resources, because there are too many of them producing too little value? Or is it that the supply of developers is too small?

A YC apprenticeship program, with in-house coaching, could play a similar role to traditional union programs.


There is also the developer !== developer problem.

I've worked with terrible developers, developers I'd trust to maybe write a blog for my cat, developers I'd trust on an important system but they all called themselves developers.

The old joke used to be "You know what they call the guy with the lowest passing grade in his medical school? Doctor".


I'm excited by projects like http://darklang.com/ that are looking to make basic development more widely accessible, rather than requiring esoteric skilled labor mostly done by people who don't actually have the skills involved. It would be great if the industry got to the point that people coming out of school could be a net positive.


That project looks interesting.


How much is that per month after taxes? I'm not from the US and here normally we describe the salary after all taxes and monthly.


Is that "$400k in base salary and max bonus?" or is that "$400k a year in base salary, max bonus, considering benefits and stock grants which are taxed heavily unless they're held 2 years?"

I very much dislike the habit of people not explaining what goes in the knapsack.


RSUs are taxed at vesting. There is no tax advantage in holding them after they are released.


You still pay tax on the gain when you sell though (assuming there is any gain). Depending on how long you hold them there will be normal income tax or long-term gains tax


Yes, but this is equivalent to purchasing the stock. You could sell the day they vest, and then use the proceeds to repurchase the stock and you'd be in the same boat. I.e. there's nothing special about them once they vest.


I personally would absolutely never take shares/options in a company, just pay me for the work I do. You can work at a startup and have fun and get extremely great compensation instead of betting on the gamble of eventually getting a small amount of payoff.


I think the open secret is that in 2018 most people who go work for startups are those who simply couldn't get a better offer from one of the big players.


Anecdotally, that's not my experience. I see a lot of people working at startups who got tired of doing things at big companies that just weren't that interesting to them. Those folks have often made enough money that they can afford to work at a startup for a few years because the work itself is more fun, the company has a mission they like, or they appreciate having a bigger day-to-day impact.

As a startup founder in San Francisco, I will say that it is increasingly hard to compete for early- to mid-career engineers. So maybe it's true that the pool of people with less than, say, 5 years of dev experience who choose to work at a startup is "lower quality" than those who choose to work at a FAANG, at least using the measures that big companies tend to use in filtering/evaluating.

But engineers with less than 5 years of work experience are often not the most valuable engineers. :-)


> I see a lot of people working at startups who got tired of doing things at big companies that just weren't that interesting to them. Those folks have often made enough money that they can afford to work at a startup for a few years because the work itself is more fun, the company has a mission they like, or they appreciate having a bigger day-to-day impact.

The kind of people you describe are basically retired, and working primarily for recreation. While they do exist, they're very rare, and one thing is certain about them: they will _not_ put up with crazy work hours, intense crunches, etc.

They are not the type of driven people you need at a startup. They're essentially doing this for fun. If there are too many long days or unpleasant tasks - they're out.

Unfortunately, startups need these long days and grueling tasks done, and fast. Far more than the big companies do.

So no, these magical people aren't the solution to the fundamental issue, which is: smart employees realized that engineer equity at startups is low value, and can't compare to what big profitable companies pay.

The only solution is to increase the equity upside, not rely on the recreationally retired to run your startups.


I agree about offering early employees as much equity upside as you can (and, just as importantly, a great work environment and team culture).

But I disagree that the kind of people I described are rare, or that they are "basically retired."

That's just not my experience. Many of the most valuable, hard-working engineers I know at startups have a few years of big company experience in their recent past, and are choosing to do the startup thing all in. Sure, because it's "fun" -- but fun doesn't mean fun every day, and it certainly isn't a synonym for easy. Nobody who has done one thinks startups are easy. :-)

Some of us like going to work to do hard things.


> Many of the most valuable, hard-working engineers I know at startups have a few years of big company experience in their recent past, and are choosing to do the startup thing all in.

I completely agree with this, except for the "all in" part. If you re-read my GP reply, that's what I was disagreeing with.

Not that they're not valuable - on the contrary. An engineer who did well at Google for 5-6 years is going to be incredibly valuable, and most startups would be lucky to get even just one or two of these in the team.

However, they have a different mindset, and I say that from experience. They don't need this job, and they don't see it as financially or otherwise important. In short, nothing is keeping them there. They're not committed to the success of the startup. Making 250K is nice, but not after you made 500K or more for several years, and can easily get the same pay if you wanted it, or find another 250K startup job in a heartbeat.

There's a reason bigger companies spend huge amounts of money to pay essential employees very well. It doesn't guarantee that they stay, but not paying them well certainly doesn't help.

So when the going gets rough, these people leave. It makes total sense, they have no reason - financial or otherwise - to commit to the success of the startup as a business. They're there for a good experience.


Three thoughts just based on my own personal experience working at startups for ~20 years:

Many, many people are committed to jobs for reasons other than money, across all walks of life. This is often true for engineers, too.

Few experienced engineers in SF (who are also US citizens or have green cards) are locked into any job. If you're making $750k/year at Google, the Apple or LinkedIn or Salesforce or Facebook will pay you $750k/year and make up the value of the RSUs that you're leaving on the table. The exception to this is if you're at a growth-stage company and have a lot of vested stock with a current valuation much higher than the strike price but no liquidity. Leaving that situation means paying a big purchase+tax bill now, without any guarantee of when you will have an asset you can sell. That's a tough decision.

It's a good thing to have employees who aren't locked into the job by a sense of financial need. I'm not saying that it's not also great to have young or otherwise early-career employees who, just situationally, aren't as financially lucky. But lots of terrible dynamics come from power imbalances between companies and employees. You only need to spend a little bit of time at a company that employs a lot of people with restrictive work visas to see this play out in soul-crushing ways.


> Many, many people are committed to jobs for reasons other than money, across all walks of life. This is often true for engineers, too.

Of course. But there's a reason why SV begun this expensive tradition of giving engineers substantial equity: the realization that startups and other ambitious companies must align employee incentives with company success.

It's possible that the employee will develop some irrational dedication to his job that is not based on any rational incentive structure, but that's not something you want to count on, especially with the type of intelligent, rational employees you hope to hire.

Incidentally, I've seen this position of "employees should just be dedicated regardless of equity" elsewhere in this thread. It feels like a step back to me. SV took a big step forward giving employees meaningful equity some 50 years ago. Now we're trying to roll this back in the name of... what? VC greed?


Again, I definitely agree about early stage employees having substantial equity.

But I would also not call dedication to a job for reasons that go beyond compensation "irrational."


There are costs to "dedication to a job". These costs must be balanced with benefits, or choosing them is irrational.

Notice you're talking about "dedication", which is different than "I'm working on rewarding problems in a fun team". That's the opposite of dedication. Dedication is what keeps you committed to a team when it's no longer fun, working on problems that are no longer rewarding.

I've seen plenty of people give their heart and soul to startups, that ended up exiting in ways that made the founders and VCs rich, while these people walked away with nothing, often not even a job (since their old job was effectively gone in the exit). Is it rational to choose such fate?


> I see a lot of people working at startups who got tired of doing things at big companies that just weren't that interesting to them. Those folks have often made enough money that they can afford to work at a startup for a few years because the work itself is more fun, the company has a mission they like, or they appreciate having a bigger day-to-day impact.

Those folks went through FAANG first (not startup first) though :). I don't know if they decided to move to startups for the experience/thrill/fun or they're just there so they can go back to FAANG and get the full 4-years RSU + sign-on.


Plenty of us don't want to work for them regardless of pay.


I'm not sure "plenty". More like "few".


My experience of working in startups is that they're populated almost entirely by people who openly mock the idea of 'selling out' by working for a big firm. Maybe that's just the places I've worked (that tend to either be in creative sectors or 'worthy' industries like education).

I'd be curious to see a poll on this though.


I don't know about that. I refuse to live in the Bay area and have no desire to live and work for one of the "big players".


Seems like a sad and shitty way to think about other people.


This.


Stupid question. What does “this” means? (“what does this means” isn’t really googleable).


It's an informal way of agreeing with/emphasizing the parent comment.

Your question isn't stupid. Using "this" in such a manner is non-standard English and I can see how the meaning would be unclear if English isn't your first language. It might be unclear even to native speakers if they don't spend much time on internet forums.


It means "I agree with this, but have nothing else to contribute to the discussion, and don't understand that an upvote would suffice, or I just want to pad the number of comments I'm making on this site."


Yea this is the big one. Even a good exit won't be able to compare monetarily.


also there can be stress every now and then


Startups in my opinion are almost never a good deal for folks who have the option to join a big successful company. My points will be directed at folks who can get a job at a big company easily but are lured by the great things they've heard about startups. Specifically I'll target the issue of compensation.

Startups, in my experience have very shady predatory compensation strategies. Along with the VCs that fund them, startups target people fresh from college, selling them the "each stock COULD be worth X, so you could be worth Y" story. They also target people who have spent their entire career at startups since this fairy tale works on them too. I have worked at both startups and big companies and my compensation at bigger companies has been so much better. People working at startups don't believe me when I tell them how much I make. Past me would not believe present me either. I am not talking about a 10% or 20% or even 50% increase in compensation. My pay is 4.2x of what it used to be and I know people who have had similar experiences. It's not like I was being paid peanuts at the startup I was at either. The pay at big companies is just much much better. It's easy to underestimate the power of performance evaluation driven stock refreshers and the sheer increase in the stock value that some of the big companies have had. Here are some things one should consider compensation wise when working at a startup: * You are essentially getting a lottery ticket with your stock options. How do you value this lottery ticket? Don't buy the stories the founders sell you on how this is a gazillion dollar market and even getting a faction of it would make FooBar a trillion dollar company. A simple but still optimistic method - just use the VC valuation. They have way more information and experience than you do and if they value it at X, it's at best valued at X. So if your tartup decides to give you 0.25% of X then you're stock is worth 0.0025X at best. You'll be surprised how little your options are worth if you use this method. * But even that valuation is optimistic. If you leave the company before they go public (or hit another liquidity event) you either leave with your existing options and pay a tax bill on something that may be worth nothing OR you leave with nothing. Now some startups let you claim your options for up to 9-10 years after you leave, but the typical ones give you a period of about 3 months - so you're forced to make this decision. The irony is that if your startup has actually done well, the tax bill might be too big for you to pay and you have no option but to stick around or leave with nothing. I've known cases of people who have poured their heart and soul into a startup, got burnt out and then were laid off and had to leave with nothing. Consider how long it takes the successful startups to go public these days and add a risk factor to your valuation based on that. * Okay, so you're rich enough to afford the tax bill on your risky options when you leave - you might still get screwed. Guess whose shares are getting diluted the most during the next round of funding? Ex-employees have no say in the company and the company has little to no loyalty towards them. A company could easily do something shady like raise money, dilute current and ex-employees, but give all the existing employees new shares to make up for the dilution.

For a sample of some of the disingenuous "I know what you need better than you do" kind of marketing that VCs do to help maintain the status quo, take a look at https://a16z.com/2016/06/23/options-timing/. These folks are not your friends.

Startup founders get the vast share of the equity and even the 3rd or 4th employee gets a tiny fraction, while having to do the same amount of work. So if you still want to work at a startup, my advice would be to either be a founder (hopefully not one that continues the cycle of screwing over other employees) or at the very least come from a big company. Founders and VCs know that big company employees make a lot of money and they wouldn't just give up on their good compensation package for the "each stock could be worth X" story. Hence they compensate them much better than their average employee that doesn't know the market. Folks coming from bigger companies can also afford the tax bill associated with early exercise of options or exercise of options when leaving a company. Further consider working at startups where they let employees buy their options years after leaving. There are also successful startups that straight up give RSUs.

The well known article by Dan Luu at http://danluu.com/startup-tradeoffs/ addresses some of the other points raised when discussing the relative meritcs of startups VS big companies.


I have found that working for startups, that unless you're the team lead or the only dev, there is usually very little room for growth or advancement. The annual pay increases are terrible and the employee turnover rate is usually quite high.

These pros/cons are based of my own experiences (I'm based in the UK).

The pros: - Come into work whenever you like (within reason) - Working with latest tech - company culture is usually great - Your team are usually very motivated and passionate about what they do - The challenges you usually face are exciting and interesting - Being present when the company meets new milestones is very satisfying

The cons: - Sometimes the features requested doesn't have enough information. This leads to the development team to either chase management for more information or make do with the information thats there. Which then leads to complaints or feedback after the work has completed (which could've been outlined before the work started) - Management usually want to know the fastest way to do a feature and then claim to allocate time to deal with the technical debt later (it usually never happens) - Management also doesn't prioritize the stabiliy of the application which in turn can lead to more issues and bugs along the way. - Deadlines get shorter and stricter as the company gains momentum. As a result you're expected to do more overtime or work later if you fall behind. There is usually no room for error here. - Work/life balance is not so great - Doesn't provide great benefits such as pensions/healthcare/dental - No room for advancement

I don't think its too bad working in a startup, but once I became employed to a (self-funded) medium sized company, their culture seemed significally better. They provided all the pros outlined above and had fewer cons. Work/Life balance was much better, allowing us to work from home or flexibility to do so if we needed to be home for a delivery or take the car to the garage for example.

Also, its more relaxed. While there were deadlines, we're also not encouraged to rush anything, we were the ones who dictated how long it takes to add a feature and set our own deadlines based on the complexity of the feature. We also had the ability to push back the roadmap accordingly if necessary in order to make sure something is done right. The reason for this is that bugs or issues can really damage the companies repuation and so its pretty important we take our time and do all the due-diligence required before our releases.

I suspect working for a self-funded company is better because the clients/customers are already there or on-boarded. There is no/little pressure from the shareholders or investors to get things done quickly. I would imagine that a startup has a lot to prove and so needs to impress in order to get more funding.

Note that these are my personal experiences, I've only worked for 4 startups but I've had very similar experiences with all of them. If Startups are able to at least alieviate all of the cons I've outlined above then I would be happy.


Agree with many others here that talented early startup employees don't tend to make enough money to offset the opportunity cost of FAANG-like total comp. That point has been argued in the thread above more eloquently than I could.

If you accept that compensation is the issue, and want to fix it, and get our best and brightest back into startups, that has to be corrected somehow. I can only think of 4 sources:

A) Pay them more, shortening operating runway B) Make their equity worth more, by making founders' worth less C) Make their equity worth more, by making startup companies worth more D) Make their equity worth more, by making investors' worth less

I'm going to argue as a current startup executive that (A) is already efficiently calibrated by the market and has yielded the current balance, so not likely to find more ground there.

The current supply/demand of founders would suggest (B) is not likely to make a dent either. If it could, that would suggest that there is an oversupply of (qualified) founders, such that we could do with fewer. I think most VCs would disagree with that world view, as most of them take 100s of meetings to do a single deal, and generally consider capital deployment to be their primary operating limitation.

If someone has serious ideas for (C) that can make a difference at scale, I think they would do well to share them here.

That leaves us with (D). Anybody who has negotiated a term sheet will tell you that this won't be easy. But I submit a humble suggestion for a cultural shift that I think could make a big difference here: make liquidation preferences unfashionable.

My reasoning is simple: in a modest outcome, the effect of the preference is much greater on employees (who lose out on their true equity value) than on investors. Most VCs have already hedged the downside risk within a given fund by diversifying over 10-20 other deals, and most of the time, at least one or two of them (if the fund is any good--and they won't be around long if not) will net a > 10x return. The value of the preference as downside protection is therefore quite limited.

On the flip side, it is a huge impact for an early employee, who might see an extra 50%+ dilution in a modest exit after the prefs get paid out. And let's face it... these modest exits are far more common than the unicorns.

Doing this would also free up better price competition among non-institutional investors who are happy to have non-controlling participation, especially in later growth rounds, and so could actually make the sector more attractive to a wider investor base.

This wouldn't produce an overnight change, but could result in more early employees having positive "EV" stories, which could eventually shift perception.


ok


This may just be a personal viewpoint but I no longer see the distinction between a startup and another company, not when I'm the senior developer coming in to head up the team. In London in particular it feels more like a marketing term to attract more naïve talent, which isn't necessarily a bad thing (corporate/enterprise still has a pretty uncharitable perception, for better or worse). You can find yourself working for a startup that has existed for four or five years, hasn't properly launched their product or found their place in the market, and on some level has stagnated.

I've no experience with the tech world in the US (or SF really), neither YC, so maybe the conditions there are different, but my vague thoughts are this (and these are usually the things I assess when I'm interviewing with any company, it's rare that everything is checked so it becomes a matter of trade-offs):

- I'm more passionate about building out a nascent product that really touches me than I am about working for a startup. There is vision, it aligns with my values, I'm confident I can help make it happen and I want to be part of it. That it happens to be the idea of a startup isn't relevant because I'm looking for fulfilment, not a cash-out. Appealing to making my day-to-day comfortable and productive, while also respecting my worth, is a good way to get me on board with that.

- With that in mind, coming in with the pitch that I have to sacrifice a fair bit in order to make this dream come true - low salary, higher equity, 10+ hour workdays/no sustainable pace - isn't going to work unless it's an intensely special idea. That means respecting boundaries about when work happens and when work doesn't, with the reasonable expectation that sometimes there might be a bit of flexibility.

- Speaking of boundaries. Fucking stop it with the mandatory fun. I love a beer with the crew as much as anyone but turning every single potential social gathering into a bacchanalian fuck-fest or making alcohol as available as possible inside the office just isn't motivating. Give me a reason to leave the place and enjoy the outside world and socialise naturally, and think of more exciting things than straight up parties if you want to do company get-togethers.

- If not fully remote, then at least temporarily remote. This is mutually beneficial if the startup is mature about it, because it means you can enjoy a change of scenery without going totally off the grid.

- Respecting experience. If I pass muster as the senior/experienced programmer you need then I expect that you're paying me because you're interested in my input, not to micromanage me. Let me bring something to the table.

I actually think you're far more likely to fulfil these wishes at many startups, and massive corporate outfits may be slower to respond to that kind of thing. But then it raises the important question: if you're moving the needle in favour of employees, how do you allow them to influence these cultural concerns?


I both founded a YC backed startup and I worked at another YC backed startup and had a great experience there. Having said that, I can't say I would ever recommend a new graduate taking an offer at a startup (at least an early stage one) over an offer at a BigCo of some sort.

A BigCo will help them get hired for the rest of their career. Anecdotally, I learned and accomplished far more at startups than at Google, but anytime someone sees my resume "Google" is what they notice first and are impressed by. This sucks because early employees at a startup have so many opportunities to learn and accomplish way more than a typical BigCo employee, but recruiters can't easily filter on this like they can "Oh this engineer worked at Google - they must be good!" As a result, working at a BigCo will likely help their career more than working at a startup.

Pay and filtering out good vs bad offers is another concern. Most engineers are unfamiliar with startups, equity, preferences, cap tables, and everything else. We on HN are probably more knowledgeable, but I founded a startup and still don't fully understand it all so I can't imagine how someone completely unfamiliar with startups could possibly evaluate an offer. This is made worse by the fact that it feels like startups for the past decade have taken advantage of this ignorance and screwed over many early employees with poor offers and a fake promise of wealth when the company is a mega-success. Many others have made this point in this thread already so I won't get into the details, but the TL;DR is that employees need to be treated as vital investors in the business and as people you want to help succeed.

A third concern is development and training. At a startup you are expected to already have a pretty solid knowledge base when joining; you typically need to know how web apps work, some of the stack the company uses, etc. That isn't to say you won't learn a lot at a startup, but this is typically done in a "sink or swim" manner where you have to have some foundational knowledge to avoid drowning. At a BigCo this isn't always the case, and many new grads will be hired with less domain specific knowledge and are given an opportunity to learn and grow over the first year. Now I realize not all startups (especially early stage ones) can afford to hire employees who won't be contributing in the immediate future, so I'm not sure how you fix this (maybe a company like Triple Byte could find promising employees who lack some specific knowledge and give a crash course before sending them off to startups to interview?), but if you can get hired at a BigCo you can basically get paid to learn these skills which is a much more enticing offer.

A fourth concern I've heard from people less familiar with startups is concern that the startup will just die at any minute leaving them jobless and in a tight situation. This mostly stems from founders not sharing important information like cash reserves, burn rate, runway, etc, so I think the general fix is to encourage founders to provide more clarity around these things. The problem is this is hard because no founder wants to admit they are failing or that the company may not be alive in 3 months. They might raise money or turn things around and they don't want their best employees to leave, but by not saying anything they risk getting into a situation where employees need to be suddenly let go and a single story like this can scare away many potential candidates. This just isn't as much of a risk (or it is perceived to be less of a risk) at BigCos, even though they do occasionally close down branches.


Con: with most startups (mostly the vc funded ones) it feels less like a startup and more like a corporate. The hacking ethos and mission driven teams have been replaced by overly nice offices, steve-jobs-wannabe-kid-ceos and mediocre team mates. I’ve lives both worlds and it seems there are few places left that are like the old days.


The lack of engineering skill among teammates is a huge con in general to working in the Silicon Valley, not just among startup. The money is too good and the bar too unrelated to actually maintaining code. Personally, I've found startups are one of the few ways to not spend a career mucking out a mess dozens of others left behind with few tests and even less design.


I was the 7th hire at a YC start-up which is now worth at least $1bn. I negotiated 2% of the stock in exchange for a 60% discount in salary, and an understanding that my work would primarily be evangelism/marketing, as I was burned out on engineering and just didn't want to be a sysadmin/devops/whatever anymore.

Anyways, I signed our two biggest customers, organized our tradeshows, did some tech work, and protected one of our employees from assault at a conference.

When I'd been there for 3 months, in the midst of a conference (where we were kicking butt, by the way), most of AWS went down and we scrambled to figure out what to do.

When I got back from the conference I was fired without severance. After I let them know I'd be speaking to the customers I'd signed, and that three of the engineers in their hiring pipeline were friends of mine, they came back with a "generous" offer of 2 weeks severance.

The funny thing, is they were really nice kids, and I do mean kids, they were children. I'm quite sure they used this as an opportunity to get rid of me because Paul or some other greedmonger at YC ordered them to screw me over so that they could sell more stock to investors later.

After that point, it hasn't mattered if I work for a start-up or a big company. YC taught me that all companies are the same, and now I just view myself as a mercenary.

It doesn't matter where you work, how much they lie to you about "culture" and "family", or how much they try to convince you that you should take a salary discount because "your stock will be yuuuuuuge and we're changing the world", or "this is a greenfield environment with a chance to do something entirely new" (it isn't. all start-ups are really just rip-offs of other start-ups. )

Your main response to every sales pitch they give you should be, "fck you, pay me".

Repeat it, memorize it, live by it. Fck you, pay me.

"This kinda shit happens all the time. You gotta get yours, but fool I gotta get mine" -- Snoop Dogg.


PS, I've also been told by several friends who have gone through YC, and one who currently works there, that there's an unofficial internal blacklist, and I'm on it.

For what it's worth, in the 3 months after I was fired I referred a few dozen new customers, and I had no animosity towards them until I found out about the blacklist last year.


Pros: for even the worst startup there are fewer useless people, bureaucrats and insane witch hunt types than there are in a large business. You learn more if you're a go-getter and your work can really make a difference.

Cons: your returns are way more volatile -CAPM adjusted, I'm pretty sure it's not worth it, and if you're trying to learn things and need formal mentoring rather than 'self serve' you won't get it.

I can't stand bureaucracy and non-contributors with power over my life, so I prefer small startups.


Work Environment:

Informal atmosphere, flat hierarchies, open mindedness are some terms that perfectly describe work environment at a Startup. So, if you are bored of your organization’s formal work environment, then Startups have a better place to work at for you.

Real ownership & Results:

By working at a Startup, you can have a freedom to work. If you have an idea, execute it, and come up with the results. There is no need to follow a hierarchy and take multiple approvals. In case, your idea is a big hit, just enjoy the equity.

Experience:

Startup gives you ample of opportunities to take decisions and that too quickly. This would not just help you in learning but also help in gaining experience in case you have plans to initiate your own startup.

Sense of Accomplishment: Working at a startup gives tremendous & quantifiable impact. Startups give you a position to be an integral part of the system that plays an important part in the fine working of the business. The sense of accomplishment one gets from this is something that money can’t buy.

Diverse Work Day :

Work day at startup is not like 9-5 corporate job. You do not have to go to office to do the defined tasks & come back home. Instead every day, in fact every minute can be unpredictable about work. There are different clients and different work, and you would have to manage all simultaneously. So, one another best aspect about working at a start-up is, you won’t be bored!

The bad side:

Lack of structure: Due to inexperience of leadership, if management loses sight of team/cost/communication of strategy with investment, then one has to face the consequences and bear the burden.

Perk-less salaries: Yes, startups have fund raising issues. So, do not expect big salary package in the beginning. There is even no scope of any sort of perks or monetary benefits in the initial years of the Startup.

Lack of work life balance: Startup also means a lot of work, which demands extended work hours. You might enjoy flexibility in work style, however it would surely demand more time from you. So, be prepared to give extended working hours to your job and compromise with work life balance at initial stage of startup.

Job insecurity: Your career is directly proportional to the growth of the company. If its future at stake, so is your career. Chances of instability are thus high with startup companies.

Now that you know the good and bad side of working at startups, take decisions wisely and then work hard to enjoy success.


- Lack of stability - Equity instead of salary - Long hours - Wearing multiple hats (hate having to do QA, Operations, even some product development)


Pros: Being surrounded by smart people, paycheck

Cons: Group think, incorrect biases, getting cucked out of royalties, helping the elite take the future


No healthcare at a startup.


The one time I worked at a startup, the lack of healthcare made me borderline suicidal.

I was beginning my gender transition when I worked there, and my doctor bills were bankrupting me.

Never again. Never ever ever ever again. I'm not touching a company with fewer than 500 employees again.


This may come across as ignorant and I apologize in advance but are health care costs associated to gender transitions typically covered by health insurance?


Depends on the kind of treatments. What was killing me then was the cost of doctor's appointments to get on hormones, which are generally covered (whereas it's a pain in the ass to get surgeries covered even with good insurance). Doctors are expensive if you don't have insurance.

When I first started out, in order to avoid the doctor costs, I ended up reading the clinical guidelines myself, finding a place for me to order my own blood tests, and looking up a reputable overseas online pharmacy I could order the medications from. The blood tests cost me $60 a pop, and the hormones cost around $80/month from the online pharmacy I used. Now, I'm also going to mention that I was also spectacularly underpaid at the startup I was working at then. That $140/month hurt. Badly. And I was constantly worried customs would confiscate the meds. Now, estradiol and spironolactone aren't controlled substances, so I couldn't be arrested for ordering them online, but theoretically customs could confiscate them anyway because they're Rx-only medications and then I'd be out $80 for nothing (yes, there is legally a level between OTC and controlled, where it's illegal to sell but not illegal to buy). In practice, they only do this one week a year (look up Operation Pangea) because they don't have the resources to do it but there was still a chance.

After a few months, I grew uncomfortable doing this without a doctor's supervision, so I eventually decided to suck up the costs and find an endocrinologist. The doctor's bill was in the neighborhood of $200 per visit, and because I was still early in my transition, I was seeing my doctor monthly at first. Oh, and I was still paying $60 to Private MD Labs for each blood test, because it turned out to be far cheaper to get my blood tests through them than through the provider my doctor worked with. The one consolation is that the medications themselves were cheaper; estradiol and spironolactone are both on the $4 generics list at Walmart, so my actual cost of meds went down from $80/month around $30/month (my doses were such that I was taking multiple pills per day). But those endo visits ruined my finances...


Healthcare is only required for companies with >10 employees.


That sounds really bad - offering health insurance for employees is a must. At least in the US - I'm not sure about other countries.


Not sure why this is down-voted. Healthcare is only required for companies with >10 employees.


The basic problem right now is that adding capital dilutes labor, but adding labor doesn't dilute capital. I think this is one of the biggest problems the blockchain can solve by driving down the costs of double entry accounting by at least an order of magnitude.


This is super interesting but I don't quite understand it.. Can you explain how adding capital dilutes labor? Also, how does blockchain make it cheaper to do double entry accounting?


When you bring on new investors, it dilutes the equity of employees. But when you add more employees, it generally doesn't dilute the equity of investors. Rather, pools of equity are created periodically for employees with investor approval, and employees get options from that pool.

With blockchain though you can give equity in realtime, e.g. every 5 minutes that people are working, rather than once per year or whatever. The fact that work and equity distribute can both be monitored very granularly at no extra cost means that labor can (and will) be given equal footing with capital, rather than having hiring and compensation changes approved periodically by investors with little to no input from labor.


Thank you for clarifying. Couldn't a well drafted contract achieve the same ends as blockchain for giving equity in realtime? It seems like that is more an issue with the terms of the current employment contracts and not a technological deficiency




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

Search: