Why this persona fits the audience
He works on the web team at a Berlin startup where marketing pages are drafted in Webflow and then exported to GitHub for code review and occasional cleanup. He handles 3 active repos, merges changes from a designer’s exports, and uses the same repo conventions as the rest of the engineering team.
- Age: 38
- Location: Berlin, Germany
- Occupation: Front-end engineer
- Income: €72k
- Education: MSc in computer science
- Company size: Startup, approx. 50 employees
- Years in role: 5
““If it’s not maintainable, it’s not truly done. Efficiency is built on solid foundations, not quick fixes.””
Thies Gunther grew up in a quiet suburb near Hamburg, developing an early fascination with how things worked, which naturally led him to computer science. He pursued his MSc at TU Berlin, excelling in theoretical aspects but finding his true passion in practical application during internships at established software firms. These early experiences instilled a deep appreciation for robust engineering principles and clean code. After graduating, he worked for a couple of years at a larger e-commerce company, where he honed his skills in front-end development but grew weary of the bureaucratic pace. Seeking a more dynamic environment, he joined his current Berlin startup three years ago. Initially focused on core product features, his role gradually shifted towards supporting marketing initiatives as the company scaled its outreach. He now finds himself spending a significant portion of his time wrestling with the output of Webflow, exporting designs, and tidying up the code for a variety of marketing pages across three key repositories. He finds the process somewhat tedious but valuable, as these sites are crucial for lead generation. His income of €72k allows for a comfortable, though not luxurious, lifestyle in Berlin; he prioritizes saving and investing over immediate consumption. He views time as a finite resource, both in his personal life and in the context of software development, driving his commitment to maintainability and long-term efficiency. He recently spent several weeks researching and implementing a new linting setup for his repositories, a task that pleased his detail-oriented nature and improved code consistency, though it took time away from other planned improvements.
Background & daily life
A day in their life
Thies's day typically begins around 7:30 AM. After a quick breakfast and checking personal emails, he cycles to the office, arriving by 9:00 AM. The first hour is spent catching up on emails, Slack messages, and reviewing overnight alerts. He then dives into code review for a designer's latest Webflow export, ensuring it adheres to project standards. After lunch, he might work on refactoring a component for better performance or investigate a bug reported on a live marketing page. Mid-afternoon often involves a stand-up meeting or a quick sync with a designer about upcoming assets. He usually leaves the office around 6:00 PM, cycles home, and spends the evening preparing dinner, perhaps reading a tech blog or working on a small personal coding project for an hour or two before winding down.
Lifestyle
Thies lives a fairly ordered life in his Prenzlauer Berg apartment, which he meticulously keeps tidy. His income allows for comfortable living, saving a decent portion, but he's not extravagant. Weekday evenings are often spent coding personal projects, reading tech articles, or planning his next cycling route. Weekends involve longer rides through Brandenburg or catching up with a small circle of close friends, usually over coffee or a casual dinner. He prioritizes his health, cycling to work most days and preparing most of his meals to avoid processed foods. Financial decisions are usually well-researched and lean towards long-term value rather than immediate gratification.
Work life
Thies's workday is a blend of focused coding and collaborative problem-solving. He spends a significant chunk of time managing three marketing site repositories, ensuring designer exports from Webflow are integrated cleanly into the codebase. This involves code reviews, refactoring for maintainability, and occasionally troubleshooting build pipeline issues. He works closely with a small design team and occasionally with backend engineers on API integrations. The startup environment means he often wears multiple hats, dabbling in performance optimization and basic cloud infrastructure tasks to keep marketing pages running smoothly. Deadlines can be tight, especially around product launches, adding a low-level hum of pressure.
Relationships
Thies maintains a small, close-knit group of friends from university and previous jobs, mostly fellow tech professionals. He communicates with his parents in Hamburg weekly via phone. At work, he has a collegial but not overly social relationship with his immediate team, respecting their technical skills and directness. He doesn't seek out large social gatherings.
How they decide
Thies is a methodical and research-driven decision-maker. He thoroughly evaluates options, weighing pros and cons, often seeking out technical documentation, benchmarks, and community discussions before committing. He values evidence and practicality over hype, and prefers solutions that demonstrably improve maintainability and efficiency.
How they sound
Speaks German fluently with a clear, measured cadence. When speaking English, he is precise and avoids slang, occasionally pausing to find the exact technical term. His tone is generally calm and analytical. He tends to state facts and observations directly, without much emotional coloring. He avoids hyperbole and overly casual language.
Personality traits
- Methodical
- Detail-oriented
- Pragmatic
- Independent
- Analytical
- Patient
- Resourceful
- Slightly introverted
- Focused
Goals
- Become a senior engineer or tech lead within the next 3-5 years
- Contribute to an open-source project he uses regularly
- Achieve a better work-life balance, allowing more time for personal projects
- Develop a deeper understanding of scalable cloud architectures
- Maintain his physical fitness and cycling endurance
Problems & frictions
- The manual cleanup of Webflow exports is repetitive and error-prone
- Limited time for in-depth learning due to daily operational tasks
- Ensuring consistent code quality across different designer contributions
- Feeling disconnected from the core product development due to focus on marketing sites
- Balancing the desire for elegant solutions with the startup's need for speed
Values
- engineering rigor
- clarity
- maintainability
- efficiency
- continuous learning
Interests
- JavaScript
- product analytics
- cycling
- cloud infrastructure
- API design
- performance optimization
Media habits
- Reads Hacker News daily
- Follows key figures in JS/React/Vue communities on Twitter
- Listens to tech podcasts during commutes (e.g., Syntax.fm, Changelog)
- Occasionally browses Reddit (r/webdev, r/programming)
- Watches YouTube tutorials for new tools/frameworks