One of my core values as a leader is to be constantly evolving and learning. Years ago when I was hired at Google, I had been a stay at home dad for 3 years, completely out of the workforce. To catch myself up, I did as much google training available, and every free online tutorial and class I could find. I reminded myself it was possible to learn new things, and I dove in head first. There is so much you can access these days to improve yourself and your skills. After a few years at Google, I started educating myself on the business side of things so I could step into a leadership role. Now as the CTO of a quickly growing company, I am still doing that. I try to follow other leaders in my field and learn from them, I read articles, I watch interviews and tutorials- there's never a point I'll reach where I can't keep learning and improving. As far as my personal style as a leader? There's nothing I ask of my team that I won't do myself. I lead by example, not by force, and I try to support them however I can when they are working on improving themselves and their skills. I think it helps my team have the courage to try new things, and take new approaches to their work without fear of repercussion or lack of support. People that feel safe to try and fail will keep trying, and eventually, they will win.
As a CTO, my leadership style has evolved from a more hands-on, directive approach to one centred on empowerment and servant leadership. Initially, I focused on deep technical oversight, but I quickly learned that true innovation flourishes when teams have autonomy. My current style prioritises providing clear vision and guardrails, then trusting my engineers to find the best solutions. One leadership principle I find particularly important is "radical candour" coupled with "psychological safety." This means fostering an environment where team members feel comfortable challenging ideas, admitting mistakes, and proposing unconventional solutions, knowing they will receive honest, constructive feedback without fear of retribution. This approach has cultivated a culture of continuous learning, rapid problem-solving, and increased ownership within my IT teams, leading to more robust and innovative technical outcomes.
My leadership style as a CTO has evolved from being deeply hands-on and solution-focused to becoming context-driven and trust-oriented. Early on, I wanted to be involved in everything every architecture decision, every framework choice, every test plan. It came from a place of passion, but if I'm honest, also from a fear of things going off-track. Over time, especially as the team grew and the stakes got bigger, I realized that hovering over the codebase doesn't scale but trust does. Now, I focus more on creating clarity: setting strong technical principles, aligning product priorities, and empowering leads to own their zones fully. I still step in when architecture decisions affect long-term maintainability, but mostly I act as a systems enabler, not a fixer. One leadership principle I hold sacred is: "Be transparent about the 'why,' and flexible about the 'how.'" If people understand the mission and trust that you respect their process, they'll deliver exceptional results and grow in the process. That's when leadership becomes less about control, and more about momentum.
My leadership style as a technology leader has evolved into a results-driven, empowering, and collaborative approach. Early in my career, I focused heavily on technical excellence—getting deep into the details of system design, performance tuning, and architectural trade-offs. While this was valuable, I realized over time that true leadership comes from amplifying the impact of the team rather than being the strongest individual contributor. Today, my focus is on enabling teams to solve complex problems autonomously while providing clear direction, aligning priorities with business goals, and creating an environment where engineers feel ownership and pride in their work. One leadership principle I consider essential is clarity of vision and purpose. Whether I'm leading a team building storage infrastructure or optimizing large-scale systems, I ensure everyone understands not just what we are doing but why it matters. When engineers see how their work directly impacts customers or business outcomes, they become more motivated and creative. I also encourage open communication and frequent feedback loops, so that we can adapt quickly when priorities shift or new challenges arise. Over time, I've also embraced a "fast but thoughtful" mindset—moving quickly to deliver impact while minimizing missteps through short iterations, experimentation, and alignment across stakeholders. I see leadership as removing friction for my teams, giving them the tools, context, and autonomy they need to succeed.
When I recognized that my leadership style was bottlenecking my teams rather than empowering them, everything changed. In Pagoralia's early stages, I was the archetypal hands-on founder: overseeing product, establishing partnerships, even debugging product code at 2 AM. However, as we expanded into our fintech, aviation, and mobility ventures, I had to relinquish control and evolve into what I now describe as "strategic enabler." My leadership evolved from directing execution to designing systems and culture that allow others to move faster, fail safer, and solve more smartly. A principle I abide by today: Autonomy with accountability. We are now a company in which we provide autonomy to our people to propose, experiment, and implement, but also with a defined outcome that is shared. This has permitted us to seamlessly scale complex infrastructure for recurring payments without needing to micromanage. One moment that solidified this was watching a junior team member lead a product launch—from end-to-end—because we had set the expectation of ownership from day one. It was at that moment I knew the system worked better than any mandate I could have issued.
My leadership approach as a CTO has changed from being very hands-on and technical to being more collaborative and empowering. I first concentrated on finding solutions on my own. Still, as time went on, I realised how important it is to create solid teams, assign tasks efficiently, and promote an innovative and trustworthy culture. I now place a high value on open communication, lifelong learning, and coordinating technology with organisational objectives. Leading by example is a leadership philosophy that I think is very essential. Whether that means upholding integrity, being inquisitive, or accepting change, I believe a leader's actions set the tone for the team as a whole.