Mathijs van Veen

Why this persona fits the audience

He is one of four engineers at an Amsterdam marketplace startup and owns security checks for the payment and login paths. He uses open-source scanners, pull-request checklists, and manual reproduction in staging because the team has never budgeted for a dedicated security tool.

• Age: 30
• Location: Amsterdam, Netherlands
• Occupation: Senior software engineer
• Income: €82k-€98k total compensation
• Education: Bachelor's degree in Computer Science
• Company size: Startup (approx. 20 employees)
• Years in role: 3

“You can't afford to cut corners on security; it's like building a house on sand, eventually, it will all come down.”

Mathijs van Veen grew up in a small town just outside of Utrecht, developing an early fascination with how things work, which naturally led him to computers. He pursued a Bachelor's degree in Computer Science at the University of Amsterdam, where he excelled in theoretical subjects and practical programming. Upon graduation, he joined a promising e-commerce startup as a junior developer, quickly demonstrating a knack for identifying subtle bugs and a meticulous approach to coding. His aptitude for detail and responsibility saw him promoted to Senior Software Engineer within three years. He's now a key member of a lean engineering team at an Amsterdam-based marketplace startup, where he's been instrumental in building out their technical infrastructure. Mathijs is highly conscientious, approaching his work with a deep sense of ownership, particularly over the security of the payment and login systems. This responsibility weighs on him, especially given the company's limited budget for specialized security tools. He's had to become incredibly resourceful, leveraging open-source scanners, implementing rigorous pull-request checklists, and dedicating significant time to manual reproduction of potential vulnerabilities in staging environments. This approach, while effective, often strains his time and requires him to forgo some of the leisure activities he enjoys, like longer cycling trips or spontaneous urban explorations. He values efficiency and clean code, believing that well-structured software is inherently more secure and maintainable. Independence is also a core value; he prefers to solve problems himself rather than wait for external solutions. His income allows for a comfortable life, but he remains pragmatic and avoids unnecessary spending, prioritizing savings for future travel and financial security. He views his role not just as writing code, but as actively defending the platform and its users against threats.

Background & daily life

A day in their life

Mathijs's day begins with a brisk cycle to the office, often listening to a tech podcast. He starts by reviewing overnight alerts and checking critical systems before diving into his primary tasks. This typically involves writing code for new features or refactoring existing components, with a significant portion of his time dedicated to security reviews of his colleagues' pull requests. He participates in a daily stand-up meeting, discussing progress and blockers. Lunch is usually a quick affair at his desk, often while reading industry news. The afternoon might involve debugging a tricky issue or manually reproducing a potential security exploit in staging, followed by more coding and code reviews before cycling home. Evenings are for dinner with his partner, board games, or personal learning.

Lifestyle

Mathijs lives in a spacious, light-filled apartment in the Oud-West district with his partner, a graphic designer. Their shared passion for design extends to their home, filled with a mix of mid-century modern furniture and plants. Weekends often involve cycling along the Amstel river or meeting friends for complex board games at a local café. He's disciplined about his finances, prioritizing saving for potential future travel and maintaining a healthy emergency fund, but enjoys good food and craft beer. He values his downtime, using it to recharge for the demanding work week.

Work life

As one of the core engineers at a rapidly growing marketplace startup, Mathijs feels the weight of responsibility heavily. His primary focus is ensuring the security of critical user paths, particularly payment and login. The team's tight budget means he relies on open-source tools, meticulous pull-request reviews, and extensive manual testing in staging environments. This often leads to late nights or weekend work when a critical vulnerability is suspected. He collaborates closely with the other three engineers, often debating architectural decisions and code quality.

Relationships

Mathijs shares a strong, supportive relationship with his partner, who understands his demanding work schedule. He maintains a close-knit group of friends from university, with whom he frequently plays board games and discusses tech. His direct manager trusts his judgment implicitly regarding security matters, but he sometimes feels a disconnect with the non-technical founders regarding the importance of security investments.

How they decide

Mathijs is a highly research-oriented and analytical decision-maker, especially concerning technical matters. He meticulously evaluates options, weighs pros and cons based on empirical evidence or established best practices, and seeks input from trusted peers when necessary. He is generally risk-averse when it comes to security-related choices, preferring a proven, albeit more time-consuming, approach over a novel, potentially unstable solution.

How they sound

Speaks in a clear, measured tone, often with a slight Dutch accent. Tends to use precise technical language but can explain complex concepts in simpler terms when needed. Avoids hyperbole and emotional language, preferring factual statements. His speech is generally unhurried, reflecting his methodical thinking. He's not one for excessive slang, but might use common English tech jargon naturally.