Aanandaswarup Chaturvedi

Why this persona fits the audience

He is a computer engineering student who builds weekend apps and small utilities for the Play Store, mostly on free tools like ChatGPT and Gemini with occasional Copilot trials, and he keeps tasks in Notion plus a spreadsheet because he has not set up a paid developer stack yet.

• Age: 23
• Location: Hyderabad, India
• Occupation: Student and side-project builder
• Income: ₹6 lakh/year equivalent from stipend and small freelance revenue
• Education: B.Tech Computer Engineering (final year)
• Company size: N/A (Student/Freelancer)
• Years in role: 0 years full-time; 3 years as a hobbyist coder

“The best code isn't the most complex one; it's the one that actually solves a problem without breaking my bank account.”

Aanandaswarup Chaturvedi is a 23-year-old B.Tech Computer Engineering student based in Hyderabad, standing at the intersection of academic rigor and the chaotic, fast-paced world of independent software development. As a final-year student, he navigates the dual pressures of maintaining high academic grades and building a portfolio that can compete with graduates from top-tier institutes. Unlike many of his peers who rely solely on internships, Aananda has carved out a niche as a 'side-project builder,' dedicating his weekends and evenings to developing small, utility-focused Android applications for the Google Play Store. His approach is defined by extreme frugality; he operates almost entirely on free tiers of AI coding assistants like ChatGPT and Gemini, only occasionally dipping into GitHub Copilot when his university grants temporary access. This constraint has forced him to become an adept integrator of disparate tools, keeping his project management fragmented across Notion pages and manual Excel spreadsheets—a makeshift stack that reflects his lack of capital for a unified, paid developer environment. Recently, he has been wrestling with the inefficiency of context-switching between multiple chat windows to generate code, a daily friction that limits his productivity. Despite these hurdles, his openness to learning and desire to create useful tools drive him forward. He views his current situation not as a deficit, but as a training ground for resourcefulness, aiming to launch a successful app before graduation that could potentially fund his transition into a full-time engineering role.

Background & daily life

A day in their life

Aananda wakes up at 7:30 AM after a restless night spent debugging a memory leak in his latest Android utility. After a quick breakfast of idli and sambar, he rushes to the university campus, spending his morning classes half-listening while sketching database schemas on his phone. By noon, he grabs a cheap lunch from the canteen and heads to the library, where he dedicates four hours to his weekend project. He cycles through prompts on ChatGPT and Gemini, manually copying code snippets into his local IDE. Lunch is interrupted by a notification about a new feature in a competitor's tool, which he quickly researches. The evening is reserved for gym time to clear his head, followed by a late-night session reviewing his Notion board and updating his spreadsheet with task progress. He goes to bed around midnight, exhausted but satisfied with the incremental progress made.

Lifestyle

Aananda lives in a cramped but vibrant shared apartment in Hitech City, Hyderabad, where the hum of three other engineering students' laptops is constant background noise. His routine is dictated by university deadlines and the unpredictable rhythm of app store submissions. He prioritizes frugality, often skipping coffee runs to afford better internet data or a new Android emulator license. His social life revolves around campus hackathons and late-night coding marathons with friends, where energy drinks replace dinner. Despite his busy schedule, he maintains a steady exercise routine at a local gym to counteract the sedentary nature of his work, viewing physical health as essential for mental clarity during crunch weeks.

Work life

His 'job' is a dual existence: attending lectures that sometimes feel disconnected from industry reality, and building weekend projects that define his actual professional identity. He spends his days navigating the friction between academic theory and the rapid evolution of AI coding assistants. His workspace is a chaotic desk cluttered with notebooks, a secondary monitor, and a laptop running multiple browser tabs. He relies heavily on free tiers of AI models, constantly switching between ChatGPT, Gemini, and occasional GitHub Copilot trials when his university provides access. The pressure comes not from a boss, but from the fear of obsolescence and the need to publish something tangible before graduation to secure a decent job offer.

Relationships

Aananda is deeply embedded in his college's engineering cohort, often acting as the go-to person for debugging code or organizing hackathon logistics. He maintains close ties with two childhood friends who are also in tech, meeting weekly for casual gaming or deep technical discussions. His parents, though supportive, view his side projects as a hobby rather than a career path, creating a subtle pressure to prioritize traditional placement exams. He finds more genuine intellectual stimulation in online communities and Discord servers where peers share tips on free tools, influencing his adoption decisions more than formal advertising.

How they decide

He approaches decisions with a mix of cautious skepticism and opportunistic experimentation. Before adopting any new tool, he spends hours reading reviews, watching demo videos, and testing free tiers to ensure there are no hidden costs or privacy risks. He is highly influenced by peer validation within his developer circles; if a tool is praised by a trusted senior developer or a popular YouTuber, he is quick to try it, but he remains wary of 'bloatware' or subscriptions that don't immediately solve a specific pain point. He prefers flexible, pay-as-you-go models over long-term commitments until he is certain of the tool's value.

How they sound

He speaks in a blend of formal English and casual Hinglish, often using tech slang like 'refactor,' 'stack overflow,' and 'context window' naturally. His cadence is fast and energetic when discussing new possibilities but slows down when explaining technical constraints. He avoids corporate jargon and overly flowery language, preferring direct, actionable statements. He rarely admits uncertainty openly, instead framing unknowns as 'areas for investigation.' His tone is generally optimistic but grounded in the harsh realities of limited resources.