Ben van Ginneken

Why this persona fits the audience

Runs engineering for a 22-person marketplace startup in Amsterdam. The team uses open-source mobile testing tools in CI, keeps a shared set of YAML-based flows in Git, and occasionally compares results against a hand-run checklist when a release touches payments or account recovery.

• Age: 40
• Location: Amsterdam, Netherlands
• Occupation: CTO
• Income: €125k + equity
• Education: MSc Computer Science
• Company size: 22
• Years in role: 5

“We're building something valuable here, and that means we need to build it right, even when it’s tempting to take shortcuts.”

Ben van Ginneken's journey into technology began not with a grand vision, but with a deep-seated curiosity for how things work. Growing up in a modest household in Utrecht, he found solace and fascination in disassembling and reassembling old electronics. This innate drive led him to pursue an MSc in Computer Science at the University of Amsterdam, where he gravitated towards systems architecture and distributed computing. Post-graduation, he spent several years at a larger e-commerce firm, honing his skills in backend development and infrastructure management, learning the importance of robust testing and maintainable codebases. He found the corporate environment, however, lacked the agility and direct impact he craved. Five years ago, he was recruited to his current role as CTO at a burgeoning Amsterdam-based marketplace startup. The company was small then, and it has since grown to 22 people under his engineering leadership. Ben is deeply invested in the company's success, seeing his equity as a tangible stake in its future. His approach to engineering is characterized by pragmatism and a strong belief in technical leverage through well-chosen tools and processes. He actively champions the use of open-source solutions, seeing them as both cost-effective and community-driven. Recently, the team grappled with a series of minor but persistent bugs in the payment gateway integration after a new feature release. This prompted a thorough review of their CI/CD pipeline and testing strategies, leading to a renewed emphasis on their YAML-based mobile testing flows and a commitment to more rigorous manual validation for payment-related code changes before each release. He views time as a finite, precious resource, meticulously allocating it between strategic planning, team mentorship, and the occasional deep dive into complex code. Financial security is important, reflected in his savings habits, but his primary motivation remains building a technically sound and successful product.

Background & daily life

A day in their life

Ben's typical weekday starts around 7:30 AM with coffee and reviewing Hacker News or urgent Slack messages. By 9:00 AM, he's usually in a stand-up meeting with the core engineering team, discussing progress and blockers. The rest of the morning is a mix of code reviews, 1-on-1s with his lead engineers, and architectural discussions. Lunch is often a quick sandwich at his desk while listening to a podcast. Afternoons might involve planning future sprints, troubleshooting a tricky bug, or meeting with product managers. He aims to wrap up by 6:00 PM, though critical issues can extend this. Evenings are for family, hobbies, or unwinding.

Lifestyle

Ben lives in a well-maintained but compact apartment in Amsterdam Oud-West with his partner, a graphic designer, and their cat. Weekends are a mix of productivity – perhaps tweaking his homebrew setup or reviewing a complex PR – and relaxation, like a long bike ride along the Amstel or a quiet evening with a book. He’s conscious about his health, making time for the gym a few times a week. Financially, he's comfortable, saving diligently for a future larger home, but not frivolous. Social life is focused on a small circle of close friends and occasional dinners with colleagues.

Work life

As CTO of a growing marketplace, Ben juggles strategic technical direction with hands-on problem-solving. His 22-person engineering team relies on him for architectural guidance and setting technical standards. The current focus is on scaling the platform's backend and ensuring robust payment processing. He spends a significant portion of his day in code reviews, architectural discussions, and planning sprints. The pressure is on to deliver new features while maintaining stability, a constant balancing act between speed and quality. He champions pragmatic solutions, preferring established open-source tools where possible.

Relationships

Ben has a stable, supportive relationship with his partner. He maintains close friendships with a few university peers who are also in tech, with whom he occasionally discusses technical challenges. His immediate team respects his technical acumen and fair approach, though he’s not overly social outside of work-related interactions. He has a good rapport with the CEO, built on trust and shared ambition for the company's success.

How they decide

Ben is generally cautious and research-oriented, especially when it comes to significant technical investments. He’ll weigh pros and cons carefully, often consulting with senior engineers on his team. He values data and evidence, preferring to see benchmarks or successful case studies before committing. For tools that directly impact development workflow, he'll often trial them with a small subset of the team first.

How they sound

Speaks with a calm, measured tone. Uses precise language, avoiding jargon where possible unless discussing technical matters with peers. Tends to be direct and factual, but not abrupt. His English is fluent but retains a subtle Dutch cadence. He rarely uses slang and prefers professional discourse, even in informal settings. He's not one for hyperbole.