This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
What does it mean to be a CTO for a startup? Should a startup CTO spend their time programming? Exploring new technologies? The role of a CTO varies as the company matures. But be careful, and mind the gap – the Founder-Developer Gap, that is! It’s understandable - a hands-on developer can produce a product.
I’ve been having discussions with several people recently about the role of the CTO (ChiefTechnologyOfficer) in very early stage companies. In December 2007, I described how I commonly take on an Acting CTO Role in a Start-up. That’s why Roger Smith puts the focus of the CTO on programming for the earliest stage.
Even when they have talked to multiple developers or development firms, we’re often the first to ask basic questions like “Who are your customers?” ” or “Are you developing for desktop, tablet, mobile, or all three?” The innovator/developer relationship needs to be a conversation.
We hear them explain that their current software development is expensive, deliveries are rarely on time, and random bugs appear. Common Signs You Need a Technical Review We’ve already mentioned the most common signs that you might need a technical review: Slow or late delivery: “I’ve authorized two new developers, and we’re still behind.”
He's the former CTO at Stocktwits, and he did the analysis and found out a lot of stuff. We all know that you develop better rapport with someone, cement relationships, and have a lot more commitment to someone when we do that. We said, huh, are there any patterns these top agents were doing that others weren't? READ MORE>>.
We organize all of the trending information in your field so you don't have to. Join 5,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content