When we talk about tech startups, a CTO plays an incredibly crucial part in its success. In today’s conversation, we dive into what being a CTO entails and how you as a software engineer or even a founder could move into a CTO position. Regardless of where you are in your startup journey, you’ll learn a thing or two about building + scaling a tech team and system.
“What is a client worth at the end of the day?”
Bug tracking, error logging, alerting and app stability tools…
They cost significant upfront dollars and it also slows your team down initially.
However, once you’re live with your app and issues start arising, the ability to debug quickly and resort to a solution because you’ve got visibility, makes it worth every penny. Like Geard said “What is a client worth at the end of the day?”
5 Days vs 5 Hours
5 Hours vs 5 Minutes
In addition to this, visibility also means that you’re able to identify bottlenecks and prevent future outages, reduce performance issues etc. In layman terms, I call this good customer service. :)
I’d like to also add Smartlook, this has been amazing for recording keystrokes within the app, so it’s quick to replicate the issues users are facing. We’ve recently managed to reduce our beta test cycle from 4 weeks to 10 days, courtesy of SmartLook.
I had an absolute ball speaking to Gerard about what a CTO role really is and his journey from Software Engineer to that leadership role. Full podcast interview in the comments below.
"They genuinely felt like development partners as opposed to a company that we had contracted."
We set an ambitious target of hiring 11 senior engineers within a month. To my surprise, we achieved that. During the entire process, PICWA felt like an in-house talent team and worked closely with us to find the right fit. Fast forward 4 years and we're still working with the same team PICWA provided and have no idea how we'd operate without them