Trilochan Gowda

Why this persona fits the audience

Software engineer in Bangalore who owns a physical collection of 150+ books across multiple editions; maintains a private wiki on Notion to track character lineages and plot holes but finds the current setup too technical for casual logging.

• Age: 34
• Location: Bangalore, India
• Occupation: Senior Software Engineer
• Income: ₹2,400,000 INR
• Education: B.Tech Computer Science
• Company size: Mid-sized product company (200-500 employees)
• Years in role: 6

“A library isn't just a room full of paper; it's a structured database of human imagination that I'm trying to query without breaking the index.”

Trilochan Gowda, 34, is a Senior Software Engineer residing in Bangalore, where he navigates the dual worlds of high-stakes fintech development and meticulous bibliophilia. With a B.Tech in Computer Science and six years of experience in his current role, he commands a salary of ₹2.4 million, reflecting both his technical expertise and the cost of living in South Bangalore. Unlike many peers who view reading as a passive escape, Trilochan treats his literary consumption as a systematic study. He owns a physical collection exceeding 150 books, spanning multiple editions of science fiction and fantasy, meticulously arranged in his home office. Driven by an innate need for order (Conscientiousness 0.9) and intellectual curiosity (Openness 0.8), Trilochan attempted to build a private wiki on Notion to map character lineages and identify plot inconsistencies across decades of reading. However, the friction of manually defining schemas, linking properties, and maintaining relational databases has become a bottleneck. He finds himself spending more time engineering the tracking system than engaging with the narratives themselves. This inefficiency conflicts with his core value of Efficiency, leading to a sense of underutilization in his hobby. Recently, he made the decision to pause his expansion of the physical collection until he resolves the data management issue, viewing the current workflow as a 'legacy system' requiring refactoring. While he is financially capable of purchasing premium tools, his skepticism toward SaaS products prevents him from blindly subscribing to anything that doesn't promise a tangible reduction in technical overhead. He remains a prosumer—someone who builds and maintains systems for their own use—seeking a solution that bridges the gap between his analytical mind and his love for storytelling without demanding a full-stack development effort.

Background & daily life

A day in their life

Trilochan wakes at 6:00 AM for a 5k run along the park near his home, using the time to mentally decompress. By 7:30 AM, he is showered and reviewing his day's priorities over a strong filter coffee. At work, he dives into code reviews and architecture planning, spending hours in deep focus blocks interrupted only by necessary stand-ups. Lunch is a quick affair, often eaten while scanning tech news or reading a chapter of his current book. Post-work, he avoids social media scrolling; instead, he returns to his physical books, perhaps digitizing a new acquisition into his Notion workspace, though this process often stalls due to the complexity of tagging characters correctly. Dinner is shared with his wife, followed by an hour of reading fiction purely for pleasure before bed, where he often reflects on how the day's work mirrored the logic of the story he just finished.

Lifestyle

Trilochan lives in a quiet, sunlit corner of Koramangala where his apartment doubles as a personal archive. His evenings are rarely spent on passive entertainment; instead, he dedicates time to cataloging his growing physical library, often rearranging shelves by color or publication era rather than author. He is health-conscious, maintaining a strict running routine three times a week to clear his mind after intense coding sprints. Financially, he is conservative yet willing to invest heavily in high-quality hardware or rare book acquisitions that offer long-term value. Socially, he prefers deep one-on-one conversations over large gatherings, often inviting close friends over specifically to discuss complex plot theories or architectural design patterns.

Work life

As a Senior Software Engineer, Trilochan spends his days architecting backend systems for a fast-paced fintech startup. His environment is dominated by terminal windows, Jira tickets, and code review meetings where precision is paramount. He thrives on solving logical puzzles but grows frustrated by vague requirements and chaotic project management. Recently, he led a migration from a legacy monolith to a microservices architecture, a decision that required weeks of rigorous testing. While his colleagues rely on Slack for quick comms, Trilochan prefers documented RFCs (Request for Comments) to ensure clarity. The pressure to deliver quarterly features is constant, forcing him to compartmentalize his work stress to protect his mental space for reading.

Relationships

He shares a stable, supportive marriage with his wife, Priya, who tolerates his book hoarding but occasionally jokes about the 'shelf real estate crisis.' Their closest friends are a mix of fellow engineers and a small group of literature enthusiasts from college; these interactions are infrequent but deeply substantive. He has no children yet, which affords him the time to dedicate to his collection. He is influenced primarily by senior mentors in his industry and online communities of 'prosumer' hobbyists who treat their interests with professional rigor.

How they decide

Trilochan employs a highly research-heavy, risk-averse decision style. Before adopting any new tool or making a significant purchase, he conducts extensive due diligence, often creating comparison spreadsheets to weigh features against long-term utility. He is skeptical of hype and relies on peer validation from trusted technical circles. Once he identifies a solution that meets his strict efficiency criteria, he commits fully, but the initial evaluation phase can be prolonged by his need to understand the underlying logic and data structure of the option.

How they sound

Trilochan speaks with a measured, precise cadence, favoring technical analogies when explaining non-technical concepts. His English is fluent and articulate, laced with occasional Kannada phrases or engineering jargon like 'latency,' 'schema,' or 'refactor.' He avoids hyperbole and emotional outbursts, preferring to state facts and observations logically. When discussing his hobbies, his tone shifts from clinical to quietly enthusiastic, though he still structures his thoughts with numbered points or distinct categories.