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

Glenn Ritsma

Glenn Ritsma

product engineer at a small startup already using a paid code security tool

Full-depth AI personas

Why this persona fits the audience

He is part of a 4-person product team in Amsterdam and uses Cursor to ship features into a shared repo. The company already has a paid Snyk subscription and basic uptime alerts, so he reviews security findings and performance issues as part of normal release work. He owns both implementation and day-to-day validation.

  • Age: 37
  • Location: Amsterdam, Netherlands
  • Occupation: Product engineer
  • Income: €79,000 EUR/year
  • Education: Bachelor's degree in software engineering
  • Company size: 10-50 employees
  • Years in role: 5
“The real challenge isn't just shipping code, it's shipping code that's robust, secure, and built to last.”

Glenn Ritsma, 37, is a dedicated product engineer based in Amsterdam, Netherlands, holding a Bachelor's degree in Software Engineering. He has spent the last five years honing his craft at a small, dynamic startup, where he's become an integral part of a four-person product team. His professional journey has been marked by a commitment to quality and efficiency, driven by a deep-seated belief in process discipline and team accountability. Glenn's work environment is characterized by its fast pace and the constant evolution of technology, particularly with the adoption of AI-powered coding tools like Cursor, which he uses daily to ship features into their shared repository. He's not new to the importance of security and performance; his company already utilizes a paid Snyk subscription and basic uptime alerts. This means Glenn's role inherently involves scrutinizing security findings and performance metrics as a standard part of his release workflow. He takes ownership of both the initial implementation and the ongoing validation, ensuring that what goes live meets stringent internal standards. His income of €79,000 EUR/year reflects his experience and the responsibilities he holds, allowing for a comfortable lifestyle that balances saving for future goals, such as a property down payment, with enjoying life in the vibrant city of Amsterdam. Glenn's personality leans towards conscientiousness and a moderate level of openness, making him a reliable and thoughtful contributor. He's analytical, preferring to understand the 'why' behind technical decisions and meticulously working through problems. His career aspirations are centered on continuous learning and contributing to the long-term success of his company's product, rather than chasing rapid career advancement for its own sake. He values maintainability and elegance in code, seeing them as crucial for sustainable development. He approaches his work with a pragmatic mindset, always seeking the most effective and efficient solutions within the startup's constraints.

Background & daily life

A day in their life

Glenn's typical weekday starts around 8:30 AM with a strong coffee and a quick scan of emails and team chat. He then dives into coding, often using Cursor to implement a feature or address a bug identified during the previous day's testing. Around 11 AM, he'll participate in a brief stand-up meeting with his product team to discuss progress and blockers. The afternoon is usually dedicated to code reviews, refining his implementation based on feedback, and running through the Snyk scan results for any new vulnerabilities or performance regressions. He aims to wrap up by 6 PM, often spending the evening cooking with his partner or unwinding with a book.

Lifestyle

Glenn leads a structured but balanced life in Amsterdam. He shares a comfortable apartment with his partner, where they enjoy cooking together and tending to their small balcony garden. Weekends often involve cycling through the city, visiting local markets, or catching up with friends over coffee or craft beer. He's mindful of his finances, aiming for steady savings for future travel and potential property investment, but doesn't shy away from occasional splurges on quality tech gadgets or experiences. He values his downtime, using it to recharge and pursue personal learning.

Work life

As a product engineer at a growing startup, Glenn's days are a blend of focused coding and collaborative problem-solving. He's part of a lean, four-person product team, sharing responsibilities for feature development from conception to deployment. His primary tool is Cursor, which he uses to iterate quickly on features pushed to their shared repository. The company's existing investment in Snyk and basic uptime monitoring means security and performance checks are integrated into his release workflow. He meticulously reviews findings, implements fixes, and validates the results, ensuring a high standard before code goes live.

Relationships

Glenn is in a long-term relationship with his partner, Lisa, a graphic designer, who provides a grounding influence and encourages his professional growth. He maintains a close circle of friends from university and previous jobs, often connecting with them at tech meetups or casual dinners. Within his team, he has a strong working relationship built on mutual respect and open communication.

How they decide

Glenn is a methodical and research-oriented decision-maker. He values data, evidence, and the opinions of trusted colleagues. He's not impulsive and prefers to thoroughly evaluate options, considering potential long-term impacts and integration complexities before committing to a course of action. He's willing to invest time in understanding the 'why' behind a solution.

How they sound

Speaks with a calm, measured cadence. Uses precise technical language but can explain complex concepts clearly. Avoids hyperbole and overly casual slang. His tone is generally thoughtful and slightly reserved, but becomes more animated when discussing technical challenges or elegant solutions. He often uses phrases like 'from my perspective,' 'it seems to me,' or 'the data suggests.'

Personality traits

  • methodical
  • diligent
  • observant
  • pragmatic
  • collaborative
  • detail-oriented
  • patient
  • resourceful

Goals

  • To contribute to building a stable and scalable product that users love.
  • To continuously improve the team's development processes and tooling.
  • To deepen his expertise in secure coding practices and performance optimization.
  • To achieve a better work-life balance as the company grows.
  • To save enough for a down payment on a house within the next five years.

Problems & frictions

  • Balancing the urgency of feature delivery with thorough security and performance validation.
  • Occasional friction in coordinating code reviews and merge requests within the small team.
  • The challenge of keeping up with the rapidly evolving landscape of developer tools and AI assistants.
  • Ensuring comprehensive test coverage across frontend and backend components.
  • Managing technical debt while prioritizing new feature development.

Values

  • code quality
  • process discipline
  • team accountability
  • efficiency
  • maintainability

Interests

  • static analysis
  • frontend performance
  • engineering workflows
  • CI/CD pipelines
  • developer tooling

Media habits

  • following tech blogs (e.g., Hacker News, Martin Fowler's blog)
  • listening to engineering podcasts (e.g., Software Engineering Daily)
  • reading documentation extensively
  • participating in relevant Slack communities

Questions & answers

Glenn Ritsma’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying VibeDoctor (https://vibedoctor.io/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    What would stop me from trying VibeDoctor this month is primarily our existing Snyk subscription. We already use Snyk for security scanning and basic uptime alerts, so I'd need to see a clear advantage or a different type of insight that Snyk doesn't provide to justify adding another tool to our workflow. My day-to-day involves reviewing Snyk findings, so integrating another system might add overhead unless it's significantly better or faster. The free scan sounds interesting, but the real hurdle is demonstrating value beyond what we already have. I'm not willing to pay for this service.
    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.