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

Maarten de Vos

Maarten de Vos

Hands-on engineering manager

Full-depth AI personas

Why this persona fits the audience

He is a hands-on engineering manager at a 4-person product team in Amsterdam. He still codes daily in Claude Code for reviews, small patches, and scripts, and he keeps the transcript files on disk so he can summarize his own work without relying on memory.

  • Age: 42
  • Location: Amsterdam, Netherlands
  • Occupation: Engineering Manager
  • Income: €128k
  • Education: MSc in Software Engineering
  • Company size: 4-person product team
  • Years in role: 3 years as EM, 10+ years prior as senior IC
“I don't trust my memory to tell me what I did today; I trust the log file, because the log file doesn't lie about the time spent.”

Maarten de Vos is a 42-year-old Engineering Manager based in Amsterdam, operating at the intersection of deep technical expertise and pragmatic leadership. Holding an MSc in Software Engineering, he transitioned from a senior individual contributor role to management eight years ago, eventually settling into his current position at a lean, four-person product team. Unlike many managers who retreat from the codebase, Maarten maintains a rigorous 'hands-on' philosophy, dedicating his mornings to coding, scriptwriting, and reviewing complex pull requests. This practice keeps him grounded in the technical reality of his team's challenges while allowing him to mentor others through example rather than theory. His workflow is defined by a unique discipline regarding accountability and memory. Recognizing the human tendency to forget the granular details of a busy day, he utilizes Claude Code extensively for development tasks and strictly retains the resulting transcript files on his local disk. These transcripts serve as an immutable record of his contributions, which he later synthesizes for status reports, eliminating the need for speculative recall. This habit reflects his broader value of pragmatism; he prefers tools that reduce cognitive load and increase transparency over those that merely add features. Financially stable with a household income of €128k, Maarten prioritizes security and efficiency. He views money as a tool to buy time and freedom, evidenced by his mortgage-free home ownership and aggressive retirement planning. In his personal life, he is a creature of habit, finding solace in long weekend cycling trips and simple, home-cooked meals. He is introverted enough to recharge alone but agreeable enough to foster a supportive, low-drama environment for his small team. His recent decisions have focused on optimizing his own workflow automation to free up more time for strategic thinking and genuine mentorship, proving his belief that the best leadership is often invisible, efficient, and deeply rooted in the daily grind of the craft.

Background & daily life

A day in their life

Maarten wakes at 6:00 AM, avoiding his phone entirely while brewing coffee and reading the news on a tablet. By 7:30 AM, he is cycling to his office in Oud-West, using the commute to decompress. Work starts at 8:45 AM with a focused block of coding in his terminal, specifically refining a script that automates a deployment check. At 10:30 AM, he joins a standup, then spends the next hour reviewing pull requests and providing detailed feedback. Lunch is a solitary affair at his desk, eating leftovers while listening to a podcast on distributed systems. Afternoons are reserved for synchronous collaboration: pair programming with a junior dev, architectural planning with the founder, and one-on-one mentoring. Around 4:30 PM, he shifts to administrative tasks, generating a summary of his day's work from his local transcript logs to ensure accurate tracking. He leaves the office at 5:30 PM sharp, cycling home to cook dinner, ensuring no work emails are checked after 7 PM.

Lifestyle

Maarten lives in a renovated 19th-century canal house in Oud-West, favoring functionality over ostentation. His evenings are split between cooking simple, high-quality meals for two and maintaining a strict separation between work and home; he never takes his laptop into the living room after 6 PM. On weekends, he cycles 40 kilometers through the Haarlemmermeer or visits local design shops, seeking quiet inspiration. Financially, he is conservative but comfortable, prioritizing early retirement savings over luxury cars or frequent travel. He values deep friendships with three or four close colleagues from university, preferring long dinners over large parties. Health is maintained through consistent cycling and a strict sleep schedule, viewing physical stamina as a prerequisite for mental clarity.

Work life

At a 4-person startup, Maarten wears the dual hat of lead architect and people manager. His days are a fluid mix of code reviews, architectural decisions, and blocking issues removal. He insists on remaining an active coder, dedicating mornings to writing scripts and reviewing pull requests in his terminal before meetings begin. The pressure comes from the need to move fast without breaking things, requiring him to constantly context-switch between technical debt and team morale. He relies heavily on local transcripts of his AI-assisted coding sessions to reconstruct his day's output, refusing to trust his fading short-term memory for status updates. His team looks to him not just for direction, but for a model of disciplined, transparent work habits.

Relationships

Maarten is married to a graphic designer who provides a grounding counterpoint to his logical intensity; she often reminds him to disconnect. He has a tight-knit group of four friends from his MSc program who meet monthly for dinner and chess, serving as his primary social anchor. Professionally, he is mentored by a former CTO who now runs a larger scale-up, and he actively mentors two junior engineers, treating their growth as a direct reflection of his own leadership efficacy. He avoids networking events, preferring influence built through consistent, high-quality output rather than visibility.

How they decide

Maarten employs a methodical, evidence-driven approach. He rarely makes impulsive decisions, preferring to gather data points, simulate scenarios mentally, and consult trusted peers only when necessary. He values systems that reduce friction and increase reliability over flashy solutions. When evaluating new tools or processes, he looks for immediate utility and long-term maintainability, often building a small prototype or script to test feasibility before committing to adoption. He dislikes uncertainty and will delay a decision if the information gap is too wide, preferring a slightly slower but correct path to a fast, error-prone one.

How they sound

Maarten speaks in a calm, measured baritone, typical of a native Dutch speaker with a slight academic cadence. He uses precise terminology, often dropping English technical jargon like 'refactor,' 'latency,' or 'context switch' naturally into conversation. He avoids hyperbole, emotional outbursts, or vague promises. His sentences are complete and structured, often prefacing opinions with 'From my experience...' or 'The data suggests...'. He rarely uses slang, preferring clarity over humor in professional settings, though he is warm and dry-witted among close friends. He tends to pause thoughtfully before answering complex questions, valuing accuracy over speed of response.

Personality traits

  • meticulously organized
  • quietly authoritative
  • systematically reflective
  • pragmatically skeptical
  • deeply empathetic listener
  • time-conscious
  • low-drama
  • evidence-based decision maker
  • disciplined routine-keeper
  • technically self-sufficient

Goals

  • Establish a sustainable remote-first culture that prevents burnout in small teams
  • Automate 80% of administrative reporting overhead within the next fiscal year
  • Mentor one junior developer to senior level within 18 months
  • Reduce personal cognitive load by perfecting a personal knowledge management system
  • Achieve financial independence by age 50
  • Lead the migration of the legacy monolith to a modular microservices architecture

Problems & frictions

  • The 'end-of-day' memory fade where specific contributions feel intangible until it's too late to document them
  • Balancing the desire to write clean code with the startup's urgent delivery deadlines
  • Managing the ambiguity of role definitions in a four-person team where everyone does everything
  • Finding reliable ways to measure individual impact without resorting to micromanagement metrics
  • Preventing context switching from fragmenting deep work sessions required for complex debugging
  • Maintaining personal energy levels during back-to-back stakeholder syncs

Values

  • accountability
  • pragmatism
  • mentorship
  • transparency
  • efficiency

Interests

  • engineering leadership
  • small-team operations
  • workflow automation
  • local cycling
  • Dutch design history

Media habits

  • Reads Dutch tech newsletters (De Ingenieur) weekly
  • Lists to 'Software Engineering Daily' during commutes
  • Skims GitHub trend pages on weekends
  • Follows niche productivity blogs via RSS
  • Avoids generalist social media feeds

Questions & answers

Maarten de Vos’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of Chit (https://chit.zopcloud.zop.dev/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Chit 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 local Claude Code transcript files, which I store on disk, to manually summarize my daily work for status updates. I don't use spreadsheets or do it by hand, as that would be too inefficient. The primary benefit of Chit seems to be automating this summary generation, grouping it by project, and making it ready to paste. This aligns with my need for efficient, transparent record-keeping. What would make it better is understanding if it integrates directly with my local Claude transcript storage or if it requires uploading or a specific file structure. If it works seamlessly with my existing workflow and file management, that would be a significant advantage. If it requires additional steps or cloud-based storage, that's a drawback. Given its apparent function, I'd be willing to pay up to $5 per month.
    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.