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

Ida Mayer

Ida Mayer

Data engineer at online retailer

Full-depth AI personas

Why this persona fits the audience

She maintains query access for an analytics squad that pulls from ClickHouse, Postgres, and Elasticsearch. Day to day she uses DBeaver, CSV exports, and notebook snippets to compare tables and validate loads, while a shared spreadsheet tracks which credentials belong to each environment.

  • Age: 34
  • Location: Berlin, Germany
  • Occupation: Data engineer
  • Income: €78k
  • Education: MSc Data Science
  • Company size: midsize e-commerce startup (~150 employees)
  • Years in role: 5
“If I have to explain why you can’t just run a DELETE * FROM production table on a whim, we have bigger problems than time management.”

Ida Mayer grew up in Munich with an engineer father who taught her that 'if it’s not documented, it doesn’t exist'—a philosophy that still governs her work life. Her academic path was unconventional: she started in computer science, pivoted to cognitive science, and finally landed in data science after a masters thesis on neural network interpretability. Her first job was at a Berlin startup where she had to wrangle a Frankenstein’s monster of data systems held together by duct tape and Post-it notes. That experience taught her two things: never trust a schema that isn’t version-controlled, and always document your exit criteria. Now at a fast-growing e-commerce company, she’s fighting a similar battle but with more institutional resistance. Her ideal solution would eliminate the spreadsheet credential mess, make query access self-documenting, and somehow convince her company to invest in proper data governance. In her spare time, she’s trying to perfect a 72-hour sourdough starter hydration test using environmental sensors to measure ambient conditions. Ida is perpetually conflicted between her love for emerging technologies and her distrust of anything that positions itself as 'revolutionary'. She’d rather have a stable, well-documented system than a flashy one that requires constant maintenance. Her biggest professional stressor is watching her team duplicate work because they’re using different access methods for the same databases. She’s contemplating writing a series of internal Medium-style posts to standardize practices, but knows from experience that even the best documentation gets ignored when deadlines loom. On a personal level, she’s in that phase where every hobby becomes a data collection project—her photography has led to a spreadsheet tracking film development times, and her baking is now a series of temperature-controlled experiments. She’s considering moving to a cottage in Brandenburg to escape Berlin’s rising rents, but the thought of leaving her favorite espresso bar keeps her rooted in the city.

Background & daily life

A day in their life

Ida wakes at 6:00am to the sound of her cat knocking over water glasses (a ritual he’s perfected). After a 6:30am gym session, she showers, blasts Italian breakfast music, and eats a sourdough toast with homemade nutella. From 8:00am-10:00am, she’s in the zone—reviewing failed ETL jobs from overnight, debugging ClickHouse queries, and documenting her changes in Confluence (a task she finds soul-crushing but does anyway). The post-lunch hours are her quiet time, when she tackles more complex modeling tasks or experiments with new data structures. At 5:00pm, she cuts off work completely to review photos from her latest city walk. Evenings are for sourdough maintenance, photography editing, or binge-reading a technical book (Kubernetes this week). She never works after 8:00pm, though she’ll reply to a Slack if it’s truly urgent.

Lifestyle

Ida lives in a compact Neukölln apartment with floor-to-ceiling bookshelves and a dedicated bread-making station. She works from home 3 days a week, structuring her schedule around morning gym sessions with a weightlifting routine she tracks obsessively. Her social life revolves around a tight-knit group of data professionals and a photography collective that meets monthly to critique work. She’s frugal by nature—her last big expense was a secondhand Leica with a broken shutter she repaired herself—though she’ll splurge on specialty flour for baking. Her health habits are methodical: she measures her sleep with Oura, ignores most fad diets, and gets annual eye exams because of long hours in front of screens. Weekends often involve long walks through Berlin’s lesser-known neighborhoods, documenting architectural details on her film camera.

Work life

Ida’s daily work revolves around maintaining data pipelines that feed the company’s analytics dashboards. Her biggest frustration is managing credential sprawl—she’s currently trying to wean her team off the shared spreadsheet tracking 37 different database access combos. She spends too much time validating data loads and troubleshooting queries that fail in production but work in staging. Her team’s workflow is a patchwork of open-source tools and homebrewed scripts, with DBeaver being the closest thing to a 'standard' client. She’s currently pushing for better error logging after a recent incident where a failed ETL job went unnoticed for 36 hours. Her relationship with the analytics squad is professional but strained—they keep asking for the same reports she built last quarter, and they never document their own query changes.

Relationships

Ida’s closest relationships are with her former university cohort, now scattered across Europe. She has a dry, sarcastic rapport with her brother who works in Berlin’s tech scene, and they meet monthly at a dive bar to complain about work. She keeps in touch with her parents in Munich through weekly video calls about recipes and current affairs. Her photography collective provides the social outlet she needs to avoid becoming completely work-obsessed. She values deep, low-friction relationships and avoids people who make big promises but don’t follow through.

How they decide

Ida is methodical to the point of over-researching. She’ll spend hours reading documentation and community forums before making a technical decision, often creating decision matrices to weigh pros and cons. She trusts peer-reputation more than marketing and has a low tolerance for hype. When it comes to tools, she expects them to respect her time and intelligence—anything that requires too much hand-holding gets rejected immediately. Her biggest fear is making a choice that creates technical debt for herself or others.

How they sound

Ida speaks in precise, slightly clipped sentences with occasional German inflections. She uses technical jargon naturally but mocks overused corporate buzzwords. Her sarcasm is dry and understated—you know you’ve angered her when she starts responding in complete technical documentation sentences. She avoids vague language and hates when people say 'it works on my machine' or 'just do it in Python'. She’s more likely to say 'That’s a one-liner in R' than 'easy fix'. Her humor is self-deprecating but sharp—she’ll laugh at herself for forgetting a semicolon but won’t suffer others’ sloppiness.

Personality traits

  • analytical to a fault
  • passionate about clean code but hates meetings
  • quietly competitive about being the most organized on her team
  • hates vague business requirements
  • secretly enjoys spreadsheets as a creative outlet
  • gets defensive about over-commercialized technology
  • loyal to tools that respect her privacy
  • treats data like a librarian treats rare books
  • prone to 3am GitHub rabbit holes
  • low tolerance for context-switching

Goals

  • Build a self-documenting data access system her team will actually use
  • Publish a research paper on ClickHouse optimization techniques
  • Take a solo photography trip to the Baltic coast before winter
  • Master the perfect ciabatta crust
  • Get promoted to senior engineer without taking on management responsibilities
  • Reduce her personal digital footprint (currently attempting to archive 5k old emails)

Problems & frictions

  • Stretching herself thin trying to fix systems that weren't designed with governance in mind
  • Constantly explaining to non-technical colleagues why 'just run the query again' isn't a solution
  • Her bread-making experiments are making her apartment smell like a bakery during work hours
  • Struggling to decide whether to spend time learning Rust or deepening her ClickHouse knowledge
  • Her photography gear is accumulating faster than she can use it
  • The company’s bad habit of treating data engineering as 'IT support for analytics'

Values

  • accuracy
  • autonomy in work
  • continuous learning
  • privacy
  • sustainable living

Interests

  • data modeling optimization
  • travel photography (especially off-season Europe)
  • sourdough bread-making (uses data to track fermentation times)
  • minimalist design
  • dark mode evangelism

Media habits

  • X/Twitter for data engineering debates
  • Reddit (r/dataengineering, r/berlin)
  • Spotify playlists (heavy on archetechno and indie folk)
  • Ephemeral newsletters (mostly technical)
  • Local Berlin podcasts (culture and urban development)

Questions & answers

Ida Mayer’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying QoreDB (https://qoredb.com) 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 shared spreadsheet tracking credentials for our databases is a constant headache, and anything that could streamline that would be a game-changer. QoreDB's promise of a single interface for multiple engines (like ClickHouse, Postgres, and Elasticsearch) is appealing, but I'm cautious about adopting new tools without thorough testing. My team is already juggling DBeaver and notebook snippets, and I need to ensure any new tool integrates seamlessly. My biggest concern is the transition period—we can't afford downtime or duplicated effort. As for pricing, because I'm not in charge of budget decisions at my company, I would need to justify the cost to stakeholders. I'd recommend testing the free Core version first, but if it's a paid feature I'd say $20 per month per user is reasonable, assuming it provides significant time savings and security improvements.
    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.