Hence a classic toxic 24/7 role where you're expected to double as operation and developer and database and architect and all. You should have run away much quicker.
Nothing to do whatsoever with CTO. It's not event relevant to anything executive or management.
I hope that you can describe your position in a more positive light than this text and without alluding to being CTO, because both will get you rejected fairly quickly in any interview.
Nothing to do whatsoever with CTO. It's not event relevant to anything executive or management.
I hope that you can describe your position in a more positive light than this text and without alluding to being CTO, because both will get you rejected fairly quickly in any interview.