Why this persona fits the audience
Works on a 4-person foundation-backed mapping project in Amsterdam. The team has an annual community budget and currently posts cash rewards for specific bugs and edge cases, especially when external contributors pick up long-tail issues.
- Age: 36
- Location: Amsterdam, Netherlands
- Occupation: Product engineer
- Income: €68k salary
- Education: Master's degree in Computer Science
- Company size: 4
- Years in role: 2.5
“The real value isn't just in the code we write, but in the pathways we build for others to contribute and improve it.”
Raf Vermeulen, 36, is a dedicated product engineer deeply embedded in the open-source ecosystem, currently contributing to a foundation-backed mapping library. His journey into this field began with a Master's degree in Computer Science from TU Delft, where he developed a fascination for the elegance of well-structured data and the power of collaborative development. After a few years in more corporate software roles, he found himself drawn to the mission-driven nature of open-source foundations. Two and a half years ago, he joined his current four-person team, attracted by the project's focus on public usefulness and its commitment to transparent development. His role involves not just writing code but also actively nurturing the project's community. He spends considerable time triaging bug reports, refining feature specifications, and ensuring the library's core functionality remains robust and accessible. A key aspect of his work is managing the foundation's community budget, which includes administering a bounty system. This system is designed to incentivize contributions by offering cash rewards for specific bug fixes and edge cases, particularly those that might otherwise be overlooked. Raf meticulously tracks these bounties, believing that well-structured incentives are crucial for sustainable open-source development and for broadening the contributor base beyond the core team. He sees this as a vital part of ensuring the project's long-term health and impact. His personal finances are managed with a similar methodical approach; he prioritizes stability and long-term security over immediate gratification, reflecting his broader values. He lives with his partner in Amsterdam, enjoying a balanced lifestyle that combines focused work with quiet personal pursuits and a commitment to sustainable living, primarily through cycling.
Background & daily life
A day in their life
Raf's typical weekday begins around 7:30 AM with coffee and a quick scan of Hacker News and project notifications. After a 30-minute bike commute to his home office, he dives into coding. Mornings are usually dedicated to focused development tasks, like implementing a new feature or refactoring a complex module. Lunch is a simple affair, often eaten at his desk while reviewing pull requests. Afternoons involve more community interaction: responding to GitHub issues, updating bounty descriptions, and participating in a brief team sync call. He often spends the last hour of his workday documenting changes or planning tasks for the next day. The commute home is a time to decompress, often listening to a podcast, before dinner with his partner.
Lifestyle
Raf's life is structured around his work and a few quiet hobbies. He cycles everywhere in Amsterdam, a habit he cherishes for its environmental and health benefits. Evenings are typically spent cooking with his partner, discussing their respective projects, or diving into a technical book. Weekends might involve a long bike ride to a nearby town, visiting a museum, or contributing to a personal open-source project. He's not one for large parties, preferring smaller gatherings with close friends. Financially, he's comfortable but not extravagant, prioritizing savings for future stability and occasional travel.
Work life
As a product engineer for a foundation-backed mapping library, Raf's days are a blend of core development, community engagement, and strategic planning. He works closely with three other core team members, often collaborating asynchronously via GitHub issues and pull requests. A significant portion of his time is dedicated to refining the library's API, ensuring it's robust and developer-friendly. He also actively monitors incoming bug reports and feature requests from the community, triaging them and sometimes crafting detailed responses or small code examples. The foundation's community budget is a key focus; he helps manage the bounty system, ensuring rewards are fairly allocated for specific bug fixes and edge cases, particularly those that external contributors tackle, fostering a more diverse contributor base.
Relationships
Raf's primary relationships are with his partner, with whom he shares a calm and supportive home life, and his three core team members at the foundation. He values their technical expertise and collaborative spirit. He also maintains a network of former university colleagues and a few close friends from the local tech scene, occasionally meeting for a beer or a focused discussion on a challenging problem.
How they decide
Raf approaches decisions methodically. He gathers information, weighs pros and cons, and often seeks input from his team or consults documentation and community discussions before committing. He's not impulsive, preferring to understand the implications of a choice, especially when it affects the codebase or community processes. For technical choices, he leans towards solutions that are well-tested, maintainable, and align with open standards.
How they sound
Speaks with a calm, measured cadence. His Dutch accent is noticeable but not strong. He uses precise technical language when discussing work but can switch to more accessible terms when explaining concepts to non-technical people. He avoids hyperbole and overly casual slang, preferring clear, direct communication. He often uses phrases like 'from a technical standpoint,' 'the implication here is,' or 'it's a matter of balancing.'
Personality traits
- Methodical problem-solver
- Patient with complex codebases
- Values clear documentation
- Slightly introverted but enjoys focused technical discussions
- Pragmatic about open-source sustainability
- Detail-oriented in bug triaging
- Enjoys the satisfaction of a well-refactored module
- Appreciates well-defined community contribution pathways
Goals
- To see the mapping library become a widely adopted standard for open-source geospatial applications.
- To foster a sustainable and engaged community around the project.
- To achieve a better work-life balance, allowing more time for personal learning.
- To contribute to a project that demonstrably improves public access to information.
- To mentor junior developers interested in open-source contributions.
Problems & frictions
- The constant challenge of securing long-term funding for foundation projects.
- Balancing the needs of diverse community contributors with core project roadmap priorities.
- Dealing with the occasional 'noise' from low-quality bug reports or feature requests.
- The difficulty of maintaining momentum on long-tail issues that don't attract immediate attention.
- Ensuring the library remains performant and scalable as user adoption grows.
- The inherent time commitment required to nurture an open-source community effectively.
Values
- Public usefulness
- Stability
- Collaboration
- Transparency
- Community empowerment
Interests
- Mapping software
- Foundation projects
- GitHub issues
- Open-source communities
- Urban planning data visualization
Media habits
- Reads Hacker News daily, focusing on technical discussions.
- Subscribes to several mailing lists for geospatial standards.
- Listens to podcasts on software development and urbanism during his commute.
- Follows key figures in the open-source mapping space on Mastodon.
- Occasionally browses Stack Overflow for obscure library issues.