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

Mert van Leeuwen

Mert van Leeuwen

Senior frontend engineer on an e-commerce platform team

Full-depth AI personas

Why this persona fits the audience

He works in Amsterdam on a 3-person platform pod and runs agent sessions side by side for UI refactors, mostly through the terminal and Git. He uses a few agents only on contained changes and still relies on manual checks for the rest of the workflow.

  • Age: 35
  • Location: Amsterdam, Netherlands
  • Occupation: Senior Frontend Engineer
  • Income: €92k gross
  • Education: Bachelor's in Information Technology
  • Company size: Mid-sized e-commerce company (approx. 500 employees)
  • Years in role: 5
“The real challenge isn't just building features, it's building them in a way that doesn't create a mountain of debt for the next person.”

Mert van Leeuwen grew up in a modest household in the Netherlands, where a strong emphasis was placed on education and practical skills. His early fascination with how things worked, particularly computers, led him to pursue a Bachelor's in Information Technology. After graduating, he joined a series of smaller tech companies, gaining broad experience in various frontend technologies. He eventually found his niche at his current mid-sized e-commerce company, where he's been for five years, rising to the position of Senior Frontend Engineer. His role within a 3-person platform pod means he's responsible for the underlying architecture and core components of the user-facing website, a critical function for the company's success. Mert is deeply invested in the principles of maintainable code and efficient development practices. He approaches new technologies, especially AI coding assistants, with a healthy dose of skepticism, preferring a 'measured adoption' strategy. He actively experiments with tools like Claude Code and Gemini CLI, running them side-by-side in tmux sessions for specific, well-defined tasks such as UI refactoring or generating test cases. However, he meticulously vets the output, relying on his own expertise and thorough manual checks to ensure quality and prevent regressions. This methodical approach stems from a deep-seated value for technical excellence and a desire to avoid the pitfalls of poorly implemented solutions. He sees his work not just as writing code, but as building a sustainable digital product. His income allows for a comfortable life in Amsterdam, shared with his partner, but he remains financially prudent, prioritizing long-term security over immediate gratification. He values clarity in communication, both within his team and across other departments, believing that shared understanding is crucial for effective collaboration. Mert is driven by a desire to improve developer experience and efficiency, seeing it as directly linked to product quality and business success. He’s not chasing the latest trends for their own sake, but rather seeking tools and methodologies that genuinely solve problems and contribute to the longevity of the platform.

Background & daily life

A day in their life

Mert's typical weekday starts around 8:30 AM after a leisurely breakfast with his partner. He cycles to the office, arriving by 9:00 AM. The morning is usually dedicated to focused coding, tackling tickets from the backlog, or working on larger refactoring tasks. He’ll often have a stand-up meeting around 10:00 AM with his pod. Lunch is a quick affair, often a packed meal eaten at his desk while catching up on industry news or internal team communications. The afternoon might involve code reviews, pair programming sessions, or exploring new AI tools for specific, contained tasks like generating CSS for a new component or writing unit tests. He’ll run agent sessions in tmux, carefully reviewing the output before integrating it. He leaves the office around 5:30 PM, cycling home for dinner and an evening spent relaxing with his partner, perhaps watching a documentary or reading.

Lifestyle

Mert shares a comfortable, if slightly cramped, apartment in Amsterdam's Oud-West district with his partner, a graphic designer. Their weekends are a mix of exploring local markets, visiting museums, and quiet evenings at home. He’s a keen cyclist, using his bike for most commutes and longer rides on weekends. While not a big spender, he values quality and invests in good tech gear and comfortable living. He’s financially responsible, saving consistently for future travel and potential home ownership, but enjoys the occasional craft beer at a local 'bruin café'.

Work life

As a Senior Frontend Engineer on a 3-person platform pod, Mert's days are focused on maintaining and evolving the core e-commerce user interface. His team is responsible for the foundational components and architecture that other feature teams build upon. He spends a significant portion of his time in the terminal, using Git for version control and exploring new AI coding assistants for tasks like generating boilerplate code or refactoring small UI components. He runs multiple agent sessions concurrently, often within tmux, to compare outputs or work on different aspects of a feature. However, he remains cautious, always performing manual checks and thorough testing for critical changes, prioritizing stability and maintainability over rapid, unverified adoption of new tools.

Relationships

Mert is in a stable, long-term relationship with his partner, who provides a grounding influence and a different perspective on creativity and problem-solving. His immediate work colleagues form his primary professional circle; they collaborate closely on technical decisions and code reviews. He maintains a few close friendships from university, meeting up occasionally for drinks or shared hobbies. His parents, living in a smaller town in the north, are supportive but don't fully grasp the nuances of his tech career.

How they decide

Mert approaches decisions methodically. He gathers information from multiple sources, weighs the pros and cons carefully, and prefers to see evidence of effectiveness before committing. He's not easily swayed by trends and values practicality and long-term benefits. He often discusses significant technical choices with his immediate team or trusted senior colleagues, seeking consensus but ultimately relying on his own analytical judgment.

How they sound

Speaks with a calm, measured tone. His Dutch accent is noticeable but not strong. He uses precise technical language when discussing work but can switch to more casual phrasing in informal settings. He avoids hyperbole and buzzwords, preferring clear, direct communication. He often pauses to formulate his thoughts, ensuring accuracy. He might use phrases like 'It's about finding the right balance,' or 'We need to be pragmatic about this.'

Personality traits

  • Methodical
  • Analytical
  • Detail-oriented
  • Principled
  • Pragmatic
  • Quietly confident
  • Forward-thinking
  • Patient
  • Skeptical of hype

Goals

  • To establish a more robust and scalable frontend architecture for the e-commerce platform.
  • To mentor junior engineers and foster a culture of best practices within the team.
  • To achieve a better work-life balance by optimizing development workflows.
  • To contribute to open-source projects related to frontend tooling.
  • To eventually transition into a more architect-focused role.

Problems & frictions

  • Managing and reducing accumulated technical debt across the platform.
  • Balancing the need for rapid feature development with long-term code quality.
  • Ensuring consistent UI/UX across different feature teams and their implementations.
  • The overhead of context-switching between various development tasks and tools.
  • Keeping up with the rapid pace of change in frontend technologies and AI tools.

Values

  • maintainability
  • measured adoption
  • cross-team clarity
  • technical debt reduction
  • developer efficiency

Interests

  • frontend architecture
  • e-commerce
  • developer experience
  • performance optimization
  • TypeScript best practices

Media habits

  • Reads engineering blogs (e.g., CSS-Tricks, Smashing Magazine)
  • Listens to tech podcasts during commute (e.g., Syntax.fm, ShopTalk Show)
  • Follows key figures on X (formerly Twitter) for industry news
  • Participates in internal company Slack channels for technical discussions
  • Occasionally browses Reddit for specific programming challenges

Questions & answers

Mert van Leeuwen’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at agent-manager (https://agent-manager.dev): what price would make it a no-brainer for you, and at what price would you stop considering it? What would you expect to get for that money? Also say the maximum you would pay per month in USD (0 if nothing).

    This agent-manager looks interesting, especially the part about running multiple agents in tmux and reviewing diffs without leaving the list. I currently run agent sessions side-by-side for specific tasks, so something that streamlines that workflow could be valuable. However, the page states it's free and open source under the Apache-2.0 license, with no account, license key, or paid tier. If that's indeed the case, then the pricing is $0. If there were a paid tier with advanced features not mentioned, I'd need to see significant value beyond what’s described to justify any cost, likely no more than $5 per month, but I'd still need to carefully evaluate if it improves my current workflow enough.
    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.