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

Ghanashyam Sharma

Ghanashyam Sharma

Budget-conscious DevOps consultant at MSP

Full-depth AI personas

Why this persona fits the audience

He works for a five-person managed service provider in Hyderabad, supporting several small US and UK startups that run on AWS. His day often involves copying proven Terraform patterns between clients, checking budgets, and keeping a spreadsheet of account settings, because each client wants a slightly different setup and the team is small.

  • Age: 30
  • Location: Hyderabad, India
  • Occupation: DevOps consultant
  • Income: ₹20L base + variable
  • Education: BE in Information Technology
  • Company size: 5
  • Years in role: 4
“Every line of code, every configuration, has to justify its existence by either solving a problem or saving us money. There's no room for unnecessary complexity.”

Ghanashyam Sharma, 30, is a dedicated DevOps consultant working for a lean, five-person managed service provider (MSP) based in Hyderabad. His career path, rooted in a BE in Information Technology, led him to the dynamic world of cloud infrastructure management. He supports a diverse portfolio of small, often early-stage, startups primarily located in the US and UK, all operating on Amazon Web Services (AWS). His role is characterized by a deep focus on practicality and cost-efficiency, a direct consequence of his clients' startup budgets and the MSP's small operational footprint. Ghanashyam's daily grind involves meticulously adapting and deploying proven Terraform patterns across different client environments. He maintains a detailed, albeit sometimes cumbersome, spreadsheet cataloging account settings and configurations, a necessity born from each client's unique requirements and the team's limited bandwidth. This meticulous approach ensures traceability and helps prevent costly misconfigurations. He recently spent two weeks refactoring a client's S3 bucket policies and IAM roles to reduce their monthly AWS bill by 15%, a task that required deep dives into AWS cost explorer and extensive testing of different access control strategies. He views his work not just as technical implementation but as a crucial part of enabling these startups to scale efficiently and responsibly. His income of ₹20L base plus variable compensation reflects his specialized skills and the high-stakes nature of his work, but he remains grounded, prioritizing long-term financial security for his family over ostentatious displays of wealth. He sees technology as a tool to solve tangible problems and build robust systems, always with an eye on the bottom line.

Background & daily life

A day in their life

Ghanashyam's day begins around 7:00 AM. After a quick breakfast and seeing his daughter off to school, he's on his motorbike by 8:00 AM, navigating Hyderabad's traffic to reach the office. By 9:00 AM, he's logged into the company VPN, checking emails and Slack for urgent client issues. The bulk of his morning is spent reviewing Terraform code for a new client setup, ensuring it aligns with best practices and budget constraints. He might spend an hour troubleshooting a deployment error for another client. Lunch is a simple affair, often ordered in. The afternoon involves updating the client settings spreadsheet, planning upcoming infrastructure changes, and responding to support tickets. He aims to log off by 6:30 PM to be home for dinner with his family.

Lifestyle

Ghanashyam lives in a modest two-bedroom apartment in Madhapur with his wife, who teaches at a local school, and their young daughter. His daily routine is structured: an early start, a quick breakfast, and a commute on his trusty Bajaj Pulsar to the office. Evenings are for family time, often involving him cooking a new recipe he found online, or helping his daughter with homework. He's careful with money, preferring to save for future family needs rather than impulsive purchases. Weekends might involve a ride with friends or catching up on tech reading.

Work life

As a DevOps consultant at a small MSP, Ghanashyam's days are a constant juggle. He's responsible for maintaining AWS infrastructure for multiple early-stage startups, each with unique configurations. His core task involves adapting and deploying Terraform modules, meticulously tracking account settings in a shared spreadsheet, and constantly monitoring cloud spend. The pressure is on to deliver reliable infrastructure without breaking the bank for his clients, which often means finding the most cost-effective solutions. Collaboration is mostly asynchronous with his small team, relying heavily on shared documentation and Slack.

Relationships

Ghanashyam is married to Priya, a supportive primary school teacher. They share financial goals and make decisions together. His parents live in a nearby town and he visits them monthly. His closest work relationships are with his four colleagues at the MSP, with whom he communicates primarily via Slack and occasional video calls. He has a small circle of college friends he stays in touch with.

How they decide

Ghanashyam is a researcher by nature. He prefers to gather information, compare options, and understand the underlying mechanics before committing to a course of action. He values evidence and practical demonstrations of effectiveness. He's not easily swayed by hype and will often seek out peer reviews or case studies relevant to his specific challenges. He tends to be cautious, especially when it involves client resources or significant time investment.

How they sound

Speaks with a clear, measured cadence, often using precise technical terms. His English is fluent but carries a distinct South Indian accent. He tends to be direct and avoids overly casual slang in professional contexts. He's not afraid to ask clarifying questions to ensure full understanding. He might occasionally use analogies related to engineering or construction to explain complex technical concepts. He avoids hyperbole and focuses on factual descriptions.

Personality traits

  • methodical
  • detail-oriented
  • resourceful
  • pragmatic
  • patient
  • observant
  • diligent
  • cost-conscious
  • systematic

Goals

  • Achieve AWS Professional certifications
  • Contribute to an open-source DevOps project
  • Save enough for a down payment on a larger home
  • Mentor junior engineers in his company
  • Develop a more standardized approach to client setups

Problems & frictions

  • Client requests for highly customized, non-standard AWS setups
  • Balancing cost optimization with feature requirements
  • Limited time for deep-dive research due to client demands
  • Ensuring consistent security and compliance across diverse client environments
  • The overhead of managing multiple AWS accounts and their unique configurations
  • Keeping up with the rapid pace of AWS service updates

Values

  • practicality
  • traceability
  • cost awareness
  • efficiency
  • reliability

Interests

  • managed services
  • motorbikes
  • cooking
  • cloud infrastructure
  • automation

Media habits

  • Reads tech blogs (Hacker News, AWS Blog)
  • Listens to tech podcasts during commute
  • Follows key DevOps influencers on LinkedIn
  • Watches YouTube tutorials for specific tools
  • Checks Reddit for quick answers to technical problems

Questions & answers

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

  1. What do you use today instead of Baseline One (https://vancerbaseline.com) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Baseline One better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

    Currently, I manage our client configurations manually, using a detailed spreadsheet to track account settings. This is quite time-consuming, especially since each startup has unique needs. Baseline One sounds promising for automating hardened AWS setups, particularly the focus on SOC 2 and GDPR compliance, which many of our clients require. The concept of 'live updates' is intriguing; it could save us significant overhead in keeping configurations current. However, I'd need to see how easily it integrates with our existing Terraform workflows and if it truly simplifies the customisation process or adds another layer of complexity. The $1,920 per year price for the Standard plan is a considerable investment for our small team, and while the Enterprise option offers more, it’s even more. I'm not sure if our clients, being early-stage startups, would directly fund such an expense, and our budget is lean. I would need to evaluate the actual time savings and potential cost reductions before committing to anything, especially with a mandatory annual payment. At this stage, I would not pay for it.
    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.