Why this persona fits the audience
He leads a 14-person engineering squad in Berlin and keeps a shared comparison sheet for dev tools, observability products, and AI coding assistants. He mostly checks official docs, changelogs, and peer recommendations, and he is fairly skeptical of category hype.
- Age: 42
- Location: Berlin, Germany
- Occupation: Engineering manager
- Income: €98,000
- Education: Master's degree in software engineering
- Company size: 50-100 employees
- Years in role: 5
“The best tool isn't the one that's loudest, but the one that quietly does the job, reliably, year after year.”
Yasin Pomp’s journey into engineering management began not with a grand ambition, but with a deep-seated desire for order and efficiency. Growing up in a family that valued intellectual pursuits, he gravitated towards the logical structures of computer science, earning a Master's degree in Software Engineering from Humboldt University of Berlin. His early career was spent as a hands-on developer, where he developed a keen eye for robust architecture and a healthy skepticism for fleeting trends. He learned early on that the allure of the 'next big thing' often masked underlying instability or complex integration challenges. This led him to meticulously document his findings, a habit that evolved into the shared comparison sheet his team now relies on. He views his role not just as managing people, but as curating a stable and productive technical environment. His current position at a Berlin-based tech company, leading a team of 14 engineers, is a testament to his steady, results-oriented approach. He’s recently been instrumental in evaluating new observability tools, pushing back against a vendor whose marketing heavily emphasized AI features but lacked clear documentation on core performance metrics. This decision, based on rigorous internal testing and comparison against established solutions, reflects his core values: reliability and technical rigor. He sees time and money as finite resources, best invested in solutions that offer long-term value and minimize operational friction, rather than chasing ephemeral hype. His personal finances are managed with similar prudence, prioritizing savings and investments for his family's future over immediate gratification.
Background & daily life
A day in their life
Yasin's typical weekday begins around 7:00 AM with coffee and reviewing overnight system alerts. After a quick breakfast with his family, he heads to the office by 8:30 AM. His morning is usually packed with stand-ups, 1:1s with his direct reports, and deep dives into architectural challenges or code reviews. Lunch is often a quick affair at his desk while catching up on industry news. The afternoon might involve cross-functional meetings, planning sessions for upcoming sprints, or hands-on troubleshooting. He aims to leave by 6:00 PM to be home for family dinner, often spending an hour after the kids are in bed reviewing documentation for a new database technology his team is considering.
Lifestyle
Yasin lives in a spacious, well-maintained apartment in Prenzlauer Berg with his wife, a graphic designer, and their two children, aged 9 and 11. Weekday evenings are structured around family dinners, homework help, and quiet time. Weekends often involve park visits, cycling, or exploring local markets. He’s not one for impulsive purchases, preferring to research significant buys thoroughly. He enjoys a good German lager and occasionally tries new craft beers, but his social life outside of close friends and family is limited. He prioritizes saving for his children's future and his own retirement, viewing financial stability as a cornerstone of peace of mind.
Work life
As an Engineering Manager for a 14-person team, Yasin’s days are a blend of strategic planning, technical oversight, and people management. He spends significant time reviewing code, architecting solutions, and unblocking his team. The pressure to deliver reliable features while managing technical debt is constant. He champions thorough evaluation of new tools, maintaining a shared internal spreadsheet where he meticulously logs pros, cons, and performance metrics for everything from CI/CD pipelines to observability platforms and nascent AI coding assistants. He’s recently pushed back against adopting a trendy new monitoring tool, insisting on a longer evaluation period based on past experiences with overhyped solutions.
Relationships
Yasin is married to Lena, a graphic designer, and they have a strong, collaborative partnership. He has a close-knit group of 3-4 long-term friends from university whom he sees regularly. Within his team, he's respected for his technical acumen and fairness, though some junior members find him a bit reserved. His parents, retired academics, are a source of intellectual curiosity and occasional advice.
How they decide
Yasin is highly research-driven and cautious. He prioritizes empirical evidence, official documentation, and peer-validated insights over marketing claims or anecdotal success stories. He prefers to test solutions internally before committing, often creating comparison matrices and running small-scale proofs-of-concept. He values long-term reliability and ease of integration above all else.
How they sound
Speaks with a measured, clear cadence. Uses precise technical language when discussing work, but can switch to more casual German when talking with friends. Avoids hyperbole and buzzwords. Tends to frame opinions with qualifying statements like 'Based on my experience...' or 'From a purely technical standpoint...'. His tone is generally calm and rational, even when discussing challenging issues.
Personality traits
- Analytical
- Detail-oriented
- Methodical
- Reserved
- Pragmatic
- Skeptical
- Diligent
- Independent
- Systematic
- Calm under pressure
Goals
- To build a highly performant and stable engineering team.
- To foster a culture of continuous learning and technical excellence.
- To achieve a better work-life balance for himself and his team.
- To contribute to open-source projects in his spare time.
- To see his children grow into well-rounded individuals.
Problems & frictions
- The constant influx of new, often unproven, technologies demanding evaluation.
- Balancing the need for innovation with the imperative for system stability.
- Managing team capacity against ambitious project roadmaps.
- Ensuring consistent code quality across a growing codebase.
- Dealing with the overhead of tool maintenance and integration.
- The challenge of filtering genuine technical advancements from marketing hype.
Values
- Reliability
- Technical rigor
- Low friction
- Efficiency
- Practicality
- Long-term stability
Interests
- DevOps
- Code quality
- Software evaluation
- Cloud infrastructure
- Performance optimization
- System architecture
Media habits
- Reading technical blogs (e.g., InfoQ, Hacker News)
- Listening to podcasts on software development and management
- Following key figures in DevOps and cloud-native communities on Twitter/Mastodon
- Skimming industry newsletters
- Consulting official documentation and RFCs