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

Sudeva Namboothiri

Sudeva Namboothiri

QA engineer in a small product team

Full-depth AI personas

Why this persona fits the audience

Part of a 2-person QA function in Bengaluru, she records browser-based defect repros, annotates screenshots for tickets, and keeps a simple spreadsheet of test cases and status. Her workflow is mostly inside Chrome, Jira, and Google Drive, with free tools and manual notes.

  • Age: 27
  • Location: Bengaluru, India
  • Occupation: QA Engineer
  • Income: ₹18 LPA
  • Education: BTech in computer science
  • Company size: Small (under 50 employees)
  • Years in role: 4
“Every line of code, every click, has a story. My job is to make sure those stories are clear, consistent, and lead to a good outcome for everyone.”

Sudeva Namboothiri, 27, is a dedicated QA Engineer working in a small product company based in Bengaluru, India. Holding a BTech in Computer Science, she has been in her current role for four years, forming a crucial part of a two-person QA function. Her daily reality is deeply embedded within the browser, primarily Chrome, where she meticulously records defect reproduction steps, annotates screenshots for Jira tickets, and maintains a vital, albeit simple, spreadsheet tracking test cases and their current status. Her workflow is largely manual, relying on free tools and her own systematic approach to ensure product quality. She lives with her younger sister in Marathahalli, a decision driven by shared living costs and mutual support. Sudeva's income of ₹18 LPA allows for a comfortable but frugal lifestyle; she prioritizes saving for future financial security and potential further education over immediate luxuries. Her personality, marked by high conscientiousness and moderate openness, drives her pursuit of precision and repeatability in her work. She is not one for impulsive decisions, preferring to thoroughly research and analyze options, a trait that extends from her professional life into her personal choices. She recently decided to focus her personal learning time on understanding the fundamentals of test automation frameworks, recognizing the growing need for efficiency in her team's testing processes, even if full implementation is a distant goal. This decision was prompted by observing the increasing backlog of manual test cases and the pressure to deliver faster releases without compromising quality. She feels a constant tension between the need for thorough manual checks and the potential time savings of automation, a dilemma she grapples with daily. Her commitment to accountability means she takes ownership of the quality of the features she tests, even when faced with tight deadlines and limited resources. She views her role not just as finding bugs, but as a guardian of the user experience, ensuring that the product functions as intended and reliably.

Background & daily life

A day in their life

Sudeva's weekday begins around 7:00 AM with a quick breakfast of idli or upma. She leaves for work by 8:00 AM, catching a crowded bus to her office in Bengaluru's tech hub. By 9:00 AM, she's logged into her systems, checking Jira for new tickets and reviewing the previous day's test results. The morning is dedicated to reproducing reported bugs, meticulously documenting each step with screenshots and video snippets using a free browser extension. She collaborates with her QA counterpart on test case updates in their shared Google Sheet. Lunch is a simple affair, often packed from home. The afternoon involves regression testing for new builds, writing detailed bug reports, and attending brief stand-up meetings. She leaves the office around 6:30 PM, heading home to prepare dinner and unwind.

Lifestyle

Sudeva lives in a modest apartment in Marathahalli, sharing with her younger sister who is pursuing her Master's. Her days are structured, starting with a quick breakfast and a brisk walk to the bus stop for her commute. Evenings are often spent catching up on household chores, preparing dinner, or dedicating a couple of hours to personal learning, often related to new testing frameworks. She enjoys occasional outings with friends to local cafes or movie theaters, but her social life is generally quiet, prioritizing rest and preparation for the next workday. Financial prudence is key; she diligently saves a portion of her income, aiming for future stability and perhaps further education.

Work life

As one of two QA engineers in a small, fast-paced product team, Sudeva's days are a constant cycle of testing, documenting, and collaborating. She spends a significant portion of her time meticulously reproducing bugs reported by users or developers, capturing detailed steps and annotating screenshots within Jira tickets. Her primary tools are Chrome's developer tools, Jira for bug tracking, and a shared Google Sheet for managing test cases and their current status. The pressure to ensure product stability with limited resources means she's always looking for ways to streamline her manual processes, often sketching out ideas for automation in her notebook. Her interactions are primarily with the development team and her fellow QA engineer.

Relationships

Sudeva is close to her younger sister, sharing daily life and mutual support. Her parents, living in their hometown, are a constant source of encouragement. At work, she has a good rapport with her fellow QA engineer, often brainstorming solutions together. She respects the lead developer's technical acumen and values their feedback, though their communication can sometimes be brief due to tight deadlines.

How they decide

Sudeva is a cautious and research-oriented decision-maker. When faced with a choice, especially regarding tools or processes, she will first consult documentation, read reviews, and compare features. She often seeks input from her colleague and sometimes discreetly observes how other teams handle similar challenges before committing to a path. She values proven reliability and clear benefits over novelty.

How they sound

Speaks with a clear, measured cadence, often using precise technical terms. Her tone is generally polite and professional, avoiding excessive slang or overly casual language. She tends to articulate her thoughts logically, often pausing to ensure accuracy. When discussing issues, she's direct but not confrontational, focusing on facts and observable behavior. She might use phrases like 'As per the requirements...' or 'The observed behavior is...' and is careful not to make assumptions.

Personality traits

  • Meticulous
  • Diligent
  • Analytical
  • Systematic
  • Patient
  • Detail-oriented
  • Reliable
  • Methodical

Goals

  • Achieve a senior QA engineer position within the next five years.
  • Contribute to building a robust, automated testing suite for the product.
  • Develop expertise in performance and security testing.
  • Maintain a healthy work-life balance.
  • Save enough for a down payment on a small apartment.

Problems & frictions

  • Limited time and resources for comprehensive test coverage.
  • Inconsistent defect reporting from external sources.
  • The challenge of keeping test case documentation perfectly up-to-date.
  • Balancing manual testing with the desire to implement automation.
  • Occasional communication gaps between QA and development teams on bug severity.

Values

  • precision
  • repeatability
  • accountability
  • thoroughness
  • efficiency

Interests

  • test automation
  • bug triage
  • developer tools
  • performance testing
  • cross-browser compatibility

Media habits

  • Follows tech blogs and forums (Stack Overflow, Reddit's r/QualityAssurance)
  • Listens to tech podcasts during commute
  • Watches YouTube tutorials for new tools
  • Reads industry news on LinkedIn
  • Occasional participation in webinars

Questions & answers

Sudeva Namboothiri’s public research answers, newest questions first. Up to 10 per page.

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

    The primary reason I wouldn't try Screen Awesome this month is the sheer volume of manual testing I'm currently engaged in. My workflow relies heavily on meticulously documenting bugs with screenshots and annotations, which I do using free browser extensions and then manually placing them into Jira tickets. While Screen Awesome's privacy features are appealing, and the MP4 export is a plus, I need to see a clear pathway to how it integrates with my existing Jira process. The product states it's free and unlocked, with no paid features, so I wouldn't pay anything.
    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.