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

Elizabeth Verhoeven

Elizabeth Verhoeven

Data engineer in a product scale-up

Full-depth AI personas

Why this persona fits the audience

Maps ETL and analytics flows for a 5-person data engineering subteam at a scale-up. Uses Excalidraw and Mermaid, with a spreadsheet of source systems and owners beside the diagrams.

  • Age: 32
  • Location: Amsterdam, Netherlands
  • Occupation: Data engineer
  • Income: €78,000 annual salary
  • Education: MSc in Data Science
  • Company size: Approximately 70 employees
  • Years in role: 5
“The beauty of data isn't just in the numbers themselves, but in the clarity and structure we bring to understanding them.”

Elizabeth Verhoeven's journey into data engineering began not with a childhood fascination for computers, but with a deep-seated appreciation for order and understanding. Growing up in a quiet town outside Utrecht, she was the child who meticulously organized her toys and sought logical explanations for everything. This inclination naturally led her to pursue a Master's in Data Science at the University of Amsterdam. During her studies, she discovered a passion for untangling complex systems and building robust frameworks, finding particular satisfaction in the process of data transformation and analysis. Her early career involved a stint at a larger, more established consultancy, where she learned the importance of rigorous documentation and standardized processes. However, she found the pace too slow and the impact too diluted. Seeking a more dynamic environment, she joined her current company, a product scale-up, five years ago. Here, she has thrived, taking on significant responsibility within the data engineering subteam. Her current focus is on meticulously mapping out the company's ever-evolving ETL and analytics flows. She champions the use of tools like Excalidraw and Mermaid, not just for their visual capabilities, but for their ability to foster shared understanding within the team. She maintains a comprehensive spreadsheet detailing every source system and its owner, a testament to her commitment to data accuracy and organized workflows. Elizabeth is driven by a desire to build systems that are not only functional but also maintainable and transparent. She sees her work as laying the foundation for the company's future success, a responsibility she takes very seriously. Her personal life is equally structured, with rowing and baking serving as outlets for her focused energy and creative problem-solving. She values her time and invests it wisely, both professionally and personally, always striving for efficiency and meaningful outcomes.

Background & daily life

A day in their life

Elizabeth's typical weekday begins around 7:30 AM with a brisk walk with her dog, Max, followed by a quick breakfast and checking urgent emails. She arrives at the office by 9:00 AM, often grabbing a coffee from a nearby cafe. Her morning is usually dedicated to focused work: refining ETL scripts, updating architectural diagrams in Excalidraw, or reviewing pull requests from her team. Lunch is a shared affair with colleagues, discussing project progress or weekend plans. The afternoon involves a mix of stand-ups, planning meetings with product managers, and troubleshooting any data pipeline issues that arise. She aims to leave by 6:00 PM, often heading straight to her rowing club for practice.

Lifestyle

Elizabeth's life in Amsterdam is a carefully balanced blend of professional dedication and personal pursuits. Her mornings often start with a quick walk with Max before heading to the office. Evenings are for rowing practice on the Amstel or experimenting with new baking recipes. Weekends are a mix of social gatherings with her partner and friends, exploring local markets, and quiet time spent reading or tending to her small balcony garden. She's financially responsible, saving diligently for future travel and potential property investments, but enjoys treating herself to artisanal coffee and good food.

Work life

Elizabeth's role as a data engineer at a rapidly growing tech scale-up is demanding but rewarding. She's responsible for designing and maintaining the ETL pipelines and analytics flows that power the company's product. Her subteam of five engineers relies on her meticulous documentation, often using Excalidraw and Mermaid for architectural diagrams, which she complements with a detailed spreadsheet tracking data sources and their owners. She collaborates closely with product managers and data analysts, translating their needs into robust data solutions. The pressure to scale infrastructure while maintaining data integrity is a constant challenge.

Relationships

Elizabeth is in a stable, long-term relationship with her partner, who provides a supportive and creative counterbalance to her analytical world. Her close-knit group of friends, many met during her university days, are a vital source of social connection and shared experiences. She maintains a good professional relationship with her team, valuing their input and collaborative spirit.

How they decide

Elizabeth approaches decisions with a methodical and research-driven mindset. She gathers information from multiple sources, weighs pros and cons carefully, and often seeks input from trusted colleagues or her partner before committing. She values practicality and long-term viability over quick fixes.

How they sound

Speaks with a clear, measured cadence, often using precise language. Her Dutch accent is subtle but present. She tends to avoid overly casual slang or hyperbole, preferring direct and factual communication. When explaining technical concepts, she's patient and thorough, often using analogies. She might say things like, 'Let's map out the dependencies,' or 'We need to ensure data lineage is clear.'

Personality traits

  • methodical
  • precise
  • patient
  • observant
  • reliable
  • thoughtful
  • calm
  • proactive

Goals

  • To contribute significantly to the company's growth and data maturity.
  • To mentor junior engineers and foster a collaborative team environment.
  • To achieve a better work-life integration, allowing more time for personal projects.
  • To travel to Japan and experience its unique culture and cuisine.
  • To potentially lead a data engineering team in the future.

Problems & frictions

  • Keeping up with the rapid pace of technological change in the data space.
  • Managing the complexity of data sources and ensuring consistent data quality as the company scales.
  • Balancing the need for detailed documentation with the urgency of delivering new features.
  • Occasional communication breakdowns between technical teams and business stakeholders.
  • Finding time for deep, uninterrupted work amidst frequent meetings and ad-hoc requests.

Values

  • data accuracy
  • shared ownership
  • organized workflows
  • transparency
  • continuous learning

Interests

  • analytics
  • rowing
  • baking
  • urban gardening
  • exploring new coffee shops

Media habits

  • Follows key data engineering blogs and newsletters
  • Listens to podcasts on data science and technology trends during commutes
  • Reads industry news sites like TechCrunch and The Register
  • Occasional browsing of Dutch news outlets

Questions & answers

Elizabeth Verhoeven’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying AI Diagram Maker (https://www.aidiagrammaker.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).

    My current process for diagramming involves using Excalidraw and Mermaid, complemented by a detailed spreadsheet for source systems and owners. This method works well for my team of five because it's collaborative and provides a clear, visual representation. While the promise of generating diagrams from plain English is intriguing, I'd need to see how well it handles complex, multi-layered data flows specific to our scale-up environment. Integration with our existing documentation practices is also a key concern. I'm not willing to pay for this service at this time, as my current tools are sufficient and free.
    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.