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

Robin van der Horst

Robin van der Horst

Engineering lead at a marketplace startup

Full-depth AI personas

Why this persona fits the audience

He leads a 7-person engineering team in Utrecht building a marketplace app. The current stack uses MongoDB for the core product and spreadsheet exports for operations reporting, and he spends time reviewing schema changes with one backend developer and an external contractor. He is responsible for keeping systems understandable for a small, fast-moving team.

  • Age: 36
  • Location: Utrecht, Netherlands
  • Occupation: Engineering lead
  • Income: €88k
  • Education: Master's in Software Engineering
  • Company size: Startup (approx. 25 employees)
  • Years in role: 3
“The real challenge isn't just building features, it's building them in a way that doesn't become a tangled mess for the next person who has to touch it.”

Robin van der Horst, 36, is an Engineering Lead at a burgeoning marketplace startup headquartered in Utrecht. Holding a Master's in Software Engineering, he has dedicated the last three years to shaping the technical direction of his current company, leading a team of seven engineers. His journey into tech began with a fascination for how systems fit together, a curiosity nurtured through university and early roles at more established software firms. However, the allure of building something from the ground up, with direct impact, drew him to the startup world. He is married to Eva, a marketing professional, and they share a comfortable life in a modern apartment, valuing both shared routines and individual pursuits. Robin's professional ethos is deeply rooted in pragmatism and a commitment to quality. He champions maintainability and team alignment, understanding that in a fast-paced startup environment, clarity and robustness are paramount for long-term success. His current technical landscape is defined by a MongoDB-centric core and a reliance on spreadsheet exports for operational reporting – a setup that necessitates constant vigilance. He dedicates significant portions of his week to meticulously reviewing schema changes with his team and an external contractor, ensuring the system remains comprehensible and manageable. This focus on understandability is not merely a technical preference; it's a strategic imperative for a small, agile team. While he appreciates the flexibility and innovation of startup life, Robin is acutely aware of the technical debt that can accumulate, and he actively seeks ways to balance rapid development with sustainable engineering practices. His income of €88k allows for a comfortable lifestyle, enabling him to pursue his passions for mountain biking and board games, but he remains mindful of financial prudence, saving for future goals. He views his role not just as a manager, but as a guardian of the codebase's integrity and the team's collective understanding.

Background & daily life

A day in their life

Robin's typical weekday starts around 7:30 AM with coffee and a quick scan of Hacker News. He arrives at the office by 9:00 AM, often cycling the 5km route. His mornings are usually packed with a stand-up meeting, followed by focused work on code reviews or architectural discussions. Lunch is often a quick affair at his desk or a walk to a nearby broodjeswinkel. Afternoons involve more team syncs, one-on-one meetings with developers, and troubleshooting production issues. He aims to leave by 6:00 PM, but late-night emergencies can sometimes extend his day. Evenings are for decompressing with his wife, perhaps a quick game of Codenames before dinner.

Lifestyle

Robin lives in a modern apartment in Utrecht with his wife, who works in marketing. They enjoy quiet evenings, often playing board games or watching documentaries. Weekends are a mix of social activities with friends, including occasional craft beer tastings, and solo pursuits like long mountain bike rides through the Utrechtse Heuvelrug National Park. He's financially responsible, saving diligently for future travel and home improvements, but doesn't shy away from investing in quality gear for his hobbies. He values a structured routine but makes time for spontaneous weekend trips.

Work life

As an Engineering Lead, Robin navigates the constant tension between rapid feature development and maintaining a robust, understandable codebase. His team of seven is spread across backend, frontend, and QA. The current stack, with MongoDB at its core and reliance on spreadsheet exports for operational reporting, presents daily challenges. He spends significant time in code reviews, particularly schema changes, working closely with a senior backend developer and an external contractor. The pressure to keep systems simple enough for a small, fast-moving team is ever-present, often requiring him to make pragmatic trade-offs.

Relationships

Robin is married to Eva, a supportive partner who understands the demands of his tech career. His close circle of friends includes a few former university colleagues, with whom he shares his passion for board games and cycling. He maintains a professional but friendly rapport with his team, respecting their expertise while guiding their technical direction. His external contractor relationship is purely professional, focused on efficient task completion.

How they decide

Robin is a methodical and research-driven decision-maker. He weighs pros and cons carefully, often seeking input from his senior engineers. He prioritizes long-term maintainability and team understanding over short-term gains, and will spend time evaluating different approaches before committing. He's not easily swayed by hype and prefers evidence-based choices.

How they sound

Robin speaks with a clear, measured cadence, often using precise technical language. He avoids excessive slang but is comfortable with common developer jargon. His tone is generally calm and professional, even when discussing challenging issues. He tends to be direct but polite, and rarely raises his voice. He might use phrases like 'From a maintainability perspective...' or 'The architectural implications of that are...' He's unlikely to use overly casual or overly formal language.

Personality traits

  • methodical
  • detail-oriented
  • pragmatic
  • calm under pressure
  • analytical
  • patient
  • slightly reserved
  • quality-focused

Goals

  • Mentor junior engineers and foster a strong team culture
  • Successfully scale the marketplace platform to handle increased user traffic
  • Achieve a better work-life balance by delegating more effectively
  • Contribute to open-source projects in his spare time
  • Eventually transition into a more product-focused technical leadership role

Problems & frictions

  • The limitations of the current MongoDB schema for complex reporting needs
  • Onboarding new developers to a rapidly evolving, somewhat idiosyncratic codebase
  • Balancing the demand for new features with the need for technical debt reduction
  • Ensuring consistent data integrity between the live application and operational exports
  • Finding time for deep architectural thinking amidst daily firefighting

Values

  • maintainability
  • team alignment
  • engineering quality
  • scalability
  • developer autonomy

Interests

  • product architecture
  • mountain biking
  • board games
  • craft beer
  • sci-fi novels

Media habits

  • Hacker News
  • Stack Overflow
  • TechCrunch
  • Ars Technica
  • The Verge
  • YouTube tech reviews

Questions & answers

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

  1. What would stop you from trying PostgreSQL (https://www.postgresql.org/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    Trying out PostgreSQL this month isn't really feasible for us. Our current stack is built around MongoDB, and shifting to a relational database like PostgreSQL would be a significant undertaking. The immediate challenge is that our reporting relies on exporting data from MongoDB to spreadsheets, which is already a bit of a workaround. Introducing PostgreSQL would require a complete re-architecture of our data layer and reporting processes, which we simply don't have the bandwidth for right now, especially with our small team focused on core feature development. We also need to ensure data integrity between the live app and our operational reports, and I'm not sure how a new database would fit into that immediately. Given that PostgreSQL is open-source, I wouldn't pay anything for the software itself, but the migration and training costs would be substantial. It's hard to put a price on that without a clear plan.
    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.