Emir Wagenaar

Why this persona fits the audience

Leads a 5-person team in Amsterdam shipping an AI sales assistant. Their production stack already includes Langfuse traces, custom Python wrappers, and feature flags for controlled rollout across a few pilot customers.

• Age: 36
• Location: Amsterdam, Netherlands
• Occupation: CTO, seed-stage SaaS startup
• Income: €120k + equity
• Education: MSc Software Engineering
• Company size: 5
• Years in role: 2

“The real challenge isn't just making the AI *do* something, it's making it do it reliably, predictably, and without burning through our entire runway.”

Emir Wagenaar's journey into the heart of AI development began not with a grand vision, but with a deep-seated fascination for systems and logic. Growing up in a modest household in Utrecht, he found solace and excitement in the intricate worlds of computer programming and strategy board games. His academic path was clear: an MSc in Software Engineering from Delft University of Technology, where he honed his analytical skills and developed a rigorous approach to problem-solving. Post-graduation, he spent several years at a well-established Dutch tech firm, gaining invaluable experience in building robust, scalable enterprise software. However, the allure of building something from the ground up, coupled with a growing interest in the burgeoning field of generative AI, led him to co-found his current startup two years ago. As CTO, Emir is the technical architect and guardian of their AI sales assistant product. His current focus is on operationalizing their AI models, a task that involves intricate work with Langfuse for detailed tracing of agent behavior, developing custom Python wrappers to interface with various LLMs and vector databases, and implementing sophisticated feature flags for controlled rollouts to their initial pilot customers. He's acutely aware of the 'black box' nature of many AI components and is driven by a need for transparency and control, constantly seeking ways to add deterministic guardrails and observability. This stems from a core value of technical rigor; he believes that speed is essential in a startup, but never at the expense of understanding and controlling the underlying systems. He champions good design not just for aesthetics, but for maintainability and future flexibility, ensuring the company retains optionality as the AI landscape evolves. His personal interests in sailing and indie games, while seemingly disparate, inform his approach: sailing teaches patience and risk management in unpredictable environments, while indie games often showcase innovative, resource-constrained design. He views his work not just as building a product, but as navigating the complex, rapidly shifting currents of AI technology, always aiming for a stable, well-architected destination.

Background & daily life

A day in their life

Emir's typical weekday begins around 7:30 AM with coffee and a quick check of overnight system alerts and key metrics. He then cycles to the office, arriving by 9:00 AM. The morning is usually dedicated to deep work: coding new features for the AI sales assistant, refining prompt engineering strategies, or architecting improvements to their Python wrappers. He leads a brief stand-up meeting around 10:30 AM to sync with his team. Lunch is often a quick affair, sometimes eaten at his desk while reviewing pull requests. The afternoon involves more collaborative work: pair programming, discussing architectural decisions, or troubleshooting production issues flagged by Langfuse traces. He also dedicates time to researching potential new tools or libraries that could enhance their stack. He aims to leave the office by 6:30 PM, often taking a longer cycle route home to decompress.

Lifestyle

Emir lives with his partner in a charming, slightly cramped apartment in Amsterdam's Jordaan district, a space they've painstakingly renovated themselves. Weekends often involve long cycling trips through the Dutch countryside or, weather permitting, heading to the coast for a day of sailing. He's a creature of habit, starting most mornings with a strong espresso and a quick scan of tech news before his commute. While he enjoys the occasional indie game session, his free time is increasingly consumed by exploring new AI research papers. He's financially prudent, prioritizing long-term security and equity over immediate luxury, but isn't afraid to invest in quality tools that genuinely improve his workflow.

Work life

As CTO of a seed-stage startup building an AI sales assistant, Emir is constantly juggling innovation with stability. His five-person team is lean and agile, pushing code daily. The pressure is immense to deliver value to early pilot customers while iterating rapidly. He spends a significant portion of his day architecting new features, debugging complex AI interactions, and ensuring the production environment, currently running Langfuse for tracing and custom Python wrappers for model orchestration, remains robust. He's also deeply involved in evaluating new tooling, always with an eye on how it can accelerate development without introducing undue complexity or vendor lock-in. The constant need to balance speed with technical debt is a daily challenge.

Relationships

Emir's closest relationships are with his partner, who understands the demands of startup life, and his small, tight-knit engineering team. He values their direct feedback and technical debates. His former university colleagues, now scattered across various tech companies, form a valuable informal network for advice and industry insights. He has a cordial but distant relationship with the company's investors, respecting their financial stake but preferring technical autonomy.

How they decide

Emir is a research-heavy decision-maker, particularly for technical tools. He deeply values empirical evidence, preferring to test solutions himself or rely on trusted peers' detailed technical reviews. He's not easily swayed by marketing hype and will spend considerable time dissecting documentation and exploring open-source alternatives before committing. While he appreciates elegant solutions, pragmatism often wins out, especially when speed is critical. He’s willing to experiment but always with a clear exit strategy or rollback plan in mind.

How they sound

Speaks with a measured, thoughtful cadence, often pausing to find the precise technical term. His English is fluent but carries a subtle Dutch accent. He avoids overly casual slang or corporate jargon, preferring direct and clear communication. He's comfortable discussing complex technical concepts but can simplify them when necessary for less technical stakeholders. He often uses analogies related to engineering or sailing to explain abstract ideas. He tends to be understated about achievements, focusing more on the technical challenges overcome.