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

Lola Illing

Lola Illing

Customer education manager at an API company

Full-depth AI personas

Why this persona fits the audience

Owns customer education for a Berlin API startup with a three-person content/support pod. She keeps developer docs, release notes, and help articles in sync, and regularly reviews which common questions can be answered from source docs versus which still need human follow-up.

  • Age: 37
  • Location: Berlin, Germany
  • Occupation: Customer Education Manager
  • Income: €78k gross
  • Education: M.A. in Technical Communication
  • Company size: Startup (approx. 50 employees)
  • Years in role: 4
“The most elegant solution is often the one that anticipates the user's next question before they even ask it.”

Lola Illing's journey into the world of technical communication began not with a passion for code, but for clarity. Growing up in a family where her father was a meticulous watchmaker and her mother a librarian, she absorbed a deep appreciation for precision, organization, and the power of well-structured information. This foundation led her to pursue a Master's degree in Technical Communication, where she honed her skills in dissecting complex subjects and rendering them accessible. Her early career involved roles in technical writing for software companies, where she consistently found herself drawn to the 'why' behind user confusion, not just the 'what' of the documentation. Four years ago, she joined her current Berlin-based API startup, initially as a senior technical writer, and was promoted to Customer Education Manager two years later. In this role, she has built the customer education function from the ground up, establishing processes and a small team to manage the company's developer documentation, release notes, and help center. She is deeply invested in the developer experience, believing that clear, accurate, and easily discoverable information is paramount to API adoption and success. Lola is currently focused on optimizing the flow of information from engineering to documentation, ensuring that the knowledge base evolves in lockstep with the product. She recently championed a project to implement a more robust internal review process for all new documentation, aiming to catch inconsistencies and technical inaccuracies before they reach customers. Her approach is highly methodical; she believes in data-driven improvements, constantly analyzing support ticket trends and user feedback to identify areas for content enhancement. While she values efficiency, she never sacrifices accuracy for speed, understanding that trust is built on reliable information. She sees her role as a bridge between the technical intricacies of the API and the practical needs of its users, a role she approaches with a quiet but firm dedication. Her financial habits are conservative, prioritizing savings for long-term security and professional development over immediate gratification, reflecting a life built on thoughtful planning and a commitment to enduring quality.

Background & daily life

A day in their life

Lola's typical weekday begins around 7:00 AM with a quiet breakfast and reviewing industry news. She commutes to the office by 9:00 AM, often listening to a podcast. Her morning is usually spent in team syncs, reviewing content drafts, and analyzing support ticket trends. After a quick lunch, she dedicates the afternoon to deeper work: refining information architecture for a new API endpoint, planning content for upcoming releases, or collaborating with product managers. She often stays until 6:00 PM, ensuring all urgent tasks are addressed before heading home for a quiet evening, perhaps with a book or a personal project.

Lifestyle

Lola's life in Berlin is a carefully curated balance of professional dedication and personal quietude. She lives alone in a bright, minimalist two-room apartment in Prenzlauer Berg, filled with plants and well-organized bookshelves. Her evenings are often spent reading technical articles, working on a personal coding project, or enjoying a quiet dinner. Weekends might involve a long bike ride through Tiergarten, visiting a small gallery, or meeting a close friend for coffee. She's mindful of her finances, saving consistently for future travel and professional development, and prioritizes a healthy routine with regular exercise and balanced meals, avoiding excessive spending on fleeting trends.

Work life

As the Customer Education Manager at a growing API startup, Lola is the linchpin for all external-facing documentation and support content. Her days are a constant juggle between strategic planning and tactical execution. She leads a small but mighty team of two, responsible for developer docs, release notes, and help articles. A significant portion of her time is dedicated to analyzing support tickets and user feedback to identify knowledge gaps. She's currently focused on refining the process for updating documentation based on new feature releases, ensuring consistency across all platforms. The pressure to scale educational resources without compromising quality is a constant, driving her to seek more efficient workflows.

Relationships

Lola maintains a small but strong circle of friends, mostly met through university or previous jobs, with whom she shares deep conversations and occasional weekend trips. Her family lives in a different part of Germany, and they connect via weekly video calls. Professionally, she has a good working relationship with her direct reports and the engineering leads, though she sometimes finds it challenging to get their immediate attention for documentation reviews.

How they decide

Lola is a highly analytical and research-driven decision-maker. She thoroughly investigates options, weighing pros and cons, and often seeks out data or expert opinions before committing. She values evidence and logic, preferring structured approaches over impulsive choices. She will consult internal stakeholders and review best practices in her field.

How they sound

Speaks with a clear, measured cadence, favoring precise language. Her tone is generally calm and professional, even when discussing complex technical topics. She avoids jargon where possible when speaking to non-technical colleagues but uses accurate technical terms when appropriate. She tends to be direct but polite, and rarely uses slang or overly casual expressions. Her German accent is subtle but present.

Personality traits

  • meticulous
  • analytical
  • patient
  • organized
  • detail-oriented
  • proactive
  • methodical
  • calm under pressure
  • resourceful

Goals

  • Establish a comprehensive, self-service knowledge base that significantly reduces inbound support queries.
  • Develop a scalable training program for new API users that can be automated.
  • Advance into a lead role managing a larger documentation and education team.
  • Contribute to open-source projects related to technical writing tools.
  • Achieve a better work-life integration, allowing more time for personal learning and hobbies.

Problems & frictions

  • Keeping documentation perfectly synchronized with rapid product development cycles.
  • Ensuring the content team has the necessary technical context without overwhelming them.
  • Measuring the true impact and ROI of customer education efforts.
  • Balancing the need for detailed, accurate information with the desire for concise, easy-to-digest content.
  • Managing the expectations of different user segments with varying technical proficiencies.

Values

  • accuracy
  • helpfulness
  • structured communication
  • clarity
  • efficiency

Interests

  • technical writing
  • developer experience
  • information architecture
  • knowledge management
  • user onboarding

Media habits

  • Reads industry blogs (e.g., Write the Docs, API-related tech news)
  • Listens to podcasts on tech and communication during commutes
  • Follows key figures in technical documentation and developer relations on LinkedIn
  • Subscribes to newsletters from documentation tools and API providers
  • Occasional participation in online forums related to technical writing

Questions & answers

Lola Illing’s public research answers, newest questions first. Up to 10 per page.

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

    This looks like an interesting tool for grounding AI responses in our documentation. My main hesitation for trying it this month would be bandwidth. My team of three is currently focused on a major overhaul of our developer docs and integrating a new internal review process. We're trying to catch inconsistencies before they reach customers, and I'm concerned that introducing a new system, even for a trial, would pull focus from these critical tasks. Currently, we handle common questions by directing users to specific sections in our help articles or developer docs. If the question is highly specific or technical and not covered, it goes to a support ticket. The pricing isn't immediately clear to me from the page; I'd need to understand how it scales with our user base and content volume. If it were straightforward, I might consider up to $150 per month, but that's highly dependent on features and scale.
    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.