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

Debbie Smith

Debbie Smith

side-project software engineer

Full-depth AI personas

Why this persona fits the audience

She is a Chicago-based software engineer who maintains a weekend Chrome extension for habit tracking, with roughly 80 paid users. She has no dedicated backend beyond static hosting and a small script that stores purchase status.

  • Age: 28
  • Location: Chicago, IL, US
  • Occupation: Senior software engineer
  • Income: $132k
  • Education: BS Software Engineering
  • Company size: mid-size tech company (approx. 500 employees)
  • Years in role: 4
“There's a quiet satisfaction in building something that works well, even if only a few people use it. It's about the craft.”

Debbie Smith discovered her passion for programming early, spending high school weekends tinkering with Python scripts and building simple websites. This led her to pursue a BS in Software Engineering, where she excelled, particularly in front-end development. Upon graduation, she joined a mid-size tech company in Chicago, quickly progressing to a Senior Software Engineer role within four years. Her current position involves working on a large, established enterprise application, where she contributes to feature development and maintains critical components of the system. She is adept with React and has a deep understanding of component-based architecture and modern JavaScript. Her side project, a habit-tracking Chrome extension, began as a personal tool to help her manage her own goals and has since grown into a small, self-sustaining venture. She keeps the technical stack deliberately lean, using static hosting for the extension's landing page and a simple Node.js script running on a cheap VPS to manage user subscriptions, storing purchase data in a basic PostgreSQL database. This minimal setup reflects her preference for efficiency and her desire to avoid the overhead of complex infrastructure. Recently, she decided to integrate a more robust payment processing solution, moving away from manual PayPal invoices for recurring subscriptions, a move that required careful research and implementation but ultimately saved her significant administrative time. Debbie views her side project not just as a potential income stream but as a proving ground for new technologies and a way to exercise her full-stack skills without corporate constraints. She is meticulous about her finances, saving aggressively towards early financial independence, and sees her extension as a small but meaningful step in that direction. Time is a precious commodity, carefully allocated between her demanding full-time job, personal well-being, and her passion project.

Background & daily life

A day in their life

Debbie's weekday typically begins around 6:30 AM with a pour-over coffee and 30 minutes of reading or planning her day. She leaves for her 9:00 AM to 5:30 PM job by 7:45 AM, listening to tech podcasts on the train. Her workday involves stand-ups, code reviews, feature development, and occasional mentoring sessions. Lunch is usually a quick affair at her desk while catching up on Hacker News. After work, she might hit the gym or run for an hour, followed by a simple dinner. Evenings are for decompressing, perhaps watching a documentary, working on her extension for an hour or two, or reading. She aims to be in bed by 10:30 PM.

Lifestyle

Debbie lives in a comfortably appointed one-bedroom apartment in Chicago's Lincoln Square neighborhood. She prioritizes experiences and personal development over excessive material possessions, channeling a significant portion of her income into savings and investments. Her weekdays are structured, but weekends are intentionally kept flexible, allowing for deep dives into her side project or spontaneous outings. She enjoys quiet mornings with a meticulously brewed pour-over coffee and a book, followed by a run along the lakefront. Social life is selective, focusing on a close-knit group of friends for meaningful conversation rather than large parties.

Work life

As a Senior Software Engineer, Debbie's workdays are a mix of collaborative problem-solving and focused coding. She spends a considerable amount of time in meetings, code reviews, and mentoring junior engineers, balancing these with dedicated blocks for feature development and bug fixing. The primary pressure comes from hitting quarterly roadmap targets and maintaining the stability of a complex, legacy codebase. She often feels the friction between the desire to innovate and the practical constraints of maintaining existing systems, leading her to seek creative outlets in her side project.

Relationships

Debbie maintains a close relationship with her parents, who live in the suburbs, and a small circle of college friends she sees regularly for dinners or weekend excursions. Her closest confidante is Sarah, a fellow engineer who offers a sounding board for both work challenges and personal projects. Her influence largely comes from respected figures in the tech community she follows online, whose work and approaches she admires.

How they decide

Debbie is a deliberate decision-maker. She tends to research options thoroughly, weighing pros and cons, and often seeks out case studies or examples of how others have tackled similar problems. She values practicality and evidence of effectiveness over flashy marketing. While she can be swayed by strong technical arguments or peer recommendations from trusted sources, she ultimately relies on her own analytical assessment.

How they sound

Speaks clearly and at a moderate pace, with a slight Midwestern lilt. Her tone is generally calm and analytical, often pausing to formulate her thoughts precisely. She uses precise technical language when discussing her work but avoids jargon in casual conversation. She tends to be understated and rarely uses hyperbole or overly emotive language, preferring factual descriptions.

Personality traits

  • Analytical
  • Detail-oriented
  • Pragmatic
  • Resourceful
  • Independent
  • Quietly ambitious
  • Methodical
  • Curious

Goals

  • Achieve financial independence through smart investing and diversified income streams.
  • Become a recognized expert in a niche area of front-end development.
  • Build her habit tracker extension into a sustainable, passive income source.
  • Continue learning and mastering new programming paradigms and tools.
  • Maintain a healthy work-life balance that supports both career and personal well-being.

Problems & frictions

  • Limited time and energy for her side project due to a demanding full-time job.
  • The technical debt and complexity of her company's main application.
  • Occasional feelings of isolation working on her extension solo.
  • Balancing the desire for perfect code with the need for rapid iteration.
  • The constant influx of new technologies making it challenging to stay current.

Values

  • personal growth
  • craftsmanship
  • financial discipline
  • usefulness
  • autonomy

Interests

  • habit tracking
  • React
  • running
  • bookstores
  • indie game development
  • coffee brewing

Media habits

  • Listens to tech podcasts during commutes and runs
  • Reads Hacker News and Reddit (r/programming, r/productivity)
  • Watches YouTube tutorials for new libraries and techniques
  • Follows key figures in front-end development on Twitter
  • Occasionally browses design blogs for inspiration

Questions & answers

Debbie Smith’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at ExtensionPay (https://extensionpay.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).

    Looking at ExtensionPay, the "no monthly fees, 5% transaction fee" structure is appealing because I'm still building up my user base. A 5% fee feels reasonable, especially since it covers a lot of complexity I'd rather not manage myself. I'd stop considering it if the fees jumped significantly, maybe above 10-12%, or if there were hidden costs. For that fee, I expect a reliable API that handles subscriptions, payment processing via Stripe, and secure licensing without me needing a backend. The biggest question for me is how well it scales with more users and how much administrative overhead it *truly* removes compared to my current setup. For now, I'm hesitant to commit to a monthly price until I see more predictable revenue, but if I had to estimate, I wouldn't want to pay more than $15 per month for this level of service, given my current ~80 paid users.
    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.