6 ms·
Can we please stop this nonsense about "cofounders" joining a company several months after it is founded? What's wrong with calling a spade a spade and saying
by cperciva 17y ago
Can we please stop this nonsense about "cofounders" joining a company several months after it is founded? What's wrong with calling a spade a spade and saying "RethinkDB looking for 1st employee"?
- zaidf 17y agoUsually expectations, pay and equity.
- deleted 17y ago[deleted]
- jmtame 17y agoIs it a fetus or is it a baby? It doesn't matter, it's so early that you can call it what you'd like. I think it's fine that they're looking for co-founders. They could just say "hiring first employee," but sounds like they're looking for a person who will be more involved than that.
- cperciva 17y agoIs it a fetus or is it a baby? It doesn't matter If it dies, the law considers there there is a very large difference. :-) More seriously: The English language says that "co-founders" are "people who found together"... not "people who found together plus anyone who joins them shortly thereafter".
- catch23 17y agoNot necessarily. LinkedIn technically had 1 founder: Reid Hoffman. But really he couldn't build LinkedIn solo, after raising a small amount of capital (and using some of his own from paypal) he recruited 4 others to help him and become additional co-founders. So LinkedIn actually has 5 cofounders, but really started with 1.
- jmtulloss 17y agoWhat we need is another word that means "1st employee and oh so much more". I'm thinking "employee++", or "founder'" (that's founder prime, if it's not obvious).
- brk 17y agoIn all honesty I think that all that is needed is a dose of reality. If this to-be-hired person is going to be on-par with the existing "founders", in terms of pay, equity, and ability to vote to affect the outcome of the company, then I would call them a co-founder. If instead this to-be-hired person is going to be a very senior employee with more equity than later employees, and some input on the product management stuff, then they are an employee, not a co-founder. I do not know which case is true, my only point is that we do not need to invent new pseudo-titles for everyone to feel special.
- wheels 17y agoUsually I'd 100% agree. But I think the RethinkDB guys are a special case. They've gotten a huge amount done in the last few months -- in my "On Applying to YC" entry, they were the most notable exception to the "the teams that were moving the fastest at the beginning were also moving the fastest at the end". But if you remove YC from the equation, RethinkDB probably wouldn't have incorporated yet. (Well, let's pretend that they wouldn't have, at least.) They're just a few months in. Really, I think it's exceedingly rare when "co-founding" teams all start on the same day. There's a period where the company comes together over a few months and the people that are there when it incorporates become codified as the "co-founders". In this case, the RethinkDB guys are early enough on that I think some of that DNA is still being laid down, and the term co-founder isn't completely off.
- kvs 17y agoI was confused too. Looks like they already have a technical co-founder there; why another? Is he leaving the company?
- coffeemug 17y agoI am the technical cofounder, I am most definitely not leaving the company :) I couldn't have described the reasons we are looking for a cofounder and not an employee better than zaidf - expectations, equity, and pay. We expect full dedication, tremendous force of will to change the world, incredible technical expertise, and capability to lead people and define the company. In exchange, we will give a significant chunk of equity (it's not a 0.25% - 0.5% deal at all), and because it's such an early stage, we cannot pay a competitive salary yet. Expecting these things and calling the person an employee would be dishonest at best. We're in this to nurture a great company, not to nurture our egos. We feel that assigning a title of employee at this stage would be a display of vanity and would significantly detract us from the real goal of building a next generation database that will change the world.
- cperciva 17y agoExpecting these things and calling the person an employee would be dishonest at best. We're in this to nurture a great company, not to nurture our egos. We feel that assigning a title of employee at this stage would be a display of vanity... We clearly have different opinions here. I'd say that calling an employee a cofounder is dishonest at best; that you're in this to nurture a great compnay, not to nurture your employee's ego; and that for someone who joins several months after a company is founded to insist on being called a founder is an unreasonable display of vanity.
- catch23 17y agodude, what the hell is wrong with you? You can still technically write someone in as a cofounder -- both in terms of equity and pay. Just because you're recruiting them later than the initial founding team doesn't reduce the title. Saying that it's dishonest is just wrong here.
- whirlycott1 17y agoYou're completely right when you say "nonsense". I'm the founder of StyleFeeder. I've worked for five startups before this. Being a founder is a unique experience characterized by a constant feeling of being angry all the time and being emotionally drained by your work. Don't get me wrong - I love what I do, the people I work with and the company is doing great, but it is fucking hard. And I feel that all the time as 'founder' whereas I never did as an 'employee.' I've also had conversations with other founders who independently used the exact same language to describe how they feel about their companies. My simple rule: if there's nothing there when you start, you're a founder.
- raffi 17y ago+1 to being angry all the time. I wasn't angry per se but I was certainly edgy. I loved my product but when I was on my first startup I really hated myself for giving up the potential to advance in my career and I desperately feared going nowhere and trying to explain to some clueless HR person the gap in my resume. Fortunately it worked out but that sucked :)
- numbchuckskills 17y agoThat threw me off as well. The product idea (and even some code) is in place, the vision done, the roadmap well on it's way, and they've already identified they need to hire. You're looking for an employee.