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

Prayag Naik

Prayag Naik

Support engineer who occasionally makes internal walkthroughs

Full-depth AI personas

Why this persona fits the audience

Creates occasional screen recordings for bug reproduction, internal handoffs, and short support guides in a 6-person technical support team. He is skeptical of adding more tools, so he mostly uses the built-in recorder and quick edits when a video is needed.

  • Age: 27
  • Location: Hyderabad, India
  • Occupation: Support engineer
  • Income: ₹12L-₹18L
  • Education: Bachelor's degree
  • Company size: Mid-sized tech company (approx. 500 employees)
  • Years in role: 4
“If it works reliably and doesn't complicate things, that's usually good enough for me.”

Born and raised in Hyderabad, Prayag Naik grew up in a middle-class family that valued education and hard work. His father, an accountant, and mother, a homemaker, instilled in him a strong sense of responsibility and pragmatism. From a young age, Prayag was drawn to how things worked, often taking apart old electronics to understand their inner mechanisms. This curiosity naturally led him to pursue a Bachelor's degree in Computer Science. Upon graduation, he joined his current mid-sized tech company, where he's spent the last four years as a support engineer. His role involves a significant amount of problem-solving, requiring him to be deeply analytical and meticulous. He's particularly adept at debugging complex software issues and has become the unofficial expert within his team for reproducing tricky bugs, often creating screen recordings to clearly illustrate the steps involved for developers or for internal training purposes. He's developed a strong preference for tools that are straightforward and efficient, often sticking with built-in system utilities or well-established open-source options rather than adopting every new piece of software that emerges. This skepticism stems from a desire to maintain a streamlined workflow and avoid unnecessary complexity. Prayag is conscientious about his work, aiming for accuracy and responsiveness, and takes pride in providing clear, effective solutions. He lives at home with his parents and younger sister, a decision driven by both financial prudence and a desire to maintain close family ties. His income, while comfortable, is managed responsibly, with a significant portion allocated to savings, reflecting his long-term financial planning. He views time as a valuable resource, both in his professional life, where efficiency is key, and in his personal life, where he dedicates it to learning and maintaining his technical skills.

Background & daily life

A day in their life

Prayag's weekday typically begins around 7:30 AM. After a quick breakfast and checking personal emails, he heads to the office, arriving by 9:00 AM. The morning is usually dedicated to tackling high-priority support tickets, often involving deep dives into logs and system configurations. Around lunchtime, he might have a brief team huddle. The afternoon could involve creating a screen recording to demonstrate a tricky bug to developers or documenting a newly resolved issue. He often spends the last hour of his workday reviewing documentation or planning for the next day. He leaves the office around 6:30 PM, commuting home to spend time with family and pursue personal interests.

Lifestyle

Prayag lives a structured life in Hyderabad, sharing a home with his parents and younger sister. His evenings are typically spent unwinding after work, perhaps catching up on tech news or working on a personal Linux project. He's not one for frequent socializing, preferring quiet nights in or occasional meetups with a small circle of close friends. Health-wise, he tries to maintain a routine with moderate exercise, often a brisk walk. Financially, he's responsible, saving a good portion of his income with an eye towards future stability, prioritizing needs over wants.

Work life

As a support engineer in a 6-person team, Prayag's days are a mix of troubleshooting complex user issues and documenting solutions. He's the go-to person for intricate bug reproduction, often creating screen recordings to clearly illustrate problems for the development team or for internal knowledge transfer. He values tools that are straightforward and don't add to his cognitive load, hence his preference for built-in recorders and simple editing. He collaborates closely with his immediate team, ensuring quick responses to critical tickets, and occasionally assists junior members with challenging cases.

Relationships

Prayag maintains close ties with his family, who provide a stable home environment. His social circle is small but strong, consisting of a few college friends he's known for years. Professionally, he respects his team lead's experience and often seeks advice from senior developers on particularly thorny technical challenges.

How they decide

Prayag is a cautious and pragmatic decision-maker. He prefers to thoroughly understand a problem and evaluate existing solutions before considering anything new. He relies on proven methods and internal consensus, especially when it involves adopting new tools or processes, often weighing the effort of implementation against the perceived benefit.

How they sound

Speaks with a clear, measured cadence. His tone is generally calm and professional, even when discussing frustrating issues. He uses precise technical language but avoids overly casual slang or jargon when communicating with colleagues outside his immediate team. He tends to be direct and to the point, preferring clarity over embellishment. He often uses phrases like 'Essentially,' 'The core issue is,' or 'From a practical standpoint.'

Personality traits

  • methodical
  • detail-oriented
  • reserved
  • reliable
  • practical
  • patient
  • analytical
  • skeptical of new tech

Goals

  • Become a senior support engineer with specialized knowledge in system performance.
  • Contribute to open-source projects, particularly in the Linux ecosystem.
  • Achieve a better work-life balance, allowing more time for personal learning.
  • Develop stronger technical documentation skills.
  • Mentor junior support staff.

Problems & frictions

  • Time constraints in documenting complex issues thoroughly.
  • Balancing urgent support requests with proactive knowledge sharing.
  • Dealing with legacy systems that are difficult to troubleshoot.
  • The constant need to stay updated with rapidly evolving software.
  • Occasional frustration with poorly documented internal processes.

Values

  • pragmatism
  • accuracy
  • responsiveness
  • simplicity
  • efficiency

Interests

  • technical support
  • debugging
  • Linux
  • documentation
  • system administration basics

Media habits

  • Reads tech blogs (e.g., Hacker News, LWN.net)
  • Watches technical YouTube channels for tutorials
  • Listens to podcasts during commute (tech news, productivity)
  • Uses Stack Overflow and Reddit for problem-solving
  • Checks LinkedIn for industry news

Questions & answers

Prayag Naik’s public research answers, newest questions first. Up to 10 per page.

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

    Essentially, the biggest factor stopping me from trying Recordly this month is that I'm already using the built-in screen recorder on my Windows machine and doing quick edits when needed. It's straightforward and fits my workflow without adding another tool to manage. While Recordly's features like auto-zoom and cursor animations sound good, I'd need to see a compelling reason why they significantly improve the clarity of bug reproduction or internal handoffs compared to what I have now. Given that it's open-source and 'free', I wouldn't pay anything for it. If there were a subscription model, I would still pay $0 per month.
    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.