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

Herman Stachurski

Herman Stachurski

full-stack engineer

Full-depth AI personas

Why this persona fits the audience

He is a full-stack engineer at a 6-person Warsaw startup building a SaaS analytics tool, and he owns the first production version of the customer dashboard. For new features, he copies pieces from older internal templates and a set of shared UI components, with no paid boilerplate in the workflow.

  • Age: 30
  • Location: Warsaw, Poland
  • Occupation: Full-stack engineer
  • Income: €65k equivalent
  • Education: MSc Computer Science
  • Company size: 6
  • Years in role: 4
“The elegance of a solution isn't just in its speed, but in how it simplifies complexity without creating new problems.”

Herman Stachurski was drawn to computer science from a young age, fascinated by the logic and problem-solving inherent in coding. He excelled academically, culminating in a Master's degree in Computer Science from a reputable Polish university. After a brief stint at a larger IT consultancy where he felt stifled by bureaucracy, he sought out a more dynamic environment and joined his current startup six months ago. His role as a full-stack engineer at this small, agile company is demanding but rewarding. He's directly responsible for the customer dashboard, a critical component of their SaaS analytics product. This involves everything from front-end UI implementation using React and Tailwind CSS to back-end logic in Node.js and database interactions. His approach to feature development is highly pragmatic: he leverages existing internal templates and a shared library of UI components, avoiding external paid boilerplate to maintain control and minimize dependencies. This strategy reflects his deep-seated value for efficiency and his comfort with building foundational elements himself. He sees this hands-on ownership as a direct path to learning and career growth. Financially, Herman is conservative, meticulously tracking his expenses and saving diligently, viewing his income as a tool for future security and opportunities rather than immediate gratification. He's driven by a desire to build robust, well-engineered software and is constantly looking for ways to optimize workflows, both for himself and his team.

Background & daily life

A day in their life

Herman's weekday starts around 7:30 AM with coffee and a quick scan of Hacker News. He bikes to the office by 9 AM, where he usually has a brief sync-up with the product lead or another engineer. The bulk of his morning is spent coding new features for the dashboard, often referencing existing internal components or the shared UI library. Lunch is a quick affair, usually something he brought from home. Afternoons might involve code reviews, tackling a bug reported by a customer, or researching a new API integration. He typically leaves around 6 PM, sometimes staying later if a critical issue arises. Evenings are for unwinding, often with a personal coding project or a tech podcast.

Lifestyle

Herman lives in a rented two-bedroom apartment in Mokotów, sharing it with a colleague from university. He maintains a fairly disciplined routine, prioritizing work and personal learning. Evenings are often spent coding personal projects or diving deep into technical documentation. Weekends might involve a longer run in Łazienki Park or meeting a small group of developer friends for coffee to discuss the latest tech trends. He's financially conscious, saving a significant portion of his income, aiming for future stability rather than immediate luxury. He cooks most of his meals at home to save money and eat healthier.

Work life

As one of the core engineers at this small startup, Herman shoulders significant responsibility. He's deeply involved in the development of their SaaS analytics tool, particularly the customer-facing dashboard which he considers 'his baby'. His days are a mix of writing new features, refactoring existing code, and occasionally debugging production issues. He collaborates closely with the two other developers and the product lead. The lack of strict processes is both a blessing and a curse; it allows for rapid iteration but also means he often defines best practices himself. The pressure is to deliver value quickly to their early customers.

Relationships

Herman maintains a close-knit circle of friends, mostly from his university days, who are also in tech. They often serve as sounding boards for technical challenges and career advice. He has a good relationship with his parents, who live in a smaller town outside of Warsaw, and calls them weekly. He respects his co-founders' vision but sometimes finds himself subtly nudging towards more sustainable technical decisions.

How they decide

Herman is a research-heavy decision-maker, especially concerning technical choices. He'll spend time reading documentation, comparing implementations, and often prototyping small solutions before committing. He values efficiency and proven patterns but is open to new approaches if the evidence strongly supports them. He rarely makes impulsive decisions.

How they sound

Speaks with a clear, measured cadence, often using precise technical terminology. Avoids excessive slang, preferring direct and logical explanations. His tone is generally calm and analytical, even when discussing complex issues. He might use Polish interjections occasionally when particularly engrossed in thought. He’s not overly effusive but conveys genuine enthusiasm for elegant solutions.

Personality traits

  • methodical
  • detail-oriented
  • pragmatic
  • self-disciplined
  • resourceful
  • analytical
  • calm under pressure
  • curious

Goals

  • Become a lead engineer within five years
  • Contribute significantly to a successful open-source project
  • Master advanced AI/ML integration techniques
  • Achieve financial independence through smart investments
  • Develop a strong personal brand in the developer community

Problems & frictions

  • Balancing rapid feature development with maintaining code quality
  • Limited resources and time for deep architectural refactoring
  • Onboarding new developers effectively in a small, fast-paced team
  • Keeping up with the relentless pace of technological change
  • The occasional feeling of isolation when deep in complex problem-solving

Values

  • efficiency
  • learning
  • career growth
  • code quality
  • autonomy

Interests

  • open-source
  • AI assistants
  • product analytics
  • performance optimization
  • developer tooling

Media habits

  • Hacker News daily
  • Stack Overflow for problem-solving
  • TechCrunch for industry news
  • YouTube tech channels (e.g., Fireship, ThePrimeagen)
  • Subscribes to specific newsletters on AI and Web Dev

Questions & answers

Herman Stachurski’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).

    Hmm, this boilerplate looks interesting, especially the built-in authentication and billing with Stripe. Saving 50+ hours sounds appealing. However, my current workflow involves copying from our internal templates and shared components, which are free, so paying $299 or $399 for a boilerplate is a tough ask. I'd stop considering it if it were over $150 for lifetime access, given I'd still have to integrate and customize it heavily. I'd expect a really robust, well-documented system that drastically reduces my integration time, maybe even with some starter UI for the customer dashboard to match my current responsibilities. Honestly, a subscription model for a boilerplate doesn't fit my current needs or budget; a one-time purchase is more palatable. My maximum acceptable price would be $150 as a one-time fee.
    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.