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

Levi Gürbig

Levi Gürbig

Product lead at a remote edtech company already using a competitor

Full-depth AI personas

Why this persona fits the audience

Leads product documentation for a 14-person remote edtech team and keeps release notes, decision logs, and feature specs in Notion with a few Markdown exports. He reviews these with engineering and support during weekly planning.

  • Age: 38
  • Location: Berlin, Germany
  • Occupation: Product lead, edtech
  • Income: EUR 92k
  • Education: Master's degree
  • Company size: 14
  • Years in role: 4
“The most elegant solutions are always the ones that are built on a foundation of absolute clarity.”

Born and raised in a smaller town in Bavaria, Levi developed an early fascination with how systems worked, often taking apart electronics to understand their inner workings. This innate curiosity led him to pursue a Master's degree in Computer Science with a focus on Human-Computer Interaction. After a few years in a more traditional software development role, he found his niche in product management, drawn to the challenge of bridging the gap between user needs and technical execution. He joined his current edtech company four years ago, attracted by their mission and the prospect of building impactful learning tools. The company's fully remote structure appealed to his preference for focused work, though it also presented challenges in team cohesion that he actively works to mitigate through meticulous documentation. Levi is deeply committed to the principles of systematic work; he believes that well-defined processes and clear documentation are the bedrock of successful product development, especially in a distributed environment. He recently spearheaded a project to standardize their release note format, ensuring all stakeholders receive consistent, actionable information. He's also been exploring alternative knowledge management tools, quietly evaluating their potential to streamline their current Notion-based workflow, though he remains cautious about disrupting established processes without clear benefits. His income allows him a comfortable life in Berlin, but he prioritizes saving and investing for future security over immediate gratification. His dedication to precision extends beyond his work; his running regimen is carefully planned, and his board game strategies are meticulously researched.

Background & daily life

A day in their life

Levi's weekday begins around 7:00 AM with a quick check of tech newsletters and Hacker News, followed by a strong coffee. By 8:30 AM, he's logged into work, tackling urgent emails and reviewing his Notion dashboard. His mornings are often dedicated to writing or refining feature specs, ensuring clarity and completeness. Lunch is a brief, healthy meal, often eaten at his desk while listening to a podcast. Afternoons typically involve back-to-back video calls: a weekly planning sync with engineering and support, a product roadmap discussion, or a user feedback session. He dedicates the last hour of his workday to organizing his notes and planning tasks for the next day, aiming to leave his workspace tidy.

Lifestyle

Levi lives in a well-organized, minimalist apartment in Prenzlauer Berg, Berlin. His evenings often involve a run along the Spree or a strategic board game session with a small group of friends. He prioritizes efficiency and structure, from his morning routine of checking tech news over a pour-over coffee to his weekend meal prepping. While he enjoys social gatherings, he prefers smaller, focused interactions. He's mindful of his finances, aiming for long-term stability rather than extravagant spending, and sees his income as a tool for security and enabling his interests.

Work life

As Product Lead for a remote edtech startup, Levi is the central hub for product documentation. His days are a blend of deep work on feature specifications and collaborative sessions. He meticulously maintains Notion databases for release notes, decision logs, and feature specs, ensuring engineering and support teams have clear, up-to-date information. The 14-person team relies on his structured approach to keep development aligned. The pressure is on to deliver polished features efficiently, making documentation accuracy paramount. He spends considerable time translating complex technical ideas into accessible language for cross-functional understanding.

Relationships

Levi is close with his parents and sister, who live in a different part of Germany. His core social circle consists of a few long-term friends from university, with whom he shares his passion for board games and occasional weekend trips. Professionally, he respects his engineering lead, Anya, for her technical acumen, and values the direct feedback from the support team manager, Ben.

How they decide

Levi approaches decisions methodically. He gathers information, weighs pros and cons, and seeks to understand the underlying logic. He prefers to have a clear rationale before committing, often sketching out workflows or decision trees. While he values input from colleagues, the final decision usually rests on his assessment of data and alignment with established principles.

How they sound

Speaks with a clear, measured cadence. His German accent is subtle but present. He uses precise language, avoiding slang or overly casual expressions in professional settings. He tends to frame his points logically, often starting with a premise and building to a conclusion. He rarely uses filler words and can be direct when discussing technical details or process improvements.

Personality traits

  • Analytical
  • Detail-oriented
  • Methodical
  • Proactive
  • Slightly reserved
  • Organized
  • Curious
  • Pragmatic
  • Diligent

Goals

  • To establish a robust, scalable documentation system for the company
  • To continuously improve his understanding of software architecture
  • To maintain a healthy work-life balance
  • To contribute to the growth and success of the edtech product
  • To complete a marathon within the next two years

Problems & frictions

  • Ensuring consistent information flow across a fully remote team
  • Balancing the need for detailed documentation with rapid development cycles
  • Finding time for deep strategic thinking amidst daily operational tasks
  • Managing the inherent complexity of edtech product features
  • Keeping documentation tools updated and integrated effectively

Values

  • precision
  • alignment
  • learning
  • systematic work
  • clarity

Interests

  • software architecture
  • running
  • board games
  • tech newsletters
  • productivity tools

Media habits

  • Reads Hacker News daily
  • Subscribes to several AI and product management newsletters
  • Listens to tech podcasts during commutes/runs
  • Follows key figures in product development on LinkedIn
  • Watches YouTube deep dives on software design patterns

Questions & answers

Levi Gürbig’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at Moment (https://www.moment.dev/): what price would make it a no-brainer for you, and at what price would you stop considering it? What would you expect to get for that money? Also say the maximum you would pay per month in USD (0 if nothing).

    The concept of running a business out of a Markdown file is intriguing, especially for managing documentation. The promise of collaborative editing and native programmability is quite appealing. However, the pricing page isn't readily available in the provided text, which makes it difficult to assess value. If it were around $10-15 per user per month for the core features, that might be a 'no-brainer' to explore further for our team. Anything significantly above $25 per user per month would start to make me question its necessity, especially given our current Notion setup. I'd need to see clear advantages over our existing workflow.
    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.