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

Tim van der Velden

Tim van der Velden

Product engineer

Full-depth AI personas

Why this persona fits the audience

Product engineer in Amsterdam at an early-stage company; contributes to open-source libraries, meets other developers through GitHub Discussions, Discord, and occasional bridge-building events, and keeps a Notion page of nearby collaborators for pair-programming sessions.

  • Age: 33
  • Location: Amsterdam, Netherlands
  • Occupation: Product engineer
  • Income: EUR 95k base salary
  • Education: Bachelor's degree in applied computer science
  • Company size: 14 employees (Seed stage)
  • Years in role: 4 years as a Product Engineer
“Code is only as good as the people who can read and improve it together; isolation is the enemy of progress.”

Tim van der Velden is a 33-year-old Product Engineer based in Amsterdam, operating at the intersection of rapid startup iteration and sustainable open-source development. Holding a Bachelor's in Applied Computer Science, Tim has spent the last decade refining a craft that values clear documentation and collaborative problem-solving above all else. Currently employed at a seed-stage company with a lean team of 14, Tim navigates the chaotic beauty of early-stage product building, often acting as the glue between disparate engineering tasks. Unlike many peers who chase the latest trendy frameworks, Tim focuses on stability and readability, believing that well-documented code is the truest form of respect for future contributors. Tim's professional identity is deeply intertwined with the global open-source community. They maintain a rigorous schedule of contributing to public libraries, frequently engaging in GitHub Discussions and Discord servers to solve complex architectural puzzles. This digital nomadism extends to their physical location; Tim maintains a meticulously updated Notion database of local collaborators, a personal hub designed to facilitate spontaneous pair-programming sessions across the city. This habit stems from a belief that serendipitous connections yield better outcomes than scheduled networking events. Financially, Tim earns a solid EUR 95k base salary, which affords a comfortable lifestyle in the vibrant De Pijp neighborhood. However, their approach to money is pragmatic; they invest in tools that save time and enhance quality of life, such as high-end cycling gear and ergonomic home office setups, while remaining skeptical of subscription bloat. Tim's personality, characterized by high openness and low neuroticism, allows them to thrive in uncertainty, viewing technical debt as a puzzle to be solved rather than a burden to be feared. Recently, Tim made the strategic decision to push back on a feature request to prioritize a documentation overhaul, a move that initially caused friction but ultimately saved weeks of debugging time for the team. This stance reinforces their reputation as a thoughtful, principled engineer who prioritizes long-term health over short-term velocity.

Background & daily life

A day in their life

Tim wakes up at 6:30 AM, brews a single-origin pour-over, and cycles 15 minutes to the office near Waterlooplein. The first hour is dedicated to reviewing GitHub notifications and clearing email without jumping into tickets. By 9:30 AM, a stand-up syncs the team on blockers. The bulk of the morning involves writing TypeScript and refactoring legacy components, often pausing to update their personal Notion wiki with new learnings. Lunch is a quick wrap-around with a colleague, usually discussing a specific bug or a new library feature. Afternoons are reserved for asynchronous collaboration: reviewing pull requests, responding to Discord threads, and drafting RFCs. A 5 PM bike ride home marks the end of the workday, followed by reading technical blogs or contributing to a side project until late evening.

Lifestyle

Tim lives in a converted warehouse apartment in De Pijp, characterized by high ceilings and exposed brick. Their days revolve around a sustainable rhythm: morning runs along the canals, followed by a slow coffee ritual using a V60 dripper. They commute via bicycle year-round, viewing it as both exercise and a way to disconnect from digital noise. Financially, they are prudent but not frugal, prioritizing spending on high-quality gear, travel to conferences, and supporting local independent businesses. Social life is curated rather than abundant; weekends are often spent hosting small dinner parties or attending niche workshops. They maintain good physical health through cycling and yoga, though stress sometimes manifests as an urge to reorganize their digital filing systems.

Work life

As a Product Engineer at a seed-stage startup, Tim splits time between shipping features directly to users and maintaining the internal engineering backbone. The environment is fluid; yesterday's roadmap might shift today based on user feedback. Tim relies heavily on TypeScript, React, and a robust CI/CD pipeline. They spend significant time documenting architecture decisions to ensure clarity as the team grows. Collaboration is key; Tim actively seeks out 'bridge-building' moments where design and engineering align. The pressure comes from the need to move fast without breaking things, often requiring them to make trade-offs between technical perfection and market velocity. Meetings are minimized, replaced by detailed PR reviews and asynchronous updates.

Relationships

Tim's closest confidants are a mix of childhood friends from Utrecht and colleagues from previous startups. They have a strong bond with their current team, treating them more as family than coworkers. Family ties are warm but distant geographically; visits happen twice a year. Community influence is strongest among the open-source maintainers they interact with online, whose opinions carry significant weight regarding tool choices and technical standards. They rarely seek validation from corporate hierarchies, preferring peer recognition within the developer ecosystem.

How they decide

Tim approaches decisions with a methodical curiosity. They gather data from multiple sources—documentation, peer reviews, and personal experimentation—before committing. While not paralyzed by analysis, they prefer to delay a final choice until they understand the long-term implications for their workflow and the broader community. Peer recommendations and transparent, well-documented options sway them more than marketing hype or aggressive sales tactics. They value autonomy and will often build a small prototype themselves before adopting a new external solution.

How they sound

Tim speaks with a calm, measured cadence, often pausing to choose precise terminology. They avoid hyperbole and corporate buzzwords like 'synergy' or 'disrupt,' preferring concrete verbs. In conversation, they ask probing questions that dig into the 'why' behind a decision rather than just the 'how.' They tend to speak softly but assertively when discussing technical constraints. Slang is used sparingly, mostly limited to internal team shorthand or specific open-source community lingo. They rarely interrupt, instead listening intently before offering a synthesized perspective.

Personality traits

  • meticulously organized yet adaptable
  • genuinely curious about others' code
  • prefers async communication over meetings
  • drawn to messy but solvable problems
  • quietly confident in technical depth
  • avoids corporate jargon
  • socially selective but warm
  • values context over status
  • pragmatic idealist
  • proactive connector

Goals

  • Lead the migration of the core library to a new architectural pattern within the next year
  • Establish a recurring monthly pair-programming meetup for Amsterdam-based open-source contributors
  • Contribute a major feature to a top-tier open-source framework used by their stack
  • Achieve financial independence to allow for sabbaticals focused on creative coding projects
  • Mentor two junior engineers from underrepresented backgrounds in the next 18 months

Problems & frictions

  • Finding reliable, like-minded peers for deep-dive pair programming outside of standard work hours
  • Maintaining up-to-date contact information for the scattered network of collaborators met at events
  • Balancing the demand for immediate feature delivery with the long-term need for technical debt reduction
  • Navigating the ambiguity of early-stage product direction while trying to implement scalable solutions
  • Filtering signal from noise in the constant stream of developer community channels
  • Lack of structured opportunities to meet other non-binary professionals in the local tech scene

Values

  • collaboration
  • curiosity
  • clear documentation
  • sustainable growth
  • transparency

Interests

  • open source
  • pair programming
  • GitHub
  • urban cycling
  • specialty coffee brewing
  • indie game design

Media habits

  • GitHub Discussions threads
  • Discord developer communities
  • The Changelog podcast
  • Local Dutch tech meetups (Bridge, etc.)
  • Notion templates for knowledge management
  • LinkedIn for high-level industry trends only

Questions & answers

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

  1. What do you use today instead of CodeNearby (https://codenearby.space/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make CodeNearby better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

    Currently, I use my Notion database to keep track of local collaborators for spontaneous pair-programming sessions. It's a bit manual, but it works for my immediate needs. CodeNearby's AI-Connect and location-based discovery sound interesting for finding new connections, but I'd need to see how well it integrates with my existing GitHub workflow and if it surfaces genuinely useful matches beyond just proximity. The 'Built in public. Open source. Forever free.' statement is a big plus. I wouldn't pay for something that replicates what I already do effectively with Notion, especially without knowing more about its long-term viability and true value proposition. I'd be willing to pay $0 per month for this.
    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.