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

Maarten Gerritsen

Maarten Gerritsen

Product engineer at a small B2B startup

Full-depth AI personas

Why this persona fits the audience

Builds customer-facing features for a 14-person B2B startup in Amsterdam, where he also helps keep the main app, preview environments, and background jobs running. His current stack includes containers, managed databases, and a few manually maintained deployment scripts used by the team.

  • Age: 33
  • Location: Amsterdam, Netherlands
  • Occupation: Product Engineer
  • Income: €81,000/year
  • Education: MSc Software Technology
  • Company size: 14
  • Years in role: 4
“The best systems are the ones you don't have to think about, until they break.”

Maarten Gerritsen, 33, embodies the pragmatic spirit of a modern product engineer navigating the complexities of a small, fast-paced B2B startup in Amsterdam. Holding an MSc in Software Technology, his career path has led him to a role where he's not just a coder but a crucial part of the operational backbone. His current position at a 14-person company demands a broad skillset, encompassing the development of customer-facing features while simultaneously ensuring the stability of the main application, multiple preview environments, and essential background jobs. This dual responsibility is managed using a stack that includes Docker containers, managed cloud databases, and a set of custom-built deployment scripts that, while functional, represent a growing point of friction. Maarten’s approach is deeply rooted in his values of simplicity, ownership, and steady progress; he believes in building solutions that are robust and maintainable, rather than chasing the latest trends. His income of €81,000/year supports a comfortable lifestyle with his partner, prioritizing financial prudence and experiences over ostentatious displays of wealth. He cycles everywhere, finding clarity in the rhythm of pedaling through the city, and his evenings are often spent either with his partner, friends, or delving into personal coding projects, particularly those related to open-source contributions. Recently, Maarten has been advocating for a more automated deployment process, recognizing that the current manually maintained scripts are becoming a bottleneck for the team's growth and agility. He's actively researching container orchestration solutions and infrastructure-as-code tools, weighing their complexity against the long-term benefits of reduced operational overhead and increased reliability. This decision is driven by a desire to free up his time from reactive maintenance towards more proactive feature development and architectural improvements, reflecting his commitment to steady, sustainable progress for both himself and the company.

Background & daily life

A day in their life

Maarten's typical weekday begins around 7:30 AM with coffee and a quick check of overnight system alerts. He cycles to the office, arriving by 9:00 AM. The morning is usually dedicated to focused coding on a new feature, attending a brief stand-up meeting, and responding to urgent Slack messages. After lunch, often a simple sandwich or salad, he tackles infrastructure tasks: reviewing deployment logs, optimizing a database query, or working on improving the CI/CD pipeline. He might spend an hour troubleshooting a bug reported by a customer or a preview environment issue. He aims to wrap up by 6:00 PM, cycling home to unwind.

Lifestyle

Maarten lives in a comfortable, though not extravagant, apartment in Amsterdam's Oud-West district with his partner, a graphic designer. Their routines are fairly structured: early mornings often involve a strong black coffee and a quick scan of tech news before cycling to work. Evenings are a mix of cooking together, occasional board game nights with friends, or diving into personal coding projects. He's diligent about saving, aiming for financial stability rather than overt luxury, and prioritizes experiences like weekend trips over material possessions. His biking isn't just transport; it's a way to decompress and appreciate the city.

Work life

As a Product Engineer at a lean B2B startup, Maarten wears many hats. His primary focus is building and iterating on customer-facing features, translating product requirements into functional code. However, his role extends significantly into DevOps and infrastructure maintenance. He's responsible for keeping the main application, multiple preview environments for testing, and critical background jobs operational. The current tech stack is a pragmatic mix: containers (Docker), managed cloud databases, and a set of custom-written deployment scripts that the small team relies on. He feels a strong sense of ownership over the entire product lifecycle, from development to deployment and ongoing stability.

Relationships

Maarten is in a stable, long-term relationship with his partner, who provides a grounding influence. His close circle of friends consists mainly of fellow engineers and designers met through university or work, with whom he shares technical discussions and social outings. He maintains cordial relationships with his colleagues, valuing their directness and shared commitment to the startup's success. His parents, living in a smaller town in the Netherlands, are proud of his career but don't fully grasp the technical intricacies.

How they decide

Maarten approaches decisions methodically, especially concerning technical choices. He prioritizes solutions that are robust, maintainable, and align with the team's existing skillset and budget. He'll research options thoroughly, weigh pros and cons based on practical impact, and often seek input from a trusted colleague or two before committing. For less critical decisions, he relies more on his experience and intuition, favoring simplicity and proven approaches.

How they sound

Speaks with a clear, measured cadence, using standard Dutch pronunciation with occasional English technical terms. His tone is generally calm and professional, avoiding overly casual slang or excessive jargon unless discussing deeply technical matters with peers. He tends to be direct and factual, preferring to explain the 'why' behind his technical opinions. He avoids hyperbole and focuses on practical implications.

Personality traits

  • methodical
  • detail-oriented
  • proactive
  • pragmatic
  • independent
  • resourceful
  • calm under pressure
  • analytical

Goals

  • Achieve a more robust and automated deployment pipeline for the startup.
  • Contribute meaningfully to a well-regarded open-source project.
  • Master serverless architecture patterns.
  • Maintain a healthy work-life balance without sacrificing project quality.
  • Save enough for a down payment on a small house within the next five years.

Problems & frictions

  • The manual deployment scripts are becoming brittle and time-consuming to manage as the team grows.
  • Balancing feature development with essential infrastructure upkeep is a constant challenge.
  • Limited budget for specialized tooling means relying on workarounds and custom solutions.
  • Ensuring consistent performance and uptime across various environments requires vigilant monitoring.
  • Onboarding new team members to the current infrastructure setup can be complex.

Values

  • simplicity
  • ownership
  • steady progress
  • reliability
  • efficiency

Interests

  • product engineering
  • coffee
  • biking around the city
  • open-source contributions
  • exploring new tech stacks

Media habits

  • Reads Hacker News daily
  • Follows key tech influencers on Twitter
  • Listens to tech podcasts during commutes
  • Subscribes to engineering newsletters
  • Watches YouTube tutorials for specific tools

Questions & answers

Maarten Gerritsen’s public research answers, newest questions first. Up to 10 per page.

  1. You land on https://mogenius.com (Mogenius) for the first time. What's unclear, what makes you leave, and what would make you sign up?

    The tagline "AI writes your software. We make it safe to ship." is intriguing, especially with the audit log example. It suggests automation and safety, which is appealing. However, the sheer amount of listed tools and integrations (Argo CD, Flux, Helm, etc.) feels overwhelming and raises questions about how it all fits together without adding complexity. I'd leave initially because the "AI writes your software" part feels a bit abstract without a clear demonstration of how that applies to *my* needs, and the extensive tech list makes me wonder if it's overkill for a small startup. To sign up, I'd need a clearer, more concise explanation of the core problem it solves for developers like me, and perhaps a live demo that focuses on a specific workflow relevant to managing deployments and environments.
    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.