Why this persona fits the audience
Works on a 4-person applied AI team in Bengaluru at a logistics SaaS company. She handles prompt routing and safety checks for an operations copilot, while usage, incidents, and model comparisons are tracked in spreadsheets and Slack threads.
- Age: 29
- Location: Bengaluru, India
- Occupation: Applied AI Engineer
- Income: ₹42,00,000
- Education: M.Tech. in Data Science
- Company size: 25-50 employees
- Years in role: 3
“'I don’t mind fixing other people’s broken code. What I hate is when they call that ‘maintenance’ instead of ‘technical debt repayment.’'”
Subhashini Varrier grew up in a Kochi home where her parents’ debates about scientific progress became her first introduction to both AI’s potential and its ethical dilemmas. She earned her MTech in Data Science from IISc Bangalore while working part-time at a healthcare analytics startup—where she developed her signature combination of technical rigor and user-advocacy. At 26, she joined her current logistics SaaS company as employee #15, originally hired to build their first prototype AI agent. Three years later, she’s effectively the team’s defacto architect, though the title ‘Senior AI Engineer’ still feels foreign to her. Her apartment walls are crowded with whiteboards (one is a git branching diagram she drew to explain version control to her mother). Recent highlights include: convincing the CTO to implement basic model versioning after six months of arguments; discovering that 32% of their prompt failures were actually mislabeled training data (she fixed it with a weekend script); and teaching herself enough guitar to play Ravi Shankar’s ‘Simple Gifts’ arrangement. What consumes most of her mental energy now isn’t the coding, but the growing mismatch between their startup’s ad-hoc governance and their production-scale challenges. She keeps a physical notebook labeled ‘Governance Ideas’ that’s now 121 pages deep, though she hasn’t shared most of its contents with anyone. On weekends, you’ll find her at The Humming Tree for experimental music nights or in her tiny kitchen attempting to recreate her mother’s beef ulundu, always with a new classical vinyl spinning quietly. Her iPhone’s home screen has exactly four apps: Slack, VS Code, a guitar tuner, and a habit tracker that verifies she’s reading exactly one academic paper per week.
Background & daily life
A day in their life
6:30 AM runs along Cubbon Park, denying all incoming calls until after meditation. 8:30 AM breakfast with curated Spotify playlist (this month’s theme: avant-garde Indian fusion). First meeting at 9:30 AM—daily standup where she’s already identified three prompt consistency issues from overnight logs. Spends rest of morning rebuilding the routing logic for a high-failure prompt path, writing detailed runbooks in Markdown. Lunchtime debate with a coworker about whether fine-tuning or RAG is better for their use case (she secretly believes neither is the right answer). Afternoon wasted in an emergency call with a client whose production agent is hallucinating addresses. Returns to her apartment at 7:30 PM, orders dal makhani, and spends two hours debugging her personal LLM eval script while listening to the latest Ravishankar Shankar reissue.
Lifestyle
Subhashini rents a minimalist Indiranagar apartment where she’s converted a side table into a standing desk. Wakes up at 6:30 AM to run 5 km, returns to meditate for 10 minutes before work. Eats South Indian breakfasts at home (she makes her own coconut chutney) but orders North Indian lunches via Swiggy. Spends weekends at Namma Metro concerts or debugging her Arduino projects. Tracks expenses religiously in YNAB but splurges on concert tickets and decade-old vinyl records. Social circle is small but tight—mostly ex-colleagues and a book club that meets every month. Prefers texts over calls and keeps Slack muted after 9 PM.
Work life
Leads prompt engineering for an AI operations copilot at a logistics SaaS startup. Spends mornings reviewing safety check failures from the previous day’s logs, afternoons benchmarking new models against production, and evenings documenting edge cases. The team’s current pain point: their makeshift governance system of spreadsheets and Slack threads is unraveling with growing traffic. Coworkers joke she’s ‘the prompt police’ because she insists on version-controlled prompts. Monthly all-hands meetings are the only time she wears anything besides jeans and Kurtis. Recently convinced management to at least trial a basic version controller after weeks of hairsplitting debate.
Relationships
Only child of Kerala-based professors (father teaches physics, mother is a biologist). Parents call daily to debate AI ethics over Zoom—her mother thinks it’s unethical for her to work on logistics automation, while her father proudly forwards her every blog post. Best friend since college is now in Berlin; they bonded over debugging Python libraries at 2 AM in hostel rooms. Keeps in touch with her MTech advisor who still sends research papers ‘just to bother her’. Most influenced by her first manager at Google who taught her that ‘elegant solutions only emerge from understanding the messy problems properly.’
How they decide
Research-heavy but ultimately prefers small, reversible experiments over big bets. Will test competitor tools under aliases to avoid bias. Values direct experience over peer reviews. Gets analysis paralysis around big decisions but once committed, executes precisely.
How they sound
Speaks in clipped, precise sentences with a slight Muthootpuzha lilt from her childhood. Uses technical jargon freely but drops it immediately when non-technical people react with confusion. Avoids hyperbole unless it’s about music—then becomes poetic. Prefers ‘rather’ over ‘but’ and ‘somewhat’ over ‘kinda’. Will say ‘that’s a non-trivial problem’ when others would say ‘that’s complicated’.
Personality traits
- Meticulous about documentation
- Tendency to over-prepare for meetings
- Quietly competitive in technical discussions
- Hates vague prompts, always asks for specifics
- Will spend hours optimizing a script for 5% better performance
- Prefers solo deep work over team brainstorms
- Keeps a spreadsheet of personal reading recommendations
- Secretly enjoys debugging more than anything else
- Strict about work hours but will gladly stay late for a good problem
- Avoids small talk unless it’s about tech or music
Goals
- Move to a 50:50 research:code balance in her role
- Complete the Coursera deep learning specialization she started 18 months ago
- Perform in a classical guitar ensemble within a year
- Save ₹80,000 for a European music festival trip
- Mentor one junior engineer before 2025
Problems & frictions
- Spreadsheet-based governance is creating friction between ops and engineering
- No standardized way to reproduce prompt variants across team members
- Management wants more ‘quick wins’ but she’s stuck in maintenance mode
- Her apartment building’s WiFi is unreliable during monsoons
- Feels intellectually stagnant since transferring from research to applied AI
- Can’t find a classical music teacher who understands modern experimental techniques
Values
- learning
- precision
- useful automation
- work-life balance
- self-improvement
Interests
- LLM evals
- product analytics
- classical music
- Indie rock
- efficient coding tools
Media habits
- LinkedIn for AI trends
- Hacker News for tech debates
- YouTube for classical music performances
- Twitter for quick news
- Medium for long reads