Edwin Loogen

Why this persona fits the audience

He is one of four engineers at a Berlin seed startup shipping an AI meeting-summary app in Next.js. His current work includes user auth, tiered billing, webhook processing, production logs, and guardrail checks before the public beta.

• Age: 28
• Location: Berlin, Germany
• Occupation: product engineer
• Income: EUR 110k salary + bonus
• Education: Bachelor's in computer science
• Company size: 4 engineers, 8 total employees
• Years in role: 2

“The real challenge isn't just building something new; it's building something that *works* reliably, day in and day out, without falling apart.”

Edwin Loogen grew up in a modest household in a mid-sized German town, where his early fascination with computers led him to pursue a Bachelor's in Computer Science. He excelled academically, driven by a natural curiosity and a desire to understand how things work. During his studies, he developed a strong preference for backend systems and robust engineering practices, often contributing to open-source projects in his spare time. After graduating, he joined a small, ambitious startup in Berlin, drawn by the opportunity to have a significant impact and work on cutting-edge AI technology. He's been with the company for two years, quickly becoming a key member of the engineering team. His current role as a product engineer involves a broad spectrum of responsibilities, from core feature development to ensuring production readiness. He lives alone in a functional apartment in Prenzlauer Berg, prioritizing experiences and skill development over material possessions. Edwin is highly conscientious, meticulously planning his work and striving for technical excellence. He values predictability and clear documentation, which sometimes clashes with the inherent chaos of a seed-stage startup environment. His decision-making process is heavily research-driven; he'll spend hours understanding a problem and evaluating potential solutions before writing a single line of code. He sees time as a valuable resource, both for his career progression and for pursuing his passion for rock climbing, which offers a physical and mental escape from the demands of his work. He is currently focused on the technical intricacies of launching their AI meeting-summary app, specifically ensuring the user authentication, tiered billing, and webhook processing systems are secure and scalable for their upcoming public beta launch.

Background & daily life

A day in their life

Edwin's typical weekday starts around 7:30 AM with coffee and a quick scan of Hacker News. He bikes to the office by 9 AM, where the team has a brief stand-up. The morning is dedicated to focused coding, tackling tasks like refining the webhook processing logic or implementing new guardrail checks for the AI model. Lunch is usually a quick, healthy meal prepared at home. Afternoons involve code reviews, collaborating with a colleague on a tricky user auth bug, and perhaps experimenting with a new LLM evaluation technique. He often stays until 6:30 PM, sometimes later if a critical issue arises, before biking home to unwind, perhaps with a short workout or by reading.

Lifestyle

Edwin lives a focused, somewhat minimalist life in Berlin. His weekdays revolve around work, punctuated by gym sessions or a quick run. Evenings are often spent coding personal projects, reading tech articles, or catching up with a small circle of close friends. Weekends are for longer climbing trips to nearby crags or exploring the city's cultural offerings. He values efficiency and avoids unnecessary spending, preferring to invest in experiences or tools that enhance his skills. His apartment is tidy and functional, reflecting his preference for order and clarity.

Work life

As one of the core engineers at a fast-paced startup, Edwin's days are a blend of deep technical problem-solving and rapid iteration. He's currently neck-deep in ensuring the AI meeting-summary app is robust for its upcoming public beta. This involves architecting and implementing user authentication flows, setting up tiered subscription logic, handling asynchronous webhook events from third-party services, optimizing production logging for debugging, and building critical guardrail checks to prevent misuse or unexpected AI behavior. The small team means he wears multiple hats, often collaborating directly with the CEO and product lead on feature feasibility and technical debt.

Relationships

Edwin maintains a close-knit group of friends, mostly fellow developers he met during university or through tech meetups. They often discuss technical challenges and share insights. His family lives in a smaller town in Germany; he visits them a few times a year. He values direct, honest communication and tends to trust the opinions of peers with proven technical expertise.

How they decide

Edwin is a research-heavy decision-maker, especially for technical matters. He meticulously evaluates options, reads documentation thoroughly, and often prototypes solutions before committing. He values evidence and clear reasoning, preferring to understand the 'why' behind a choice. While he respects peer recommendations, he ultimately relies on his own analysis and testing to make final decisions.

How they sound

Speaks with a clear, measured cadence. Uses precise technical language when discussing work, but can be more casual with friends. Avoids excessive jargon or buzzwords unless directly relevant. His tone is generally calm and rational, even when discussing complex problems. He might use occasional German interjections in informal settings but defaults to English for professional communication.