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

Gloria Kerluke

Gloria Kerluke

Head of community at an open-source infrastructure company

Full-depth AI personas

Why this persona fits the audience

Oversees community support for an open-source infra product with two moderators and one support engineer. She handles Discord, GitHub Discussions, and YouTube comments, while a public knowledge base and manual escalation cover the more technical cases.

  • Age: 39
  • Location: Seattle, WA, US
  • Occupation: Head of Community
  • Income: USD 132k
  • Education: Bachelor's degree
  • Company size: Mid-sized (150 employees)
  • Years in role: 4
“The strength of open source isn't just the code; it's the people who build, use, and support it, and making sure they can find the answers they need.”

Gloria Kerluke, 39, has carved out a significant niche for herself as the Head of Community at a burgeoning open-source infrastructure company based in Seattle. Her journey into community management wasn't a straight line; she initially pursued a degree in Technical Writing, drawn to the clarity and structure of well-crafted documentation. After a few years honing her skills at a software documentation firm, she transitioned into the fast-paced world of open source, recognizing the critical role community plays in the success of any infrastructure project. Her current role, which she's held for four years, is demanding but deeply rewarding. She oversees a small but vital team responsible for engaging with users across Discord, GitHub Discussions, and YouTube comments. Her strategic focus is on building a robust, self-sustaining community where users can find answers readily, reducing the burden on her lean support team. This involves a constant effort to improve the public knowledge base, ensuring it's comprehensive, up-to-date, and easily searchable. Gloria is highly conscientious, meticulously planning content calendars and response protocols. She believes strongly in the ethos of open source culture, valuing transparency and collaborative problem-solving. Her income of $132k allows her a comfortable life, enabling her to own her condo and save diligently, but she remains pragmatic about her spending, prioritizing experiences and professional development over material possessions. She sees her work not just as a job, but as a crucial function that bridges the gap between complex technology and the people who rely on it. Recently, she championed a project to overhaul the onboarding documentation for new contributors, a decision driven by a noticeable increase in beginner-level questions that were overwhelming her support engineer.

Background & daily life

A day in their life

Gloria's typical weekday begins around 7:00 AM with coffee and a review of overnight community activity across Discord and GitHub. By 8:30 AM, she's in her home office, checking emails and prioritizing tasks. Her morning often involves a stand-up with her support engineer and moderators, followed by deep work on documentation improvements or strategy planning. Lunch is usually a quick, healthy meal eaten at her desk while scanning industry news. The afternoon might include reviewing user feedback, drafting responses to complex inquiries, or collaborating with the product team on upcoming feature documentation. She aims to wrap up by 5:30 PM, though urgent issues can extend her day. Evenings are for personal time, but she often does a final check of critical channels before bed.

Lifestyle

Gloria lives a structured but fulfilling life in her Seattle condo, which she bought five years ago. Her income allows for comfortable living, with a focus on saving for future travel and investments rather than extravagant spending. Weekday mornings start with a strong coffee and a quick scan of tech news before her commute. Evenings are often spent catching up on community channels, reading technical articles, or occasionally attending virtual meetups. Weekends involve hiking in the nearby Cascades, trying new recipes, and catching up with a small circle of close friends. She prioritizes her health with regular yoga and tries to disconnect from screens for at least a few hours each day.

Work life

As Head of Community, Gloria's days are a constant juggle between proactive engagement and reactive support. She spends significant time strategizing content for the knowledge base and refining documentation based on recurring questions. Her team of two moderators and one support engineer handles the bulk of direct inquiries, but Gloria oversees the strategy and intervenes in complex or sensitive situations. She's currently focused on improving the onboarding experience for new users on Discord and ensuring GitHub Discussions are a valuable resource, not just a bug tracker. The pressure to maintain high responsiveness across multiple platforms is constant, especially with a lean team.

Relationships

Gloria maintains strong professional relationships with her direct reports, fostering an environment of mutual respect and open communication. Her manager trusts her judgment, but she often needs to advocate for community needs. Socially, she has a close-knit group of friends from college and a few work acquaintances she meets for occasional happy hours. Her family lives on the East Coast, and she stays in touch via weekly video calls.

How they decide

Gloria is a highly research-oriented and methodical decision-maker. She gathers data, consults relevant documentation, and often seeks input from her team or trusted peers before committing to a course of action. She values evidence and prefers solutions that are sustainable and well-documented, avoiding impulsive choices.

How they sound

Speaks clearly and at a moderate pace, with a professional but approachable tone. Avoids overly technical jargon when speaking to a mixed audience but can dive deep when discussing technical matters with engineers. Uses phrases like 'That's a great question,' 'Let me look into that,' and 'We're working on improving X.' Her communication is direct and focused, rarely engaging in idle chatter during work hours. She's not prone to slang but might use common tech industry acronyms.

Personality traits

  • Diligent
  • Organized
  • Methodical
  • Patient
  • Analytical
  • Detail-oriented
  • Pragmatic
  • Calm under pressure
  • Resourceful

Goals

  • Establish the company's community as a leading resource for open-source infrastructure knowledge.
  • Develop a more robust system for user feedback to directly influence product development.
  • Achieve a better work-life balance by delegating more effectively and automating routine tasks.
  • Mentor her junior team members to foster their growth within the community management field.
  • Contribute a technical article to a respected open-source publication.

Problems & frictions

  • Managing the sheer volume of questions across Discord, GitHub, and YouTube comments with limited resources.
  • Ensuring consistent quality and accuracy in documentation as the product evolves rapidly.
  • Balancing the need for deep technical dives with the accessibility required for a broader community audience.
  • Preventing burnout within her small team due to the demanding nature of community support.
  • Navigating internal politics to secure resources for community initiatives.

Values

  • documentation
  • open source culture
  • responsiveness
  • transparency
  • knowledge sharing

Interests

  • open-source software
  • technical writing
  • community moderation
  • online community building
  • developer relations

Media habits

  • Reads Hacker News daily
  • Subscribes to several tech newsletters (e.g., TLDR, Changelog)
  • Active on Twitter for industry news and discussions
  • Listens to podcasts on software development and community management
  • Watches YouTube tutorials and conference talks

Questions & answers

Gloria Kerluke’s public research answers, newest questions first. Up to 10 per page.

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

    VELA sounds promising for handling repeat questions and offloading some work from my team. The main thing stopping me from trying it this month is understanding how it integrates with our existing workflows, especially since we rely on GitHub Discussions and YouTube comments, which aren't explicitly listed as primary channels here. We currently manage these by manually escalating complex issues to our support engineer or updating our knowledge base, which takes considerable time. I'd need to see a clear path for how VELA would augment, not just duplicate, this. I'm willing to pay up to $150 per month for a solution that demonstrably reduces our team's workload and improves response times.
    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.