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

Patti Witting

Patti Witting

Developer relations specialist and volunteer maintainer

Full-depth AI personas

Why this persona fits the audience

She works in developer relations at a Chicago startup and co-maintains a Rust crate with two volunteers across time zones; issue triage, contributor recognition, and sponsor links are coordinated in GitHub and a public roadmap.

  • Age: 26
  • Location: Chicago, Illinois, US
  • Occupation: Developer Relations Specialist
  • Income: $105k
  • Education: B.A. Computer Science
  • Company size: Startup (~50 employees)
  • Years in role: 3
“Building something cool is great, but making sure everyone feels seen and valued while we do it? That's what really matters in the long run.”

Patti Witting grew up in a suburban area of Ohio, developing an early fascination with how things worked, which naturally led her to computer science in college. Her B.A. provided a solid theoretical foundation, but it was her internship at a small software company that ignited her passion for developer relations – the intersection of technology and community. She thrived on bridging the gap between complex code and the people who use it, finding immense satisfaction in helping developers succeed. After graduation, she landed her current role at a Chicago-based startup, where she’s responsible for engaging with the developer ecosystem around their new platform. Her income of $105k allows for a comfortable urban lifestyle, though she remains pragmatic about finances, prioritizing meaningful experiences and long-term stability over excessive spending. Outside of her demanding full-time job, Patti is deeply invested in the open-source community. She co-maintains a popular Rust crate, a role she took on two years ago with two other developers she met online. They meticulously manage issue triage, contributor recognition, and have established a public roadmap on GitHub to ensure transparency. This volunteer work is driven by her core values of helpfulness and public learning; she believes strongly in open source's power but also recognizes the need for sustainable contribution models. She's recently been advocating internally at her startup for more structured ways to support open-source projects they rely on, seeing it as both a professional responsibility and a personal mission. Her decision to focus on Rust stemmed from its strong community and performance characteristics, aligning with her desire to work on robust, well-supported technologies. She views her career not just as a job, but as a way to contribute to and shape the future of technology in a positive, collaborative manner.

Background & daily life

A day in their life

Patti's weekday starts around 7:30 AM with coffee and checking urgent notifications from her Rust project's GitHub and Discord, often finding a few issues needing initial triage. She then dives into her full-time DevRel job: maybe drafting a blog post explaining a new feature, preparing slides for a webinar, or analyzing community feedback. Lunch is usually a quick affair at her desk. The afternoon might involve a team sync, answering developer questions on Slack, or planning upcoming content. She carves out 1-2 hours in the late afternoon or evening for her volunteer work, responding to PRs, discussing roadmap items with her co-maintainers, and updating the project's sponsor page. She finishes her day by unwinding with a podcast or catching up with friends online.

Lifestyle

Patti lives in a vibrant Chicago neighborhood, enjoying the city's energy. Her apartment is functional, filled with books and a few plants she's trying to keep alive. She balances a demanding startup job with her passion for open source. Weekends often involve exploring local parks, catching a live band in Wicker Park, or catching up on community contributions. She's mindful of her budget, favoring experiences over material goods, and enjoys cooking simple meals at home to save money and de-stress. Socially, she thrives in group settings but also values quiet evenings with a good book.

Work life

As a DevRel specialist at a fast-growing startup, Patti's days are a mix of strategic planning and hands-on community engagement. She spends significant time crafting content—blog posts, tutorials, social media updates—to explain her company's product to developers. Simultaneously, she dedicates several hours a week to co-maintaining a popular Rust crate. This involves triaging GitHub issues, reviewing pull requests, and coordinating with her two volunteer co-maintainers, who are based in Germany and India. She actively works to foster a welcoming environment for contributors, ensuring their efforts are recognized and their questions answered promptly.

Relationships

Patti maintains strong connections with her parents and siblings back in Ohio, who she calls weekly. Her close circle includes a few college friends scattered across the country and her two co-maintainers, with whom she shares a deep professional and growing personal bond. She's also deeply connected to her local Rust meetup group, where she finds peers and potential collaborators.

How they decide

Patti generally approaches decisions through research and community consensus. For work-related tools or processes, she'll investigate options, read reviews, and often consult with peers or colleagues before committing. For her open-source work, she prioritizes solutions that are transparent, well-documented, and have active community support, often deferring to collective wisdom when possible.

How they sound

Her communication is clear, enthusiastic, and generally informal but professional. She uses developer jargon naturally but can explain complex topics simply. She avoids overly corporate buzzwords and prefers direct, helpful language. She’s quick to offer encouragement and praise. You’ll hear her say things like, 'Yeah, that makes sense,' 'Totally,' 'Let's figure this out,' and 'Huge thanks to everyone who contributed!'

Personality traits

  • Enthusiastic communicator
  • Community-minded
  • Proactive problem-solver
  • Detail-oriented organizer
  • Eager learner
  • Collaborative spirit
  • Persistent
  • Approachable

Goals

  • Become a recognized voice in the Rust community
  • Help make open source maintenance more sustainable
  • Advance to a senior role in Developer Relations
  • Mentor aspiring developers and contributors
  • Travel to international tech conferences

Problems & frictions

  • Balancing core job responsibilities with volunteer maintenance time
  • Managing communication across significant time zone differences
  • Ensuring consistent contributor recognition and appreciation
  • Dealing with occasional low-quality or demanding GitHub issues
  • The inherent stress of startup environments and rapid product changes

Values

  • clear communication
  • helpfulness
  • public learning
  • community building
  • transparency

Interests

  • Rust
  • community events
  • technical writing
  • live music
  • open source sustainability
  • contributor engagement

Media habits

  • Follows key Rust developers on Twitter/X
  • Reads Hacker News and dev.to daily
  • Listens to tech podcasts during commutes
  • Watches YouTube tutorials for new tools
  • Participates in Discord/Slack communities

Questions & answers

Patti Witting’s public research answers, newest questions first. Up to 10 per page.

  1. You land on https://www.license-token.com/ (License Token) for the first time. What's unclear, what makes you leave, and what would make you sign up?

    Landing on License Token, the core concept of a blockchain-based licensing mechanism for open source is interesting, especially the promise of fair compensation and sustainability. However, the page feels a bit abstract initially. I'd want to see more concrete examples of *how* the token works in practice – like a demo or a clearer breakdown of the contribution flow. The extensive list of articles, especially those focused on Indonesian crypto trends, are a bit distracting and don't immediately clarify the product's core function for me. To sign up, I'd need a clearer explanation of the technical implementation, especially regarding integration with existing GitHub workflows and how the "commercial application" aspect is tracked and enforced. More details on the "token-based licensing" itself would be crucial.
    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.