Ask HN: CTO wants me to leave

403 points by cantlookaway ↗ HN
I'm the tech orientated founder (the other is the business guy), not the best coder but I understand my domain and know my abilities.

We brought in a guy as CTO to help us move past problems we were having (feature creep, project management, enterprise level etc.).

The guy has a lot of experience as CTO (I had very little, also little as a coder), and he was instrumental in getting us to the point of launch where we were enterprise grade ready (as opposed to hacker ready).

Now he is advising me to leave, that I'm not a good coder, that he wouldn't hire me if I wasn't already a founder and not what the company needs.

I have improved significantly in the last few months from where I was (generally unstructured development, no tests, poor formatting / naming etc., but functional, generally coding to working with others instead of by myself) but he has said that it's not enough.

We have hired another coder who I get along well with and I have learned from.

My question is, does he have a point? Is this something that is common? Has he overstepped the boundaries?

EDIT: He's not asking me to leave now, since I'm still desperately needed, but in 3-6 months time after we have raised more funding.

292 comments

[ 2.7 ms ] story [ 528 ms ] thread
First off, I'm sorry about your situation. Nobody here will be able to judge with any degree of accuracy whether he has a point. I personally would not look at this situation as a technical one; this is a business relationship situation.

Regardless of whether there is any grain of truth, the CTO has lost confidence in you. Not just a little bit. He has asked you to leave. The rest of my advice assumes the CEO (your co-founder) has quite a bit of confidence in the CTO. If that is the case, I'm not quite sure you can come back from having the CTO asking you to leave, nor am I certain you should.

I think it would be advisable to talk to a lawyer to see how you can cleanly and professionally leave on your own terms. Save the emotional stuff for friends and your alone time. You will no doubt need to grieve (this was your baby). But I think it would be better for you to be proactive about leaving and professionally extract yourself from this situation. That said, make sure you know your rights and what your contracts entitled you to in such a situation.

Once extracted, take your hurt pride and prove them wrong.

Thank you for taking the time to respond.

> The rest of my advice assumes the CEO (your co-founder) has quite a bit of confidence in the CTO.

This is the case, it is in my interest however to remain in the company because my equity is vested, the sooner I leave the less I will get in return, apart from my time, and opportunity cost I invested all my personal wealth.

If you can come to some agreement with the CEO/CTO, it's possible to accelerate a portion of your vesting for your departure. Or, since you said they want to wait until the company raises funding, you could negotiate some other kind of severance.

Either way, if possible, figure out a compromise which feels fair for everybody involved. This doesn't need to be completely one-sided.

This.

Being asked to "leave in 3-6 months" is the new CTO's opening gambit in the negotiation you're about to start.

Your _worst_ negotiating option will be to say "OK, bye".

Work out what you want.

Work out your best idea of what the CTO/company wants (depending on what you want, the first step here is most likely to be asking them outright - if what you want most is to get rid of this CTO, this step will need to be approached much more subtly and delicately, and probably with someone much more experience helping you out).

Work out some "next best alternatives" to your optimal outcome, and what you'd accept as compensation for agreeing to those non-optimal alternatives.

Mostly though - work out what _you_ want - and why, and once you've done that, look at it with the most objective view you can and determine if it's actually plausible and realistic. (To be honest, a guy who wasn't even writing tests a few months ago _isn't_ going to be the technical lead or chief architect of an enterprise software startup - at least not a startup with a high chance of succeeding or getting serious funding. Be realistic here.)

If it's just the vesting(/money) - you'll negotiate one way. It's it's actually an ego/ownership/founderdhip issue for you, then acknowledge that (at least to yourself) and work out how to negotiate your desired outcome while keeping that perspective firmly in mind (and seriously, think about whether you need to rethink that - if it's mostly an ego thing).

For what reason would the OP need to negotiate with the CTO?
Stay for the 3-6 months, until you get your stake sorted, then get out in time before the shit hits the fan. Don't bother trying to reconcile relationships, don't get involved in the politics. It's a shame it's turned out this way, but by the sounds of it, it's not worth it. gone sour. There'll be another opportunity elsewhere for sure.
> it is in my interest however to remain in the company because my equity is vested

This is negotiable. But you shouldn't necessarily be the one to negotiate it, so you should probably start talking to your own lawyer (not the company's).

> I invested all my personal wealth.

I think this is being overlooked. You invested all your personal wealth into this company and in return you got unvested shares?

This right here. The money OP invested -- whether hard cash, or equivalent deferred pay or both -- should have resulted in direct, fully vested stock, just as it does for angels and VC's. (to clarify: it should vest at the rate that the work is performed, not over some arbitrary schedule).

There's this underlying meme in our community that "elbow grease" investment -- working for low pay, no benefits, rejecting other career opportunities -- is somehow worth less than an investor's cash. IMSHO, it's just the opposite -- cash typically doesn't draw down one's pool of emotional well-being and spirit the way hard work does. Work investment should be rewarded with a premium, not treated as somehow less than just money.

What I don't get; shouldn't it already have vested if he is a founder? I'm not sure about the system there but when I found a company those shares are mine?
The advice has been given several times, on HN, that founders should vest, so that you don't need to claw back 1/3 the company from a founder who walks away a month in.
This is sane advice if you're playing the standard VC game where you shop around for a co-founder, raise funds, and build a product (not necessarily in that order).

OP's situation sounds more like a bootstrapped small business where he invested his life savings and blood/sweat/tears. I'm not sure that vesting shares is ideal there -- perhaps a well defined shotgun clause or similar is more reasonable to handle unruly founders.

(comment deleted)
You need to sit down in a room with the CEO and CTO, and have the CTO describe his concerns and then you can all resolve the issue together. For the sake of the culture of the company you can not let this slide as back-room talk, as that would create a poisonous culture. When that is answered talk to a lawyer before signing any papers, and remember that the companys lawyers are obligated to protect the company and not your interests so really get your own laywer.
I don't know exact your situation but I saw similar case. In summary, the founder who showed support to company without ego made company successful, not the CTO or VP engineering who joined later stage. That’s your baby, but to CTO, that’s neighbor’s. You are happily clean up your baby’s diaper or mess, while neighbor will blame you and not clean up. If you need process to get enterprise ready, you can hire process guy and experienced enterprise software guy and adjust your team. I think when CTO say it to you, he have talked CEO already. In that case, if CEO is mature, CEO should stop CTO blame you and discuss that matter with you first. If you are not sure about CEO’s intention, you should talk him and understand about it. In this case, I feel that CTO have hired couple of his guys and they are all point same direction. But don’t be afraid those and think whether you still can help company or not. (I think you still can help company) you should talk to CEO and let him know that company need you for technical evangelist or customer meetings or … and at last as back up to CTO. (For me, It seams CTO is a type of guy who build castle inside house, which will cause problem soon within organization.) By the way, you should consult with the lawyer if possible, and understand what you can get worst case.
Your question and many of the comments so far tend to focus on the CTO. I'd like to focus on your co-founder, the "CEO".

If he wanted to start with a less-experienced technical person, and jettison them early on -- he could have hired an employee and paid them.

Instead he co-founded with you, as a partner. He was happy to take your money -- you have skin in the game. He doesn't get to shoo you out the door now like a temp.

He also doesn't get to do it via the CTO. He owes you a frank conversation. Also you need a lawyer.

tl;dr: From hearing your side of the story, although the CTO is handling this like a tool, the CEO is the biggest schmuck.

I agree with this point. The CEO does just what he was told to. I assume he's just an employee without ownership, and employees don't fire owners unless someone much stronger is behind them.

Definitely lawyer up, that would be a first thing. Then, if you want to regain control about he company, consider CEO your enemy, not the CTO. Invent a reason and fire the CTO, if you can do it. Then, step up as CTO yourself, or at least hire a person you trust. Then, hire COO, CFO, CMO. Make sure those are people that are loyal to you and where each one will take over one of the CEO responsibilities. At the latest stage, let those people document every mistake of CEO, and you try to push him out together with C team and investors.

That's exactly what he is doing to you. He convinced you to voluntarily step out from CTO position and hired his tool. Now, your chances to fight back are much worse from this position, but the war is not yet over.

So, lawyer up, read Machiavelli, know your enemy and fight fire with fire. Remember, the CEO that did this to you is not your friend anymore, and deserves whatever you do to him.

Personally, i consider this bad advice. Fighting is never really a good thing. SO please don't start a civil war, all it will do is destroy the company. The whole vengeance thing is very counter productive. I'd say lawyer up to get compensation and not to take revenge. And then leave and find a place where you are more appreciated. perhaps focus your energies on something new , something productive
It depends. Is company worth fighting for? What would be your share if you keep your part of the slice? If that is bigger than compensation you would get, than it certainly is worth fighting for. It's not about vengeance, it's about founders own interests, even if that would make company worse off.

45% share of 100M$ worth company is still much more than 10% share of 200M$ worth company or 1M$ compensation. You are not fighting to optimize for the company success, you are fighting to optimize your own wealth. If the company gets destroyed, and you still manage to get more then what would be your compensation package, you are still better off then retreating. Why caring about the company that doesn't benefit you, you would certainly not enjoy the success of the company that squeezed you out.

So yes, lawyer up and fight if it's worth to you to fight for the control. Don't be emotional about he company and business. It's your weakness, and they are already playing on that.

Well as someone here pointed out, the whole fighting thing is toxic. It even marks YOU for the rest of your career. You can't just go to everyone and say "he started it!". outsiders would see BOTH of you as dangerous, and would likely avoid working with you. So it's more of a suicide mission really
You can simply tell him that you'll leave if you get the rest of your vested stock, of if you get a new position as an "advisor" that allows you to stay on at a low salary until your stocks have finished vesting. If he really wants you out he'll find a way to make it happen, and if that way is writing a check instead of dealing with a bunch of drama he'll probably take it.
The questions you want to be asking are to a lawyer regarding corporate law given your current situation. (Talk to your own lawyer, not the company lawyer who represents the company and not your interests as a shareholder)

I would work on retaining control of the company and your shares, possibly isolating the CTO in terms of power, if not outright dismissal.

The CTO is way out of line speaking to a board member, and majority shareholder like that. I assume you are a director and hold ~50% of the company in addition to a few of the officer positions in the company. Utilize corporate law to eliminate risk to your portfolio.

The tech shit is completely irrelevant, you should be discussing with the other shareholders how out of line the CTO is and your contingency plan for dealing with officers who are not respectful of the owners of the company.

Also check whether the company owes you any debt, if the other founder can't come up with the money you could also use debt to take control. Again, talk to a lawyer, and keep in mind that it doesn't matter if the company tanks if you're not going to be part of any success it has. Scorched earth the mother fucker if no one wants to play ball. (Shareholder and board meetings can be a great way to get internal feuds into the corporate minute book)

Do you think anyone at Facebook cares that Mark Zuckerberg is not their top coder? (And even if he was do you think that the best value he could provide to the company would be from writing code?)

Is he/she an employee or a third partner?
> apart from my time, and opportunity cost I invested all my personal wealth.

You can try to negotiate a settlement (still consult a personal lawyer) of retaining some of your money put in (maybe after they receive investment) as well as an additional accelerated vesting of a small part of your remaining unvested shares. You still have some rights to make a big stink about all of this, but I wouldn't advise trying to stay on. You may end up with nothing and have burnt some bridges with the CEO and future investors.

You seem to think it matters what the CTO thinks of the co-founder.
(comment deleted)
Wow, that's tough. I have heard that when a biz scales, sometimes the early employees don't fit as well, because the skills needed are different than when first starting out. To get things going you do a lot of everything, and later they need specialists. How passionate are you about this startup? What does your co-founder think? You would think there could be some role you could fit into, maybe COO? Depending on its success I would hold your ground , or they should be willing to buy you out or something. Best wishes!
He's trying to fuck you over. Remind him that he works for you, not the other way around. Start looking for his replacement. Check with a lawyer about the security of your own stake and make sure you are good with the business guy, because the CTO has probably been whispering poison in his ear about you.
> .. the CTO has probably been whispering poison in his ear about you.

This just has to be true.

FWIW, he may just have been saying exactly what the OP says himself:

"I have improved significantly in the last few months from where I was (generally unstructured development, no tests, poor formatting / naming etc., but functional, generally coding to working with others instead of by myself) but he has said that it's not enough.

We have hired another coder who I get along well with and I have learned from."

There's quite possibly a good argument to be made saying "this guy shouldn't have commit access to our code base" and it's not beyond the bounds of reasonableness to read into that "a few mid level developers under normal CTO oversight will give us a much better starting codebase than this guy is likely to deliver without significant extra training and experience".

Not saying that's definitely the case, but it's certainly plausible. (And I've seen it before, more than once... Hell, I've _been_ "that guy" myself, back in the day.)

It's one thing to say 'to be honest Bob, your code is pretty messy...' I'd have no problem with that, indeed as CTO it is part of his job to be honest and say that something should be rewritten or someone with deeper experience brought in to work on part of it if that's what's going to make the product better.

But it's another thing entirely to be telling a founder that they should be leaving. This is saying 'not only are you not good enough to write the production code, you're so awful that you shouldn't even be involved in the company you founded any more,' as if the OP has no possibility of developing him/herself as an owner of the business.

We took commit access away from our CEO once (who was also an owner). It was fine.

The fool who tells the business owner that he should probably leave _his own business_ may as well go and tie the noose to hang himself because that's what he's doing here.

Fuck what is right, fuck what the CTO thinks. The business owners always have the last say. This CTO is toast.

but the CTO wouldn't be saying that unless there was another "conversation" out there. Why is this guy CTO anyway while a Co-owner is left at coder? You don't bring somebody in as "CTO" without a promise of a cut of the pie... and that cut is going to come from you obviously.
+1 he works for you. He's got you ready leave because you doubt your abilities. It's one thing if your company needs all rock star engineers to make a product push but if it was that I'm sure you'd see it that way. That's an opportunity for you to shift focus to something else but it just doesn't sound like that. It sounds like he's trying to get rid of a technical founder. Don't let him.
yep and depending on your product, you might not even need a CTO until way later. Your ability to deliver a working product quickly and measure it's performance (metrics wise) is way more important than writing the best code evar.
> He's trying to fuck you over.

Do you always assume people are full of malice based on one side of the story or...

I would be pissed that out of a four "man" team (2 founders, 2 employees) that the first employee would have the gall to ask them to leave. How is this acceptable? Only in the world of companies seeking funding.

If the CTO came and said hey in 6 months I think we should discuss you stepping away from coding and into a new role. I wouldn't want to hear it but if they told me to leave my very small company I would think they crossed a line. The CTO maybe management but he isn't the owner.

In this sort of circumstance, yes. There's no other justification for the actions they're taking and the manner in which they're taking them. The CTO is pursuing a course contrary to the OP's own interests. He need to take this seriously and start talking to his attorney.
I hope as a cofounder you signed contracts and have equity.
"EDIT: He's not asking me to leave now, since I'm still desperately needed, but in 3-6 months time after we have raised more funding."

Means they do actually need you, the CTO is waiting for a payday before kicking you out for a higher stake. Tell the CTO to go stick it if they need you before funding but not after.

The question I would try and answer if I were in your shoes is the following:

Does he want me to leave the company or does he want me to stop writing production code for the product?

If its the first one, there is likely a personal issue between the two of you that needs to be resolved one way or another.

If you think the second option is what he is really trying to communicate, then I would look for other opportunities to contribute to the company. It sucks to grasp your own limitations and admit that you might not be a good enough coder to contribute to the product at this point, but this is a critical time for the future of the product. Any technical debt acquired at this phase of development is going to be very costly to pay off later since you are developing the core of the system.

However, you are a founder of the company, and I am assuming very passionate about the company's mission as well as financially motivated to see this thing through. There are tons of jobs that will need to be done as you guys grow, and each one of those is an opportunity for you to contribute above and beyond what a new hire off the street could accomplish. A lot of those jobs can also take advantage of your coding skills to either automate processes or utilize your deeper understanding of how the product works to better support it.

This is of course assuming that you guys have the cash in the bank to pay you for this work, if that is not the case then the situation is a little trickier and you will have to explore other options.

> If you think the second option is what he is really trying to communicate, then I would look for other opportunities to contribute to the company.

This was my thought. It would be worth looking into roles like developer evangelist, if it makes sense for your company: you're clearly technical enough to make things happen, and you have the domain knowledge to be very useful.

I was under the impression that "co-founder" carried a lot more weight than CTO; is this not the case? My gut feeling was that, if I were in the co-founder's shoes, I'd fire the CTO immediately.
This would be dumb though, because it would tank your company.
You are assuming that the CTO is the only CTO in the world.
Leaving the situation as-is would tank that company.

In a small team, infighting is a much bigger threat to survival than losing skills/results of any single individual.

Hmm, I'm sure infighting is bad, but often enough individuals do have skills and in particular experience with the setup and/or code and/or business contacts that the startup has made that you're not going to find a replacement nor train one without losing lots of time and money. Certainly that's an avoidable risk with effort, but I'm pretty sure that some level of infighting may be less risky than losing certain individuals.
A CTO with polarized vision would tank the company faster.
So, if that would tank the company noone gets nothing. If he doesn't fire the CTO, he gets nothing and company may or may not get anything. To me, pretty clear situation what would I do. I would risk the company to save myself from certain loose.
(comment deleted)
> I was under the impression that "co-founder" carried a lot more weight than CTO

Depends on the circumstances. If one founder controls a majority share, they can fire anyone they wish.

In this current situation, if the CEO controls more than 50% of the shares and the CTO reports directly to the CTO, the CTO can fire the OP.

agree completely. I'd have a frank discussion with him and attempt to determine if this is political. If it is, fire him immediately even if there's short-term pain because the politics will fk the company anyway.

If it's not political, and you agree with his assessment of your production code, then there's an R&D role that probably needs filling and that you've already proven you can do - finding profitable market niches and creating prototype products/services to address them.

Don't sweat being a "bad coder". Every coder (yes, even the awesome ones) feels a little worried that their code is bad, and he's just playing on this insecurity that we all have. Part of the 'your code is crap' syndrome we see in tech is just defensive projection.

You managed to build a production system that is gaining traction, which is amazing. Go do more of that :)

I'd second your words about "bad coder" arguments. This argument is ridiculous, particularly if he had managed to to build a production system that is gaining traction. And did it single-handed (or in a team of two).

I would disagree however about the advice to 'fire him immediately because the politics will fk the company'. The problem is, the moment there is some money on the table politics and power play starts. Unavoidable.

You can be a terrible coder and build an MVP in PHP or something. Doesn't mean you can scale it, both in terms of adding new features, or in terms of increased traffic.
Um. That kind of thinking is pretty close to my own from some years back. Not any more, but who knows, I may change my way of thinking again ;) In the moment I'm just reserving my judgement regarding skills of other developers. And only make judgements regarding particular pieces of code, mostly trying to find positive things in it, rather than negative ones.

Out of curiosity, a personal question. In terms of years of active software development, what's your level of experience? Is it say, 20 years of building code for moneys? Two times less than than? Two times more? You don't have to answer.

About 20 years, yes.

There's nothing bad about being a terrible coder who manages to put together a basic product. There are plenty of terrible musicians who still release albums for example. But it takes wisdom and maturity to understand ones own limitations.

If I owned 50% of a company, and a guy who had measurably increased my wealth by improving the product and hence the value of the company, gave me some advice like this I would listen very carefully. I would not "cut off my own nose to spite my face" or "throw the baby out with the bathwater".

Interesting. Well, my current way of thinking is that there are no terrible coders, it is just that mature and experienced engineers are slightly less prone to making terrible and difficult to correct mistakes. Like using an obscure language or something, just because they feel that way and without considering the implications ;)
I disagree, somewhat :-) There are people whose contribution is horrible but it's rarely confined to the quality of their code. It's more about being able to lead the company in directions that are ultimately wasteful in some way or other and not being able to change direction when the time is right. That leadership may be expressed in code, but the code is as much or more a symptom than the root cause.

With basic QA practices in place (peer review, coding standards, designs grokked by teams not individuals etc.) a single person usually can't muck up the codebase very badly. He or she can still poison a whole project or company.

Well, my understanding is that developer's experience changes the shape of the probability distribution of excellent/horrible contributions. But it is always a distribution. And that it is difficult to accurately distinguish between excellent/horrible contributions without hindsight.
I find that as I get more experienced, I'm more aware of how much of this huge discipline I don't know, and how many mistakes I've made in the past, and I'm much less likely to call myself a "good coder".

When I was younger and slapping shit together any old how, I thought I knew it all.

There are, apparently, those who cannot implement FizzBuzz. Perhaps it's incorrect to call them "coders". But beyond that, you have a spectrum of skill. Do they become competent before they become coders in your books?
I take it you've never had to work with bad code. It's ruinous to the company's prospects since it slows everyone down and makes' developers lives miserable until they quit. It starts to take an entire afternoon to make a simple change, and your business is paralyzed.
+1 on all pointers. That's what his co-founder is supposed to say. Unfortunately, failing to support each-other in such ugly cases, says much about the future (or the lack of one) of this partnership. :(
I agree with you. Of course, I don't know the full story but given what I have seen in the past I would guess it's the second option.

Some of the coders simply can't deal (or, more accurately, their egos) when someone less skilled is above them in the hierarchy.

If this is the case, I'd say just fire him. It sucks now, but will save from a lot of pain later on. For instance, when you hire someone else who might happen to be less skilled than the CTO.

Good software developers know that there are less skilled people, they used to be like them, and deal with that appropriately (i.e. with respect and without offending). And then there are prima donnas who can't deal with working with another human being for whatever the reason is.

At the end of the day, being a good software developer is not all about writing code. Far from it.

Let's assume that what the CTO says is true: you're not a good enough coder that you're any longer needed on a day-to-day basis in a few months. You're still a cofounder and I assume owner of quite a bit of equity of this company. Can't you talk to your other co-founder and find a different role for you on a day to day basis so that your stock still vests?

Or is this all about money/power? Is the new CTO threatened by you for some reason or trying to consolidate his power? Does the new CTO just not like you?

If you and your other co-founder are even remotely close, you guys need to talk. Sit down and figure out what other roles work for you at the company. Perhaps you will need to move out of management and become something like a "developer evangelist" or "head of support". Anything to keep vesting, right?

Why would he ask you to leave unless you were a liability?

It makes no sense as there are so many other positions that become available as a company grows.

Go learn Product. It doesn't take nearly as long, and you can have just as big of a positive impact.

I have no idea why people are actually recommending moving on.

You not only own part of the company but can use this experience to grow both technically and professionally.

Don't waste the chance to learn more than you ever could.

Are you taking a salary?

I don't see how you could contribute negatively to the company if you are at least somewhat productive and know the domain.

If there's a reason to leave, it's that the situation might be too far gone to salvage. From the one side we can see here it seems unlikely that the CTO has kept this conversation/complaint limited to the OP, and his desire to remove one of the founders is already undermining that founder's leadership position in the company.

Getting out with compensation for the equity or accelerated vesting might be the best case scenario, depending on how far this has gone.

It's your company. Even if one aspect of the company has outgrown your abilities, you could definitely find other ways to contribute. Your cofounder ought to be someone you trust. If so, this is something you should also discuss with your cofounder.
A good CTO would help you improving. I know it's stupid to make assumptions, but I'd assume he's trying to manipulate himself into higher equity in an early stage. Telling someone that he's about to be let go is poison motivation-wise. He may be trying to reduce your performance so he can use your declined output against you.
It is REALLY stupid to tell someone you want them to leave in 3 months. Why not wait until three months have gone by? My totally uninformed guess is there is some kind of long game / ego thing at play besides just actually ability to contribute. Don't feel ashamed that you aren't the alpha tech. If you are trying your hardest, and especially as a cofounder, you would be more than welcome at any company I have ever worked at.
And why would you tell someone this right before fundraising? What a great way to fuck up your round...tell a cofounder you don't want his ass around in 3 months.

Oh, by the way, can you come to this meeting and pretend you're happy here?

I wonder how your co-founder will feel when the VC's ask him to leave because he's "just not what the company needs at this time"?

Whose company is this, you and your co-founder's or the CTO's?

It looks like you have real equity in the company and there is possible traction in the business.

You are a co-founder. That counts for a lot. I am also assuming that your equity stake is significant.

First of all, deal with this right now. Don't wait for the 3-6 months. You are basically being told that once they have raised money, they will find a way to get you out. Right now, it's a fishing expedition between the CTO and the other founder. Will you be a nice gentle person and go along with their approach or are you going to turn into an attack dog.

You likely have tremendous leverage right now due to this funding round coming up. They will not want to rock the boat. But this is exactly when you should be doing it as I don't believe the "we need you" bit means anything other than "we don't want you to fk up our funding round coming up".

At the end of the day, if they really want you out, they'll find a way to do so. The main thing is that you got to get on the offensive and make sure if you do end up leaving the company, you've left on the best financial terms possible for yourself. Make them pay. In fact, throw out a number you are comfortable with and have them pay you out from that in the next funding round.

If you approach this as "what's best for the company", you have already lost because that's not what this CTO and your other founder are approaching this from.

EDIT: You should provide some more detail on the equity position you have and how formalized it is (ie. proper contracts). Being a co-founder isn't about just writing code. As others have said, if you have significant equity, you have a lot of power. Don't underestimate this.

It also might depend if they were smart and have a vesting schedule for everyone. But that also means pushing people out may be selfishly advantageous in the short term, so it really matters to have known your cofounders long before the current venture.
That's a good point: They don't want to you to leave now, so leverage that. But this situation is not fixable by staying at the company. Recognize the CTO and CEO want you leave when it's convenient for them, and that's it's probably a personal issue, they probably don't like,working with you or else they would've suggested some other role for you. So find a way to leave now with your equity intact, with the help of a lawyer.
Listen ‎Eduardo Saverin:

FIRST THING GET YOUR OWN LAWYER AND TALK TO THEM NOW!

The key question here is : do you have equity, and how much equity do you have in percentage terms?

If you are an equal cofounder, then when someone turns up and says "you have to leave cause better people have been employed", you say "fuck off". Think about it - EVERY company that grows will employ people who are better than the cofounders in some way, that is the whole point. You are the FOUNDER, you brought value to the company early. Just because smarter or more experienced people have been employed in no way devalues what you did in the early stages. In fact this is PRECISELY what is meant to happen. Do you think that Zuckerberg is the best developer at Facebook - legend may say so but it's not true - can't be. So should Zuck be fired cause he's not their strongest tech guy?

You also need to think separately about your rights as employee and rights as a shareholder/owner - they are not the same thing. You DO have clear contracts as both employee and shareholder DON'T YOU? Those contracts specify (or should specify) your rights.

And who the fuck does this guy think he is that he can tell a cofounder to leave? You are his BOSS.

DO NOT LEAVE. And if you do leave, DO NOT SELL YOUR SHARES IN THE COMPANY - just say "I want a MASSIVE payout to accept being fired, and I WILL NOT sell my shares as part of settlement". Hang on to those shares because now these guys are going to do all the hard work in growing the company and you can chill out and do other things and when they IPO, you'll take home your share. And if this is the path you take, look out cause some time in the future they will try to play a legal game in which you hang on to your shares but they get diluted down to almost nothing. This cannot happen if you are careful to look out for it.

This is all on the assumption that you do have equity and contracts in place. If you don't, then you should go and watch "The Social Network" repeatedly until you learn your lesson.

"Do you think that Zuckerberg is the best developer at Facebook - legend may say so but it's not true"

What is this legend? I think everybody is aware of the fact that the infrastructure that allowed facebook to scale was not (and probably could not have been) built by Zuckerberg. He had guys like Adam D'Angelo working for him from the beginning.

The employees of tech companies with charismatic leaders sometimes elevate their Great Leader to legendary status in their field of expertise, whether its true or not. Worshipping is part of the tech company cult thing - you do see the parallel of course with cults and tech firms? There will be plenty who believe the Zuck is the best coder there or amongst the best at least.
He's more like the Bill Gates of the company. Has serious technical chops, and knew that technical thing like scaling were not optional. Compare to the object lesson of competitor Friendster, where the people running it after they ousted the computer programmer founder ignored that minor detail....
> And who the fuck does this guy think he is that he can tell a cofounder to leave? You are his BOSS.

This is the key point. OP founded the company. Presumably he has close to a 50% equity stake. There are other CTOs available -- ditch this one you can't trust immediately.

You helped build something to a point that a job position was created for the CTO, and if you are passionate about what you're working on and eager to learn, it's unfortunate that he took the approach of telling you that you "are not good enough" rather than mentoring you and helping you grow as a developer. I'm sorry for your situation, it's rough.

That said, is this someone who you want to be working closely with? It could be something in your work relationship that is hard to get past. As others have said, understand what you are entitled to in terms of contracts and equity, and try having an open conversation with the CEO if you haven't already. Handle it professionally, and keep in mind that if you are desperately needed now (as you said) that you have some bargaining leverage. :)

You founded the company,doesnt matter how bad you are at coding there is more to running a company than coding skills.

I'd fire the CTO,no matter how good he is,you're the boss,he is merely an adviser,he shouldnt be talking to you like that. What matters in business is loyalty, not skills.You'll learn it soon enough.

>>What matters in business is loyalty, not skills.You'll learn it soon enough.

You got that one right.

What matters in business is loyalty, not skills.

And what matters even more than loyalty, in this kind of game?

Contracts.

If this is getting ugly, and the company has a product/service that could take off and be worth serious money, your only friend is your lawyer, and your primary assets should words with some signatures underneath.

And if, heaven forbid, we're talking about a cofounder who doesn't have a rock solid contract, the time to fix that is right now, with the help of that lawyer, while leaving immediately still appears to be a significant threat to the business.

Loyalty? Really? You think that matters?

Another poster said exactly the right thing. Contracts, agreements, documentation, MOU, etc are the things that matter. Case in point: I am leaving company after being acquired. It's a mutual decision so both sides are happy, but we are negotiating an agreement right now to release me so I am free to pursue concepts (repeat: concepts not IP) that I pitched the CEO 2 years ago. They are only ideas but it still needs to be in writing since I don't want them coming back some years down the line. It's all about contracts.

Are you and your partner equal partners? Can you do more stuff on the biz side? product management/dev side? He's prob right, you shouldnt be coding enterprise level delivery with hackery crappy code. Be of service elsewhere or it will be a pain in the ass.
I say tell him to fuck off. No offense to him or you, but if your willing to keep learning code, then say no and don't look back.

The great thing about being human is our ability to learn. If your willing to learn, then there is nothing to argue about. You want to keep doing this and that is that. It took me 7 years to get where I am now, but I believe I am excellent at coding, where I didn't know anything 7 years ago. So if your willing, tell him to back the f off.

Sorry to barge in on this thread - but I have a question that turns this on its head.

Let's say you are a brilliant CTO/cofounder, but you are already doing something. Now you had this idea (or someone else had this idea) ... and you want to set them up for seed/series-A round and then you want to leave. assumption - you trust the CEO to not screw you.

How do you structure your equity compensation so that you have some benefit after 5 years? One of the thoughts I had was to show the short-term CTO as an investor with vested stock (in return for some negligible investment ... say 100$). Does this protect you from future investor rounds ?

You don't need to be set up as an investor. You can structure shareholder agreements and different stock classes etc. pretty much as you please, or directly award vested stock (beware your local tax rules if awarding/being awarded vested stock in a pre-existing company - chances are good it'll be taxed as income based on some estimate of market value; but if you enter from the start, as a founder, that's not an issue).

The issue in that respect is not what you legally can do, but structuring it in a way that won't scare away investors with too much complexity.

Generally, though, nothing will "protect you from future investor rounds" if they really want to fuck you over, other than being diligent and keeping a lawyer around, and picking honest co-founders. If the investors coming in and other still employed founder(s) wants to mess things up for you, it can be tricky to protect against them diluting your share holdings to next to nothing, for example (e.g. do a round on a very low valuation; issue large amount of options to remaining founders to make up for the extra dilution they take). Of course, if investors try to do that, chances are they'll screw the remaining founders first chance they get too.

Ask for the same terms as the founders, and ask for a big enough stake that you have something left after a prospective Series B round assuming 20-25% watering down in each round. That makes it so that the founders have to do to themselves what they do to you so your interests are aligned.
Provided you're not writing anything that detrimentally impacts the product, there's no reason for you to leave. It's your company.

Now I say this not so you can sit back and let others do the hard work, but for you to figure out how else you can contribute. Every startup, hell every mature company, has issues to deal with on a daily basis. I would be very surprised if there wasn't something else you could be doing for the company.

Worst comes to worst, your job from here on out is to do the tasks nobody else wants to do. From a technical perspective that could mean things like sanitizing the database (if it needs it) or going back and writing some good tests for already-implemented code. From a business perspective, this could mean researching, scraping, generating leads to customers, users, etc. Hell, you can even be the glorified secretary by helping others manage their day-to-day tasks, schedules, appointments. Be the office janitor. Be the guy they send to campus events to talk to students.

If you can no longer contribute to the code for your product, that's OK. There's a million and one things you can do outside that realm to support the product as well as your teammates.

Of course you can always buckle down on your coding game and get better at it. Take online courses. If you (and your company) can afford the time and money, go to one of those schools that teach you to be a better programmer. Tell your CTO that you want to get better and want to learn from him/her.

Be the glue that holds everyone together. Be the swing man that can bounce from activity to activity and ensure everything is running smoothly. Be the founder who's relentlessly resourceful and continues to move the company forward in any shape or form.

(comment deleted)
is it possible that you stop writing code for few months, revisit your programming skill and meanwhile remain active on administration level ??? If you think ur coding is not good, then there is always a chance to improve. And leaving the company is out of question. You have founded it. So you MUST be there because every story dont end like Steve Job's firing from Apple.
Uh, you are a founder. Nobody asks you to leave. You took part of the risk to start the company, the new CTO did not. He does not get to tell you to leave. Ever. Period. I'm actually shocked that you're even considering it.
I'd immediately fire the guy. He works for you not the other way around. You are the co-founder, the big kahuna - not some engineer they hired along the way. Fire his pompous ass.
He has overstepped his boundaries. The CTO works for the founders, he cannot really fire you (asking you to leave is just a polite war of phrasing it). Remind him that it is the duty of any smart manager to hire people who are smarter than him. That is what you did.

My guess is that your position with your cofounder is rather weak at the moment. The cofounder is probably stepping back and saying "This CTO guy knows what he is doing and if I have to choose, I would much rather go with him". That is a tough situation to be in. If that is true, it isn't your CTO firing you (he is just the front man), it is your cofounder. In fact, ONLY your cofounder can fire you (or your investors if you have sold them a big enough share).

(comment deleted)