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

Eleanor Wunsch

Eleanor Wunsch

Product engineer at a remote SaaS company

Full-depth AI personas

Why this persona fits the audience

At a 5-person remote startup, she covers both UI fixes and backend tweaks, moving between customer-facing tickets and small internal tools. She mostly relies on free autocomplete, Stack Overflow, and hand-built code templates, with implementation details tracked in Notion and spreadsheets.

  • Age: 31
  • Location: Boston, MA, USA
  • Occupation: Product engineer
  • Income: $122k/year
  • Education: BSc Information Systems
  • Company size: 5
  • Years in role: 3
“The best code is the kind you barely have to think about, both to write and to maintain.”

Eleanor Wunsch, 31, is a product engineer deeply embedded in the fast-paced world of a five-person remote SaaS startup. Hailing from Boston, MA, she earned her BSc in Information Systems, a degree that provided a solid foundation for her current role. Her professional journey has been characterized by a need to be versatile; she seamlessly transitions between fixing UI glitches reported by users and optimizing backend processes that keep the service running smoothly. This dual responsibility means her days are a constant exercise in context-switching, moving from customer support tickets to internal tool development. Her technical toolkit is lean and practical, heavily relying on the ubiquitous Stack Overflow for complex problems, a suite of custom-built code templates she’s meticulously crafted over time, and the free tier of popular autocomplete tools. Implementation details, project plans, and even bug tracking are meticulously managed within Notion and a series of interconnected spreadsheets, reflecting her organized and detail-oriented nature. She thrives in environments where adaptability is key, valuing team harmony and practical, efficient solutions above all else. Her income of $122k/year allows for comfortable living and diligent saving, but she remains budget-conscious, always evaluating the true value of any investment, whether in time or money. Eleanor is driven by a desire to build things that work well and solve real problems, finding satisfaction in the tangible impact of her code. She recently spent two weeks refactoring a critical data processing module, a task that required deep dives into legacy code and careful coordination with the company's sole backend developer to minimize disruption. This project, while challenging, ultimately improved performance by 15% and reduced error rates, reinforcing her belief in the power of focused, pragmatic engineering.

Background & daily life

A day in their life

Eleanor's typical weekday begins around 7:30 AM with coffee and a quick scan of overnight notifications and emails. By 8:30 AM, she's logged into Slack and her IDE, tackling the most pressing customer-facing bug report. Mid-morning often involves a stand-up meeting with her team, followed by focused work on a backend feature she's been developing. Lunch is usually a home-cooked meal eaten at her desk while catching up on Hacker News. The afternoon might involve pair programming on a UI fix, updating documentation in Notion, or troubleshooting a deployment issue. She aims to log off by 6:00 PM, often followed by a run or some time in the kitchen.

Lifestyle

Eleanor lives in a compact but well-organized one-bedroom apartment in Somerville, just outside Boston. She's a creature of habit, starting her day with a quick run along the Charles River or a home workout before diving into work. Her evenings are often spent experimenting in the kitchen, trying out new recipes from blogs or cookbooks, or occasionally diving into a personal coding project. She's financially responsible, saving diligently for future travel and potential homeownership, but doesn't shy away from investing in quality tools that genuinely improve her life or work. Socially, she prefers smaller gatherings with close friends over large parties.

Work life

As a product engineer at a lean startup, Eleanor's days are a dynamic mix of urgent customer issues and proactive feature development. She's the go-to for both front-end bugs and back-end performance tweaks, often context-switching between a UI ticket and a database optimization. Her toolkit is intentionally lean: VS Code with custom snippets, extensive use of Stack Overflow, and Notion for documenting everything from API changes to user feedback. Spreadsheets are her fallback for tracking metrics or project timelines. The small team size means direct impact is visible, but also that everyone wears multiple hats, requiring constant adaptability and problem-solving.

Relationships

Eleanor maintains close ties with her parents and a younger sibling, with whom she has weekly video calls. Her core friend group consists of about five people, mostly met through university or previous jobs, who share similar interests in tech and personal growth. They often exchange recommendations for books, tools, or local events. Her direct manager, the CTO, is her primary professional influence, valuing her pragmatic approach and technical contributions.

How they decide

Eleanor is a methodical decision-maker. She researches options thoroughly, weighing pros and cons, often creating comparison tables or flowcharts for complex choices. She values peer recommendations but ultimately trusts her own analysis and practical experience. She's not impulsive but will act decisively once she's confident in a direction, especially if it addresses a clear pain point.

How they sound

Speaks clearly and at a moderate pace, with a tendency towards precise language. Avoids excessive jargon when speaking to non-technical people but uses industry terms naturally with peers. Her tone is generally calm and measured, even when discussing challenging issues. She might use phrases like 'That makes sense,' 'Let's break that down,' or 'From a practical standpoint...' She's not overly effusive but conveys genuine enthusiasm for elegant solutions.

Personality traits

  • resourceful
  • detail-oriented
  • pragmatic
  • collaborative
  • analytical
  • proactive
  • organized
  • calm under pressure

Goals

  • Contribute to a product that genuinely solves user problems
  • Achieve a better work-life balance as the company scales
  • Deepen her expertise in scalable backend architecture
  • Mentor junior engineers in the future
  • Travel to Japan and experience its culture firsthand

Problems & frictions

  • Context switching fatigue from juggling diverse tasks
  • Limited bandwidth for deep architectural refactoring
  • Reliance on manual processes for certain documentation and tracking
  • Occasional frustration with the limitations of free tooling
  • Balancing rapid feature delivery with long-term code quality

Values

  • adaptability
  • team harmony
  • practicality
  • efficiency
  • continuous learning

Interests

  • startup tools
  • running
  • home cooking
  • indie game development
  • productivity hacks

Media habits

  • Hacker News
  • Reddit (r/programming, r/cscareerquestions)
  • TechCrunch
  • The Verge
  • YouTube tech channels (e.g., Fireship, Ben Eater)

Questions & answers

Eleanor Wunsch’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: Show HN launch (163 pts, 2024-02-22): the product, the first code completion tool with 300k token context. Site shows pricing/signup. 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.

    A 300k token context window is certainly impressive, especially for a Show HN launch. My biggest problem right now is the sheer volume of context-switching between UI fixes and backend tweaks. We're a small team, and I'm often pulled in many directions. While I rely on free autocomplete and Stack Overflow, implementing more advanced tools feels like a significant investment of time and money we just don't have budgeted. I'd need to see a clear, immediate productivity boost to justify exploring a new tool, especially given our current reliance on lean, existing solutions and Notion for tracking.
    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.