Ashok Tandon

Why this persona fits the audience

Part of a 4-person content team in Bengaluru that prepares short training videos for internal and client use. He receives caption files from transcription vendors, checks encoding for accented names and mixed-language terms, and converts between SRT and VTT as part of the regular handoff process.

• Age: 30
• Location: Bengaluru, India
• Occupation: Content producer
• Income: ₹16L
• Education: BTech in computer science
• Company size: Small (approx. 50 employees)
• Years in role: 3

“If I can write a script to do it in five minutes, there is no reason to spend an hour doing it manually.”

Ashok Tandon is a thirty-year-old Computer Science graduate from VTU who settled in Bengaluru shortly after finishing his degree. Unlike many peers who chased high-frequency trading firms or startups with grand visions, Ashok found his niche in the unglamorous but critical infrastructure of corporate learning and development. Currently working as a Content Producer for a mid-sized IT services firm, he serves as the linchpin between creative video production and technical deployment. His role is less about storytelling and more about ensuring the delivery mechanism works flawlessly, a responsibility he takes with quiet pride. Over the last three years, Ashok has developed a reputation for being the person who fixes the 'impossible' formatting issues that cause other teams to panic. He lives in a shared apartment in Koramangala, a neighborhood that balances his need for connectivity with a reasonable commute cost. His income of ₹16 lakhs annually allows him a comfortable life, though he remains frugal, allocating significant portions to savings and occasional hardware upgrades. He views money not as a status symbol but as a tool to buy freedom from repetitive tasks. Technologically, Ashok is self-taught in automation. While his formal education focused on software engineering principles, his real expertise lies in shell scripting and file manipulation. He has built a personal toolkit of Python scripts to handle subtitle conversions, yet he constantly hunts for better, lighter alternatives. Recently, he made the decision to stop using a commercial video editor for simple text corrections, switching entirely to VS Code extensions to reduce licensing costs and increase speed. This pragmatism defines his worldview: technology should serve the user, not the other way around. He is currently evaluating whether to invest time in learning React for building a custom internal dashboard or to stick with maintaining his existing CLI tools, a classic dilemma between innovation and stability. His life is a study in efficient execution, driven by a desire to eliminate friction wherever it appears.

Background & daily life

A day in their life

Ashok wakes up at 7:00 AM, skips breakfast, and cycles to his shared office space in Koramangala to avoid Bangalore traffic. By 9:30 AM, he is logged into Jira, reviewing the day's ticket queue. His morning is spent debugging a batch of SRT files sent overnight by a vendor in Hyderabad, where he discovers the 'é' character is rendering as 'é' across multiple filenames. He spends two hours writing a quick regex script in Python to auto-correct the encoding, a task he usually hates but finds oddly satisfying when it works. After lunch, he attends a 30-minute stand-up where he explains why the current video player doesn't support their custom font. The afternoon involves converting ten client-specific VTT files, manually checking timestamps against the video timeline. He leaves at 6:30 PM, stops at a juice stall for a post-work vitamin drink, and heads home to review a GitHub repository for a new subtitle parser library, hoping to find something that solves his encoding headaches permanently.

Lifestyle

Ashok lives in a modest but well-connected flat in Koramangala, sharing expenses with two male friends to keep rent manageable. His weekends are split between low-key gaming sessions with his brother via Zoom and exploring new coffee shops in Indiranagar, where he works remotely when the office is too chaotic. He maintains a strict budget, prioritizing savings for a potential down payment on a car over luxury dining. Health-wise, he manages sedentary work habits by cycling three times a week, viewing it as essential maintenance rather than recreation. Financially, he is cautious, avoiding subscription fatigue and preferring one-time purchases or free tiers unless a tool offers undeniable time savings.

Work life

As one of four core members in his content unit, Ashok acts as the technical gatekeeper for all video assets before they reach clients. His day is dominated by the friction of file formats: receiving raw SRT files from external vendors that often contain garbled UTF-8 characters for Kannada or Tamil names, requiring manual correction. He spends hours converting these to VTT for specific client LMS requirements, a task he has automated partially using local Python scripts but still finds tedious. The pressure comes from tight deadlines; if a vendor sends a broken file an hour before a client demo, Ashok is the one who must fix it without panicking. He relies heavily on VS Code and command-line tools, finding GUI-based editors clunky for bulk operations.

Relationships

Ashok is close to his younger sister, whom he supports financially, and maintains a steady, albeit distant, connection with his parents in Pune. At work, he has a respectful but professional relationship with his manager, often acting as the go-to problem solver for technical glitches. His social circle is limited to his housemates and a few college friends who share his interest in tech efficiency; he avoids large social gatherings, preferring intimate dinners where conversations remain substantive. He values reliability in relationships and rarely engages in gossip, focusing instead on practical support.

How they decide

Ashok approaches decisions with a 'measure twice, cut once' philosophy. He is highly skeptical of marketing fluff and relies on peer reviews, open-source documentation, and hands-on testing in sandbox environments before adopting any new workflow or tool. He prefers solutions that offer immediate, tangible ROI in terms of time saved rather than long-term strategic promises. If a tool requires a sign-up or credit card, he will likely abandon it unless a trusted colleague vouches for its utility.

How they sound

His speech is calm, measured, and precise, often pausing to choose the exact technical term. He speaks in clear, concise sentences, avoiding emotional exaggeration or hyperbole. In casual conversation, he might slip into a mix of English and mild Kannada slang, but generally keeps it professional. He tends to avoid saying 'I don't know' directly, instead prefacing uncertainty with 'Let me verify the specs.' He rarely uses corporate buzzwords like 'synergy' or 'disruptive,' finding them empty.