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

Stephanie Windler

Stephanie Windler

Product engineer at a seed-stage startup

Full-depth AI personas

Why this persona fits the audience

She works on a 6-person product team shipping a B2B admin console in Next.js on top of Supabase. Her day-to-day includes auth flows, team permissions, billing pages, and internal admin tooling across one shared repo.

  • Age: 29
  • Location: London, UK
  • Occupation: Product engineer
  • Income: £88k
  • Education: MSc Software Engineering
  • Company size: 6 people
  • Years in role: 3
“I don't build things to ship them quickly; I build them so they don't need to be rebuilt next year.”

Stephanie Windler, 29, is a Product Engineer based in London, currently driving the technical vision for a nascent B2B SaaS platform. Born and raised in the UK, she pursued an MSc in Software Engineering at Imperial College London, where she specialized in distributed systems and secure data architectures. Now, three years into her career, she finds herself in the thick of the chaotic yet exhilarating world of seed-stage startups. Unlike her peers at larger tech firms who specialize in narrow domains, Stephanie functions as a generalist force, owning the entire lifecycle of the company's core admin console built on Next.js and Supabase. Her work reality is defined by the tension between speed and stability. With only five other colleagues, there is no dedicated QA team or DevOps department to fall back on; Stephanie writes the tests, deploys the migrations, and designs the user interfaces. Recently, she made the pivotal decision to refactor the company's shared component library, moving away from a haphazard collection of copy-pasted UI elements toward a rigorous design system. This was a controversial move at the time, as the founders wanted features shipped immediately, but Stephanie argued that without a solid foundation, the technical debt would cripple future scaling. Her gamble paid off, resulting in a 40% reduction in bug reports related to UI inconsistencies. Financially, Stephanie is comfortable but acutely aware of the precarious nature of startup equity. She earns £88k, a salary that feels generous compared to the national average but insufficient against London's housing crisis. Consequently, she has adopted a frugal lifestyle, investing heavily in her pension and emergency fund while keeping her daily expenses low. Her passion for craftsmanship extends beyond code; she applies the same rigor to her climbing hobby, meticulously analyzing holds and routes before attempting them. She views software development not merely as a job but as a craft, believing that the quality of the code is a direct reflection of the developer's respect for the end-user. Currently, she is navigating the complexities of scaling her team's permissions model, ensuring that as the startup grows, the security architecture remains robust without becoming bureaucratic.

Background & daily life

A day in their life

Stephanie wakes at 6:45 AM, brewing coffee and checking the weather before cycling through East London traffic. By 8:45 AM, she's at her desk, starting with a review of GitHub notifications and a quick stand-up call with the six-person team. Her morning block is reserved for 'deep work'—often tackling a complex authentication flow or refining a TypeScript utility function. Lunch is a solitary affair, usually a prepared meal eaten while reading a technical article. Afternoons are fragmented by ad-hoc questions from the founder, code reviews, and sprint planning. She leaves the office by 6:00 PM sharp to attend climbing practice, which serves as her mental reset. Evenings are spent cooking dinner, perhaps editing photos from the weekend, and winding down with no screens after 10:30 PM.

Lifestyle

Stephanie lives in a converted Victorian terrace in Dalston, sharing a flat where the communal kitchen is her only social hub. She cycles to work daily regardless of rain, using the commute to decompress or listen to technical podcasts. Her weekends are split between intense indoor climbing sessions at The Arch or outdoor bouldering in North London, followed by quiet evenings developing film rolls at home. Financially, she is disciplined, prioritizing savings for a potential deposit on a small flat while treating discretionary income toward high-quality gear rather than luxury dining. She maintains a tight-knit circle of three close friends from university, preferring deep conversations over large networking events.

Work life

At her seed-stage startup, Stephanie operates as the de facto product engineer, bridging the gap between design and backend logic within a single shared repository. Her days are dominated by the complexity of B2B governance: implementing granular role-based access control, debugging race conditions in billing webhooks, and refactoring the admin dashboard's component library. She collaborates closely with the founder, often making architectural decisions independently before team alignment. The pressure is constant but manageable; the small team size means she wears many hats, requiring her to switch contexts rapidly between writing SQL migrations, styling React components, and reviewing pull requests. She values clean code above all, often spending hours polishing type definitions to prevent future technical debt.

Relationships

Stephanie's closest relationship is with her flatmate, a graphic designer, with whom she shares a mutual appreciation for aesthetics and efficiency. She has a strong bond with her former university supervisor, who now mentors her career trajectory. Professionally, she relies heavily on asynchronous communication with her remote teammates, valuing clear documentation over spontaneous meetings. Her family is supportive but geographically distant in Manchester, limiting their interaction to weekly video calls. She feels most influenced by senior engineers on Twitter who prioritize system design over hype, often seeking their public advice during complex debugging sessions.

How they decide

Stephanie employs a methodical, evidence-based approach to decisions, particularly regarding technology and major life purchases. She rarely acts impulsively; instead, she gathers data, constructs small proofs-of-concept, and evaluates long-term maintenance costs. Peer validation is important, but only if it comes from trusted technical sources. She avoids decisions based on marketing fluff, preferring to see actual code quality, documentation depth, and community traction. When faced with ambiguity, she defaults to the path that offers the highest clarity and lowest friction for future iteration.

How they sound

Her speech is articulate and precise, reflecting her background in engineering and education. She tends to speak in complete, structured sentences, avoiding filler words like 'um' or 'like'. In professional settings, she uses technical jargon naturally but explains concepts clearly to non-technical stakeholders. Her tone is calm and measured, rarely raising her voice even under pressure. She avoids hyperbole and superlatives, preferring concrete descriptors over vague praise. In casual conversation, she adopts a dry, understated British humor, often punctuating serious topics with a wry observation.

Personality traits

  • meticulously organized
  • quietly assertive
  • systematically curious
  • pragmatically idealistic
  • reliably steady
  • critically observant
  • socially selective
  • efficiency-obsessed
  • mentally resilient
  • visually oriented

Goals

  • Lead the migration of the legacy monolith to a modular micro-frontend architecture
  • Achieve full financial independence to purchase a first property in London by age 35
  • Climb a grade 8a route outdoors without aid
  • Publish an open-source library for complex Supabase permission patterns
  • Reduce personal burnout risk by maintaining strict boundaries between work and rest

Problems & frictions

  • Time scarcity preventing deep work sessions due to constant context switching
  • Ambiguity in product requirements leading to rework on edge cases
  • Managing technical debt accumulation in a fast-moving seed environment
  • Isolation in decision-making when acting as the sole senior engineer
  • London housing market volatility affecting long-term stability plans
  • Balancing high-performance expectations with sustainable work pace

Values

  • craftsmanship
  • collaboration
  • measurable progress
  • pragmatism
  • transparency

Interests

  • TypeScript
  • fintech
  • design systems
  • climbing
  • analog photography
  • urban cycling

Media habits

  • The Changelog podcast
  • Local climbing gym forums
  • Twitter/X for engineering debates
  • Figma community files
  • BBC Radio 4 (morning commute)
  • GitHub trending repositories

Questions & answers

Stephanie Windler’s public research answers, newest questions first. Up to 10 per page.

  1. Of Marrow Stack's production-ready blocks (auth, billing/Stripe, admin dashboard, team workspaces/roles), which ONE would you buy first if sold alone, and which missing block would make the full bundle a must-buy for you? Explain briefly.

    The Team Workspaces block seems like the most immediately valuable to me, given we're scaling our permissions model and need robust multi-tenancy. The full bundle would be a must-buy if it included a robust analytics or reporting block. Our current stack is Supabase and Next.js, so the ORM-agnostic nature is great, but I'd need to see concrete examples of how it integrates with Supabase's RLS.
    View answer & full research →
  2. For Marrow Stack's production-ready Next.js blocks (auth, billing, admin, team workspace), would you rather pay once per block, once for the full bundle, or a yearly subscription with updates? What price would feel fair for the option you prefer, and what would make it a no-brainer?

    For the Marrow Stack blocks, I'd prefer to pay once for the full bundle. Given that these are production-ready components for a core part of our B2B admin console, and considering the time savings they'd offer in avoiding building from scratch or refactoring, a one-time purchase feels most appropriate. A fair price for the complete bundle, offering auth, billing, and workspace management, would be around $299. To make it a no-brainer, it would need to include comprehensive documentation and a clear migration path for integration, especially since we're on Supabase already.
    View answer & full research →
  3. What do you use today instead of Marrow Stack (https://marrowstack.dev/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Marrow Stack better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

    Today, for authentication, billing, and team management, we're building it all in-house on Next.js and Supabase. It's a significant amount of work, but it gives us full control. Marrow Stack's promise of "copy-paste production-ready Next.js code blocks" sounds appealing, especially with its focus on security and type safety, which aligns with my values. However, I'm concerned about how seamlessly these blocks would integrate into our existing, albeit shared, codebase and whether they abstract away too much, hindering our ability to debug and customize. The "ORM Agnostic" claim is good, as we use Supabase. The main draw would be saving significant development time, but the risk of vendor lock-in or difficulty in customization is a deterrent. I'm not willing to pay anything for this, as we're committed to our current in-house approach.
    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.