Chandrabhan Jha

Why this persona fits the audience

Supports a 6-person product team by drafting release notes, converting snippets between formats, and using browser tools for quick code and text cleanup. He works mostly in VS Code, GitHub, and spreadsheets, and keeps everything lightweight because the team is still small.

• Age: 27
• Location: Bengaluru, India
• Occupation: Software engineer
• Income: ₹18L
• Education: B.Tech in computer science
• Company size: Startup with 20 employees
• Years in role: 2

“The best documentation is the one that's not necessary because the code is so obvious. But since we're humans, I guess we'll keep deleting empty JIRA tickets forever.”

Chandrabhan Jha graduated from IIT Bhubaneswar with a B.Tech in Computer Science in 2021, immediately joining a buzzy fintech startup as their fourth engineer. At 27, he's exactly where he expected to be career-wise but feels like he should be further along ethically. His current role is a mix of code maintenance and 'whatever needs doing' work, which he secretly enjoys but finds underappreciated. The team's ad-hoc tooling drives him up the wall, but he's been quietly building a private repo of scripts to automate their worst pain points. Recently, he replaced their patchwork API documentation system with a GitHub wiki that syncs to their developer portal. The team barely noticed, but it cut three hours of weekly toil. He's particularly proud of a Vim macro that killed over 200 duplicate lines in a single command (he screenshotted it for his personal 'wins' spreadsheet). Chandrabhan's biggest constraint isn't technical skill but time - between work, side projects, and his 10:30 PM journaling habit, sleep is the first thing sacrificed. He knows his current salary won't cut it long-term in Bengaluru, but the startup's equity makes him hold on. His parents pressure him to 'just do the job' and marry, but he's focused on building something that matters. Recently, he's been spending evenings learning Stable Diffusion to create concept art for his side projects, which he views as more valuable than his day job. He quietly fears he'll be stuck in 'support roles' forever, but the idea of leaving for another company terrifies him. His own tools might be the escape hatch he needs.

Background & daily life

A day in their life

Chandrabhan's day starts with checking his personal GitHub notifications and responding to pestering company Slack messages from the US team. After black coffee and a bowl of poha, he commutes listening to the latest Indie Hacker podcast. At the office, his first task is updating the release notes spreadsheet that no one reads but keeps getting last-minute edits for. He spends 90 minutes cleaning up a messy pull request before lunch (dosa from the canteen). Post-lunch, he attends a standalone meeting about a feature that already shipped. The rest of the day is spent converting a product manager's messy Google Doc into a clean md file and helping the intern debug Docker issues. He rejects two team-building ping pong invitations before finally leaving at 8 PM, stopping at a chai stall to watch a random tech talk on his phone. At home, he secretly works on a side project until 11 PM, then writes in his journal about how his team's tooling is falling behind competitors.

Lifestyle

Chandrabhan lives in a compact but well-organized Koramangala apartment he found through a referral. His routine starts at 6:30 AM with black coffee and coding practice (Leetcode or a personal project) before work. He bikes to the office when it rains, otherwise takes the metro. His weekends are split between coding meetups, weekend hackathons (he avoids sleep for these), and long walks in Cubbon Park. Health-wise, he skips gyms but does push-ups while waiting for builds to compile. Financially prudent, he saves 30% of his salary but splurges on mechanical keyboards and noise-cancelling headphones. Socially, he's part of a WhatsApp group of ex-collegemates that debates everything from tech to politics, though he mostly lurks. He secretly writes terrible poetry that no one will ever read.

Work life

Chandrabhan works at a Series A fintech startup building developer tools. His days are a mix of maintaining documentation, cleaning up build scripts, and automating Tedium for the product team. He's the go-to person for 'Can we make this spreadsheet generate markdown?' type requests. Currently wrapping up a project to replace a fragile Python script with a more maintainable workflow. His team uses GitHub Projects but keeps slipping back into spreadsheets. He's implicitly responsible for the team's VS Code extensions and constantly nudges them toward better Git workflows. The biggest friction is explaining why good documentation matters to engineers who just want to ship. He tries to mentor a junior intern once a week, which helps him feel less like a glorified note-taker.

Relationships

Chandrabhan is close with his family in Bhubaneswar but visits only twice a year. His parents don't understand what he does ('Isn't all programming the same?') but are proud he's in a 'software job'. His older sister, a public health researcher, is his only tech-agnostic friend who actually listens to his grievances. At work, he's friendly with the engineering team but especially close with the design lead who understands his need for visual consistency. He's in a loose-knit group of startup engineers who meet once a month at a café to complain aboutfounder nonsense. Most of his learning comes from this peer group rather than his manager, who's swamped with board presentations.

How they decide

Research-heavy but not paranoid. Will try new tools but only after reading multiple forum posts and blogs. Prefers to test things in private before recommending to the team. Trusts his gut for technical decisions but seeks validation from more senior engineers. Overthinks tooling choices but not team politics. Hates being sold to but respects demonstration of real problems being solved.

How they sound

Speaks in measured, slightly formal English but slips into Hindi slang with friends. Uses precise technical terms but avoids buzzwords unless mocking them. Prefers short, direct sentences when explaining concepts. Avoids saying 'I don't know' but will say 'That's not my area' to redirect questions. Prone to saying 'That's not scalable' about messy workarounds. His laugh is quiet and self-conscious. When frustrated, speaks even more slowly and precisely.