Darshan Dwivedi

Why this persona fits the audience

24-year-old man in Bengaluru in the final semester of an MTech, drafting his thesis and one workshop paper in LaTeX, using a free online editor for collaboration with two classmates, and maintaining references alongside code notes.

• Age: 24
• Location: Bengaluru, Karnataka, India
• Occupation: MTech student, computer science
• Income: ₹18,000/month internship stipend
• Education: BTech; MTech candidate
• Years in role: 1.5

“If the code compiles but the logic is flawed, you haven't solved anything; you've just built a faster wall.”

Darshan Dwivedi is a 24-year-old Computer Science MTech candidate based in Bengaluru, currently navigating the critical final stretch of his academic career. Born into a middle-class family in Pune, he developed an early affinity for mathematics and logic, which led him to pursue a BTech followed by this specialized Master's degree. Currently living in a modest shared apartment in Koramangala, Darshan survives on a modest internship stipend of ₹18,000 per month, forcing him to be extremely judicious with his finances. This financial reality has shaped his worldview: he believes deeply in efficiency and frugality, preferring to invest time in mastering free, open-source tools rather than paying for bloated commercial software. His primary focus right now is the completion of his thesis on reinforcement learning agents, a project that requires rigorous documentation and precise mathematical formulation. He is simultaneously preparing a workshop paper intended for submission next month. To manage these dual demands, he relies on a free, browser-based LaTeX editor to collaborate with two classmates, a choice born out of necessity rather than preference. This arrangement often leads to friction; version control issues and citation mismatches consume hours that could be spent on actual research. Despite these challenges, Darshan remains highly conscientious, meticulously organizing his code notes and bibliographic references, even if the tools he uses make the process laborious. Technically competent and self-reliant, Darshan spends his weekends contributing to open-source repositories and attending local tech meetups. He is not a trend-chaser but a pragmatist who values stability and depth. While his peers might chase internships at big tech giants for the brand name, Darshan is focused on building a portfolio that demonstrates genuine technical mastery. He is currently weighing the trade-offs between spending precious study time troubleshooting his current document editor versus seeking alternative solutions, all while managing the stress of impending deadlines and the pressure to secure a high-quality research position upon graduation.

Background & daily life

A day in their life

Darshan starts his day at 6:00 AM with a cup of strong filter coffee and thirty minutes of sitar music to center himself. By 7:00 AM, he is commuting to the university campus or setting up his dual-monitor workspace in the shared flat. His morning is dedicated to reading arXiv papers and refining the mathematical proofs for his thesis chapter. Around noon, he joins a brief stand-up call with his two collaborators to resolve merge conflicts in their shared LaTeX document. After lunch, he spends three hours debugging a reinforcement learning algorithm, running simulations in the background while taking notes on reference management. Late afternoon is reserved for administrative tasks: formatting citations, updating his CV, and replying to emails. He finishes work by 8:00 PM, then either goes for a quick jog or meets friends for a casual game of cricket. Evenings are for winding down, often involving more reading or exploring a new Linux utility, before sleeping around midnight.

Lifestyle

Darshan lives in a cramped but functional shared apartment in Koramangala with three other engineering students, splitting rent to keep costs down. His routine is rigid: he wakes at 6 AM, spends an hour listening to Hindustani classical raga before work, and cycles to the university campus or works remotely from a quiet corner of the flat. He eats simple, home-cooked meals or cheap street food like *vada pav* to save money, viewing frugality as a necessary discipline rather than a sacrifice. Socially, he balances intense study blocks with occasional weekend cricket matches at the local ground or small gatherings where he debates open-source licensing. He avoids debt, keeps a strict monthly budget, and prioritizes saving for a future master's program or specialized hardware.

Work life

His days are consumed by the finalization of his MTech thesis on reinforcement learning agents. He currently drafts the manuscript in a browser-based LaTeX editor shared with two peers, often fighting synchronization conflicts and version control headaches that slow down their collaboration. Alongside writing, he manages complex citation databases and maintains separate repositories for his experimental code, ensuring every result is reproducible. The pressure is high as he navigates the final semester, balancing advisor feedback loops with the need to submit a workshop paper by month-end. He spends hours debugging formatting issues in his document, wishing for a tool that could handle citations automatically without breaking his workflow.

Relationships

He shares a close bond with his parents in Pune, who fund his education but rely on him for financial updates. His closest friends are fellow MTech scholars in his cohort; they form a support network for sharing resources and debugging code. His thesis supervisor is a respected figure whom Darshan respects but finds intimidating due to high expectations. He interacts regularly with the broader open-source community via GitHub issues and local meetups, though these interactions remain professional and focused on technical exchange rather than personal bonding.

How they decide

Darshan adopts a research-heavy, cautious approach to any new tool or investment. He never buys immediately; instead, he reads reviews, checks GitHub stars, tests free tiers extensively, and consults his peer group. He values long-term utility over immediate convenience and will only commit if a solution demonstrably saves time or reduces error rates compared to his current manual processes. He is skeptical of marketing fluff and looks for concrete technical specifications.

How they sound

His speech is articulate and precise, often peppered with technical jargon like 'latency,' 'overfitting,' or 'syntax' when explaining concepts. He speaks with a calm, measured cadence, avoiding hyperbole. In conversation, he tends to ask clarifying questions rather than making broad assertions. He avoids complaining about costs openly, preferring to frame financial constraints as strategic choices. When discussing technology, he uses terms like 'scalable' and 'robust' frequently, reflecting his focus on engineering quality.