Chandak Khanna

Why this persona fits the audience

CTO of an Indian fintech scale-up (15 employees) who built their own internal dashboard using open-source Python scripts. Highly skeptical of 'black box' AI SaaS solutions due to data privacy concerns and prefers maintaining full code control.

• Age: 29
• Location: Bangalore, India
• Occupation: Chief Technology Officer
• Income: ₹3,500,000 - ₹5,000,000
• Education: B.Tech in Computer Science
• Company size: 15
• Years in role: 2

“If I can't see the source code and trace every byte of data flow, I don't trust the intelligence, no matter how pretty the dashboard looks.”

Chandak Khanna is a 29-year-old Chief Technology Officer based in Bangalore, India, who epitomizes the modern engineer's struggle between rapid innovation and rigid security requirements. Born into a family of educators, he developed an early fascination with how systems function, eventually earning a B.Tech in Computer Science from a prestigious institute in Chennai. Two years ago, he joined a fledgling fintech scale-up as its first technical hire, quickly rising to CTO as the company grew from five to fifteen employees. Unlike many peers who rushed to adopt commercial AI tools, Chandak championed the development of a proprietary, open-source Python-based dashboard that aggregates transactional data, giving the leadership team real-time visibility without exposing sensitive customer PII to third-party servers. His professional identity is defined by a fierce commitment to technical sovereignty. He believes that in the fintech sector, the ability to audit every line of code is non-negotiable. This philosophy often puts him at odds with investors pushing for faster, cheaper implementations via black-box SaaS products. Recently, he made the strategic decision to reject a popular AI automation platform after discovering its opaque data handling policies, opting instead to spend three weeks training a custom model on their internal infrastructure. This move delayed a product launch by a month but secured the company against potential regulatory breaches. Chandak's income, ranging between ₹3.5 million and ₹5 million annually, reflects his seniority and the high demand for his specific skill set, though he remains frugal, viewing his salary as a resource to fund his hobbies and investments rather than a status symbol. Outside of work, he is a dedicated hiker, finding solace in the Himalayas where the silence allows for deep reflection away from the digital noise. A competitive chess player, he approaches business problems with the same strategic foresight he applies to the board. His life is a carefully curated balance of rigorous technical discipline, intellectual curiosity, and a quiet, grounded existence that prioritizes long-term resilience over short-term gains.

Background & daily life

A day in their life

Chandak wakes at 5:30 AM, runs three kilometers through the greenery of Cubbon Park, and returns for a quick shower and breakfast. By 7:45 AM, he is commuting to his office in Koramangala, listening to a podcast on cryptography or debugging a script on his phone. At work, he attends a stand-up at 10:00 AM, focusing on blockers rather than status updates. From 11:00 AM to 2:00 PM, he codes directly into the core ledger system, refactoring a legacy module to improve query performance. Lunch is a packed meal eaten at his desk while reviewing a new open-source library for potential integration. The afternoon is reserved for code reviews, mentoring a junior developer on database normalization, and meeting with the CEO to discuss Q3 roadmap constraints. After work, he might attend a local tech meetup or head home to hike, chess, or read, ensuring he disconnects completely from screens by 9:00 PM.

Lifestyle

Chandak lives in a modest but tech-savvy 2BHK in Koramangala, Bangalore, filled with mechanical keyboards, server racks hidden behind bookshelves, and plants he meticulously tends to as a form of digital detox. His mornings begin at 5:30 AM with a run through the Cubbon Park trails, followed by a strong filter coffee and chess puzzles before work. He is financially disciplined, maxing out his EPF and investing heavily in index funds rather than speculative crypto, viewing wealth as a tool for security rather than status. Socially, he prefers small dinner gatherings with close friends or hiking weekends over crowded pubs, often engaging in deep debates about ethics in technology rather than superficial networking.

Work life

As CTO of a 15-person fintech scale-up, Chandak's day is split between high-level architecture and hands-on coding. He rejects external SaaS dependencies for core logic, preferring to build custom Python dashboards that give him absolute visibility into data flows. The pressure is constant; regulatory compliance in fintech leaves no room for error, so he spends hours auditing logs and reviewing pull requests from junior devs. He works in a quiet corner of the office, surrounded by dual monitors displaying terminal windows and documentation, often skipping lunch to debug a race condition. His team respects his technical depth but finds his skepticism toward new tools a hurdle during rapid scaling phases.

Relationships

Chandak is married to Priya, a graphic designer who grounds his abstract thinking with practical aesthetics; they share a quiet life focused on personal growth. His closest confidants are two former college classmates who now run infrastructure startups, providing a safe space for technical venting. He is not deeply embedded in the broader Bangalore social scene, preferring the intimacy of his hiking club and chess community. His parents, retired school teachers in Pune, influence his conservative financial views and love for education, often calling weekly to discuss his career trajectory rather than asking for money.

How they decide

Chandak employs a highly research-heavy, evidence-based decision-making process. He rarely trusts marketing claims or case studies alone, preferring to inspect source code, read GitHub commit histories, and simulate environments locally before committing to any solution. He is cautious and deliberate, often delaying decisions until he has exhausted all logical angles. Peer influence matters only if those peers have demonstrated technical competence and integrity. He values long-term stability over short-term convenience, willing to endure friction today to avoid dependency risks tomorrow.

How they sound

His speech is precise, articulate, and devoid of corporate fluff. He speaks in clear, declarative sentences, often pausing to formulate exact terms. He avoids vague buzzwords like 'disruptive' or 'synergy,' preferring concrete descriptors like 'latency,' 'throughput,' or 'audit trail.' There is a slight intensity in his tone when discussing security flaws, and he often uses analogies related to mechanical systems or chess strategy to explain complex concepts. He does not use slang unless among close friends, and even then, it is minimal.