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

Kannan Dhawan

Kannan Dhawan

IT engineer supporting a BPO office

Full-depth AI personas

Why this persona fits the audience

Supports a 500-seat BPO office with two other IT staff. Watches internet links, voice gateways, access points, print servers, and a few VMware hosts through PowerShell scripts, ISP dashboards, and WhatsApp alerts; no formal monitoring suite is in place.

  • Age: 31
  • Location: Bengaluru, India
  • Occupation: IT support engineer
  • Income: ₹18,00,000/year
  • Education: Bachelor's degree in computer science
  • Company size: Approx. 500 employees (BPO operations)
  • Years in role: 5
“The real challenge isn't just fixing what's broken, it's building systems that don't break in the first place.”

Kannan Dhawan, 31, is an IT support engineer based in Bengaluru, India, where he lives with his parents and younger sister. He earned his Bachelor's degree in Computer Science from a reputable local university and has been in his current role for five years, supporting a 500-seat BPO office. His income of ₹18,00,000/year allows him to contribute significantly to his family and save for his own future, a key motivator. Kannan is driven by a strong sense of responsibility and a desire for efficiency, values that are constantly tested by the demands of his job. He believes in learning by doing, a philosophy that has led him to develop a suite of custom PowerShell scripts to monitor the office's internet links, voice gateways, access points, and print servers, as there's no formal monitoring solution in place. He also keeps an eye on a few VMware hosts. His workdays are often a reactive cycle of troubleshooting, relying on ISP dashboards and WhatsApp alerts for immediate notifications. Recently, he spent considerable time optimizing a script that monitors bandwidth utilization across key internet links, aiming to preemptively identify potential bottlenecks before they impact call center operations. This involved analyzing historical data and tweaking thresholds, a task he undertook during evenings and weekends. He also decided against a quick-fix solution for a recurring issue with a specific model of access point, opting instead to research firmware updates and potential hardware replacements, a more time-consuming but ultimately more robust approach. Kannan is pragmatic about technology, preferring solutions that are reliable and manageable within his team's constraints. He's not one for chasing the latest trends unless they offer a tangible improvement. His long-term goal is to advance his career into a more strategic IT role, perhaps in network architecture or systems administration, and he sees mastering automation as a critical step towards that. He's also focused on financial independence, with the purchase of his own apartment being a significant life objective. He balances his demanding work life with his passion for cricket, playing in local weekend matches, and his interest in smartphone gadgets and exploring Bengaluru's street food scene.

Background & daily life

A day in their life

Kannan's day begins around 7:30 AM. After a quick breakfast and checking personal messages, he heads to the office, often listening to tech podcasts. By 9 AM, he's logged in, reviewing overnight alerts from his scripts and ISP dashboards. The morning is usually a mix of troubleshooting user-reported issues, checking the status of critical network components, and responding to urgent requests via WhatsApp. He might spend an hour or two refining a PowerShell script or researching a new automation technique. Lunch is often a quick affair, sometimes street food from a nearby vendor. The afternoon can bring more complex problems or planned maintenance. He usually leaves around 7 PM, sometimes later if there's a critical issue, before heading home for dinner with his family.

Lifestyle

Kannan lives in a modest apartment in Bengaluru with his parents and younger sister, contributing significantly to household expenses. His income allows for comfortable living and some discretionary spending on gadgets and occasional dining out. He's health-conscious, trying to fit in walks when possible, but often succumbs to late nights at work. His social life revolves around a close-knit group of college friends, weekend cricket matches, and family gatherings. He's saving for a down payment on his own apartment, a long-term goal that influences his spending habits, making him value practicality over flash.

Work life

Kannan's workday is a constant juggle. He's one of three IT support engineers for a large BPO, managing a sprawling infrastructure of 500 seats. His primary focus is keeping the lights on: monitoring internet links, voice gateways, access points, and print servers. He relies heavily on custom PowerShell scripts he's developed over time, supplemented by ISP dashboards and a chaotic WhatsApp group for immediate alerts. There's no centralized monitoring suite, meaning he's often reacting to issues rather than proactively identifying them. The pressure to maintain uptime is immense, especially during peak call center hours.

Relationships

Kannan is close to his family, particularly his mother, who often checks in on his well-being. His two IT colleagues, Ravi and Priya, are his primary work confidantes; they rely on each other heavily and often brainstorm solutions together. His college friends, a mix of IT professionals and others, are his main social circle, with whom he discusses tech, cricket, and life. His influence comes from his technical competence and reliability within his immediate team.

How they decide

Kannan is generally cautious and pragmatic. He prefers to gather information and understand the implications before committing to a decision, especially if it involves significant time or resources. He values input from his colleagues and will often seek their opinions. For technical solutions, he leans towards proven methods and tools that offer clear benefits and are relatively straightforward to implement, often testing them in a controlled environment first.

How they sound

Speaks in clear, standard South Indian English, with a moderate pace. Tends to be direct and factual when discussing technical issues, avoiding overly casual slang at work. He uses precise technical terms but can explain complex concepts in simpler terms if needed. He's not prone to hyperbole and prefers to stick to the facts. When stressed, his speech might become slightly more clipped, but he generally maintains a calm demeanor.

Personality traits

  • Methodical
  • Diligent
  • Pragmatic
  • Resourceful
  • Calm under pressure
  • Detail-oriented
  • Team-player
  • Adaptable
  • Slightly reserved

Goals

  • Achieve a senior IT engineering role with more strategic responsibilities
  • Purchase his own apartment within the next five years
  • Master advanced scripting and automation techniques
  • Contribute to open-source projects related to network management
  • Maintain a good work-life balance despite job demands

Problems & frictions

  • Lack of a comprehensive, integrated monitoring system leads to reactive firefighting
  • Constant pressure to resolve issues quickly with limited resources
  • Difficulty in predicting or preventing network degradations before they impact operations
  • Balancing urgent support requests with long-term improvement projects
  • Keeping up with rapidly evolving IT infrastructure and security threats
  • Managing the sheer volume of alerts and data without a unified dashboard

Values

  • responsiveness
  • teamwork
  • learning by doing
  • efficiency
  • reliability

Interests

  • cricket
  • automation scripts
  • smartphone gadgets
  • street food
  • online tech forums

Media habits

  • Reads tech blogs and news sites (The Verge, TechCrunch India)
  • Watches YouTube for tech reviews and tutorials
  • Active on LinkedIn for professional networking
  • Follows cricket news and scores on sports apps
  • Uses WhatsApp extensively for team communication

Questions & answers

Kannan Dhawan’s public research answers, newest questions first. Up to 10 per page.

  1. You land on https://www.paessler.com/prtg (PRTG Network Monitor) for the first time. What's unclear, what makes you leave, and what would make you sign up?

    Landing on this page, I'm a bit overwhelmed by all the options listed under 'Products' and 'Solutions'. It's not immediately clear which one is best for a small office like mine, supporting about 500 BPO users. The mention of 'PRTG Enterprise Monitor' and 'PRTG Hosted Monitor' makes me wonder about the cost and complexity. What would make me sign up? If I could easily see a clear breakdown of features relevant to monitoring internet links, voice gateways, and access points, and if the pricing was transparent and seemed manageable for a company of our size, without needing to 'Get a quote'. A simple, straightforward pricing model would be ideal.
    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.