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

Sverre Schipper

Sverre Schipper

Developer relations manager for an open-source project

Full-depth AI personas

Why this persona fits the audience

He manages a small community blog for an open-source project with two volunteer editors, collecting ideas in GitHub issues, drafting in Google Docs, and using a spreadsheet to track author, translation status, and publish dates. The site runs on paid shared hosting and is updated mostly around releases and community events.

  • Age: 36
  • Location: Amsterdam, Netherlands
  • Occupation: Developer relations manager
  • Income: €66k
  • Education: Bachelor's degree in Information Systems
  • Company size: Small (under 50 employees for the open-source project)
  • Years in role: 4
“The real value isn't just in the code, but in how we share the knowledge around it, making it accessible for everyone.”

Born and raised in a smaller town near Utrecht, Sverre Schipper developed an early fascination with how things work, a trait that naturally steered him towards information systems during his Bachelor's degree. After graduation, he spent a few years in a junior developer support role, which exposed him to the nuances of community management within technical projects. He found his niche not in coding itself, but in bridging the gap between developers and the wider community, fostering understanding and participation. Four years ago, he joined his current open-source project as their first dedicated Developer Relations Manager. His role is characterized by resourcefulness; he thrives on making the most of limited budgets, evident in his management of the community blog. He meticulously uses GitHub issues for content ideation, Google Docs for collaborative drafting, and a robust spreadsheet to track the complex workflow of authoring, translation, and publishing. This structured approach is essential given the blog's reliance on volunteer editors and its update cadence, which largely aligns with project releases and significant community events. Sverre isn't driven by status or immense wealth; his satisfaction comes from enabling clear communication and reliable information flow within the open-source ecosystem. He views his income as a means to maintain a comfortable, stable life and occasionally invest in tools that genuinely improve his work or personal learning. His apartment in Amsterdam is functional and minimalist, reflecting a preference for order and efficiency over excessive possessions. He’s conscious of time, seeing it as a precious resource to be managed effectively, both in his professional life and his personal pursuits, which often involve exploring new open-source technologies or contributing to community documentation.

Background & daily life

A day in their life

Sverre's weekday typically starts with a cycle commute to a local co-working space, followed by reviewing GitHub issues and pull requests related to the project blog. He spends a good portion of the morning responding to community members, coordinating with his volunteer editors on upcoming posts, and drafting new content in Google Docs. Lunch is usually a quick, healthy meal from a nearby cafe. The afternoon might involve reviewing translated content, updating the blog's spreadsheet tracker, or participating in a brief async sync with the core dev team about upcoming release announcements. He often dedicates the last hour to exploring new open-source tools or reading industry news before cycling home, sometimes stopping at the gym or for a quick drink with a friend.

Lifestyle

Sverre lives a fairly routine life in his Amsterdam apartment, enjoying the city's cycling culture and the proximity to green spaces. He's not extravagant with his income, prioritizing experiences and occasional tech purchases over material goods. Weekends often involve a mix of catching up with a small circle of close friends, exploring new cafes, or dedicating time to personal side projects related to open source. He’s mindful of his health, trying to incorporate regular runs along the canals and enjoys cooking simple, healthy meals. His social interactions are usually comfortable and focused on shared interests rather than superficial small talk.

Work life

As a DevRel manager for a niche open-source project, Sverre's role is hands-on and community-driven. He juggles content creation for the project's blog, coordinating with volunteer editors, and managing contributions from the developer community. The tight budget means he's resourceful, relying on free tools and shared hosting, which necessitates careful planning around release cycles. His days are often a blend of writing, reviewing pull requests for blog posts, engaging in GitHub discussions, and planning future content. Collaboration with the core development team is crucial but infrequent, with most communication happening asynchronously.

Relationships

Sverre maintains a close-knit circle of friends, mostly met through university or shared tech interests, with whom he enjoys thoughtful discussions. His relationship with his parents is supportive but geographically distant. Within the open-source project, his primary interactions are with the two volunteer editors and the core maintainers, fostering a relationship built on mutual respect and shared project goals.

How they decide

Sverre is a methodical and research-driven decision-maker. He prioritizes gathering information, assessing long-term implications, and seeking consensus from stakeholders when appropriate, especially when it involves community resources or project direction. He tends to be cautious, weighing pros and cons carefully before committing to a course of action.

How they sound

Speaks with a clear, measured cadence. His Dutch accent is noticeable but refined. He uses technical terms accurately and without pretension. Tends to be formal in initial communications but warms up, incorporating common Dutch phrases like 'gezellig' when appropriate. Avoids overly enthusiastic or sales-like language, preferring direct and informative communication. His tone is generally calm and reassuring.

Personality traits

  • Methodical
  • Pragmatic
  • Detail-oriented
  • Patient
  • Slightly reserved
  • Organized
  • Consistent
  • Thoughtful
  • Adaptable

Goals

  • Increase community engagement with the project's blog by 20% next year.
  • Develop a sustainable workflow for content translation to reach a broader international audience.
  • Contribute a small, useful tool to another open-source project he uses.
  • Maintain a healthy work-life balance without sacrificing his commitment to the project.
  • Explore more effective ways to archive and surface valuable historical community discussions.

Problems & frictions

  • Balancing the need for consistent content with the sporadic availability of volunteer contributors.
  • Limited budget for hosting and necessary tooling for the blog.
  • Keeping up with the rapid pace of open-source development and ensuring blog content remains relevant.
  • Managing translation efforts efficiently with limited resources.
  • Finding time for proactive community outreach amidst daily content management tasks.
  • Ensuring the blog platform remains stable and performant on shared hosting.

Values

  • open collaboration
  • reliability
  • transparency
  • community empowerment
  • knowledge sharing

Interests

  • open source
  • dev communities
  • web publishing
  • technical writing
  • distributed systems
  • digital gardening

Media habits

  • Reads Hacker News daily
  • Follows key figures in open source on Mastodon
  • Listens to tech podcasts during commute
  • Subscribes to newsletters from open-source foundations
  • Watches talks from developer conferences on YouTube

Questions & answers

Sverre Schipper’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Drukarnia (https://drukarnia.blog/en/) 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 Drukarnia this month? Well, currently, we manage our community blog using GitHub issues for ideas, Google Docs for drafting, and a spreadsheet for tracking. It’s a system that works for our limited resources. The main hesitation would be integrating Drukarnia into our workflow without disrupting our volunteer editors or our release-cycle driven publishing schedule. I'm also curious about the extent of its SEO capabilities beyond what's mentioned, as that's crucial for visibility. Given our tight budget, I'd be looking for a very affordable solution. I would not pay more than $10 per month.
    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.