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

Manuel Vermeulen

Manuel Vermeulen

Senior backend engineer with infra duties

Full-depth AI personas

Why this persona fits the audience

He is a senior backend engineer at a 45-person e-commerce company in Amsterdam and shares AWS infrastructure duties with one dedicated DevOps colleague. Their team uses Terraform Cloud for state and collaboration, but baseline account setup, IAM patterns and module conventions are still documented in an internal wiki and implemented manually when new environments appear.

  • Age: 38
  • Location: Amsterdam, Netherlands
  • Occupation: Senior backend engineer
  • Income: €95k gross
  • Education: MSc in Software Engineering
  • Company size: 45-person
  • Years in role: 5
“Consistency isn't just about making things look the same; it's about building systems that are predictable and easier to manage in the long run.”

Manuel Vermeulen grew up in a middle-class family in Utrecht, developing an early fascination with how complex systems worked. His academic path led him to a Master's degree in Software Engineering, where he excelled in subjects related to distributed systems and architecture. After graduation, he worked for a couple of larger tech firms, gaining experience in various backend technologies, but found himself increasingly drawn to the infrastructure layer that supported the applications. Around five years ago, he joined his current e-commerce company, attracted by the smaller team size and the opportunity to have a broader impact. He shares infrastructure responsibilities with a DevOps specialist, a setup that allows for focused backend work but also necessitates hands-on involvement with AWS. Manuel's current professional frustration stems from the manual overhead involved in setting up new environments – a process he views as repetitive and error-prone. He believes strongly in the principle of 'measured change,' preferring well-thought-out, incremental improvements over disruptive overhauls. This methodical approach extends to his personal life; he meticulously plans his photography projects and researches extensively before making significant purchases. He values his autonomy at work, enjoying the freedom to architect solutions, but recognizes the need for standardization to improve team efficiency and maintainability. His income affords him a comfortable life in Amsterdam, but his savings are primarily directed towards future security and meaningful experiences rather than immediate gratification.

Background & daily life

A day in their life

Manuel's weekday typically starts around 7:30 AM. After a quick breakfast and scanning Hacker News, he cycles to the office, arriving by 9:00 AM. His mornings are usually dedicated to focused backend development tasks, coding new API endpoints or optimizing database queries, often involving code reviews. Lunch is a shared affair with colleagues. The afternoon might involve a stand-up meeting, tackling Jira tickets, or, increasingly, diving into infrastructure tasks. This could mean updating Terraform configurations, investigating IAM permissions, or documenting a new setup process in the wiki. He often leaves the office around 6:00 PM, heading home for dinner and personal time, which might include editing photos or planning his next coding project.

Lifestyle

Manuel lives in a spacious, though somewhat cluttered, apartment in Amsterdam Oud-West with his partner, a graphic designer. Evenings often involve cooking a healthy meal together, followed by either a quiet night in with a book or a board game session with friends. Weekends are a mix of exploring the city, visiting photo exhibitions, and occasionally attending meetups related to photography or tech. He enjoys cycling for short distances but prefers public transport or walking for longer trips. Financially, he's comfortable, saving diligently for future travel and potential home renovations, prioritizing experiences and long-term security over flashy possessions.

Work life

As a senior backend engineer at an e-commerce company, Manuel's days are a blend of coding new features and wrestling with infrastructure. He shares AWS responsibilities with one DevOps colleague, a partnership that works well due to shared pragmatism. Their current challenge is standardizing environment provisioning. While Terraform Cloud provides a solid framework for collaboration on application infrastructure, the initial AWS account setup, IAM policies, and module conventions are still managed via an internal wiki and manual configuration. This leads to occasional inconsistencies and time-consuming setup when new projects or testing environments are spun up, a process Manuel finds increasingly inefficient.

Relationships

Manuel maintains a close relationship with his partner, who is his primary confidante. He has a solid group of about five close friends from university, with whom he regularly plays board games and discusses life. His professional network is smaller, mostly consisting of colleagues and a few contacts from tech meetups. He respects his DevOps colleague's expertise and trusts their judgment on infrastructure matters.

How they decide

Manuel is a cautious and research-oriented decision-maker. He values evidence, logic, and proven methodologies. He'll thoroughly investigate options, weigh pros and cons, consult documentation, and often seek input from his DevOps counterpart or trusted online resources before committing to a technical approach or adopting new tools.

How they sound

Speaks in a calm, measured tone, often with a slight Dutch accent. Uses precise technical language but avoids overly complex jargon when explaining things to less technical colleagues. He tends to use phrases like 'from a practical standpoint,' 'the core issue is,' or 'what we've observed is.' He avoids hyperbole and focuses on factual descriptions.

Personality traits

  • methodical
  • detail-oriented
  • pragmatic
  • inquisitive
  • patient
  • self-sufficient
  • principled
  • calm under pressure
  • slightly introverted

Goals

  • Achieve a higher degree of automation in infrastructure provisioning
  • Mentor junior engineers on best practices for backend development and IaC
  • Continue to refine his photography portfolio and maybe exhibit work
  • Master a new backend programming language or framework
  • Save enough for a significant extended trip to Japan

Problems & frictions

  • Tedious manual configuration for new AWS environments
  • Inconsistent adherence to IAM patterns across different projects
  • Lack of standardized reusable Terraform modules for baseline infrastructure
  • Balancing feature development pressure with infrastructure maintenance needs
  • Keeping up with the rapid pace of cloud service updates

Values

  • maintainability
  • autonomy
  • measured change
  • systematic improvement
  • clarity of process

Interests

  • backend systems
  • photography
  • board games
  • cloud architecture
  • infrastructure as code
  • craft beer

Media habits

  • Reads Hacker News daily
  • Subscribes to several backend/DevOps newsletters
  • Listens to tech podcasts during commute
  • Follows specific engineers on Twitter/Mastodon
  • Watches YouTube tech deep dives

Questions & answers

Manuel Vermeulen’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of Baseline One (https://vancerbaseline.com) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Baseline One 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).

    Currently, we document our baseline AWS account setup, IAM patterns, and module conventions in an internal wiki, and then implement them manually when new environments are needed. So, we are essentially doing it by hand, or at least, without any dedicated tooling. Baseline One seems promising because it automates the setup process, which is exactly the tedious overhead I'm looking to eliminate. The promise of 'production-ready, hardened Terraform infrastructure in minutes' is appealing. What concerns me is the 'private registry gateway' and how that integrates with our existing Terraform Cloud setup. I'd need to understand how tightly coupled it is. The pricing is annual ($1,920 per year for Standard) which is quite a bit upfront for us, and I'm not sure if our company would budget for that. I would consider paying around $50 per month, which is roughly €45, but an annual commitment is a hurdle.
    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.