Mario Poehn

Why this persona fits the audience

Staff backend engineer in Berlin for a Series B developer tools company. He maintains the internal LLM proxy for about a dozen engineers, with self-hosted logs, token accounting, and basic approval rules for EU customer data; he is often asked to compare new infrastructure options against internal builds.

• Age: 37
• Location: Berlin, Germany
• Occupation: Staff Backend Engineer
• Income: €110,000
• Education: Ph.D. in Computer Science
• Company size: 50-100 employees
• Years in role: 4

“The elegance of a system isn't just in its speed, but in its resilience and how well it respects the data it handles.”

Mario Poehn, 37, is a Staff Backend Engineer based in Berlin, Germany, holding a Ph.D. in Computer Science. His career trajectory has been marked by a consistent focus on building robust, scalable backend systems, particularly within the challenging domain of AI infrastructure. He joined his current company, a Series B developer tools firm, four years ago, drawn by their commitment to open-source principles and the opportunity to tackle complex engineering problems. His current role places him at the forefront of managing the company's internal LLM proxy, a system he designed and continues to evolve. This involves intricate work with self-hosted logging, meticulous token accounting to control cloud spend, and the implementation of granular approval rules, especially critical given the company's EU customer base and the stringent requirements of GDPR. Mario is often tasked with evaluating new infrastructure technologies, a responsibility he undertakes with extreme diligence, meticulously comparing vendor offerings against their existing internal solutions. His academic background instilled a deep appreciation for theoretical underpinnings, which he translates into a pragmatic, hands-on approach to engineering. He views technology not just as a tool for immediate problem-solving but as a long-term investment requiring careful consideration of maintainability, security, and operational stability. His personal finances are managed with a similar long-term perspective; he prioritizes saving and sensible investments over immediate gratification, reflecting his value for security and future preparedness. This methodical approach extends to his personal life, where his passion for road cycling involves detailed planning of routes and equipment maintenance, mirroring his professional dedication to technical rigor and operational excellence. He is deeply committed to data privacy, seeing it as a fundamental ethical and technical imperative, which heavily influences his decisions regarding infrastructure choices and data handling policies within the company.

Background & daily life

A day in their life

Mario's typical weekday begins around 7:00 AM with coffee and a review of Hacker News and internal system alerts. After his cycle commute to the office, he dives into coding, focusing on refining the LLM proxy's token accounting logic or implementing a new routing rule. Mid-morning often involves a stand-up meeting with his team, followed by a deep-dive session with another engineer about integrating a new vector database. Lunch is usually a packed meal eaten at his desk while reading documentation. The afternoon might include responding to urgent operational issues, reviewing a pull request for a new feature, or preparing a comparison document for a potential new AI gateway solution. He aims to leave by 6:00 PM, often cycling home to prepare dinner.

Lifestyle

Mario lives in a modest but well-maintained Altbau apartment in Prenzlauer Berg, shared with his partner, a graphic designer. His routine is structured: early mornings often involve a quick coffee and scanning tech news before cycling to work. Evenings are typically quiet, dedicated to cooking, reading technical documentation, or occasionally meeting a few close friends for a beer. Weekends are for longer cycling routes outside the city or working on personal open-source projects. He's financially prudent, prioritizing savings for future stability and occasional high-end cycling gear over impulsive purchases. His social circle is small but deep, valuing intellectual connection.

Work life

As a Staff Backend Engineer at a Series B developer tools company, Mario is the primary architect and maintainer of the internal LLM proxy. This critical piece of infrastructure serves about a dozen engineers, handling requests to various large language models. His responsibilities include ensuring self-hosted logs are secure and compliant with EU data privacy regulations, implementing token accounting to manage costs, and developing basic approval workflows for sensitive customer data. He's frequently pulled into discussions comparing external infrastructure solutions against their current internal builds, a task he approaches with deep technical scrutiny. The pressure is on to keep operations stable and costs predictable.

Relationships

Mario's closest relationships are with his partner, with whom he shares a quiet, intellectually stimulating home life, and a small group of long-time friends from university, mostly engineers and academics. He values their opinions on technical matters and occasionally seeks their advice on complex system design challenges. His influence within the company stems from his deep technical knowledge and consistent delivery, earning him respect from his immediate team and engineering leadership.

How they decide

Mario is highly research-driven and cautious. He meticulously analyzes technical specifications, benchmarks, and potential failure modes before committing to any significant infrastructure decision. He prefers to build internal proofs-of-concept or run small-scale tests to validate claims made by external vendors. Peer consultation within his trusted circle is common, but the final decision rests on rigorous data and his own assessment of long-term stability and maintainability.

How they sound

Speaks with a measured, precise cadence. His German accent is noticeable but not heavy. He avoids hyperbole and buzzwords, preferring clear, technical language. When discussing complex topics, he might pause to formulate his thoughts carefully. He uses phrases like 'from a systems perspective,' 'the primary concern is,' and 'it's crucial to consider.' He rarely uses slang and maintains a professional, slightly formal tone even in casual conversation.