Hari Gill

Why this persona fits the audience

Ships side-project SaaS apps after work and keeps them all public, with one-page sites, docs, and launch posts. He updates links manually in a notes file and usually prefers free utilities, open-source snippets, or quick custom code over paid subscriptions.

• Age: 29
• Location: Bengaluru, India
• Occupation: Software engineer and side-project founder
• Income: ₹18L-₹30L
• Education: Bachelor's degree

“Every line of code I write, whether for work or my own projects, has to serve a purpose. If it doesn't, it's just noise.”

Hari Gill is a 29-year-old software engineer based in Bengaluru, India, who embodies the spirit of the solo indie hacker. He navigates the demanding world of corporate software development by day, contributing to a large e-commerce platform, but his true passion lies in building and shipping his own small-scale SaaS applications after hours. His income, ranging between ₹18L and ₹30L annually, provides a comfortable living but fuels his deep-seated commitment to frugality. Hari views every rupee spent as a resource that could be better allocated, whether to personal savings, future investments, or reinvested into his own ventures – though he rarely opts for the latter when free alternatives exist. His technical journey began with a Bachelor's degree in Computer Science, and he has since honed his skills in backend development, cloud infrastructure, and database management. Hari's approach to building is characterized by a relentless pursuit of technical control and steady, incremental progress. He meticulously crafts one-page websites for each of his side projects, complete with documentation and launch announcements, often hosted on low-cost or free tiers. A defining aspect of his workflow is his aversion to paid software subscriptions; he actively seeks out open-source libraries, custom-coded scripts, or free utilities to manage tasks, including the critical need to link his various applications together. He maintains a personal notes file where he manually updates these links, a testament to his preference for direct control over automated, potentially costly, solutions. This meticulous, self-reliant approach extends to his decision-making, where he prioritizes deep research and personal validation over convenience or brand recognition. Hari's recent focus has been on optimizing the cross-promotion between his suite of small tools, aiming to turn visitors of one app into users of another without incurring any additional service fees. He recently spent two evenings writing a small Python script to automate the generation of the badge code he embeds on each app, rather than exploring a paid service that offered similar functionality.

Background & daily life

A day in their life

Hari's typical weekday begins at 6:00 AM with a strong cup of filter coffee. He spends the next two hours coding on one of his side projects, perhaps refining the landing page for a new utility or adding a small feature to an existing app. By 8:00 AM, he transitions to his full-time software engineering job, attending daily stand-ups and diving into team tasks. Lunch is a quick, packed meal eaten at his desk while scanning Hacker News. The afternoon is a blur of coding, code reviews, and meetings. After logging off around 6:00 PM, he might spend an hour on household chores or a brief walk before returning to his personal projects until 10:00 PM. He winds down by reading a tech article or watching a short tutorial before sleeping around 11:00 PM, ready to repeat the cycle.

Lifestyle

Hari lives in a compact, rented apartment in a bustling Bengaluru neighborhood, sharing the space with two other software engineers. His routine is highly structured; he rises before dawn to dedicate a few hours to his personal projects before his day job. Meals are often simple and home-prepared to save money, with occasional street food for variety. He views leisure time as an opportunity for learning or building, often spending evenings tinkering with code or reading technical articles. Financial discipline is paramount; he meticulously tracks expenses and prioritizes saving for future investments rather than immediate gratification. Socially, he prefers small, focused gatherings with like-minded peers over large events.

Work life

Hari's professional life as a software engineer involves developing and maintaining backend systems for a growing e-commerce platform. His days are filled with coding, debugging, attending stand-ups, and collaborating with a team of about fifteen engineers. The pressure is on to deliver features on time and ensure system stability, often leading to late nights or weekend work during critical deployment phases. He navigates internal company politics with a degree of detachment, focusing primarily on the technical challenges. His primary tools include Java, Spring Boot, Docker, Kubernetes, and various AWS services. He values clear documentation and efficient code reviews, though sometimes finds the pace of corporate development stifling compared to his personal projects.

Relationships

Hari maintains close ties with a small circle of college friends who are also in tech, often exchanging technical advice and project ideas. His family, while supportive, doesn't fully grasp the nuances of his entrepreneurial aspirations, viewing his side projects as hobbies. He has a few online mentors he follows and occasionally interacts with on developer forums, valuing their experience and insights.

How they decide

Hari is a highly analytical and research-driven decision-maker, especially concerning tools and services. He will exhaust free options, read documentation thoroughly, and compare features meticulously before even considering a paid solution. He often prototypes solutions himself using open-source components or custom scripts to validate their effectiveness before committing resources. Peer recommendations from trusted developers carry weight, but only after he has conducted his own due diligence.

How they sound

Speaks with a measured, slightly formal cadence, often using precise technical terms. He tends to be direct and avoids hyperbole or overly casual slang. His tone is generally calm and thoughtful, even when discussing challenges. He might pause to formulate his thoughts, ensuring accuracy. He's unlikely to use buzzwords unless they are directly relevant to a technical concept he's explaining. He often uses phrases like 'Essentially,' 'The core issue is,' or 'From a technical standpoint.'