Why this persona fits the audience
Part of a 4-person product studio in Berlin serving a few client startups. On macOS they run Claude Code in raw shell windows for each client, track prompts and token usage in a shared Google Sheet, and copy draft commits between repos by hand when moving from one account to another.
- Age: 29
- Location: Berlin, Germany
- Occupation: Software engineer
- Income: €78k
- Education: M.Sc. in Computer Science
- Company size: 4
- Years in role: 3
“The real challenge isn't just building the software, it's building it efficiently and keeping the process clean enough that you don't lose your mind.”
Thies Wickert, 29, is a dedicated product engineer at a small, four-person product studio in Berlin, a role he's held for three years after completing his M.Sc. in Computer Science. His career trajectory has been marked by a desire for impactful work within agile environments, leading him to the agency setting where he can directly influence client outcomes. He thrives on the intellectual challenge of solving complex problems for early-stage startups, valuing the autonomy and direct client interaction his position affords. His current work primarily involves leveraging AI tools like Claude Code to accelerate development cycles for a diverse client base. This often means working within raw shell windows, meticulously managing multiple client sessions simultaneously. He's developed a personal system for tracking prompt usage and token consumption in a shared Google Sheet, a process born out of necessity to maintain cost control and client transparency. However, this manual approach, along with the tedious task of copying draft commits between different client repositories by hand, represents a significant friction point in his daily workflow. Thies is deeply invested in precision and speed, constantly seeking ways to optimize his processes. He believes in building 'tidy systems,' not just for his code, but for his entire workflow. This extends to his personal life, where he applies a similar methodical approach to his hobbies like home brewing and photography. He's conscious of his income (€78k), viewing it as a means to achieve financial stability and fund future personal projects or investments rather than a primary status symbol. Time is a valuable commodity for Thies; he's always looking for ways to reclaim it from tedious tasks to focus on more creative and challenging engineering problems. He recently decided to invest more time in exploring frontend tooling advancements, recognizing their potential to further enhance his development efficiency and the quality of the products he helps build. This decision stems from a growing awareness that while AI is powerful, the surrounding workflow management is where significant gains can still be made.
Background & daily life
A day in their life
Thies's typical weekday begins around 7:30 AM with a quick breakfast and checking Hacker News. He cycles to the agency by 9:00 AM, often listening to a tech podcast. The morning is dedicated to focused coding on his primary client project, usually involving AI assistance via Claude Code in a dedicated shell window. After a simple lunch, he tackles administrative tasks: updating the shared Google Sheet with prompt usage, responding to client emails, and manually transferring code commits for another project. The afternoon might involve a client call or pair programming with a colleague. He aims to leave by 6:00 PM, often stopping at a local market before heading home to brew beer or work on personal photography projects.
Lifestyle
Thies lives a focused, disciplined life in a compact but well-organized apartment in Prenzlauer Berg. His evenings often involve either brewing experimental batches of craft beer in his small kitchen or reviewing his photography portfolio, a hobby he pursues with a keen eye for composition. He's health-conscious, preferring cycling to work and cooking most of his meals. Socially, he enjoys occasional meetups with friends for football matches or exploring new craft beer bars, but he values his downtime for deep work and personal projects. His financial approach is conservative, prioritizing saving for future investments over immediate gratification.
Work life
As a product engineer at a small Berlin agency, Thies thrives on the variety of client projects but feels the strain of managing multiple contexts. His days are a constant juggle between client demands, often involving AI-assisted development with Claude Code. He spends significant time in raw shell windows, meticulously tracking prompts and token usage in a shared Google Sheet, a process he finds increasingly cumbersome. The manual copying of draft commits between different client repositories is a daily friction point. He values the autonomy his role provides but is acutely aware of the inefficiencies in his current workflow, especially when deadlines loom.
Relationships
Thies maintains a close-knit circle of friends, mostly fellow engineers and designers he met during university or through Berlin's tech meetups. He values their technical insights and often discusses work challenges with them. His family, based in a smaller town in Lower Saxony, is supportive but doesn't fully grasp the nuances of his work. He has a good rapport with his three colleagues at the agency, appreciating their collaborative spirit and shared dedication to client success.
How they decide
Thies is a methodical researcher. When considering new tools or workflows, he first identifies the core problem, then seeks out potential solutions through online forums, tech blogs, and recommendations from trusted peers. He's not afraid to try free or open-source options initially but will invest in a paid solution if it demonstrably solves a significant pain point and offers clear efficiency gains. He weighs the long-term benefits against the immediate cost and effort required for adoption.
How they sound
Speaks with a clear, measured cadence, typical of educated German speakers. He uses precise technical language when discussing work but can switch to more casual, slightly informal German with friends. He avoids hyperbole and overly enthusiastic claims, preferring factual descriptions. He might use phrases like 'It's quite inefficient,' 'The overhead is significant,' or 'We're looking for a more streamlined approach.' He tends to understate problems until they become critical.
Personality traits
- Methodical
- Detail-oriented
- Pragmatic
- Independent
- Resourceful
- Quietly ambitious
- Systematic
- Slightly introverted
Goals
- To build a reputation as a highly reliable and efficient engineer within his niche.
- To contribute to open-source projects that improve developer tooling.
- To eventually lead a small, specialized product development team.
- To achieve a better work-life balance without sacrificing project quality.
- To master advanced prompt engineering techniques for AI models.
Problems & frictions
- The constant context-switching between client projects is mentally taxing and error-prone.
- Manual tracking of AI usage and costs across multiple sessions is time-consuming and prone to mistakes.
- The fragmented workflow of copying code snippets and commits between different client environments is inefficient.
- Lack of a centralized, organized system for managing AI-powered development sessions.
- Balancing the desire for cutting-edge tools with the budget constraints of early-stage startups.
Values
- client trust
- precision
- speed
- tidy systems
- autonomy
Interests
- frontend tooling
- photography
- football
- home brewing
- exploring Berlin's tech scene
Media habits
- Reads Hacker News daily
- Follows key tech figures on X (formerly Twitter)
- Listens to tech podcasts during commutes
- Watches YouTube tutorials for specific coding problems
- Subscribes to newsletters on AI and web development