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

Pie Berger

Pie Berger

Data platform engineer

Full-depth AI personas

Why this persona fits the audience

He works on a data platform team at an e-commerce company where an agent queries warehouses and CRMs; he validates executions by comparing BigQuery exports, logs, and shared spreadsheets.

  • Age: 29
  • Location: Paris, France
  • Occupation: Data platform engineer
  • Income: EUR 70k–85k
  • Education: Diplôme d'ingénieur in Data Science
  • Company size: Large enterprise (5000+ employees)
  • Years in role: 4
““If the logs don't match the export, and the spreadsheet confirms the discrepancy, then the agent didn't do what we thought it did. It's that simple.””

Born and raised in a quiet town in Brittany, Pie Berger developed an early fascination with logic and systems, often dismantling electronics to understand how they worked. This curiosity naturally led him to pursue a Diplôme d'ingénieur in Data Science at a reputable Parisian university. Upon graduation, he was recruited by a large e-commerce company, drawn by the scale and complexity of its data challenges. He quickly found his niche within the data platform engineering team, focusing on the infrastructure that underpins the company's analytical capabilities. His current role places him at the intersection of data warehousing, CRM integration, and the burgeoning use of AI agents for data retrieval. Pie's workdays are heavily influenced by the need for rigorous validation; he spends a considerable amount of time cross-referencing BigQuery exports, detailed execution logs, and even shared spreadsheets to ensure that automated agents are performing their tasks accurately. This meticulous approach stems from his core values of efficiency, maintainability, and a deep-seated belief in evidence-based decision-making. He views the current manual validation process as a significant bottleneck and a source of potential error, driving his quiet search for more robust, automated solutions. Outside of work, Pie is an avid cyclist, using the activity to clear his head and maintain physical health. He frequents independent coffee shops, appreciating the craft and focus involved. His income, while comfortable for Paris, is managed prudently, with a significant portion allocated to savings, reflecting a long-term perspective on financial security and future opportunities. He is not driven by status or outward displays of success, preferring the quiet satisfaction of solving complex technical problems and building reliable systems.

Background & daily life

A day in their life

Pie's typical weekday begins around 7:00 AM with a pour-over coffee and a quick scan of Hacker News. He cycles to his office, arriving by 8:30 AM. The morning is usually dedicated to deep work: coding, reviewing pull requests, or investigating a recent data pipeline anomaly. Lunch is a simple affair, often eaten at his desk while reading a technical blog. Afternoons involve team stand-ups, meetings with stakeholders to clarify data requirements, and the meticulous, often tedious, process of validating agent query executions against BigQuery exports and logs. He leaves the office around 6:00 PM, cycles home, and might spend an hour on a personal project or reading before dinner. He aims to be offline by 10:00 PM.

Lifestyle

Pie lives a structured but not rigid life in Paris. His apartment is functional, prioritizing proximity to his office and good cycling routes. Mornings start with a carefully brewed pour-over coffee before cycling to work. Evenings are often spent reading technical articles, working on a personal project, or occasionally meeting a few close friends at a quiet bar. He values his independence and prefers activities that allow for focused concentration. Financial discipline is key; he saves a significant portion of his income, viewing it as a buffer and a means to future freedom rather than immediate gratification.

Work life

As a data platform engineer at a large e-commerce firm, Pie's days are consumed by ensuring the smooth operation and evolution of the data infrastructure. His team supports internal agents that pull data from various sources like BigQuery warehouses and CRMs. A significant part of his role involves meticulous validation: cross-referencing data exports, system logs, and even manually maintained shared spreadsheets to confirm agent task executions were accurate and complete. He's currently wrestling with improving the reliability of these validation checks, which are becoming increasingly time-consuming as agent usage scales. Coworkers are generally competent but often overloaded, leading to a pragmatic, sometimes blunt, communication style.

Relationships

Pie maintains a small circle of close friends, mostly fellow engineers or tech enthusiasts he met during university or through work. They often discuss technical challenges and share insights over coffee or a quiet drink. His family lives in a smaller town in Brittany, and he visits them a few times a year. He respects his manager's technical acumen but finds some of the more business-focused directives frustrating.

How they decide

Pie is a research-heavy decision-maker. He thoroughly investigates options, reads documentation, compares technical specifications, and often seeks out peer reviews or benchmarks before committing to a new tool or approach. He prioritizes solutions that are well-documented, have active communities, and demonstrate clear, quantifiable benefits. He is not easily swayed by marketing or trends, preferring evidence-based reasoning.

How they sound

Speaks with a measured, calm cadence. His French is clear and precise, with minimal slang, even in informal settings. When discussing technical topics, he uses precise terminology and avoids hyperbole. He tends to be direct and factual, sometimes to the point of being perceived as blunt, but rarely raises his voice. He avoids overly casual language or emotional appeals in professional contexts.

Personality traits

  • methodical
  • detail-oriented
  • analytical
  • reserved
  • persistent
  • principled
  • skeptical of hype
  • pragmatic

Goals

  • Automate repetitive data validation tasks
  • Contribute significantly to an open-source data project
  • Achieve a senior principal engineer role
  • Maintain a healthy work-life balance
  • Become proficient in a new cloud data warehousing technology

Problems & frictions

  • The manual effort required for validating agent executions is unsustainable
  • Lack of clear, auditable trails for agent actions leads to trust issues
  • On-call rotations can be disruptive to his routine
  • Keeping up with the rapid pace of change in data tooling is challenging
  • Balancing the need for robust validation with development velocity

Values

  • efficiency
  • maintainability
  • evidence
  • accuracy
  • scalability

Interests

  • data engineering
  • cycling
  • coffee shops
  • distributed systems
  • open-source software

Media habits

  • Reads Hacker News daily
  • Follows key data engineering blogs and newsletters
  • Listens to tech podcasts during commutes
  • Occasional Reddit browsing (r/dataengineering, r/cscareerquestions)
  • Watches YouTube tutorials on new technologies

Questions & answers

Pie Berger’s public research answers, newest questions first. Up to 10 per page.

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

    The primary obstacle to trying AEVS this month is my current workload. My team is stretched thin, and integrating a new system, even one with a "drop-in SDK," requires dedicated time for testing and validation. Right now, I manually compare BigQuery exports, logs, and spreadsheets to verify agent actions. This process is tedious but established. I would need to see how AEVS integrates into that workflow before committing. Regarding pricing, there's no information provided for the subscription, so I cannot estimate a maximum price. I'd need to see the pricing tiers.
    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.