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

Marcel van den Broek

Marcel van den Broek

Independent software consultant with a cautious workflow

Full-depth AI personas

Why this persona fits the audience

Moves between client teams of 2-5 developers in the Netherlands, often acting as the person who stabilizes builds and documents release steps. Uses shell scripts, Trello, and Confluence notes for coordination, and keeps AI tools limited to small helper tasks while the core workflow stays manual and inspectable.

  • Age: 45
  • Location: Amsterdam, Netherlands
  • Occupation: Independent Software Consultant
  • Income: €120k annual
  • Education: MSc in Software Engineering
  • Years in role: 15
“The most elegant solution is often the one you can clearly see through, from start to finish.”

Marcel van den Broek, 45, is an independent software consultant based in Amsterdam, Netherlands, holding an MSc in Software Engineering. For the past fifteen years, he has carved out a niche by focusing on the often-overlooked but critical aspects of software development: build stabilization and release process documentation. His career trajectory has been a deliberate move away from the high-pressure, feature-driven environment of larger corporations towards a more controlled, impactful role within smaller teams. He operates on a principle of meticulousness, preferring to ensure the underlying infrastructure of a software project is robust before new features are added. His current engagement, typical of his work, involves a team of four developers working on modernizing a substantial Java application. Marcel’s role is to act as the guardian of the build pipeline and the architect of the release process. He spends his days diagnosing and resolving build failures, optimizing CI/CD configurations, and meticulously documenting every step required for a successful deployment. He relies on a toolkit of shell scripts for automation, Trello for task management, and Confluence for detailed documentation, viewing these as transparent and inspectable tools. While aware of AI advancements, he limits their use to auxiliary tasks, such as generating initial drafts of documentation or suggesting code snippets for utility scripts, always ensuring the core logic remains human-authored and verifiable. This cautious approach stems from a deep-seated value for privacy and control; he believes that understanding the entire process, down to the last script, is paramount. His income of €120k annually reflects his specialized expertise and the reliability he brings to his clients. He lives a relatively frugal lifestyle, saving diligently, with a long-term goal of achieving financial independence to pursue his passion for sailing and photography more extensively. His decision to work independently was driven by a desire for autonomy and the ability to choose projects that align with his values of simplicity and reliability, rather than chasing status or rapid career advancement.

Background & daily life

A day in their life

Marcel's typical weekday begins around 7:00 AM with a strong black coffee and a review of overnight build logs and news feeds on Hacker News and LWN.net. After a quick breakfast, he cycles to his current client's office in the Sloterdijk area. His morning is usually spent troubleshooting a build issue or refining a deployment script, often collaborating with one or two developers on the team. Lunch is a simple sandwich eaten at his desk while reviewing documentation. The afternoon might involve a planning session for the next release, documenting new steps in Confluence, or writing a small shell script to automate a repetitive task. He leaves the office around 5:30 PM, cycles home, and spends his evening either working on personal photography, planning his next sailing trip, or reading technical articles. He aims to be offline by 10:00 PM.

Lifestyle

Marcel lives in a compact but well-maintained apartment in the Jordaan district of Amsterdam, a short bike ride from the canals. He enjoys a quiet, predictable routine: early morning coffee and news, a brisk bike ride to his client's office, and evenings spent editing photographs or preparing his sailboat for the upcoming sailing season. He’s remarkably frugal, preferring quality over quantity and saving diligently for future maintenance of his boat and occasional travel within Europe. He rarely goes out, preferring the company of a good book and the comfort of his own space. Socializing is limited to a small circle of close friends, often met through sailing or open-source communities.

Work life

Marcel’s work is deliberately focused on stability and clarity. He thrives in small, agile teams where he can directly impact the build and release process. His current contract involves a team of four developers working on a legacy Java application undergoing modernization. He spends his days troubleshooting build failures, optimizing CI/CD pipelines, meticulously documenting deployment steps, and ensuring that release notes are accurate and comprehensive. He finds satisfaction in untangling complex build issues and creating clear, actionable documentation that prevents future headaches for the team. He avoids roles with high pressure for rapid feature delivery, preferring to ensure the foundation is solid.

Relationships

Marcel maintains a small but strong network. His closest relationships are with his sailing club members and a few long-time friends from his university days, with whom he shares a passion for technology and photography. He has a cordial but professional relationship with his clients, earning their trust through consistent, reliable delivery rather than overt friendliness. He has no immediate family in the Netherlands, making his chosen community and professional network particularly important.

How they decide

Marcel is highly analytical and research-driven in his decision-making, especially concerning tools and processes. He prioritizes evidence of reliability and maintainability over novelty or hype. He will meticulously investigate options, often running small, controlled experiments or proofs-of-concept before committing. He values peer reviews and established best practices, and is slow to adopt anything that introduces significant unknowns or requires a steep learning curve without clear, demonstrable benefits.

How they sound

Speaks in a calm, measured tone with a slight Dutch accent. His vocabulary is precise and technical, often using specific terminology without much explanation, assuming a baseline understanding. He avoids hyperbole and overly casual slang. Sentences are well-structured and logical. He tends to pause briefly before answering complex questions, indicating careful consideration. He rarely expresses strong emotional opinions, preferring factual statements.

Personality traits

  • Methodical
  • Reserved
  • Precise
  • Pragmatic
  • Skeptical
  • Detail-oriented
  • Reliable
  • Independent
  • Unassuming
  • Quietly competent

Goals

  • Achieve a state of financial independence that allows for extended sailing trips.
  • Contribute meaningfully to a significant open-source project, perhaps related to build tooling.
  • Maintain a consistent level of high-quality work that earns him repeat client engagements.
  • Develop a deeper understanding of secure software development practices.
  • Complete a personal photography project documenting Amsterdam's industrial heritage.

Problems & frictions

  • Client teams often underestimate the complexity of build and release management, leading to rushed timelines.
  • Keeping up with the rapid pace of new tooling and framework introductions without compromising his stable workflow.
  • The inherent isolation of independent consulting can sometimes lead to a lack of peer technical discussion.
  • Navigating client expectations around the integration of newer, less-proven technologies.
  • Finding time for personal projects amidst demanding client work.

Values

  • Simplicity
  • Privacy
  • Control
  • Reliability
  • Transparency

Interests

  • Open-source software
  • Photography
  • Sailing
  • Dutch Maritime History
  • Urban exploration photography

Media habits

  • Hacker News
  • LWN.net
  • Reddit (r/programming, r/sysadmin)
  • The Register
  • Local Dutch news sites (NOS, NRC)
  • Technical blogs focused on build systems and CI/CD

Questions & answers

Marcel van den Broek’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at Klyve (https://klyve.online): 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).

    The concept of an "Automated Software Factory" that handles the full lifecycle sounds intriguing, especially the "You Architect, It Builds" aspect. However, the pricing isn't clear from this page. I'd be willing to consider a subscription if it genuinely automates repetitive tasks like initial test generation or documentation updates, freeing me up for the more complex stabilization work. A price around $50-$75 USD per month would be a no-brainer for a tool that proves reliable and integrates well with my existing shell scripts and Confluence workflow. Anything above $150 USD per month, without clear evidence of significant time savings and without compromising my control over the process, would make me pause.
    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.