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

Jessica Feeney

Jessica Feeney

Product operations analyst at a SaaS startup

Full-depth AI personas

Why this persona fits the audience

Works in a 28-person SaaS company where customer exports, webhook payloads, and CRM payload samples often arrive as JSON. She regularly pastes snippets into a browser tool, checks field structure, and turns them into tables for internal review in Sheets or Excel before sharing with support and product.

  • Age: 31
  • Location: Austin, Texas, US
  • Occupation: Product operations analyst
  • Income: $92k
  • Education: B.A. in Information Systems
  • Company size: 28 employees
  • Years in role: 3 years
“I just need the data to make sense, to show me what's actually happening so we can build better things. If it's messy, it's like trying to read a book with half the pages ripped out.”

Jessica Feeney, a 31-year-old Product Operations Analyst, has carved a niche for herself in the fast-paced world of SaaS startups. Growing up in a middle-class family in suburban Dallas, she developed an early aptitude for organization and problem-solving, often found meticulously cataloging her belongings or helping her parents navigate new software. This inclination led her to pursue an Information Systems degree at the University of Texas at Austin, where she honed her analytical skills and gained a foundational understanding of data structures. Upon graduation, she joined her current company, a 28-person SaaS firm, initially in a more general operations role before gravitating towards product operations due to her knack for data interpretation. Her income of $92k reflects her growing expertise and the critical nature of her contributions. Jessica’s work life revolves around making complex data accessible. She regularly receives customer exports, webhook payloads, and CRM samples, all often in JSON format. Her primary function involves taking these raw, sometimes unwieldy, data snippets, validating their structure using browser-based tools, and then meticulously transforming them into organized tables within Google Sheets or Excel. This process is vital for internal reviews, supporting the customer success team, and informing product development decisions. She recently advocated for a more consistent data logging strategy across new feature development, pushing back gently against engineering requests for ad-hoc data formats, emphasizing the long-term maintenance burden. She sees her role as a bridge, translating the technical intricacies of data into actionable insights for her colleagues. Outside of work, Jessica is focused on building a stable future; she's diligently saving for a down payment on a condo, a goal that shapes her practical approach to spending and her preference for reliable, long-term solutions over fleeting trends. Her apartment in Austin is her sanctuary, a space she's carefully curated for efficiency and calm. She views time as a valuable, finite resource, constantly seeking ways to optimize her workflows, both professionally and personally, to maximize her impact and personal fulfillment.

Background & daily life

A day in their life

Jessica's typical weekday starts around 7:00 AM with a quick check of urgent Slack messages and emails before making coffee. She arrives at the office by 8:30 AM, immediately diving into any critical data issues that arose overnight. Her mornings are often spent processing customer data requests, creating JSON-to-table conversions for support tickets, and preparing data for the daily product stand-up. After lunch, which she usually eats at her desk while catching up on industry news, she dedicates time to more in-depth analysis, documenting data flows, or collaborating with the product team on upcoming feature requirements. She often stays until 5:30 or 6:00 PM to ensure all immediate tasks are completed.

Lifestyle

Jessica enjoys a balanced life in Austin, prioritizing her career while maintaining personal pursuits. She lives alone in a modern one-bedroom apartment, finding solace in its quiet efficiency after busy workdays. Her evenings often involve experimenting with new recipes, occasionally meeting friends for happy hour at a local brewery, or diving into a complex spreadsheet for a personal project. She's mindful of her finances, aiming to save for a down payment on a condo within the next few years, which influences her practical spending habits. Weekend mornings are reserved for yoga or a long run at Zilker Park.

Work life

Jessica's role as a Product Operations Analyst is central to her professional identity. Her days are a constant juggle between proactive analysis and reactive problem-solving, often involving intricate data wrangling. She's the go-to person for translating raw JSON data from customer exports, webhook payloads, and CRM samples into digestible formats for her colleagues. This often means meticulously copying and pasting snippets into browser tools to validate structures before transforming them into organized tables in Google Sheets or Excel. The pressure to deliver accurate, timely information to support and product teams is ever-present, requiring her to maintain a high level of focus and precision.

Relationships

Jessica maintains strong connections with her close-knit group of college friends, often bonding over shared professional experiences and weekend outings. Her parents, living in a suburb outside of Dallas, are a source of steady support, though she occasionally feels pressure to visit more often. At work, she has a positive, collaborative relationship with her immediate team and a professional, respectful rapport with the product and engineering leads.

How they decide

Jessica is a methodical and research-oriented decision-maker. She prefers to gather all available information, weigh the pros and cons systematically, and often seeks input from trusted colleagues or relevant documentation before committing. She values reliability and evidence over quick fixes or flashy trends.

How they sound

Speaks with a clear, measured cadence. Tends to be direct and articulate, using professional language but capable of using industry-specific jargon when appropriate. She avoids overly casual slang or excessive emotional expression in professional settings, preferring to convey information logically and calmly. Her tone is generally helpful and earnest.

Personality traits

  • Methodical
  • Detail-oriented
  • Proactive
  • Organized
  • Analytical
  • Patient
  • Collaborative
  • Resourceful

Goals

  • Achieve a senior product operations role within 5 years.
  • Develop expertise in data pipeline management and automation.
  • Contribute to the strategic roadmap of the company through data insights.
  • Mentor junior analysts as the team grows.
  • Purchase her first property in Austin.

Problems & frictions

  • The manual, repetitive nature of converting JSON snippets is time-consuming and prone to minor errors.
  • Lack of standardized data formats across different customer integrations.
  • Balancing urgent data requests from support with long-term analytical projects.
  • Communicating complex data findings clearly to non-technical stakeholders.
  • Keeping up with the rapid pace of product development and new feature releases.

Values

  • clarity
  • reliability
  • cross-team alignment
  • efficiency
  • data integrity

Interests

  • product analytics
  • spreadsheets
  • workflow automation
  • SQL
  • system design

Media habits

  • Reads industry newsletters (e.g., Stratechery, Product Hunt)
  • Listens to podcasts during commutes (e.g., This Week in Startups, Acquired)
  • Follows tech influencers on LinkedIn and Twitter
  • Uses Reddit for niche technical discussions (e.g., r/ProductManagement, r/SQL)
  • Watches YouTube tutorials for new software tools

Questions & answers

Jessica Feeney’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at jsontables (https://www.jsontables.com): what price would make it a no-brainer for you, and at what price would you stop considering it? What would you expect to get for that money? Also say the maximum you would pay per month in USD (0 if nothing).

    This tool looks really promising for quickly converting JSON snippets into tables, which is a huge time saver for me. The fact that it's free and works entirely in the browser addresses my concerns about data privacy. If there were a paid tier that offered more advanced features, like handling larger files beyond 10MB or perhaps an API for automation, I could see myself paying around $15-$20 per month. I'd expect robust support and maybe batch processing capabilities for that price. If it remained just the free version, it's already a no-brainer for basic use.
    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.