For the past two years, since I joined a startup as a Chief Technology Officer (CTO), many people think it’s an easy job. They assume it’s easier when you’re hired rather than co-founding a company or being a technical co-founder. However, what most people don’t see is the hard work and dedication required from a CTO, regardless of which way they became CTO. In this blog post, I’ll share my journey, from where I started to how I ended up in this position.
Before becoming a CTO, I had a diverse background. I started as a computer networking designer, which required a solid understanding of how computers and operating systems work fundamentally. This led me to my second role as an Information Security Analyst, where I applied my networking skills, making my work much easier. I then pursued an undergraduate degree in Cybersecurity from Edith Cowan University in Singapore (off-shore campus). This allowed me to broaden my knowledge in technology and explore emerging areas such as Artificial Intelligence and Blockchain. My curiosity for innovation grew during my studies in Singapore. I attended numerous Information Security conferences and events, such as RSA Conference and BlackHat Asia. While attending these conferences, I developed an interest in software development after seeing various product demos, ranging from simple risk management software to AI-powered SaaS SIEM tools. At the same time, when interacting with product vendors, I learned about their startup stories, which further fueled my desire to explore the world of startups.
After graduating, I landed a job at a Security Manpower Services company, which was undergoing a digital transformation stage under a new director. I joined as an IT Manager, overseeing the development work with an outsourced team in India. This experience allowed me to gain valuable knowledge about project management in a live environment. One of the applications I worked on was an end-to-end private property resident management solution that incorporated an integration of Mobile Apps, Web Application, IoT, Data Analytics, and custom hardware. This project taught me to wear multiple hats. First, I approached it from a solution architect’s perspective, designing a flow to integrate different components. Second, I performed operational activities, including finding suitable suppliers and vendors who could support our solution design. Third, I had to identify the exact components and libraries, and conduct a proof-of-concept (POC) for the application to ensure that the developers had well-defined resources and requirements. For example, one of the mobile app features (in 2022) was Bluetooth-based access control for private properties. However, typical iOS devices did not allow permissions over Bluetooth for such communications. At the time, Singapore was using the SafeEntry application for COVID-19 tracking, and upon closer inspection, I realized that the method they were using could solve my requirements. I conducted a simple POC using Flask, and it worked as expected. The feature was then developed in the mobile application. There are many such situations that I could quote, and these experiences helped me improve my IT skills, especially when it comes to integrated solutions. Additionally, I learned how to manage remote and offshore development teams more effectively.
After working as an IT Manager, I was referred to and hired as a Chief Technology Officer (CTO) for a startup. When I initially joined, I felt quite confused, as it took me some time to understand the situation. The role also started with the huge task of setting up a remote team. However, I applied the knowledge and skills I had gained from my previous job to establish a solid foundation for the startup. The major difference was that, unlike my previous role, I didn’t have formal structures in place. Therefore, I needed to ensure that the process and product were neat and clean, as it was a Fintech-related product that required extra measures. So, I underwent my own transition from being an IT Manager to a CTO, and it wasn’t as easy as I had expected. The hardest thing for me, by far, was accepting that not everyone works at the same quality or pace that I do. To overcome this, I constantly remind myself that not everyone has the same experiences, and they may not understand a technical solution or its benefits (just as I may not understand accounting or commerce). However, they are good people trying to do good work; they’re not trying to cut corners, but rather doing their best with the resources and knowledge they have.
Being a CTO involves more than just technical responsibilities; it also comes with operational duties that go beyond the technical realm. Especially when you have limited resources, you need to take action by not only providing requirements but also designing, architecting, laying down, and keeping things simple enough for everyone to understand. As a CTO, I get my hands dirty in every stage of application development. For design, I create process flows and workflow designs. Then, I architect the API endpoints and payloads. For QA, I create test cases. For deployment, I write scripts to ensure that the servers are configured securely and are reliable. Throughout each stage, I apply the knowledge and skills I’ve learned from the beginning, including secure coding, firewall (WAF) configurations, and ITIL & TOGAF practices. This is never an easy task to handle, as I constantly need to keep myself updated with the latest technologies and best practices. While it may be challenging, it is a necessary part of being a successful CTO in today’s fast-paced and ever-evolving tech landscape.
Working in a startup, especially in a critical area like Fintech, is not as easy as it may seem. It challenges you every single day, both technically and operationally. In the morning, you might have to face a customer saying the website is not loading, where you have to explain to them to clear their cache. In the afternoon, you could encounter a user complaining about not being able to log in, only to find out they’re trying to log in to a different portal of the application instead of the designated one. After 9 PM (since it’s a remote team), you need to review the work done and plan for the next phase of development. Amidst all this, you might get a call from partners or suppliers experiencing some internal issues, leading to downtime, and now you need to find a solution. The learning never stops in such a dynamic environment. You constantly need to adapt, troubleshoot, and find innovative solutions to keep the business running smoothly. It’s a challenging yet rewarding journey that requires resilience, adaptability, and a passion for technology.
Throughout this journey, I’ve learned that it’s crucial to understand those around you who need more help and to appreciate that they are on their own journey, developing at their own pace. No matter whether you are an IT Engineer, Admin, HR, or CTO, it’s important to have accountability for your actions. Finally, it’s okay to ask for help when you need it. One of the unexpected benefits I’ve experienced is how friendly people are and their willingness to help whenever I reach out. As a CTO, it’s essential to foster a collaborative and supportive environment where everyone feels comfortable seeking assistance and sharing knowledge. By embracing this mindset, I’ve been able to navigate the challenges of working in a startup and continue learning and growing alongside my team.
It may seem like I accomplished all of this alone, but the truth is, there are people behind the scenes who have helped me tremendously, although not technologically. From providing me with the opportunity to do something meaningful to allowing me to work on my own schedule and timeline, there are people who have kept their trust in me and are always ready to lend a helping hand. This serves as a reminder to me to do good work and pay it forward. However, I sometimes wonder if I should have someone to report to (in the same way my developer team reports to me), so they can review my work and let me know if I’m doing something wrong. This feedback loop could help me develop and improve myself further. Ultimately, it’s the support and trust of the people around me that has enabled me to navigate the challenges of being a CTO in a startup environment.
If you’ve read through this entire post, I thank you for your patience and interest in my journey. If you feel you need more stories about me or what I do, please check out my website. And if you’d like to get in touch with me directly, feel free to send me an email. I’m always happy to connect with fellow tech enthusiasts, entrepreneurs, and anyone interested in learning more about the life of a startup CTO. Thank you for taking the time to read my story, and I hope it has provided you with some insights and inspiration on your own path in the world of technology and entrepreneurship.