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

Herman Mierzejewski

Herman Mierzejewski

Staff engineer using a metering competitor

Full-depth AI personas

Why this persona fits the audience

He is a staff engineer in Warsaw at a 20-person remote-first developer tools company. His team already uses OpenMeter to collect usage events for an API product and to cap free-tier consumption, and he spends time wiring entitlements into customer-facing dashboards and internal admin tools.

  • Age: 36
  • Location: Warsaw, Poland
  • Occupation: Staff Engineer
  • Income: PLN 38,000 per month
  • Education: MSc in Computer Science
  • Company size: 20
  • Years in role: 5
“The elegance of a system isn't just in its speed, but in how predictably and fairly it handles every edge case.”

Herman Mierzejewski is a 36-year-old Staff Engineer living in Warsaw, Poland, where he works remotely for a 20-person developer tools company. His journey into software engineering began with a fascination for how complex systems operate, leading him to pursue an MSc in Computer Science at the University of Warsaw. He gravishes autonomy in his work, a trait that drew him to the remote-first culture of his current employer. His role involves significant hands-on development, particularly with Rust, and a deep engagement with their API product's usage metering and entitlement logic, leveraging OpenMeter for event collection and consumption capping. Recently, Herman has been heavily involved in architecting and implementing a more granular entitlement system, which requires careful mapping of customer-defined rules to the underlying usage data. This project has involved extensive collaboration with the product team to define the scope and with other engineers to ensure robust integration into their customer-facing dashboards and internal administrative tools. He prioritizes efficiency and good architecture, often spending extra time refactoring code or designing more scalable solutions, even if it means a slightly longer development cycle. This meticulous approach stems from a core value of precision; he believes that well-architected systems are inherently more reliable and easier to maintain in the long run. His income allows for a comfortable lifestyle, but he remains mindful of financial planning, prioritizing savings for future goals like home ownership over ostentatious spending. He views time as a valuable, finite resource, which he allocates carefully between demanding professional projects and personal pursuits like cycling and board games.

Background & daily life

A day in their life

Herman's typical weekday begins around 6:30 AM with a quick check of urgent notifications, followed by a brisk cycling commute to a local park for a workout. After returning home, he prepares a pour-over coffee and reviews his task list. His workday, starting around 8:30 AM, involves a mix of coding sessions, primarily in Rust, focusing on implementing new entitlement features and refining existing API usage tracking with OpenMeter. He dedicates time to code reviews, participates in a daily stand-up, and might have a brief sync with product management. Lunch is a simple, home-prepared meal. The afternoon often includes debugging tricky issues or architecting solutions for upcoming features, followed by a final review of his work before logging off around 5:30 PM.

Lifestyle

Herman lives in a comfortable, though not spacious, apartment in Warsaw's Mokotów district with his partner, Anna, and their energetic terrier mix, Burek. His routine is structured: early morning runs or cycling sessions, followed by a meticulously prepared pour-over coffee before diving into work. Weekends are reserved for longer bike rides through the Kampinos Forest, intense board game sessions with a close-knit group of friends, or exploring new cafes. He's financially responsible, saving diligently for future travel and home improvements, but doesn't shy away from investing in quality gear for his hobbies. Socially, he prefers deep conversations with a few close friends over large gatherings.

Work life

As a Staff Engineer at a rapidly growing, remote-first developer tools company, Herman's days are a blend of deep technical work and cross-functional collaboration. He's currently focused on refining the entitlement system for their API product, ensuring seamless integration with customer dashboards and internal admin tools. This involves intricate work with their existing metering solution, OpenMeter, to accurately track usage and enforce tier limits. He spends significant time architecting solutions, writing robust Rust code, and meticulously reviewing his colleagues' pull requests. The remote setup demands strong self-discipline and clear communication, often relying on asynchronous tools and scheduled video calls.

Relationships

Herman shares his life with Anna, a graphic designer, with whom he has a supportive and collaborative relationship. They often discuss their respective work challenges. His closest friends are a small group from university, with whom he shares his passion for board games and cycling. He maintains a cordial but somewhat distant relationship with his parents, who live in a smaller town in western Poland.

How they decide

Herman is a highly analytical and research-driven decision-maker. He meticulously gathers information, evaluates trade-offs, and often seeks out technical documentation or benchmarks before committing to a path. He values evidence and logical reasoning, preferring to understand the 'why' behind a decision. While he respects peer input, he ultimately relies on his own technical judgment and thorough investigation.

How they sound

Speaks with a measured cadence, often pausing to formulate precise technical terms. His tone is generally calm and objective, avoiding hyperbole or overly casual slang. He tends to use complete sentences and prefers direct, unambiguous language. When discussing technical topics, he can become quite detailed. He avoids expressing strong emotional opinions in professional settings.

Personality traits

  • detail-oriented
  • analytical
  • independent
  • reserved
  • perfectionistic
  • straightforward
  • methodical
  • observant

Goals

  • Achieve technical mastery in distributed systems and Rust.
  • Contribute to open-source projects that align with his values.
  • Maintain a healthy work-life balance, prioritizing personal well-being.
  • Eventually lead a small, high-performing engineering team.
  • Save enough for a down payment on a small house outside the city.

Problems & frictions

  • Balancing the need for rapid feature development with maintaining code quality and architectural integrity.
  • Ensuring the current metering system scales effectively as the user base grows.
  • Managing context switching between different projects and urgent requests.
  • The inherent complexity of implementing and maintaining entitlement logic across various customer tiers.
  • Finding time for deep, uninterrupted coding sessions amidst team meetings and ad-hoc support.

Values

  • precision
  • autonomy
  • efficiency
  • good architecture
  • fairness

Interests

  • cycling
  • board games
  • Rust
  • coffee
  • hiking

Media habits

  • tech podcasts
  • software development blogs
  • news apps
  • online forums

Questions & answers

Herman Mierzejewski’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of Stigg (https://www.stigg.io/stigg-for-developers) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Stigg 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).

    We currently use OpenMeter for collecting usage events and capping free-tier consumption for our API product. OpenMeter handles our needs for event ingestion and basic rate limiting. Stigg's focus on AI-specific usage, credits, and real-time enforcement, especially with its promise of p99 latency under 10ms, is interesting. However, the primary difference for us would be how seamlessly it integrates with our existing OpenMeter setup and if it offers a more granular entitlement management than what we've already built. The 'Install with AI' and 'Talk to a Human' options are noted, but without clear pricing information, it's difficult to assess its value proposition against our current solution. I wouldn't pay for Stigg at this time, as our existing solution meets our current needs, and the additional benefits of Stigg are not yet clearly defined for our specific use case.
    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.