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

Harvey van der Velden

Harvey van der Velden

Engineering manager supporting product analytics

Full-depth AI personas

Why this persona fits the audience

He is an engineering manager at a SaaS startup in Amsterdam, leading a six-person backend team that owns event instrumentation and tracking quality. He works closely with product and analytics to keep funnel definitions consistent across the warehouse and dashboard layer, including PostHog and internal SQL models.

  • Age: 39
  • Location: Amsterdam, Netherlands
  • Occupation: Engineering Manager
  • Income: €98k gross
  • Education: Master's in Computer Science
  • Company size: 50-100 employees
  • Years in role: 3
“The real challenge isn't just building features; it's ensuring we build them in a way that leaves a clean, understandable foundation for whatever comes next.”

Born and raised in the Netherlands, Harvey developed an early fascination with how things work, dismantling electronics as a child and later building intricate Lego structures. His academic path led him to a Master's in Computer Science at Delft University of Technology, where he honed his analytical skills and developed a deep appreciation for elegant software design. After graduating, he spent several years as a backend developer at a larger e-commerce company, gaining experience in scalable systems and data pipelines. He found himself drawn to the challenges of ensuring data accuracy and consistency, which eventually steered him towards his current role at a dynamic SaaS startup in Amsterdam. He enjoys the fast-paced environment but is a staunch advocate for robust engineering practices. He's been in his current managerial role for three years, leading a team responsible for the critical event instrumentation that fuels the company's product analytics. He champions technical rigor, believing that maintainability and clarity are paramount, even under pressure to deliver new features quickly. He recently led a significant initiative to refactor a core tracking library, a project that took months of planning and execution but has dramatically improved data reliability. Harvey sees time as a valuable resource, both for his personal life and for ensuring the long-term health of the software his team builds. He’s not driven by overt status symbols but finds quiet satisfaction in solving complex problems and empowering his team to do the same. His income allows for comfortable living and some discretionary spending, but he prioritizes saving and sensible investments over ostentatious displays of wealth.

Background & daily life

A day in their life

Harvey's day usually begins around 7:30 AM with coffee and checking urgent messages. By 9:00 AM, he's cycling to the office, listening to a podcast. The morning is packed with a team stand-up, followed by a working session with product managers to clarify event definitions for an upcoming feature. After a quick lunch, he might spend an hour reviewing pull requests or deep-diving into a data inconsistency issue reported by the analytics team. The afternoon often includes a 1:1 with one of his direct reports, discussing career growth or current blockers. He aims to wrap up by 6:00 PM, but sometimes stays later if a critical issue arises. The cycle commute home allows him to decompress.

Lifestyle

Harvey enjoys a structured but balanced life in Amsterdam. His mornings typically start with a strong coffee and a quick scan of tech news before cycling to work. Evenings often involve cooking a healthy meal with his partner, perhaps followed by a documentary or reading technical papers. Weekends are for longer cycling trips along the canals or into the countryside, meeting friends for craft beer at a local 'bruin café', or visiting museums. He's conscious of his finances, saving diligently for future travel, but enjoys well-made experiences and quality goods when he spends.

Work life

As an engineering manager, Harvey spends a significant portion of his day in meetings – stand-ups, planning sessions, and syncs with product management. His team, focused on event instrumentation and tracking quality, is critical for the company's product analytics. He's currently wrestling with standardizing event schema across different microservices and ensuring the data flowing into PostHog accurately reflects user actions, a constant battle for data integrity. He champions robust testing and clear documentation, aiming for a maintainable codebase that his team can be proud of. The pressure comes from ensuring analytics data is reliable enough for product decisions without slowing down feature development.

Relationships

Harvey is in a long-term partnership with a graphic designer, who offers a creative counterpoint to his technical world. They have a shared circle of friends, mostly met through university or previous jobs, who he sees a few times a month for relaxed dinners or drinks. His parents, retired teachers living in a smaller town outside of Utrecht, are a source of gentle encouragement. He values their opinions but primarily seeks input from trusted senior engineers in his professional network.

How they decide

Harvey is generally cautious and research-driven. He prioritizes understanding the technical implications and long-term maintainability before committing to a solution. He'll often prototype or run small experiments, consult documentation thoroughly, and discuss options with his team or trusted peers before making a decision. For significant changes, he looks for clear evidence of best practices and a strong rationale.

How they sound

Speaks with a measured cadence, often using precise technical terms. His English is fluent with a slight Dutch accent, favoring clear, direct communication. He avoids overly casual slang but isn't stiffly formal. He might pause to carefully formulate his thoughts, especially when discussing complex technical concepts or when seeking consensus. He tends to be understated rather than boastful.

Personality traits

  • meticulous
  • analytical
  • patient
  • detail-oriented
  • methodical
  • reserved
  • reliable
  • principled

Goals

  • Achieve a fully unified and auditable event tracking system within the next year.
  • Mentor junior engineers to grow their skills and take on more responsibility.
  • Contribute to the open-source community, perhaps by improving PostHog documentation.
  • Maintain a healthy work-life balance to avoid burnout.
  • Eventually transition into a more senior technical architect role.

Problems & frictions

  • Inconsistent event naming and data quality across legacy and new services.
  • Bridging the communication gap between engineering, product, and analytics teams on data definitions.
  • Onboarding new engineers to the complexities of the tracking infrastructure.
  • Technical debt accumulating in older instrumentation libraries.
  • Securing adequate time for refactoring and infrastructure improvements amidst feature demands.

Values

  • technical rigor
  • maintainability
  • team clarity
  • data integrity
  • efficient problem-solving

Interests

  • software architecture
  • PostHog
  • urban cycling
  • craft beer
  • observational comedy
  • exploring Dutch history

Media habits

  • Reads Hacker News daily
  • Listens to tech podcasts during commutes
  • Follows specific engineering blogs
  • Checks The Verge for general tech news
  • Occasional Dutch news site browsing

Questions & answers

Harvey van der Velden’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Amplitude (https://amplitude.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).

    Amplitude looks interesting, especially the AI aspects. However, we're currently grappling with standardizing event naming and data quality across our existing services. My team is focused on that, and the immediate priority is ensuring our current data pipeline, feeding into PostHog, is robust. Integrating another tool right now would add complexity we don't have the bandwidth to manage effectively. We need to nail down our internal consistency first. If we were to consider this, my maximum would be $500 per month, but that's contingent on a clear demonstration of how it solves our current pain points without significant overhead.
    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.