© All rights reserved. Powered by Techronicler
A Techronicler interview with Amit Aghara, CTO, Fintech

Techronicler: Thank you for joining us, Amit! Well, everyone has an origin story! What was the first piece of technology you ever broke, built, or fell in love with?
Amit Aghara:
My first real exposure to technology came in high school in India, where we had the option of taking computer languages instead of a traditional language class. More than 30 years ago, I started with Logo and Pascal, which gave me my first taste of coding and building applications. Pascal, especially, sparked my interest in problem-solving and writing object-oriented programs, and it came naturally to me. That experience ultimately led me to switch my college major to computer science.
Techronicler: A lot of careers look like straight lines on LinkedIn. How was yours different? Was there a pivotal moment or ‘happy accident’ that actually steered you toward your current role or niche?
Amit Aghara:
My career may look like a straight line on LinkedIn, but it really evolved through a series of intentional choices and a few pivotal moments. Early on, my IBM career followed a traditional path with promotions, leadership opportunities, and a fast-track trajectory in software development. But after about nine years at IBM, things took a turn during a paternity leave when a recruiter reached out to me about joining a mobile app development startup. A lot of people thought leaving IBM was a risky decision, but I felt that being “just fine” at a large company wasn’t enough for me.
What really motivated me was wanting to understand how much of my success came from my own capabilities versus the strength of the IBM brand. I wanted to test myself in a startup environment where small teams had to compete against companies like IBM and SAP and simply “make it happen.” That decision led me first to Kony Solutions during its unicorn-growth phase, then to Kore.ai, and eventually to Fintech.
Techronicler: What is the one problem or project that is taking up 80% of your brain space this month?
Amit Aghara:
The project taking up most of my brain space this month is AI adoption at Fintech, both for internal productivity and future customer-facing applications. Right now, the focus is on using AI internally first, with heavy field testing before bringing solutions to customers. The bigger challenge is shifting focus from improving individual productivity to increasing organizational efficiency across the entire workforce, especially the product, engineering and infra teams.
To support that, Fintech is investing heavily in AI and building its own agentic platform, since existing enterprise offerings have not met the company’s needs. I also bring experience from a previous AI company, which has helped shape how we approach implementation and adoption.
Techronicler: Tell us about a time you had to make a deeply unpopular technical decision (e.g., killing a feature, swapping a tech stack) that turned out to be the right call. How did you handle the pushback?
Amit Aghara:
One of the most unpopular technical decisions I made was during the early days of an AI conversational platform company I previously worked at. At the time, there were three competing approaches emerging in the chatbot space: traditional machine learning models, language-based AI systems, and knowledge graph models focused on word relationships and semantic mapping. This was before the advent of today’s LLM-based conversational models.
Each engineering team strongly believed its approach was the best and wanted the company to fully commit to its technology. Instead of choosing a single winner, I pushed for a different strategy of combining all three models into a unified analysis platform.
The decision was unpopular because it increased complexity and required the teams to collaborate rather than compete. We built an analysis feature that routed every user query through all three models simultaneously, then compared and scored the outputs. This required six months of alignment work to establish common evaluation criteria, scoring techniques, and transparency into why one model’s response was ultimately selected.
I handled the pushback by reframing the conversation away from “which team wins” and toward “how do we deliver the best and most explainable outcome for customers.” I also made the evaluation process data-driven so decisions were based on measurable performance rather than opinions.
In the end, it proved to be the right call. The combined approach gave customers better accuracy, greater transparency, and the flexibility to evolve as AI technologies matured, instead of locking the company into a single approach too early.
Techronicler: What is the one book every leader in tech should read this year?
Amit Aghara:
One book tech leaders should read is “Give and Take” by Adam Grant. As you grow in technology leadership, success becomes about far more than technical skill alone. The book explores three common workplace personalities: givers, takers, and matchers. One of its most important lessons is that even the most talented engineer or product leader may struggle to advance if people do not want to collaborate with them.
The book argues that the leaders who create the greatest long-term impact are often the “givers” or people who are collaborative, supportive, and focused on helping others succeed without constantly expecting something in return. For tech leaders building teams and organizations, that mindset becomes just as important as technical expertise.
Techronicler: How do you evaluate ‘potential over polish’ during the hiring process to ensure a more equitable team?
Amit Aghara:
How I evaluate potential over polish really depends on the stage of the organization and team goals. In a high-growth startup environment, we sometimes had to prioritize polish over potential because of the pace and pressure we were operating under. We needed people who could contribute immediately without extensive mentoring or ramp-up time. If we hired below a certain bar, it could slow the entire team down, so decisions around performance and fit had to happen quickly. Those choices may seem harsh in hindsight, but they were driven by the realities of scaling rapidly under intense pressure.
In organizations focused on long-term sustainability, such as larger enterprises building for the next 10–15 years, I believe investing in potential is critical. Technical polish can fade or become outdated, but people with strong learning ability, adaptability, curiosity, and collaboration skills often grow into exceptional long-term contributors and leaders.
Building an equitable team means recognizing that not everyone has had the same opportunities to develop “polish.” Potential, when nurtured properly, creates stronger and more sustainable organizations in the long run.
Techronicler: How can existing data be made AI-ready?
Amit Aghara:
Making data AI-ready requires a structured approach. Organizations need clear data ownership, consistent definitions, and measurable quality standards for accuracy, completeness, and consistency. A practical approach is a 30/30/30-day framework: spend the first 30 days assessing data and identifying gaps, the next 30 standardizing and cleaning the data, and the final 30 aligning data pipelines to specific AI use cases.

Amit Aghara is a seasoned technology executive and innovation leader with more than 20 years of experience building and scaling enterprise software businesses across startups, private equity-backed organizations, and Fortune 100 companies. As CTO of Fintech, he drives technology strategy, product innovation, and platform transformation initiatives that accelerate growth and deliver measurable business impact.