10 fictional AI personas. Exploratory perspectives, not a survey of real customers. Methodology & limitations

Aagam Embranthiri-Sharma

Aagam Embranthiri-Sharma

Solo documentation engineer

Full-depth AI personas

Why this persona fits the audience

He maintains developer docs and internal knowledge pages for a B2B API startup. The docs live as Markdown in GitHub, release tracking sits in Sheets, and he keeps a manual checklist in Jira while handling most of the writing and build pipeline himself.

  • Age: 28
  • Location: Pune, India
  • Occupation: Documentation engineer
  • Income: ₹19 LPA
  • Education: BTech Computer Science (Pune University)
  • Company size: 20-30 employees
  • Years in role: 3
“Good documentation doesn't just exist - it's a wilfully maintained artifact that requires constant attention. Most companies treat it like a gardener who's only called when the weeds are already overtaking the flowers.”

Aagam Embranthiri-Sharma graduated with a BTech in Computer Science from Pune University, where he developed a reputation for producing meticulously organized lab reports. After brief stints at two larger tech companies where he found documentation processes inconsistent, he joined a fast-growing B2B API startup as their first and only dedicated documentation engineer three years ago. The role was initially seen as a secondary concern, but Aagam's persistence in establishing rigorous documentation practices has gradually earned him more influence. His current/documentationkit maintains all company docs in a GitHub repository, using a custom build pipeline to publish updates. He's currently grappling with the complexity of versioned documentation as the company's API evolves. While he's comfortable with his salary (₹19 LPA), he's frustrated by the lack of budget for proper documentation tooling. His personal project is building a Python-based system to better track documentation changes, though he's considered looking for tools to replace his current manual processes. He's highly self-sufficient at work, handling most writing and build pipeline maintenance himself. His greatest professional fear is that the company will grow too quickly for him to maintain documentation quality without better tooling. Outside work, he maintains a strict personal discipline, from his workout routines to his meticulous note-taking system. He's particularly proud of his personal blog where he writes about documentation patterns, though he refuses to monetize it, seeing it as a labor of love rather than a potential income source. His social life is limited, primarily consisting of his college friends who share his interests. He occasionally fantasizes about speaking at technical conferences but hesitates due to his introverted nature.

Background & daily life

A day in their life

Aagam's day begins at 6:15 AM with coffee and a quick scan of GitHub notifications. He walks to work through Koregaon Park, listening to an audiobook about software architecture. At 8:30, he checks Jira tickets and Slack messages while opening his Markdown editor. Most of the morning is spent reviewing PRs for documentation changes and updating the release tracking spreadsheet. At 12:30, he eats lunch at his desk while reading Stack Overflow threads about Markdown tooling. The afternoon involves writing new API documentation and updating version matrices. He avoids the 3:00 PM team standup when possible but attends when forced. Around 5:30, he works on his personal project to automate documentation validation before heading to the gym. Dinner is usually dal, rice, and vegetables he cooks in bulk on Sundays. After 9:00 PM, he spends time improving his personal documentation blog or playing competitive fencing games while listening to tech podcasts.

Lifestyle

Aagam lives alone in a compact but efficiently organized flat in Pune's Koregaon Park neighborhood. His mornings start with black coffee and a quick review of GitHub notifications while standing at his kitchen counter. He walks 45 minutes to work most days, using it to listen to audiobooks about software architecture. Weekends are spent maintaining a personal blog about documentation patterns (which he refuses to monetize), practicing Muay Thai at a local gym, and occasionally gaming (mostly competitive fencing simulators). He's frugal by habit, avoids food delivery apps, and tracks every rupee in a spreadsheet. Social life is limited to a small group of former college classmates who share his interest in minimalist tech and API design.

Work life

As the sole documentation engineer at a B2B API startup, Aagam spends his days balancing writing, maintenance, and process improvement. His current top project is restructuring the entire documentation site to better handle API versioning, which requires careful coordination with the engineering team. He's currently building a Python script to automate some of the release-validation steps. The biggest frustration is dealing with last-minute documentation requests from engineering teams that wait until the night before releases. He maintains a meticulous Jira board but secretly dreams of a tool that could handle versioned documentation with proper change tracking.

Relationships

Aagam is close with his parents who live in Cochin, who he video calls on Sundays. His older sister in Bangalore occasionally consults him on technical matters (which he enjoys) but frequently nags him to 'meet more people.' At work, he has a good rapport with the lead engineer but finds it difficult to push back against product managers who see documentation as an afterthought. His closest friends are from his college days - they share his interests in API design and minimalist computing.

How they decide

Research-heavy with a strong preference for technical correctness. He'll spend hours evaluating small tool choices but values his own experience over user reviews. Once he decides on a process, he sticks to it unless presented with clear data that it's failing.

How they sound

Speaks in precise, measured sentences. Uses technical jargon but explains concepts clearly when necessary. Avoids slang and informal language, even with close colleagues. Has a slightly dry sense of humor that manifests in perfectly timed understated observations. Prefers email for complex explanations over Slack messages. When frustrated, he'll say things like 'The current processes are not scalable' or 'This workflow violates our consistency principles' rather than more emotional language.

Personality traits

  • Fastidious about consistency in documentation
  • Prefer to automate repetitive tasks even when trivial
  • Quietly competitive about documentation quality
  • Dislikes ambiguity in process definitions
  • Tends to over-document internal processes just in case
  • Patient with technical explanations but impatient with vague requests
  • Prefers writing at night when the office is empty
  • Dislikes meetings but attends them diligently
  • Hates adhoc documentation requests
  • Surreptitiously organizes chaotic knowledge bases when no one's looking

Goals

  • Build a sustainable documentation process that scales with company growth
  • Automate 50% of his manual documentation validation tasks
  • Complete a technical writing course from Purdue University
  • Improve his public speaking skills to present at local meetups
  • Reduce his personal documentation repository's technical debt

Problems & frictions

  • Engineering teams frequently bypass documentation processes at the last minute
  • No central tool exists for tracking documentation updates across API versions
  • Finding time to refactor old documentation while keeping up with new releases
  • Difficulty convincing stakeholders of the value in maintaining documentation quality
  • His GitHub workflows are becoming unwieldy as the documentation grows

Values

  • Technical correctness
  • Ownership
  • Efficiency
  • Clarity
  • Autonomy

Interests

  • Documentation tooling
  • API specifications
  • Git workflows
  • Python scripting
  • Minimalist tech

Media habits

  • Dev.to
  • Stack Overflow
  • YouTube tech tutorials
  • LinkedIn (passively)
  • Newsletter 'Write the Docs'

Questions & answers

Aagam Embranthiri-Sharma’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Val (https://val.build/docs) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    As a documentation engineer managing everything from Markdown to versioning, I handle my current workflow manually: Markdown in GitHub, release tracking Sheets and Jira. The idea of Val's Git-centric, TypeScript-based system is intriguing, but I have concerns. My primary workflow is already code-adjacent, but I'm cautious about adopting a new CMS right now because our startup is hyper-focused on API changes, and I need stability more than new features. If I tried Val, I'd worry about migrating existing content, an unwelcome distraction when I'm drowning in documentation updates. I might pay something, but it would have to offer instant-value for my current workflow. As it stands, I'd need to see undeniable proof that Val integrates with our existing GitHub ecosystem without disruption. $150 USD per month might be acceptable, but I'm not optimistic unless there's a clear migration path and minimal learning curve. The $0signup is helpful, but I'd still need to allocate time for the switch.
    View answer & full research →
Keep exploring

What would you ask next?

Test another angle with this panel, or create an audience for your own market.