Why this persona fits the audience
Senior data engineer on a 4-person product squad in Amsterdam. He owns the prompts for a search assistant, stores them in a repository with handwritten comments, and uses a paid competitor prompt platform for audit logs and change tracking.
- Age: 28
- Location: Amsterdam, Netherlands
- Occupation: Senior Data Engineer
- Income: EUR 84k salary
- Education: MSc in Information Systems
- Company size: Small (100-500 employees)
- Years in role: 3
“I don't mind complicated systems—as long as every part has a single, unambiguous purpose. What I hate are systems that claim to be simple but actually just hide complexity.”
Koen van de Veen developed his obsession with traceability during a disastrous internship where a production outage was blamed on 'someone changing something'. After graduating from the University of Amsterdam with a focus on data systems architecture, he joined a now-defunct startup where he learned that maintaining prompt quality was more art than science. His current role involves owning all the prompts for a search assistant used by 150+ customer support agents. He currently manages these with a hybrid approach: GitHub for version control (with handwritten YAML comments), a paid prompt platform for audit trails, and a personal Confluence page documenting the 'why' behind major changes. This system works, but it's not ideal—he often finds himself manually cross-referencing notes between systems. His team recently debated adopting a more sophisticated prompt management system, but the conversation stalled when the product manager prioritized other features. Koen envies companies with dedicated LLM engineering teams but doesn't push for such resources, knowing his small team's budget can't sustain it. His ideal workflow would involve versioning prompts as first-class citizens, with performance metrics tied directly to each variation. He's particularly frustrated by how little tooling exists for rollback scenarios. Outside work, Koen's approach to hobbies mirrors his professional mindset—he meticulously documents his home automation experiments, cycling routes, and coffee brewing parameters. He refuses to upgrade his phone until the performance degradation becomes unbearable, and his wardrobe consists mostly of black, gray, and navy items that require no particular care. Status doesn't motivate him; he's driven by the satisfaction of building systems that 'just work' and the quiet satisfaction of making things more maintainable than he found them.
Background & daily life
A day in their life
Koen's alarm goes off at 6:15 AM, but he's usually already awake, tracking his heart rate on his smartwatch. After a shower, he meticulously brews his coffee while listening to a data infrastructure podcast. His 45-minute commute includes 12 stops to adjust his Garmin's settings, noting the precise wind speed and traffic conditions. At work, he starts by checking the overnight data pipeline logs, then schedules a 1.5-hour focused block to refactor a prompt evaluation script. At 11 AM, he has a standup where he pushes back on a suggestion to skip testing by noting it would create technical debt. Lunch is a pre-packaged meal from the local organic market. Afternoon is spent documenting the team's prompt versioning process in a Confluence page. He leaves by 5:30 PM, stops at the hardware store to buy components for his home server, then spends the evening assembling them while watching a Formula 1 race. After lights out by 10:30 PM, he runs a script that sends him a summary of the search assistant's performance overnight.
Lifestyle
Koen sublets a 65m² apartment in De Pijp with high ceilings and a small balcony where he grows chilies. His routine revolves around 45-minute cycling commutes in all weather, which he documents in a private spreadsheet tracking routes, times, and weather conditions. He brews coffee on a manual pour-over setup he calibrated with a kitchen scale, and his kitchen counter is cluttered with half-built electronics projects. Health-wise, he sticks to strength training 3x/week and avoids processed foods—not for aesthetics, but because it helps his focus. He socializes in small, controlled settings: a monthly board game night with two colleagues, occasional bike repair meetups, and monthly video calls with his sister in Utrecht. Money is managed with a strict 50/30/20 split, though he occasionally splurges on high-end bicycling equipment. He avoids social media entirely, preferring niche forums and email newsletters.
Work life
At the fintech startup where Koen works, his squad of 4 (a product manager, two full-stack devs, and himself) builds an internal search assistant for customer support. The team uses a mix of GitHub, a paid prompt platform for audit trails, and Koen's personal notations in a private repo for prompt versions. His biggest daily friction comes from the fragility of prompt testing—small changes have unpredictable effects, and the current workflow of redeploying the entire microservice for every tweak is inefficient. He spends most workdays in the 'flow state' of building pipelines, annotating prompt versions in his notebook, and doing pre-mortems on potential failures. He distrusts vague metrics and insists on measuring everything that impacts the search quality. His biggest pressure is maintaining reliability during rapid iteration cycles. He gets irritated by 'just try it' suggestions from colleagues and prefers to identify edge cases proactively.
Relationships
Koen is the youngest child of a pharmacy manager and a retired civil engineer. He speaks to his parents weekly, mostly about their attempts to fix up their holiday home in Zeeland. His closest friend is Jeroen, a DevOps engineer they met through a mutual interest in retro gaming consoles. Koen is skeptical of most professional networking but maintains loose connections with alumni from his MSc program. He rarely socializes with coworkers outside work but has learned to read the dynamics of his small team accurately. His sister, a PhD student in neuroscience, is the only person he debates philosophy with. He admires developers who treat infrastructure like a craft and actively seeks out their advice.
How they decide
Koen makes decisions by creating exhaustive lists of pros/cons, then over-indexing on potential failure modes. He consults documentation first, people second, and only trusts peer recommendations if the recommender has shown consistent good judgment in the past. He avoids 'hype-driven development' and gives new tools months of observation before adoption. Once he trusts a system, he defends it stubbornly. However, his decisions about his personal time and money follow a different pattern—he commits to physical objects (bikes, gadgets, appliances) only after long periods of research and comparison.
How they sound
Koen speaks in measured, precise sentences with a slight Dutch accent that becomes more pronounced when he's tired. He uses exact technical terms but avoids jargon when talking to non-engineers. He never says 'just' or 'simply' when describing technical work, as he finds those words dismissive. His humor is deadpan and often involves self-deprecating observations about his own rigidity. In meetings, he speaks only when prepared and avoids speculation. In casual conversation, he tends to respond to questions with additional detail rather than direct answers. His speech patterns make him seem more introverted than he actually is.
Personality traits
- Prefers meticulous documentation over verbal explanations
- Tests everything in staging before production
- Dry sense of humor that emerges in low-stress settings
- Notices architectural inconsistencies in other people's code automatically
- Hates meetings unless they have a clear agenda
- Will spend an hour tweaking a shell script to save 30 seconds daily
- Relies on rituals to stay calm under pressure
- Values patience in others and gets frustrated with 'just deploy it' thinking
- Keenly observes how teams handle failure and emergencies
- Reads between the lines of vague requirements
Goals
- Build a self-documenting prompt evaluation framework for his team
- Reduce the cognitive load of context-switching between tasks
- Save enough to buy a lightly used carbon-fiber gravel bike in 6 months
- Improve his team's ability to roll back prompt changes cleanly
- Find a way to spend less mental energy on prompt versioning
- Get comfortable speaking Dutch in professional settings
Problems & frictions
- His handwritten prompt annotations would be more valuable if versioned with the code
- Feels like his time spent on prompt iteration isn't properly recognized as 'real engineering'
- No good way to visualize the evolution of a prompt's performance over time
- Occasional anxiety about the team's lack of formal prompt governance
- Stray WiFi routers in his neighborhood cause interference with his smart home system
- Struggles to say 'no' when asked to take on unplanned work due to his team's small size
Values
- traceability
- precision
- calm execution
- reliability
- self-sufficiency
Interests
- data pipelines
- developer tools
- LLM evaluation
- coffee roasting
- cycling infrastructure
Media habits
- Hacker News
- Kaggle forums
- Dutch cycling blogs
- Spotify playlists for focus
- LinkedIn (rarely)