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

Matilda Gehrig

Matilda Gehrig

Data engineer at a nutrition startup

Full-depth AI personas

Why this persona fits the audience

She works on the data pipeline for a 14-person Berlin nutrition startup whose mobile app syncs meals, recipes, and scanned barcodes. Her team already normalizes food records from a paid competitor API plus internal spreadsheets to reconcile calories and macro values.

  • Age: 37
  • Location: Berlin, Germany
  • Occupation: Data Engineer
  • Income: €92,000
  • Education: MSc in Data Engineering
  • Company size: 14
  • Years in role: 4
“The beauty of data lies not just in its volume, but in its absolute, undeniable truth when it's clean.”

Matilda Gehrig's journey into data engineering began not with a childhood fascination for computers, but with a deep-seated curiosity about how systems work and a desire for order. Growing up in a quiet town outside of Munich, she excelled in mathematics and physics, finding satisfaction in solving complex problems. Her academic path led her to pursue an MSc in Data Engineering at the Technical University of Munich, where she honed her skills in database management, ETL processes, and data warehousing. She was drawn to the field's potential for creating tangible improvements and uncovering hidden patterns. After graduating, she spent a few years at a larger, more established tech company, gaining valuable experience but feeling a growing desire for a more impactful role in a smaller, agile environment. This led her to the Berlin-based nutrition startup two years ago. Her current role is central to the company's mission; she is responsible for the integrity of the data that powers their mobile app, which tracks meals, recipes, and scanned barcodes. This involves a constant battle with data quality, particularly when integrating information from a paid competitor API and internal spreadsheets. She is currently engrossed in a project to refine the normalization of calorie and macro values, a task that demands meticulous attention to detail and a deep understanding of nutritional science principles. Matilda is driven by a strong sense of responsibility for the data she manages, viewing it as a reflection of the company's commitment to its users. She is methodical in her approach, preferring to build robust, well-tested pipelines rather than quick fixes. Her personal values of privacy awareness and transparency heavily influence her work, ensuring that user data is handled with the utmost care and that the data processes are as clear as possible. She views her work not just as a job, but as a contribution to a healthier future, grounded in accurate information. Her income allows for a comfortable life in Berlin, but she remains frugal, prioritizing experiences and long-term financial security over material possessions. Time is a valuable commodity for Matilda; she carefully balances her demanding work with her passion for trail running and her personal life, finding that the discipline and focus required for her job also serve her well in her athletic pursuits.

Background & daily life

A day in their life

Matilda's typical weekday begins around 7:00 AM with a quick breakfast and checking personal emails. She then heads out for a 45-minute trail run if the weather permits, or does a home workout. By 9:00 AM, she's at her desk, diving into her work. The morning is usually spent reviewing data pipelines, addressing any alerts from the previous night, and collaborating with her team on current normalization tasks. Lunch is a simple, healthy meal, often prepared at home. The afternoon involves deep-dive analysis, writing SQL queries, working with dbt models, and attending stand-ups or technical discussions. She aims to wrap up by 6:30 PM, leaving time for dinner with Johannes, reading, or a quiet evening.

Lifestyle

Matilda lives in a cozy shared apartment in Berlin's Kreuzberg district with her partner, Johannes, and their cat, Luna. She prioritizes her health and well-being, dedicating time to trail running in the Grunewald forest several times a week and experimenting with healthy recipes. Financially, she's pragmatic, saving a significant portion of her income for future travel and potential investments, while maintaining a comfortable but not extravagant lifestyle. Her social life is focused on a small, close-knit circle of friends and colleagues, preferring quality interactions over large gatherings. She values quiet evenings at home with Johannes, discussing their day or planning weekend excursions.

Work life

Matilda's days are consumed by the intricate task of ensuring the accuracy and reliability of the nutrition startup's food data. She spends a significant portion of her time wrestling with the complexities of the competitor API, meticulously cleaning and transforming its output, and cross-referencing it with internal spreadsheets. Her team is currently focused on refining the normalization process for calorie and macro values, a critical step for the app's user-facing features. The pressure to maintain data integrity is high, as any inaccuracies directly impact user trust and the app's core functionality. She collaborates closely with the backend developers and the product manager, often finding herself explaining the nuances of data discrepancies.

Relationships

Matilda shares her life with Johannes, a graphic designer, with whom she has a stable and supportive partnership. Her closest friends are a small group from her university days, with whom she maintains regular contact. Within the startup, she has a professional rapport with her immediate team and the CTO, valuing their technical acumen and collaborative spirit.

How they decide

Matilda is a highly analytical and research-driven decision-maker. She prefers to gather comprehensive information, weigh pros and cons meticulously, and consult with trusted colleagues or subject matter experts before committing to a course of action. She is not prone to impulsive choices and values evidence-based reasoning.

How they sound

Matilda speaks with a clear, measured cadence, her German accent subtly present. Her vocabulary is precise, reflecting her technical background, but she avoids overly jargonistic language in casual conversation. She tends to be direct and factual, preferring to articulate her points logically. She rarely uses slang and speaks with a moderate tone, conveying thoughtfulness and a degree of reserve.

Personality traits

  • detail-oriented
  • analytical
  • reserved
  • loyal
  • ambitious
  • perfectionistic
  • methodical
  • principled

Goals

  • Achieve a senior data engineering role within the next five years.
  • Contribute to open-source data projects related to nutrition or health.
  • Complete a marathon, ideally an ultra-trail event.
  • Develop a deeper understanding of machine learning applications in food science.
  • Maintain a healthy work-life balance.

Problems & frictions

  • The inconsistency and occasional poor quality of data from the third-party API.
  • Balancing the need for rapid feature development with the imperative of maintaining data accuracy.
  • Limited resources and personnel within the small startup environment.
  • The constant challenge of keeping up with evolving data engineering best practices and tools.
  • Ensuring robust data privacy measures are in place, given the sensitive nature of user health data.

Values

  • data integrity
  • methodical work
  • privacy awareness
  • transparency
  • sustainability

Interests

  • dbt
  • APIs
  • nutrition science
  • trail running
  • photography

Media habits

  • Der Spiegel
  • The New York Times
  • podcasts on data science
  • tech blogs

Questions & answers

Matilda Gehrig’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at Calorie API & MCP (https://calorieapi.com/): 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).

    Honestly, pricing is difficult to assess without seeing the tiered plans. The 1,000 free calls per month is a good starting point, but for a startup, we'd likely need significantly more. If a 'no-brainer' price point meant a substantial increase in calls, say 100,000 per month, for around $100-$150 USD, that would be compelling. I'd expect reliable data quality and clear documentation at that level. However, if the cost escalates quickly beyond that for more requests, it becomes a consideration to re-evaluate. The maximum I'd consider paying per month would be $200 USD.
    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.