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

Sanne Wagenaar

Sanne Wagenaar

Frontend developer at startup

Full-depth AI personas

Why this persona fits the audience

Works on a 3-person product team in Amsterdam and already pays for a hosted screenshot service used in CI checks and customer-facing documentation. Sends captured images and PDFs into GitHub issues, Confluence pages, and release notes.

  • Age: 27
  • Location: Amsterdam, Netherlands
  • Occupation: Frontend developer
  • Income: €65,000
  • Education: B.Sc. Informatics
  • Company size: Startup (approx. 15 employees)
  • Years in role: 3
“The best code is the kind you don't have to think about later.”

Born and raised in Utrecht, Sanne developed an early fascination with how things worked, a trait that naturally led her to computer science. She excelled academically, earning a B.Sc. in Informatics from the University of Amsterdam, where she discovered a passion for frontend development and the tangible impact of well-crafted user interfaces. After a brief stint at a larger consultancy firm, she sought a more dynamic environment and joined her current startup two years ago. She's deeply invested in her role, appreciating the autonomy and the direct influence she has on the product. Sanne is pragmatic about her finances, viewing her income as a means to build a secure future and fund her continuous learning. She values her time immensely, optimizing her routines to maximize both productivity and personal well-being. Recently, she's been focused on refining their automated visual testing suite, a project that requires meticulous attention to detail and a deep understanding of their current screenshot API’s capabilities and limitations. She's been pushing for better integration between their CI/CD pipeline and documentation generation, recognizing the potential for errors when manual steps are involved. This involves ensuring the API reliably captures specific states of their web application for regression checks and customer guides, and she recently approved a small but consistent monthly spend on a hosted service to ensure this process is automated and reliable, rather than relying on ad-hoc scripts or manual work.

Background & daily life

A day in their life

Sanne's day typically starts around 7:30 AM. After a quick breakfast and checking personal messages, she cycles to the office, arriving by 9:00 AM. The morning is usually dedicated to focused coding, tackling tickets from their Kanban board, or pair programming. She dedicates a block of time around lunchtime to reviewing documentation and integrating any necessary updates for their screenshot service, which currently involves tweaking API parameters for specific PDF output formats. The afternoon involves team stand-ups, code reviews, and addressing urgent bug fixes or collaborating with the backend developer on API integrations. She usually leaves around 6:00 PM, heading home for dinner and perhaps an hour of personal learning or relaxing before bed.

Lifestyle

Sanne lives in a shared apartment in Amsterdam-Noord, a trendy but still developing area she chose for its slightly lower rent and good cycling infrastructure. She’s disciplined about her routine, cycling to work daily and hitting the gym three times a week. Her social life is active but focused; she prefers intimate dinners with close friends or attending local tech meetups over large parties. Financially, she's responsible, saving consistently towards a down payment for her own apartment, and prioritizes experiences and tools that enhance her productivity or well-being over fleeting luxuries.

Work life

Working in a lean startup means Sanne wears multiple hats, but her core focus is the frontend. The team is small, fostering a high degree of collaboration and shared responsibility, which she thrives on. Her current challenge involves optimizing the deployment pipeline for their core product, specifically integrating automated visual regression testing to catch UI bugs early. This requires careful coordination between frontend and backend, and she’s been refining the scripts that trigger screenshots via API for these checks. The pressure is constant but manageable, driven by shared goals and a genuine belief in the product.

Relationships

Sanne maintains strong ties with her parents and younger brother, visiting them monthly. Her close-knit group of university friends provides her primary social support. Within her startup, she has a respectful working relationship with her two colleagues, the backend lead and the product owner, appreciating their direct communication style.

How they decide

Sanne approaches decisions methodically. For work-related tools and processes, she researches extensively, comparing features, reading documentation, and checking community feedback. She values practical solutions that integrate well into existing workflows and often discusses significant choices with her immediate colleagues before committing, especially if it impacts shared resources or team processes.

How they sound

Speaks with a clear, measured cadence. Uses precise technical language when discussing work but is casual and friendly in social contexts. Avoids excessive slang or overly informal phrasing, even with close friends. Her tone conveys competence and thoughtful consideration. When stressed, her speech might become slightly more rapid but remains articulate.

Personality traits

  • meticulous
  • organized
  • detail-oriented
  • pragmatic
  • dedicated
  • methodical
  • slightly reserved
  • problem-solver

Goals

  • Become a senior frontend engineer within 3 years
  • Contribute to an open-source UI library
  • Achieve financial independence early
  • Mentor junior developers
  • Master advanced performance optimization techniques

Problems & frictions

  • Balancing feature development speed with robust testing
  • Onboarding new team members effectively
  • The overhead of managing multiple, disparate developer tools
  • Maintaining high code quality under tight deadlines
  • Ensuring consistent visual output across different environments

Values

  • clean workflows
  • build quality
  • accountability
  • efficiency
  • craftsmanship

Interests

  • web performance
  • UI systems
  • dev tooling
  • API design
  • modern CSS

Media habits

  • Reads Smashing Magazine and CSS-Tricks daily
  • Follows key tech figures on Twitter/X and Mastodon
  • Listens to 'Syntax.fm' and 'ShopTalk Show' during commutes
  • Watches YouTube tutorials on new JS frameworks
  • Occasional lurker on Stack Overflow for complex issues

Questions & answers

Sanne Wagenaar’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: Maker launch on TinyLaunch: Screenshot any website with one API call. Free to start.. the product is a screenshot API for developers. One HTTP request turns a URL, HTML or Markdown… 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.

    The biggest problem for us right now with screenshotting is reliability and integration. We're already paying for a hosted service to ensure consistent captures for CI checks and documentation, but it's not always perfect. Sometimes the API calls time out, or the output format isn't quite right for our Confluence pages, which means I or one of my colleagues has to manually intervene. That wastes valuable development time – easily a few hours a week collectively when things go wrong. We’ve tried tweaking parameters and checking network latency, but it’s a constant battle to get exactly what we need without manual workarounds.
    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.