Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Not to worry, they've just read the article on why you should not be the first employee in a startup, and more specifically, what terms you should not necessarily agree too.

Being the first employee of a startup can be the best thing since sliced bread. You take little risk (compared to the actual owners), yet the reward is usually way better than employee number 100. Who do you think is more likely to get 1) a bumb in pay and 2) a better position first?



Most startups don't get anywhere near employee #100. If you're in a startup that does, you'll likely be happy to be either #1 or #100.

Being #1 means you work as hard as the owners but for much less -- often you will end up making less than you'd make elsewhere.

Being an early hire seems to be about trading salary & security for experience running a business. Friends who have joined a startup early have said it's the absolute best way to learn what to do -- and many times, what not to do -- when you're starting your own company.

Of course, YMMV. I've heard from plenty of early hires that don't end up near the business side, and don't get much out of it.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: