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

Xaver Arens

Xaver Arens

product engineer at a seed startup

Full-depth AI personas

Why this persona fits the audience

He is the only frontend engineer at a 4-person Berlin SaaS startup, building a customer portal and internal admin in Next.js. The team uses a shared internal starter with auth, role checks, and onboarding flows that gets cloned for each new product line.

  • Age: 28
  • Location: Berlin, Germany
  • Occupation: Product engineer
  • Income: €72k
  • Education: MSc Software Engineering
  • Company size: 4
  • Years in role: 2
“The real challenge isn't just building features, it's building them in a way that doesn't become a tangled mess a year from now.”

Born and raised in a quiet university town in Bavaria, Xaver Arens developed an early fascination with how things work, which naturally led him to computer science. His academic journey culminated in a Master's degree in Software Engineering from a reputable German university, where he honed his theoretical knowledge and practical coding skills. He gravitated towards frontend development due to its immediate visual feedback and the intricate logic required to create seamless user experiences. After a brief stint at a larger, more established tech company where he felt stifled by bureaucracy, Xaver sought the dynamic environment of a startup. He joined his current Berlin-based SaaS company two years ago, drawn by the promise of building something impactful from the ground up. As the sole frontend engineer in a team of four, he's instrumental in shaping the user-facing aspects of their product. His primary focus is on developing and maintaining the customer portal and internal admin interfaces using Next.js. A significant part of his role involves nurturing and evolving the company's shared internal starter kit, a crucial piece of infrastructure that includes pre-built authentication, role-based access control, and onboarding workflows. This starter kit is designed to be cloned for each new product line, emphasizing efficiency and consistency. Xaver is deeply committed to code quality and maintainability, often spending extra time refactoring or writing comprehensive tests to ensure the long-term health of the codebase, even under the pressure to ship features rapidly. He views his work not just as coding, but as engineering robust solutions. His income of €72k reflects his specialized skills and the demands of his role in a competitive tech hub like Berlin. He lives frugally, prioritizing savings for future investments and potential property ownership, viewing financial stability as a key component of long-term security. His personal time is often dedicated to further learning, cycling, and maintaining a small but strong social circle, balancing the intense demands of startup life with personal well-being.

Background & daily life

A day in their life

Xaver's day typically begins around 8:00 AM with a strong filter coffee and a quick scan of Hacker News and his team's Slack channels. By 9:00 AM, he's at his standing desk, diving into the day's primary task: implementing a new feature for the customer portal, likely involving complex state management in React. He'll spend a few hours coding, punctuated by brief syncs with the backend team to clarify API endpoints. Lunch is usually a quick, healthy meal prepared the night before. The afternoon might involve code reviews for a colleague, tackling a bug reported by QA, or refining the shared internal starter kit based on recent learnings. He often works until 6:30 PM or later, especially if a critical bug needs squashing or a deployment is imminent. Evenings might include a short bike ride to clear his head before dinner.

Lifestyle

Xaver lives in a shared flat in Prenzlauer Berg, a compromise for Berlin rent prices, though he dreams of a small place with a dedicated home office. His evenings are often spent coding on personal projects or diving deep into technical documentation. Weekends are a mix of long cycling trips through Brandenburg's forests and catching up with a small circle of close friends, usually over craft beer at a local Kneipe. He's conscious about his health, opting for home-cooked meals and regular exercise, but occasionally indulges in late-night coding sessions fueled by strong coffee. Financial discipline is key; he saves diligently, aiming for future stability and perhaps a down payment on a property.

Work life

As the sole frontend engineer at a nascent SaaS startup, Xaver shoulders significant responsibility. His days are a whirlwind of building features for the customer portal and internal admin tools, all within their Next.js framework. He's deeply invested in the shared internal starter kit, constantly refining its auth, role checks, and onboarding flows, knowing it's the bedrock for future product lines. Collaboration with the two backend engineers and the product manager is constant, often involving whiteboard sessions and detailed Slack discussions. The pressure to ship quickly is palpable, but Xaver prioritizes maintainability, ensuring the codebase remains robust and scalable as the company grows. He often finds himself debugging complex issues late into the evening.

Relationships

Xaver maintains a close-knit group of university friends, with whom he shares tech discussions and weekend activities. His parents, both academics, live in a smaller town in Bavaria and offer steady, albeit sometimes distant, support. He values direct, honest communication with his colleagues, particularly his CTO, who acts as a technical mentor.

How they decide

Xaver is a methodical researcher. He weighs options carefully, often creating pros and cons lists, and seeks out technical documentation and community consensus before committing to a technical direction. He values evidence and practical application over hype, and will often prototype solutions to validate his assumptions. Peer recommendations from trusted developers carry significant weight.

How they sound

Speaks with a clear, measured cadence, often using precise technical terminology. His German is standard, with occasional subtle Bavarian influences from his upbringing. He avoids overly casual slang or hyperbole, preferring direct and factual communication. When explaining technical concepts, he's thorough and patient, but can become slightly more animated when discussing elegant solutions or efficient code patterns. He tends to use phrases like 'fundamentally', 'from a maintainability perspective', and 'the core issue is'.

Personality traits

  • methodical
  • detail-oriented
  • pragmatic
  • diligent
  • focused
  • resourceful
  • slightly reserved
  • analytical

Goals

  • Become a principal engineer or tech lead within 5 years
  • Contribute to an open-source Next.js project
  • Achieve financial independence through smart investments
  • Own a small apartment in Berlin
  • Maintain a healthy work-life balance despite startup demands

Problems & frictions

  • Balancing the need for rapid feature delivery with long-term code quality
  • Limited bandwidth for deep architectural refactoring
  • Onboarding new team members effectively onto the existing codebase
  • The constant pressure to stay updated with the rapidly evolving frontend landscape
  • Managing technical debt in a fast-paced startup environment
  • Finding time for personal development outside of core work responsibilities

Values

  • maintainability
  • collaboration
  • shipping
  • efficiency
  • code quality

Interests

  • TypeScript
  • SaaS metrics
  • cycling
  • Next.js performance
  • developer tooling
  • frontend architecture

Media habits

  • Reads Hacker News daily
  • Follows key figures on Twitter/X for tech insights
  • Listens to programming podcasts during commutes
  • Watches YouTube tutorials for specific libraries
  • Subscribes to newsletters on SaaS growth

Questions & answers

Xaver Arens’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at Staarter (https://staarter.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 pricing for Staarter, a one-time payment of $299 (down from $399), seems reasonable for a comprehensive SaaS starter kit with features like authentication, billing, and localization. It's a lifetime access deal, which is appealing. For a "no-brainer" price, I'd be looking closer to $150-$200, especially considering we already have a shared internal starter kit that needs constant evolution. If it were priced significantly higher, say over $400, I'd start to question the long-term value and explore building more in-house or using more specialized, potentially open-source solutions. The maximum I would pay per month is $0, as this is a lifetime purchase. My maximum acceptable price for lifetime access would be $250 USD.
    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.