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

Aadrika Kakkar

Aadrika Kakkar

QA engineer on an edtech team

Full-depth AI personas

Why this persona fits the audience

Works on a 6-person edtech engineering team in Pune and does daily browser regression checks on sign-up, lesson playback, and payment flows. Uses spreadsheets, Jira, and a mix of free Chrome extensions plus handwritten notes to compare behavior across builds because the team has a small testing budget.

  • Age: 24
  • Location: Pune, India
  • Occupation: QA Engineer
  • Income: INR 12 lakh
  • Education: BE Information Technology
  • Company size: Small (6-person engineering team)
  • Years in role: 2
“Every pixel, every click, every flow has to be right. If it's not perfect, it's not done.”

Aadrika Kakkar, 24, is a dedicated QA Engineer working for an edtech startup based in Pune. Growing up in a middle-class family, she was always drawn to the logic and order of technology, which led her to pursue a BE in Information Technology. Her current role on a small, six-person engineering team is a testament to her meticulous nature and commitment to quality, especially given the team's limited testing budget. She lives with her parents and younger brother, a setup that provides stability but also means her personal time is carefully managed. Her income of INR 12 lakh allows for comfortable living and a growing savings account, with a clear goal of future financial independence, perhaps owning her own apartment someday. Aadrika’s professional life is defined by her rigorous approach to manual testing. She spends her days performing critical browser regression checks on the platform's sign-up, lesson playback, and payment functionalities. The team's budget constraints mean she’s become adept at leveraging free Chrome extensions and maintaining detailed spreadsheets, often supplementing these with handwritten notes to track subtle behavioral differences between software builds. This hands-on, detail-oriented work aligns perfectly with her values of precision and dependability. Recently, she advocated for a more structured approach to documenting browser-specific quirks, a decision that required careful justification to the product manager, highlighting the potential impact on user experience and the long-term cost of fixing such issues later. She’s also begun exploring basic test automation concepts in her own time, driven by a desire for continuous learning and a pragmatic understanding that manual testing alone has its limits, especially as the product scales.

Background & daily life

A day in their life

Aadrika's weekday begins around 7:00 AM with a quick breakfast and helping her mother with household chores before her commute to the office. By 9:30 AM, she's logged into her workstation, checking Jira for urgent bugs and planning her day's regression suite. The morning is dedicated to executing test cases for the sign-up and lesson playback flows, meticulously documenting any deviations in her spreadsheet. Lunch is a brief affair, often with colleagues discussing work or weekend plans. The afternoon involves testing the payment gateway, a critical flow requiring extra attention, and then tackling any new bugs reported. She often stays a bit late, reviewing her notes and preparing for the next day's testing cycle, aiming to leave by 7:00 PM.

Lifestyle

Aadrika lives a structured life in a joint family in Pune, sharing a room with her younger brother. Her days are regimented, balancing work with family responsibilities and personal study. She prioritizes saving a portion of her income, aiming for future financial independence and perhaps a down payment on her own apartment. Evenings are often spent reviewing test cases or learning new testing methodologies. Weekends might involve a quiet outing with a few close friends or catching up on family visits. She’s health-conscious, opting for home-cooked meals and trying to fit in a brisk walk when time permits.

Work life

As a QA Engineer on a lean edtech team, Aadrika's work is characterized by a constant push for quality under tight resource constraints. Her primary focus is on meticulous manual regression testing, ensuring the core user journeys—sign-up, lesson playback, and payment—remain stable across different browser versions. She juggles Jira tickets, meticulously updates spreadsheets with test results, and relies on a collection of free Chrome extensions to help identify inconsistencies. The team's small testing budget means she often has to get creative, documenting browser quirks and edge cases in handwritten notes. Her colleagues are a mix of seasoned developers and a junior product manager, all working towards rapid feature deployment.

Relationships

Aadrika is close to her parents, who provide a stable home environment and often offer practical advice. Her younger brother is a source of lighthearted banter. Her core social circle consists of a few college friends, with whom she shares career aspirations and personal updates. Her immediate team members are her primary professional influence, particularly the lead developer, whose pragmatic approach to problem-solving she admires.

How they decide

Aadrika is a cautious and research-driven decision-maker, especially when it comes to work-related tools or significant personal purchases. She meticulously gathers information, compares options, and often seeks input from trusted colleagues or online communities before committing. For smaller, everyday decisions, she relies on established routines and efficiency.

How they sound

Aadrika speaks with a clear, measured cadence, her tone generally polite and professional. She uses standard Marathi and Hindi in casual conversation but defaults to precise English at work. She avoids overly casual slang or jargon, preferring to articulate her points directly and logically. Her speech can become slightly more rapid when discussing a complex bug or a particularly frustrating browser inconsistency, betraying a hint of her underlying conscientiousness and mild neuroticism.

Personality traits

  • Meticulous
  • Diligent
  • Analytical
  • Patient
  • Detail-oriented
  • Methodical
  • Slightly anxious
  • Pragmatic
  • Observant

Goals

  • Achieve a senior QA engineer position within the next five years.
  • Master at least one test automation framework.
  • Contribute to improving the team's testing processes and documentation.
  • Save enough for a down payment on a small apartment.
  • Become proficient in performance testing.

Problems & frictions

  • Limited budget for essential testing tools and services.
  • Time pressure to complete thorough regression testing before new releases.
  • Inconsistent browser behavior that's difficult to replicate and document.
  • Balancing manual testing depth with the need for faster feedback cycles.
  • Keeping up with the rapid pace of edtech product development and new features.

Values

  • precision
  • dependability
  • continuous learning
  • efficiency
  • thoroughness

Interests

  • manual testing
  • test cases
  • browser quirks
  • automation basics
  • exploratory testing
  • user experience flows

Media habits

  • Follows tech blogs and QA forums online
  • Watches YouTube tutorials on testing tools and techniques
  • Listens to podcasts during commute
  • Uses LinkedIn for professional networking
  • Reads tech news aggregators

Questions & answers

Aadrika Kakkar’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: Maker launch on TinyLaunch: AI devtools in the browser you're already signed into. the product is an AI browser automation extension and MCP server for Chrome, Edge, Firefox,… What is the single biggest problem you have there right now? Be specific about what it costs you (time, money, customers) and what you have already tried.

    AI devtools within the browser sounds interesting, especially for automating browser regression checks. My biggest challenge right now is the inconsistency we see across different browsers, particularly with our payment flows. Documenting these quirks manually, using spreadsheets and handwritten notes, takes up so much time – easily an extra 5-7 hours a week during busy release cycles. We have a very limited budget for new tools, so finding something effective that doesn't break the bank is key. I'm not sure how something like this integrates with our existing Jira workflow or if it could even handle the specific, complex edge cases we encounter. What kind of results can it actually generate for us compared to what I'm doing now?
    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.