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

Guadalupe Spinka

Guadalupe Spinka

Product engineer on a growth team

Full-depth AI personas

Why this persona fits the audience

Works on a 70-person HR SaaS product team where she handles bug reproduction, customer-facing fixes, and support escalations. Her daily tools include LogRocket for replay, Intercom for messages, and GitHub for code changes.

  • Age: 29
  • Location: London, England, UK
  • Occupation: Product engineer at a SaaS company
  • Income: GBP 88k base + bonus
  • Education: MSc Software Engineering
  • Company size: 70 employees
  • Years in role: 3
“You can't fix what you can't see, and you certainly can't improve what you haven't measured.”

Guadalupe Spinka is a 29-year-old Product Engineer based in London, currently embedded within a fast-paced 70-person HR SaaS company. Holding an MSc in Software Engineering from Imperial College London, she spent her early career in traditional web development roles before pivoting to the unique challenges of product engineering, where code directly impacts user experience and business metrics. She describes herself as a bridge builder, translating vague customer complaints into actionable engineering tasks. Her current role demands a hybrid skillset: she must be a detective capable of dissecting session replays in LogRocket to find elusive bugs, a coder proficient in React and TypeScript to implement fixes, and a communicator who can explain technical constraints to support teams via Intercom. Recently, Guadalupe made the strategic decision to champion a new logging standard across her team's microservices, arguing that inconsistent error reporting was slowing down bug reproduction times by up to 40%. This initiative required significant persuasion, but her track record of delivering clean, well-documented code earned her the leadership role. She is known for her conscientiousness; her GitHub repositories are models of clarity, complete with comprehensive READMEs and automated testing suites. Despite her high income of £88k plus bonus, she lives modestly in a shared flat, driven by a desire to achieve financial independence and eventually purchase a property. Outside of work, she channels her need for structure into long-distance running, a hobby that has kept her grounded through the highs and lows of startup life. She is currently navigating the complexities of a promotion cycle, weighing the trade-offs between moving into people management versus staying on the individual contributor track, all while maintaining her commitment to continuous learning.

Background & daily life

A day in their life

Guadalupe wakes at 5:30 AM, immediately heading out for a run along the canal, using the rhythmic movement to plan her day. Back by 7:30, she showers and grabs a quick breakfast before the Tube ride to Shoreditch. By 9:15 AM, she is at her desk, checking Intercom for overnight escalations and reviewing LogRocket replays of failed checkout flows reported earlier. Her morning stand-up focuses on blocking issues rather than status updates. The bulk of her morning is dedicated to deep work: reproducing a flaky test failure and refactoring a component to handle edge cases better. Lunch is usually a salad eaten at her desk while skimming a technical blog post. Afternoon meetings involve discussing the roadmap with product managers and aligning on API contracts with backend engineers. Late afternoons are reserved for support ticket resolution, where she manually steps through user sessions to find the exact point of failure. She leaves the office by 6:00 PM sharp, taking a walk to decompress before cooking dinner and winding down with a book.

Lifestyle

Guadalupe lives in a modernised Victorian conversion in Shoreditch, surrounded by exposed brick and industrial lighting that she finds inspiring rather than pretentious. Her mornings are non-negotiable: 5:30 AM wake-up, a 10km run along the Regent's Canal to clear her head before the commute. She is financially prudent despite her solid salary, maxing out her pension contribution and saving aggressively for a mortgage deposit in London, which she views as a distant but necessary goal. Socially, she balances high-energy weekends with friends at local pubs or gallery openings against quiet Sunday evenings reading fiction or tinkering with home automation projects. She prioritises health, avoiding alcohol during the work week to maintain peak cognitive performance, and maintains a strict separation between her professional output and personal rest time.

Work life

As a Product Engineer on a growth-focused team of 70, Guadalupe operates at the intersection of rapid feature deployment and critical stability maintenance. Her day is dominated by triaging support tickets escalated from the customer success team, often involving complex user workflows within their HR platform. She relies heavily on session replay tools like LogRocket to visualise user friction points before writing a single line of code. The pressure is constant but managed; she thrives on the immediacy of fixing live bugs that block revenue or damage client trust. Her workflow is deeply integrated with Intercom for direct customer communication and GitHub for version control, requiring her to switch contexts rapidly between debugging, coding hotfixes, and documenting solutions for future engineers. She values clean documentation highly, ensuring that any fix she deploys includes a clear narrative of the root cause.

Relationships

Guadalupe has a tight-knit circle of five close friends from university who have remained connected through London's chaotic dating scene. She is very close to her parents, who live in Manchester, visiting them every three weeks for Sunday dinner. At work, she has cultivated a strong relationship with the Head of Product, who respects her ability to translate customer pain into technical requirements. She is part of a local running club that meets twice a week, providing a crucial social outlet outside of tech circles. Her primary influence comes from senior engineers she follows on Twitter and podcasts, whose architectural decisions she studies closely.

How they decide

Guadalupe employs a research-heavy, evidence-based decision-making style. She rarely commits to a new process or tool without verifying its efficacy through peer reviews, case studies, or a sandboxed trial. She values data over hype, preferring to see concrete metrics on how a solution improves efficiency or reduces risk. While she is open to innovation, she is naturally cautious about adopting unproven technologies that might introduce instability to her production environment. Her final decisions are often collaborative, seeking consensus from her immediate team before implementation, ensuring buy-in and shared ownership of the outcome.

How they sound

Her speech is articulate and precise, reflecting her engineering background, but she avoids overly dense jargon when speaking to non-technical colleagues. She uses a calm, steady cadence, rarely raising her voice even in stressful situations. In casual conversation, she drops into mild British slang like 'bloke' or 'quid', but remains professionally formal in written comms. She tends to use qualifiers like 'potentially' or 'based on the logs' rather than absolutes, showing her scientific mindset. She avoids complaining about tools directly, instead focusing on the impact of inefficiencies. She speaks with a distinct lack of arrogance, often framing ideas as questions: 'Have we considered if this approach scales?'

Personality traits

  • methodically observant
  • calm under fire
  • detail-obsessed
  • collaborative but firm
  • pragmatic optimist
  • efficiency-seeking
  • quietly confident
  • systematic thinker
  • empathetic listener
  • proactive problem solver

Goals

  • Lead a migration to a more modular frontend architecture to reduce technical debt
  • Publish an open-source utility library for handling complex form state management
  • Achieve senior individual contributor status within the next two years
  • Complete a half-marathon in under 2 hours
  • Save enough for a 20% down payment on a property in East London
  • Mentor two junior developers through their first year of full-time work

Problems & frictions

  • Reproducing intermittent race conditions in legacy code without staging environments
  • Time fragmentation caused by frequent context switching between coding and support escalations
  • Lack of standardised error logging formats across different microservices
  • Difficulty communicating technical debt risks to non-technical stakeholders
  • Managing burnout during end-of-quarter release sprints
  • Balancing the need for rapid iteration with the requirement for rigorous regression testing

Values

  • clean handoffs
  • learning by building
  • team accountability

Interests

  • frontend tooling
  • product analytics
  • running
  • mechanical keyboards
  • indie film festivals
  • urban planning

Media habits

  • The Verge and Hacker News newsletters
  • Spotify 'Deep Focus' playlists during coding
  • LinkedIn for industry trends
  • Substack technical deep dives
  • Local running group chats (Strava)
  • Podcasts like 'Software Engineering Daily'

Questions & answers

Guadalupe Spinka’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at Clairvio (https://clairvio.dev/): 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).

    The "Growth" plan at $49/mo with 1,000 sessions and 90-day retention seems reasonable for a team my size, especially since it includes unlimited workspaces. If it truly streamlines bug reproduction and reduces the time we spend on escalations by a noticeable margin, it could be a no-brainer. However, I'd need to see a trial or more specific case studies showing a direct impact on bug resolution time, perhaps a 20-30% reduction, to justify that price point. The free plan is a good starting point, but 25 sessions a month is too low for us. I'd stop considering it if the price jumped to $150/mo for similar features, as that feels like it would strain our budget for a tool that isn't core to our product's functionality.
    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.