Trilokanath Kakkar

Why this persona fits the audience

Leads a 9-person engineering team at a SaaS startup in Bengaluru. The product stores customer data in PostgreSQL and the team maintains tenant-level access controls, audit trails, and a few embedded account dashboards for customers and support.

• Age: 35
• Location: Bengaluru, India
• Occupation: Chief Technology Officer
• Income: INR 55L gross
• Education: BTech Computer Science
• Company size: 42 employees total (9-person engineering)
• Years in role: 2.5

“Security isn't a feature you turn on; it's the foundation you build the house upon, or the whole thing collapses when the wind blows.”

Trilokanath Kakkar, 35, is the Chief Technology Officer of a rapidly growing Bengaluru-based SaaS startup specializing in secure data analytics. Holding a BTech in Computer Science from IIT Delhi, he spent eight years in various engineering leadership roles at established fintech firms before joining his current venture-backed company two and a half years ago. Currently leading a lean team of nine engineers, Trilokanath is responsible for the entire technology stack, which relies heavily on PostgreSQL for multi-tenant data storage. His recent focus has been tightening tenant-level access controls and implementing robust audit trails to meet emerging regulatory requirements. Despite his executive title, Trilokanath remains deeply hands-on. He is known for personally auditing the most complex queries and designing the schema migrations that allow the platform to scale from thousands to millions of records without performance degradation. His approach to engineering is defined by a 'security-first' philosophy; he believes that scalability is meaningless if the data integrity cannot be guaranteed. This stance often puts him at odds with the sales team, who push for rapid feature delivery, forcing Trilokanath to constantly negotiate timelines based on technical feasibility and risk assessment. Financially, he earns a substantial INR 55L gross annually, yet he maintains a frugal lifestyle, viewing money as a tool for security and flexibility rather than status. He invests aggressively in index funds and real estate, avoiding speculative ventures. His professional reputation is built on reliability and technical depth; colleagues know that if Trilokanath says a system is ready, it will hold under load. However, this high standard creates internal friction, as junior engineers sometimes struggle to match his pace of scrutiny. Recently, he has begun exploring self-hosted options for their BI layer to reduce vendor lock-in, a decision that reflects his broader desire for total control over his data environment.

Background & daily life

A day in their life

Trilokanath wakes at 5:30 AM for a run and meditation, then prepares breakfast for his wife and son before heading to his home office. By 9:00 AM, he joins the daily standup, listening intently to blockers regarding the new tenant dashboard implementation. He spends the late morning reviewing pull requests, specifically checking for SQL injection vulnerabilities in the latest API updates. Lunch is usually a quick sandwich while reading a paper on partitioning strategies. In the afternoon, he leads a meeting with the CEO about the upcoming investor demo, focusing on how the system handles concurrent user loads. At 6:00 PM, he leaves early to pick up his son from daycare. Evenings are reserved for family time, perhaps a board game or helping with homework, followed by reading industry news or tinkering with a side project until 10:30 PM. Sleep is non-negotiable.

Lifestyle

Trilokanath lives in a modern 3BHK apartment in Whitefield, a hub for tech professionals. His mornings are rigid: 5:30 AM wake-up, a 45-minute run along the lake edge, followed by meditation to clear his head before the workday. He drives his own sedan to avoid traffic unpredictability, though he often works from home on Tuesdays and Thursdays to manage toddler pick-ups. Financially, he is cautious; despite his income, he tracks every expense in a spreadsheet and prioritizes investing over luxury spending. Socially, he prefers small dinners with close friends or family over loud corporate networking events. He values quality time with his wife and son, ensuring weekends are device-free whenever possible.

Work life

His day is split between architectural planning, code reviews, and incident management. As the sole CTO of a 9-person engineering team, he wears multiple hats but focuses heavily on security compliance and database performance. He spends mornings reviewing CI/CD pipelines and discussing tenant isolation strategies with his lead backend engineer. Afternoons are often blocked for deep work on system design or debugging complex PostgreSQL locking issues. He frequently engages with investors on technical due diligence, explaining how their current stack scales to millions of rows. The pressure comes from maintaining high availability while keeping burnout low among the small team. He relies heavily on Slack, Jira, and internal GitHub repositories, rarely delegating critical security decisions.

Relationships

He is married to Priya, a pediatrician, who grounds him emotionally and manages the household logistics. Their toddler, Aryan, is his primary motivation for stability. He has a tight-knit circle of four college friends from IIT Delhi, mostly working in senior tech roles across the US and Europe, whom he calls weekly for deep technical debates. Professionally, he looks up to a former mentor now at a FAANG company for advice on scaling, but remains skeptical of external consultants unless they bring proven, niche expertise.

How they decide

Highly research-heavy and iterative. Trilokanath does not make impulsive decisions. He typically runs small-scale proofs of concept (POCs) before committing to any major tool or architectural shift. He values peer validation and technical documentation over marketing claims. If a solution lacks transparency in its code or security model, he will walk away regardless of convenience. He prefers gradual adoption phases to mitigate risk, often testing tools on non-critical environments first.

How they sound

Trilokanath speaks in a calm, measured baritone with precise vocabulary. He avoids hyperbole, preferring 'likely' over 'definitely' and 'potential' over 'guaranteed'. He uses technical jargon freely but explains it clearly when necessary. He tends to ask clarifying questions rather than making immediate assertions. There is a slight formal cadence to his speech, reflecting his academic background, but he is comfortable with casual slang when joking with peers. He never says 'I think' without backing it up with data or logic.