Aaditya Saini

Why this persona fits the audience

Applies to master's programs and internships in English and drafts statements, emails, and short answers with help from free tools and peer feedback. He keeps a document of corrections from previous applications and practices phrases he tends to repeat.

• Age: 22
• Location: Bengaluru, India
• Occupation: Final-year engineering student
• Income: ₹4-7 lakh/year
• Education: Bachelor's degree in progress

“I don't just want to write code that works; I need to write stories about my work that convince people I belong in a room full of experts.”

Aaditya Saini is a twenty-two-year-old final-year Bachelor of Engineering student based in Bengaluru, currently navigating the high-stakes transition from academic theory to professional reality. Hailing from a middle-class family in Pune, he carries the weight of their educational investments, viewing his current trajectory not just as a personal milestone but as a collective family achievement. His life is defined by a relentless pursuit of 'mobility'—specifically, the physical and professional relocation required to access world-class research environments in the West. Academically, he excels in logic and coding but faces a persistent friction point: the nuance of advanced English composition. Despite scoring well on standardized tests, he knows that his Personal Statements and Statement of Purpose drafts often feel clunky or overly literal compared to native speakers. To mitigate this, Aaditya has developed a highly disciplined, almost obsessive routine. He maintains a digital 'Error Log' in Excel, meticulously cataloging every correction he receives from free tools like Grammarly (free version) and peer reviewers. He treats these errors as bugs in a system that must be patched systematically. He spends his evenings reverse-engineering successful essays from Reddit threads and YouTube analyses, trying to internalize the rhythm of persuasive academic writing. His income, derived partly from a small stipend and freelance tutoring, is strictly allocated; he cannot afford premium subscription services without rigorous justification. Consequently, he is a power user of free tiers, constantly searching for loopholes or alternative open-source tools that might offer the same depth of explanation. Recently, he decided to pause applying to mid-tier universities to focus entirely on securing a spot at a Tier-1 institution, a gamble that has increased his daily stress levels. He is currently in the thick of drafting three different versions of his cover letter for a summer internship, tweaking one phrase at a time, driven by the fear that a single awkward sentence could derail his international ambitions.

Background & daily life

A day in their life

Aaditya wakes at 6:30 AM, skipping breakfast to start a 45-minute run while listening to a podcast on technical interviews. By 8:30 AM, he is at his university lab, collaborating with his thesis team on sensor calibration until lunch. Post-lunch, he retreats to a quiet corner of the library to focus on his Master's application essay. This involves writing a paragraph, running it through a free grammar checker, analyzing the red flags, and then manually updating his 'Mistake Tracker' spreadsheet. He spends an hour practicing specific sentence structures from his notes. At 6:00 PM, he heads home, grabs a quick meal, and codes a small Python script for fun to unwind. Evenings are for socializing via WhatsApp with his friend group or reading sci-fi. He sleeps by 11:30 PM, exhausted but satisfied with his day's productivity.

Lifestyle

Aaditya lives in a cramped but functional shared flat in Koramangala, Bengaluru, where the hum of construction and traffic is a constant backdrop. His days are a rigid balance between final-year project deadlines and the silent grind of application prep. He prioritizes health through evening runs around his neighborhood park, using it as mental decompression rather than just exercise. Financially, he is tight; every rupee saved goes toward application fees or potential visa costs, making him wary of subscriptions unless the value is undeniable. Socially, he is not a partygoer; his weekends are often spent refining essays or coding side projects, though he maintains close bonds with a small circle of friends who share his drive for mobility out of India.

Work life

His 'work' is currently dominated by the dual pressure of his undergraduate capstone project and the parallel universe of graduate school applications. As a final-year engineering student, his days are split between lab time with his thesis group and hours hunched over his laptop drafting personal statements. He relies heavily on Google Docs for collaboration, using the 'Suggesting' mode to get peer feedback on his writing. The pressure is internalized; he feels the weight of needing to prove his competence beyond his grades. He spends his evenings cross-referencing his draft against online grammar checkers, manually logging errors in a dedicated spreadsheet to track his recurring weaknesses, a process that consumes more time than he initially anticipated.

Relationships

Aaditya is deeply connected to his family in Pune, who view his education as their primary investment. They call weekly, offering emotional support but little technical advice. In Bengaluru, he has a 'study buddy' network of four other engineering seniors; they exchange drafts and critique each other's tone, creating a low-stakes feedback loop. He respects his professors but finds them too busy for detailed writing mentorship. His closest confidants are older cousins working in tech abroad, whose experiences shape his expectations of life outside India.

How they decide

Aaditya is a methodical researcher who hates making impulsive choices, especially with money. He approaches decisions like a codebase: gathering requirements, testing solutions via free trials or community forums, and only committing after verifying efficacy. He trusts peer consensus and data-driven results over marketing hype. If a tool doesn't offer a clear, demonstrable improvement over existing free methods, he sees no reason to pay. He values transparency and dislikes hidden costs, preferring to understand exactly how a solution works before integrating it into his workflow.

How they sound

His speech is articulate and precise, reflecting his careful editing habits, but he occasionally slips into technical jargon when discussing code. He speaks with a moderate Indian accent, slightly formal in professional settings but relaxed among peers. He avoids hyperbole and superlatives, preferring measured, factual statements. When explaining complex ideas, he uses analogies. He rarely complains openly about problems; instead, he frames challenges as 'optimization tasks.' He pauses frequently to choose the right word, ensuring clarity over speed.