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

Sheela Jha

Sheela Jha

SRE at a payments company using only free tools

Full-depth AI personas

Why this persona fits the audience

Supports a 12-person payments startup in Pune with Prometheus, Grafana, Slack, and a spreadsheet runbook. The team has never paid for a dedicated incident-analysis platform and shares on-call across 4 engineers while handling API, queue, and database outages.

  • Age: 30
  • Location: Pune, India
  • Occupation: Site Reliability Engineer
  • Income: ₹18L-₹28L total compensation
  • Education: B.E. Information Technology
  • Company size: 12-person payments startup
  • Years in role: 4
“We build robust systems by being smart with what we have, not by wishing for what we don't.”

Sheela Jha, 30, is a Site Reliability Engineer at a burgeoning payments startup in Pune, India. Holding a B.E. in Information Technology, she has carved a niche for herself in a demanding field, driven by an innate sense of responsibility and a knack for resourcefulness. Her career trajectory has been shaped by a pragmatic approach to technology, focusing on leveraging free and open-source tools to their maximum potential. Sheela's current role is emblematic of this philosophy; she supports a 12-person payments company by ensuring the reliability of their critical infrastructure using only Prometheus for monitoring, Grafana for visualization, Slack for communication, and a meticulously maintained spreadsheet for incident runbooks. This setup, while effective, means her team of four engineers shoulders significant on-call responsibilities, tackling outages across APIs, message queues, and databases without the aid of expensive, dedicated incident management platforms. Sheela's decision to stick with this lean, cost-effective tooling is rooted in her value system, which prioritizes smart allocation of resources and deep understanding of system fundamentals over acquiring the latest, often costly, software. She believes that true engineering prowess lies in making complex systems resilient with the tools at hand. Her income, between ₹18L-₹28L, allows for comfortable living and savings, but she remains judicious with company expenditures, mirroring her personal financial habits. Sheela's commitment extends beyond her immediate tasks; she actively seeks ways to automate repetitive processes and improve system observability, viewing each challenge as an opportunity for growth and learning. Her background instilled a strong sense of teamwork, and she thrives in collaborative environments where problems are tackled collectively. Sheela is not just maintaining systems; she is building a foundation of reliability through ingenuity and dedication.

Background & daily life

A day in their life

Sheela's day begins around 6:30 AM with a quick yoga session and checking her personal finance apps. After a simple breakfast, she commutes to the office, listening to a tech podcast. Her workday starts with a stand-up meeting, followed by reviewing system dashboards in Grafana and addressing any alerts from Prometheus. She spends a significant portion of her day optimizing scripts for automation, refining alert thresholds, and updating the team's shared spreadsheet runbook. Lunch is usually a quick affair, often with colleagues discussing technical challenges. The afternoon might involve a deep dive into a recent incident's root cause or collaborating with developers on deployment strategies. She leaves the office by 7 PM, commutes home, has dinner with Raj, and winds down by reading or watching a cricket match highlights.

Lifestyle

Sheela lives in a 2-bedroom apartment in Pune with her husband, Raj, a software developer, and their cat, Mint. They manage their finances carefully, aiming to save a significant portion of their income for future investments and travel. Weekdays are structured around work, with early morning yoga sessions and evenings dedicated to reading or catching up on tech news. Weekends often involve exploring nearby hiking trails or watching cricket matches, especially during major tournaments. Sheela prioritizes healthy eating and tries to cook most meals at home.

Work life

As an SRE at a fast-paced payments startup, Sheela's days are a constant balance of proactive system maintenance and reactive incident response. Her team of four engineers shares on-call duties, meaning late-night alerts are a reality. They rely heavily on Prometheus for metrics, Grafana for dashboards, and Slack for communication. Incident documentation and runbooks are meticulously maintained in a shared spreadsheet, a testament to their resourcefulness. The pressure to maintain high uptime for critical payment APIs and queues is immense, especially with a lean team and no budget for specialized incident management tools.

Relationships

Sheela is married to Raj, who understands the demands of her tech career. They are a strong support system for each other. Her immediate family lives in a different city, so they connect via video calls weekly. At work, she has a collaborative relationship with her three fellow SREs and the small engineering team.

How they decide

Sheela is a research-heavy decision-maker, especially when it comes to work-related tools or processes. She thoroughly evaluates options, considers long-term implications, and seeks input from her team. For personal decisions, she tends to be pragmatic and budget-conscious, weighing pros and cons carefully.

How they sound

Speaks clearly and precisely, with a measured cadence. Her tone is generally calm and professional, even under pressure. She avoids excessive slang, preferring standard technical terminology. When discussing challenges, she's direct but not alarmist, focusing on solutions. She might use occasional Marathi phrases when speaking casually with close colleagues.

Personality traits

  • detail-oriented
  • analytical
  • team player
  • self-motivated
  • frugal
  • patient
  • methodical
  • pragmatic

Goals

  • Achieve a senior SRE position within the next five years.
  • Contribute to open-source projects related to monitoring or incident management.
  • Develop a personal investment portfolio that provides passive income.
  • Complete a half-marathon.
  • Mentor junior engineers entering the SRE field.

Problems & frictions

  • Managing on-call fatigue with a small team.
  • The constant need to innovate and improve system resilience with limited resources.
  • Difficulty in performing deep, post-incident analysis without dedicated tooling.
  • Balancing urgent incident response with long-term system improvement projects.
  • Keeping up with the rapidly evolving landscape of cloud-native technologies.

Values

  • resourcefulness
  • responsibility
  • teamwork
  • automation
  • self-improvement

Interests

  • automation
  • personal finance
  • cricket
  • reading fiction
  • hiking

Media habits

  • listens to tech podcasts during commute
  • follows SRE and DevOps blogs
  • watches cricket matches on streaming services
  • reads online news

Questions & answers

Sheela Jha’s public research answers, newest questions first. Up to 10 per page.

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

    Our current setup with Prometheus, Grafana, and a spreadsheet runbook is quite lean, and honestly, it gets the job done for our 12-person startup. The biggest hurdle to adopting something new like Sherlocks.ai this month would be the time and effort required to integrate it and ensure it genuinely adds value beyond what we already have. We're on-call 24/7 with just four engineers, so any new tool needs to be a clear win and not add to our workload. I'd need to see how it fits with our existing Prometheus and Grafana setup without causing disruption. Regarding pricing, I'd be looking at a free or very low-cost tier initially, perhaps up to $100 USD per month if it proved significant value in reducing our incident response time and fatigue.
    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.