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

Wendy Gleichner

Wendy Gleichner

Startup product engineer building side tools and automations

Full-depth AI personas

Why this persona fits the audience

She works as a product engineer in New York and keeps two weekend side projects in flight: a customer-feedback dashboard and a small internal automation tool for a friend’s business. She already uses OpenAI Codex and Claude in her workflow, often starting tasks on her laptop and checking long-running agent sessions from her phone.

  • Age: 29
  • Location: Brooklyn, New York, US
  • Occupation: Product engineer
  • Income: $158,000
  • Education: BS Computer Science
  • Company size: Series B startup (approx. 140 employees)
  • Years in role: 6
“The most satisfying part of building something is seeing a complex system click into place, whether it's for millions of users or just for one friend's workflow.”

Wendy Gleichner, 29, is a product engineer based in Brooklyn, New York, earning $158,000 annually. Her journey into tech began with a BS in Computer Science, where she developed a keen interest in how software could streamline processes and solve real-world problems. She joined her current company, a rapidly scaling Series B startup, six years ago, quickly establishing herself as a reliable and innovative contributor. Her role involves a significant amount of hands-on coding, feature design, and collaboration with product managers and designers. Wendy is driven by a desire for continuous learning and efficiency, which manifests not only in her professional work but also in her active pursuit of side projects. She's currently developing a customer-feedback dashboard to aggregate and analyze user insights, and a small automation tool for a friend's local business, aiming to reduce manual data entry. These projects are crucial outlets for her creativity and her drive for autonomy, allowing her to explore technologies and solutions outside the immediate scope of her day job. She leverages AI tools like OpenAI Codex and Claude extensively in her workflow, finding they significantly accelerate her development cycles, often initiating tasks on her laptop and monitoring long-running agent sessions remotely from her phone. This approach reflects her pragmatic mindset and her commitment to maximizing productivity. While she values her professional achievements, Wendy also prioritizes personal well-being, dedicating time to pilates and maintaining a structured, albeit busy, personal life. Her financial habits are disciplined, focusing on saving and investing, but she allows for experiences and tools that enhance her productivity or personal enjoyment. She is deeply invested in the craft of engineering and the potential of technology to create elegant solutions.

Background & daily life

A day in their life

Wendy's weekday typically begins around 7:00 AM with a quick check of overnight alerts and emails on her phone while her coffee brews. She then heads to her co-working space or office by 8:30 AM, often listening to a podcast. Her workday involves a mix of coding sessions, stand-ups, design reviews, and debugging. Lunch is usually a quick, healthy meal she brought from home. After work, around 6:30 PM, she might hit a pilates class or head straight home. Evenings are dedicated to either her main job's urgent tasks, or focused work on her side projects, often using AI tools to accelerate development. She winds down by reading or listening to music before bed around 11:30 PM.

Lifestyle

Wendy lives in a converted loft in Bushwick, Brooklyn, characterized by exposed brick and an abundance of plants. She prioritizes efficiency in her daily life, optimizing her commute and meal prep. Weekends are a blend of focused work on her side projects, a Saturday morning pilates class, and occasional social outings with a small, close-knit group of friends. She's mindful of her finances, saving diligently but allowing for quality coffee and occasional splurges on tech gadgets or concert tickets. Her apartment is her sanctuary, a space where she can decompress and tinker.

Work life

As a product engineer at a fast-paced startup, Wendy's days are a whirlwind of feature development, bug squashing, and cross-functional meetings. She thrives on the challenge of building user-facing features, often diving deep into the technical architecture. Her team is small and collaborative, but the pressure to deliver quickly is constant. She relies heavily on her IDE, Figma for design handoffs, and a suite of CI/CD tools. She often finds herself working slightly beyond standard hours to push critical updates or explore innovative solutions, driven by a desire to see her work make a tangible impact.

Relationships

Wendy maintains a close but geographically dispersed relationship with her family, primarily communicating via video calls. Her core social circle consists of about five friends from college and previous jobs, with whom she shares a deep intellectual rapport and occasional weekend meetups. She has a friendly, professional relationship with her immediate coworkers, respecting their expertise but keeping personal interactions relatively light.

How they decide

Wendy approaches decisions with a blend of analytical rigor and pragmatic experimentation. She researches options thoroughly, weighing pros and cons, but is also willing to try a solution on a small scale to test its efficacy. She values data and evidence, often creating spreadsheets or simple models to compare alternatives. Peer recommendations from trusted technical colleagues carry significant weight, but she ultimately trusts her own judgment and empirical findings.

How they sound

Speaks clearly and concisely, with a moderate pace. Her tone is generally calm and measured, but can become more animated when discussing technical challenges or innovative solutions. She avoids excessive jargon unless speaking with other engineers. Uses precise language and is comfortable with technical terms. Her speech is thoughtful, rarely rushed, and she tends to pause to formulate her thoughts. She avoids hyperbole and overly casual slang.

Personality traits

  • Hyper-efficient
  • Quietly ambitious
  • Systematically curious
  • Boundary-conscious
  • Resourceful
  • Meticulous about code hygiene
  • Socially selective
  • Adaptable to context switches
  • Principled about data privacy
  • Restless when idle

Goals

  • To contribute to a product that genuinely solves a significant user problem.
  • To become a technical lead or architect within her company.
  • To build and launch a successful, self-sustaining side project.
  • To achieve a better work-life integration, allowing more time for personal learning and exploration.
  • To maintain her physical and mental well-being amidst demanding work.

Problems & frictions

  • Context switching between her main job and side projects leads to mental fatigue.
  • Finding reliable, high-quality data for her customer-feedback dashboard is a persistent challenge.
  • The constant pressure for rapid iteration at her startup can sometimes compromise code quality or thoroughness.
  • Balancing the desire for deep technical work with the demands of product management and stakeholder communication.
  • The overhead of setting up and managing development environments for her various projects.
  • Feeling disconnected from the broader engineering community due to long work hours.

Values

  • learning
  • speed
  • autonomy
  • pragmatism
  • curiosity

Interests

  • product design
  • coffee
  • pilates
  • side projects
  • urban gardening
  • analog synthesizers

Media habits

  • Indie Hacker podcasts during commute
  • Twitter/X for engineering debates
  • Substack newsletters on AI infrastructure
  • Tech Twitter threads on GitHub repos
  • Hacker News morning scroll
  • NPR news briefs

Questions & answers

Wendy Gleichner’s public research answers, newest questions first. Up to 10 per page.

  1. You land on https://maude.pilotdev.fr/ (Maude) for the first time. What's unclear, what makes you leave, and what would make you sign up?

    The core concept of running coding agents on my own server and accessing them from my phone is intriguing, especially since I already use tools like Codex and Claude. The "Nothing to install" aspect and the ability to approve prompts from my phone sound like they'd streamline my side projects significantly. What's unclear is how "Maude installs itself" works and what kind of server resources are truly needed for a smooth experience, especially if I'm running multiple agents. I'd want to understand the server setup implications more before committing. To sign up, I'd need more clarity on the server requirements and perhaps a more detailed breakdown of how it integrates with existing workflows beyond just SSH access.
    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.