My experience as the first employee of a Y Combinator startup | Hacker News Reader

My experience as the first employee of a Y Combinator startup

nathanmarz.com

192 pointsbudu106 comments

My experience as being employee 8 million at a Large Corporation is nearly identical. I can choose my own tools, work from home when I want to, take breaks, etc.

We've already taken care of the cash flow thing, so it ends up being much more relaxing than working for a small company. We aren't going to go out of business if our software isn't released tomorrow, so we have lots of time to write quality solutions. We can build stuff that's really nice to work on, instead of stuff that will give us one more checkbox in a TechCrunch comparison article.

(I worked at a small company for a long time. It was less flexible, and every year, we "don't have enough money" for a raise. Eventually it was very stressful, my input didn't matter at all, and I got paid nothing. All for what most people consider "the ideal job". "Going corporate" was the best thing I ever did!)

I assume you don't want to tell us which Large Corporation you work for, but I think your experience is not the typical BigCo employee experience.

It's better if you actually own the small company, though...

Maybe for having an impact, but for stress? I doubt it.

So that I can spend 99% of my time doing something I'm bad at, and 1% of my time doing something I'm good at? No thanks.

As an employee, I spend at least 80% of my time doing my best work -- no billing, no taxes, no finding new clients. I wake up, do some programming, chat with coworkers, eat lunch, do some more programming, then go home. And oh yeah, I get paid even if the company has a slow month or year.

Don't get me wrong; in many ways, I would love to have my own company. But I am pretty sure I will make more money, be less stressed, and have more free time not doing that.

(Anyone want to pay me to implement whatever random useless ideas interest me? Exactly.)

Will you still be happy with this kind of job in 20 or 30 years?

There is nothing wrong with being an employee at a large company. It all depends on your priorities. The important thing these days is to stay marketable in case circumstances change, and that large company decides not to be so accommodating any longer.

It was less flexible, and every year, we "don't have enough money" for a raise. Eventually it was very stressful, my input didn't matter at all, and I got paid nothing.

As always, it depends on the company you're working for (it sounds like you're working for a great one!). I'm sure there are plenty of people who could claim the exact same thing while working for a big corp.

What do your stock options look like?

If BigCo doubles revenue this year (probably impossible if it really is a big company) how will it affect your life?

If BigCo gets acquired next year will you be popping champaign or worried about your job?

No stock options, they just give us cash instead. Bonuses end up being a pretty good percentage of the base salary.

I'm interested in hearing about experiences on people who are not founders and made money in an IPO/buyout. How much can that realistically be? You're diluted down to 0. something percent by the time the exit happens. Compared to the opportunity cost of just getting paid each month for several years, do employees in a startup come out ahead, financially?

I personally think the first one to five employees in a minimally funded startup with small m&a exit as the likely exit are getting a bad deal, vs. the founders or employees who join after financing.

An early employee will get about a percent tops as an individual contributor...maybe up to five percent tops if he is more of a vp engineering. In exchange, a seriously below market salary, equally high if not higher risk of losing one's job vs. founders, and vastly less respect when he later goes to try to do his own startup.

Assuming the same caliber of individual, it makes a lot more sense to either found your own startup, or join after real financing (where you get a market salary, and have a lot less risk, plus a lot of startups with problems have been shaken out.).

Obviously being am early employee at a great startup like google or Facebook makes sense, but for companies more likely going for 10 to 50m base hits, I don't think early employee is a financially rational decision. (note to future people I want to hire: I only do high risk potentially high value exit startups, so your initial equity actually is worth it!)

That's probably true, but there's a lot more that goes into employment decisions beyond compensation.

As an early startup employee, I'm working for (all things considered) less money than I was when I was working in the defense industry. But I also don't loathe my job or lay awake at night, stressed about the idiocy and bureaucracy that made my days hellish, Kafkaesque, comedic nightmares.

That's worth more a LOT more than ~$10k/year and a guaranteed 'career'.

False dilemma: there are plenty of jobs that pay fair market rates that don't involve hellish idiocy and bureaucracy. It's not somehow automatic in companies that are a different age than post-founder pre-funding.

There's nothing about a pre-funded startup that magically banishes the "kafkaesque". Conversely, there's nothing about being well-funded that keeps you from sleeping at night (quite the opposite, actually).

I didn't say otherwise. I'm saying that my current job, taken as a whole, as valued by me, benefits me more than my last job.

But the implication was that it had something to do with it being a startup. There are plenty of startups with neurotic founders, and plenty of big companies that aren't a Kafkaesque nightmare.

Right, I implied that it had something to do with being a startup because it does. In this specific example.

I'm not saying that 'all startups good, all big company bad' is some sort of globally applicable law and I'm not sure how or why anyone would read that into what I've said.

"False dilemma: there are plenty of jobs that pay fair market rates that don't involve hellish idiocy and bureaucracy. It's not somehow automatic in companies that are a different age than post-founder pre-funding."

True in California.

Not so much in other places. In India, you can work for body shopper process heavy companies (Wipro Infosys etc) , "India dev center" s of MegaCorps, which are universally severely dysfunctional and bureaucratic (Even Google and Yahoo aren't immune, their Indian operations are overrun by Middle Management and by and large, you get (relatively) crappy work (ops/legacy code etc)). Or you can work for the very few decent startups at below-market rates.

Choices, choices ;-)

Not so much opposing your view point as qualifying it a bit.

PS: If anyone knows of an Indian company that pays well, has great work, and is not infested by bureaucracy, let us know. I have friends who are looking to move from both Kafkaesque BigCo jobs and underpaid startup jobs.

Financial compensation is only part of it. Most startups include longer hours and additional responsibilities that limit what else you can do with your life, such as have a relationship, spend time with friends, or work on a side project.

I'd guess you're at an established startup if you're only making ~$10k/year less than your last job in the defense industry. Pre-Series A startups are unlikely to pay even a third of what you'd make in that industry.

A good eng in defense (at the level needed to be a startup founder) should be making 150 uncleared to 250 secret to 300 ts or project lead or more if deployable. Working 40 hour weeks (well, working 5 hour weeks with 35 hours of meetings, admin, paperwork, and overhead)

A pre series a eng is making 30 to 60 if lucky. At series a, maybe 80 to 100.

Defense is almost a perpetual job, whereas the half life of a pre series a startup is maybe 3 months, 1 yr for series a.

(apologies for formatting, on iPad)

A programmer working defense state-side does not make nearly those figures.

80 to 100 is much closer to what a software engineer with several years of experience makes working for a defense contractor than 250, though of course actual years of experience and how well one has played the corporate ladder game can make a big impact.

Past a certain point it is relatively difficult to advance salary-wise without taking on management roles and giving up the hands-dirty side of programming / engineering. Once you're there it's an apples-to-oranges comparison for the kind of startups that are typical for HN-types ~ certainly no early stage startup is going to hire a 10-year manager to be employee #1 when what they really need is a hotshot programmer.

I admit my knowledge of stateside engineers in the large defense contractors is secondhand; trying to convert known deployed salaries and known eng and pm salaries at small product companies selling to usg.

Substitute working for a fund on the dev side and double my numbers to make the original argument stronger.

> and vastly less respect when he late goes to try to do his own startup.

Can you elaborate on this?

If you are founding CEO of a startup which fails honorably, or exits, investors and future team members pretty much ascribe all the good accomplishments of the company to you personally, and think you have a good shot at doing it again. A non CEO founder gets a lesser share of the resulting glory, plus way less name recognition.

Only rarely and with big successes will vp eng, product designer, non founding cto, etc get much cred from a startup. If it fails, ceo can usually easily get a job (sometimes as eir or though investor portfolio companies)

When did 5% of 50M stop being a lot of money?

edit: I think something far more deceiving is employee #75 receiving 10k shares and the impression they're walking away with gobs of money after a big sale.

5% is unrealistic. 1% is.

50 million * .01 * .65 (tax) / 4 years = 81,250

considering opportunity cost and time spent. likely not worth it.

It's also often not even 1% of 50m, but 1% of (50m minus liquidation preferences).

Liquidation preferences are wacky -- I would have never understood them without several patient explanations on HN. I'm curious: is modeling their effects just common Valley knowledge that you'd do effortlessly during a job interview, or would most candidates be as unknowingly ignorant of their effects as I was a year ago?

I sit with people with a googledocs spreadsheet and we plug in numbers for various scenarios, so they can see what happens if there is a quick sale vs. multi round and then later. And show how cash comp to engineers affects this too. I believe in total transparency for at least the first 20 or so employees wrt budgets, salaries, equity, etc.

If you "trick" someone into working for less, you have screwed yourself more than you have saved money.

GitHub's first employee owns more than 1% of the company, so I'm not sure why it's unrealistic. Maybe in the world of businesses letting VC's tell them how to run their company this is the norm, but it doesn't have to be.

GitHub also brags about not taking outside funding, so it's a potentially better deal for them: http://news.ycombinator.com/item?id=1454597

Name one company in the USA which didn't take outside funding and exited for more than 30mm usd?

I'm somewhat sure that would describe National Instruments (IPO'd at a $380M market cap)

Wow. I was secretly trying to get you to find an answer to one of Keith Rabois questions on quora. I forgot he qualified it as post 1999. Can you do that too?

National Instruments is an amazing company...I was fortunate to get to use their products on some projects as a teenager.

I'm not 100% positive on NI. I just recall that claim being made when I interned there and can't find any info suggesting otherwise.

They IPO'd in 1995, btw.

Sas. Still private no funding, founder is worth 8 billion.

Yeah, and how much of those do the employees get? Right.

SAS has a profit sharing programming. That's often a better deal for employees.

In SAS's case they pay up to $70,000 as a bonus, in Canada anyway: http://www.eluta.ca/top-employer-sas-canada. Averages seem to range from $9000 to $32,000 (http://www.glassdoor.com/Bonuses/SAS-Institute-Bonuses-E3807...)

The first few hires often happen before VC funding is raised, right? And 2-3% for the first few employees isn't unusual amongst companies that later raise VC funding and make it big.

Right..when your best case is less than salary differential, before factoring in working 3x more, and the ten percent or less odds of getting the 50 exit! Something is irrational about participating.

That said I would work with certain people or on certain projects as an early employee. With some, it would be economically rational, with others then entertainment value would be worth it.

Someone who comes in for five is a potential founder anyway.

At 1 you have another fifty percent dillution from follow on financing, and the odds of any exit at all.

Exmployee 75 is making market, and a 75 man shop will not sell at 50. They are shooting for 500 or more, or failure.

A 5 person startup might sell for 5 to 10 direct, in which case your 1 just bought a nice car, after tax, but not a really nice car, and less than your risk adjusted forgone salary vs. Being a soulless corporate drone in defense, or maybe number 75 at a well funded tech company.

If by "real" financing you mean a series A round, then you're probably mistaken. People who join a startup with just angel funding might get roughly 4-5x as much stock as they'd get post series A. It's only a worse deal if a series A round makes a company 4-5x less risky.

There's a market price for all the different options, from founder to early hire to later hire. It would not make sense for there to be points on the continuum that would suddenly be a much worse (or better) deal, and in my experience there aren't.

You're also mistaken in saying that an early hire will get 1 percent tops. This number varies by 30-40x, depending on where the company is and how early the hire is. 1 percent would be typical for a very good hacker fairly soon after a series A. You can get much more pre series A.

"You're also mistaken in saying that an early hire will get 1 percent tops. This number varies by 30-40x, "

so the #1 and #2 employees are going to get 60% equity combined?

Or was that x supposed to be a % sign?

Also none of my argument applies to a startup with one or more non technical non domain expert founders hiring a tech guy as employee number one. In that case he is a founder without the title and might get a founder level share. However I think those companies are generally born wearing the stink of death and nor worth consideration.

"depending on where the company is and how early the hire is." In the case where a new hire gets 30%, presumably the company is early enough that they are basically joining as an additional co-founder. Certainly possible.

One company might choose to give an early hire 20%, possibly even making them a cofounder. Another company might give an early hire 0.5%. Hence the 40x variability in the amount of equity given to early hires.

all equity isn't created equally -- .5% of google is worth vastly more than 20% of a brand new startup.

"There's a market price for all the different options"

The market isn't efficient though, because there isn't enough information (tho your comment and the GP are helping increase that). It may very well be that there are worse deals at some points.

Believe me, I know how inefficient the market is. There are certainly overpriced and underpriced startups. But his claim requires more than an inefficient market. He's saying that startups in a certain phase are consistently overpriced. That I've seen no evidence of.

Haven't you previously argued that founding is consistently undervalued?

I am drawing a distinction between someone likely to only currently be a good individual contributor, and thus who will not have the option of founding his own startup at that point in time, and a well rounded candidate who brings a lot more to the table. One percent is a lot of equity even as employee one if that person is not going to be in a leadership role later. It was what the mint designer and a few other first hire top notch individual contributors at startups I know have received.

I definitely agree you get more equity during bootstrap time vs. in series a funded startups. I just think the combination of survivorship bias and cash comp makes it a better deal to wait.

Actually someone respectable (Suster?) posted a few months back about how there are discontinuities...and that immediately pre series a closing is a much better time to join than immediately post, since the reduction in risk is far smaller than the reduction in equity. I think the opposite is true between employee one and immediately post a.

By real financing I include mega angel seed rounds. For me a 1.5 seed round vs a 3 vc series a is a distinction without a difference.

My experience as en early-stage employee wasn't quite so bad. As we received funding my salary tended to increase pretty nicely. There was a point that I was the lowest paid employee (with the highest level of responsibility)... but I quickly moved to fix that.

The biggest mistake I find that folks in that position make is in how they value their equity (in that they HUGELY over-value it).

As employee #2 of a now well-funded startup, I would have to agree with this whole heartedly. I wrote a large part of the company's initial product. I can't say that it's translated into nearly the respect, career advancement, and stock options I was sold on. Remember that a startup is as much about business connections as anything - who do you think the VCs are going to credit with success, the guy like them, or the technical founder(s) they barely understand?

the thing is, the startup job market selects for people who don't place a high value on job security, and who are willing to work (temporarily, at least) for below market rates. If you want something safe and high paying, startups generally don't compete with the big boys.

Now, obviously, the first hire gets a worse deal than a founder wrt compensation... but I think everyone is aware of that going in to the deal, and that this is part of why it's so hard to hire experienced people for those (non-founder, early employee) roles.

The big factor people don't realize is employee number one has worse job security than the founders. If you they have huge equity and no salary, and you draw a salary, guess who goes when the bank account is short? If you all make subsistence only, you are losing due to lack of equity and opportunity cost. And still, if there is only enough for 2 of 3 to subsist, the employee goes. If the company tanks, you all go.

I think people realize this. Nobody who cares about job security works for a startup unless they have no other options.

Working for a startup when you want job security would be like getting an art degree if you want money.

My experience has been that if you want to hire people for significantly below market rates, you need to accept that you will be getting inexperienced people who probably can't get good stable corporate jobs. They are getting paid in experience rather than equity. It's just not really something that people who are good and experienced do very often, because as you said, it's not a very good deal compared to the other options available to people who are good and experienced.

(note, I said "hiring" - the rules are rather different if you make them a founder, or give them founder-level equity.)

Or excellent, qualified employees looking for a lot more security. For me to go that route again, I'd be looking for a lot of vacation time (6-8 weeks). Even then the salary would have to be pretty solid as well.

be a sole founder and get 100% equity. then land some paying customers. keep the 100% equity. add features, polish, maybe hire other folks, maybe give away some equity early to bring on a contributing partner with key skills, etc. then this whole "1% is generous" belief and worrying about dilution caused by outside investment rounds simply goes away. does it always make sense? no. but I think it's ideal.

Of course it's "ideal", but in almost every case capitalization gives you a huge advantage and greatly increases your odds of success. You can only iterate and perform customer development as long as there is money to fund that. The less money you have, the greater your chance of failure (but the greater the reward at the end as well).

If it takes you weeks to recover from a burn-out you haven't burned out - yet.

Burn out is a serious issue and some people never fully recover from it. If you're working hard and you need a break after a few months of hard labour that's normal, but it's not the same as being burned out.

Otherwise a great piece and nice to get some insight in to what goes on behind the scenes of backtype.

Can you provide more info on burn-out? What it's like at its worst?

Real burnout is something like losing confidence in your own ability, or the overall system or world. It doesn't go away with time, per se, but requires a real change of your life....like getting a manual labor type job for a few years, going back to school, etc.

Absolutely. I burned out at a tech job in 2000, and spent several subsequent years working as a climbing instructor, outdoor gear retail clerk, cable technician, etc. ... anything that didn't require the use of a computer.

There's a difference between simply needing a vacation, and being completely and absolutely disgusted with your field and everyone in it.

What got you back into tech?

I think that i am fortunate in that I direct all my wrath and loathing outward.

Inamorata? Did you mean to write that, or did your phone just teach me a new word? :-)

As totally cheezy as it sounds, I "gradually woke up one morning" and realized what it was that I wanted to accomplish with my life. My newfound goal was going to require more resources than I could ever accumulate by selling backpacking gear, so at that moment I decided it was time to get back into the tech industry. (I still have fond memories of my time away from it though.)

I haven't felt anything close to the same burnout since. Although I'm often stressed out over one thing or another, for the most part I'm pretty happy with the way everything is now.

exhibit a:

http://viewsourcecode.org/why/

Good point. If I may wager a guess on why _why left, it's because of the worship-like behavior that people are still directing at him.

Years ago I suffered what I would now call "burn out" although at the time I didn't know what was happening. I found this essay to be an accurate description of my experience, but I think a doctor would be a better source of information on this topic: http://www.stressdoc.com/four_stages_burnbout.htm

At the worst point I was experiencing anxiety, paranoia and depression. My only strategy for coping with stress and difficult situations at the time was to put my head down and work through it. I thought if I was having problems getting the job done, I would just put in more hours. This turned out to be a terrible idea. I worked 80 hour weeks for months at a time in highly stressful situations. Initially this work ethic bought me promotions and raises, but you can't work these kinds of hours under a huge load of stress for years and not suffer consequences. In two years I gained 40 pounds and became a pack a day smoker. When you never put a limit on how much you work you eventually break down.

I nearly ended up quitting and going to seminary. Instead I just got a new job with less hours and responsibility on the other side of the country. After a few years I'm finally getting to the point where I can handle stress like I used to: until now any moderate level of stress has caused me to spiral into anxiety and paranoia again. I was worried I was permanently damaged, but thankfully I'm getting better.

EDIT: I haven't smoked for two years. I've lost over 40 pounds and I'm running my first 5K on Thursday. I got better but I had to drastically change my life.

I've found exercise to be one of the best ways to help prevent burnout. Especially exercises that put one into a meditative state. (Running, rowing, swimming, yoga, etc.)

Good luck on the 5K. :-)

I definitely agree re exercise.

A good relationship, kids, and general family life also seems to help people survive high stress, but high stress often leads to a bad home life which can make it worse yet.

That's quite a story. Good to see you come out on the other end in one piece and much good luck on your run.

http://sentientmachine.blogspot.com/2010/07/burnout-how-to-r...

You must have experienced this yourself first hand. This is a great description of the problem and the solution.

Employee compensation from startups depends on many factors including how much they value employees, but it's really important for prospective startup employees to understand that you'll probably work longer hours, have more responsibility, and earn less than if you keep your day job.

Someone with experience in a great "normal" job may be surprised that the compensation, including equity, of a first employee is usually significantly less than what they're already earning. A first employee is taking a risk in opportunity cost by accepting a lower salary, but the risk should have an associated reward, namely equity. However, if a company has to do well just for the employee to break even with the opportunity cost, joining a startup doesn't seem like a sound choice. And not just in terms of money, but also general wealth and quality of life.

Further, the hours conserved by remaining at the day job can be used to build your own product. When the risk-level is acceptable, leave the day job for your own startup where you can maintain control and keep a meaningful equity percentage.

There are benefits to being a startup employee, such as the exposure to growing a company and the opportunity to join a support network and work with good people. Those things have value, but not always enough to offset the opportunity cost of either keeping the day job or founding your own startup.

Personally, I'd still consider joining a startup as an employee if it was a great match.

As a side note, RethinkDB has done a great job with posting a mapping of position/experience to compensation. They set compensation expectations before a prospective employee has even applied.

Interesting read but the details are a bit scary from my comfy chair here in enterprise software land:

- Six years at Stanford, two CS degrees

- Works up to 90 hours a week from home, has burned out multiple times in only six months with the company

- Founders work even more

- All three appear to be single white 20something males

- Job and tech (Clojure!) sound cool.

Edit: All that said he seems like a nice guy and I hope he gets rich off of Backtype. I love the service. I just can't quite project myself into the profile above.

Why is it bad that they're white?

Obviously it's not bad in and of itself, it's just an additional layer of homogeneity that a prospective teammate will consider before applying.

The 90+ hour workweeks are already a big red flag to anyone with a spouse and/or children. It's hard to get along at work when everyone else is comfortable contributing in ways that you can't match directly. No one wants to be the odd man out in a high pressure work environment.

Edit: Fwiw I am also a white 20something male! I have always worked in relatively diverse environments and I have enjoyed it and would look for the same in my next employer.

I have always worked in relatively diverse environments and I have enjoyed it and would look for the same in my next employer.

My current company had no diversity until I joined (the founder and employee #1 even went to the same school), but it never struck me as being worth thinking about. I'm honestly curious, what benefits do you get from a company with ethnic diversity?

Racial and ethnic diversity really seem like non issues...they are pretty superficial differences within a work environment. Age, children, and sex are a little more relevant, and even those are pretty minor and only loosely correlated with traits relevant in a work environment.

Bringing a windows guy into a unix shop, or hiring a sales guy too early at a product development stage startup, or hiring a stupid or lazy person would be real diversity of a bad kind. Good diversity is bringing in people with domain expertise outside your core specialty, like having a font and calligraphy aficionado on your os team.

Superficial diversity is really overvalued.

I've often found cliquishness when there's, say, five people, of which four are from the same age/sex/ethnic/cultural/etc. background, and the fifth is from something different. It's worse when the four are from a quite narrow background of similarity, like four guys of the same age/race/major/etc. from Stanford, or four immigrants from the same country.

If you put it that way I sort of agree, although I think Americanized ethnicity or race is much less dominant as a trait than other traits.

Racial and ethnic diversity really seem like non issues...they are pretty superficial differences within a work environment.

Superficial diversity is really overvalued.

And very undervalued by people in the majority ...

For the past 12 years I have often been either the only American in a group, or the only white guy, or the only person who went to a top-tier tech school. I've been in groups that have been totally multicultural, or groups where one other ethnicity or race predominated. (admittedly, everything has been at most 30% female).

I really haven't observed ethnicity or race as a primary factor in team dynamics. Even first language, assuming people have a minimal level of fluency, hasn't been a major factor; even with my minimal French, I've ended up hanging out with French video gamers and sci fi fans (all 3 of them at a big base; they spoke maybe 100 words of English) vs. a bunch of other Americans.

Volitional things like the kind of music you like, the job you do, your hobbies, etc. are really a much bigger factor, at least in my limited experience, than race or ethnicity.

In an 100 person office, racial and sexual homogeneity would be creepy.

In a 3 person office, who cares?

It's not bad that they're white - it's bad if they're three identical clones.

And their race is supposed to predict this? I've heard white people can actually be quite different from one another.

If it's one item in a long list it seems reasonable to take it as one factor, especially if they're, in the case I've encountered most often, twentysomething male nonimmigrant whites who grew up in an urban area in the northeast or west coast, in a middle-class or better family. Any one of those factors aren't particularly predictive, but taken as a whole they narrow down a culture with some accuracy.

In a long enough list, by definition it's reasonable.

The problem is, this was a short list.

No, the problem is that in a list of eleven points, you pick one to make a fuss about - alledging that the original poster said them being white was a bad thing.

It was in a list including "two degrees" (good) and "burned out twice in 6 months" (bad). Why do you take away that he said white is bad?

Why do you have an issue with skin colour being mentioned, but not age or gender or which college the degrees were from or how many hours they work or which specific tech they use? Why are you pushing so hard to make a great big racial controversy out it?

The list _delirium and I are referring to is this one of 4 items:

    All three appear to be single white 20something males

I am in fact pretty nearly as bothered by the claim that it's a problem that all 3 are male, or in their 20s.

It's lame when someone writes off a group of people based on such superficial characteristics.

I've had some weeks where I've pulled 90+ hours, but my normal week is more like 70 hours.

The sentence about working from 11:00 am until 2:00 am is probably the source of confusion there, if you don't read the part about taking breaks. 11-2 * 6/week = 90.

My work week could be described the same way, but my breaks are for 2 or 3 hours each, and with no commute (which most people don't count in their work week), it's pretty comparable. If you enjoy what you do, those two late hours working uninterrupted are great.

this is similarly ridiculously high.

Well, I really enjoy what I do, and I'm passionate about seeing this company succeed.

How many hours of that would you say you are in flow? [1]

[1] http://en.wikipedia.org/wiki/Flow_(psychology)

What salary can one expect while working for a YC startup? Is it comparable with the industry's average?

http://rethinkdb.com/jobs/ has one data point

When comparing salaries, http://indeed.com/salary has been somewhat useful as well.

The general feeling I get from reading HN is that early stage employees take lower salaries in exchange for higher stock options.

As the company matures and expands its perceived risk drops so later hires tend to be more experienced, higher paid, and with less in the way of stock options.

Seeing as BackType has only three people right now I think we can guess it's on the low salary, high stock side of the curve.

I took an almost 50% salary cut when I first started working at justin.tv. I don't think you can generally expect the industry average in an early-stage startup. My salary is nearly back up to what it used to be now though.

> My salary is nearly back up to what it used to be now though.

How much do you figure is your overall loss because of joining (in $) ? Does your equity make up for that ?

If you assume the company's most-recent valuation accurately reflects its worth, then yeah, my equity more-than makes up for my loss. Until there's an exit though of course, the equity is essentially worthless (I find I stay more sane if I just act like it has no more value than a random lottery ticket has).

I love the layout on http://www.backtype.com/about

Seeing the two open positions in line with the current team really drives home the point that you'll be taking on key people and not just filling out an org chart.

Wow, having read that I'm genuinely horrified. You work 6 days a week. Why? You're an employee. Seriously even if you weren't theres more important things in life. I can understand where you're coming from but believe me, it's not that the founders are abusing you, it's that you're abusing yourself.

Seriously, go out, enjoy yourself. Live.

Just wanted to comment that this is a great post and I enjoyed reading it.

Nice post. I think I would have a hard time pulling the trigger so quickly after meeting someone, but it sounds like serendipity.

Reply on news.ycombinator.com