Why this persona fits the audience
Works at a 16-person compliance SaaS in Berlin and leads the frontend side of a shared React component library used across two product squads. The team documents variants in Figma and Storybook, tracks spacing and color decisions in spreadsheets, and has kept the system in-house rather than adopting a paid UI kit so far.
- Age: 41
- Location: Berlin, Germany
- Occupation: Staff Frontend Engineer
- Income: €92k
- Education: M.Sc. in Software Engineering
- Company size: 16 people
- Years in role: 5 years
“The real challenge isn't building components, it's building a system that helps everyone build better, faster, and more consistently, without becoming a bottleneck.”
Piet Hermann, 41, is a Staff Frontend Engineer at a 16-person compliance SaaS company based in Berlin. Holding an M.Sc. in Software Engineering, he has dedicated the last five years to leading the frontend development and maintenance of the company's homegrown React component library. This system serves as the backbone for two distinct product squads, aiming to enforce consistency and streamline development. Piet's journey into this role was gradual; he initially joined the company as a senior frontend engineer and naturally gravitated towards the challenges of unifying the UI codebase. He believes strongly in the principles of maintainability and team autonomy, which fueled the decision to build and iterate on their own design system rather than relying on external, off-the-shelf solutions. This approach, while demanding, allows for deep customization and control over the technology stack. His daily work involves a meticulous balance of coding, code reviews, architectural planning, and documentation, often using Figma for visual specifications and Storybook for interactive component previews. Decisions regarding spacing, color palettes, and typography are meticulously tracked, often in shared spreadsheets, reflecting his conscientious nature. Piet is deeply invested in web accessibility, viewing it not as an add-on but as a fundamental requirement for any robust design system. He advocates for TypeScript adoption across the frontend, valuing its ability to catch errors early and improve code quality. His income of €92k allows for a comfortable life in Berlin, but he remains pragmatic about finances, prioritizing long-term stability and value over immediate gratification. He sees the design system as a critical asset, a testament to the team's engineering prowess and a key enabler for future product growth.
Background & daily life
A day in their life
Piet's typical weekday starts around 8:30 AM after a leisurely breakfast. He begins by checking emails and Slack for urgent issues before diving into his primary task: refining a new set of form input components. This involves writing TypeScript definitions, updating Storybook stories, and ensuring accessibility compliance. Around lunchtime, he might join a brief stand-up with one of the product squads to answer questions about component usage. The afternoon is often dedicated to code reviews, providing detailed feedback on pull requests from other engineers, and occasionally pair programming to resolve complex issues within the design system. He aims to wrap up by 6:00 PM, often taking a short walk before dinner.
Lifestyle
Piet lives with his partner in a well-maintained Altbau apartment in Prenzlauer Berg, Berlin. They share responsibilities for household chores and enjoy quiet evenings at home, often cooking vegetarian meals. Weekends are for longer cycling trips along the Spree or exploring Brandenburg's countryside. He's financially prudent, preferring to save for future travel or home improvements rather than impulse purchases. Socially, he prefers smaller gatherings with close friends over large parties, valuing deep conversations.
Work life
Piet's days are consumed by the intricate task of maintaining and evolving the company's in-house React component library. He juggles code reviews for two product squads, architectural discussions about component patterns, and the ongoing effort to document new variants in Figma and Storybook. The pressure to ensure consistency across products, coupled with limited resources, means he often finds himself deep in spreadsheets tracking design tokens. He champions accessibility standards, pushing for better keyboard navigation and ARIA attributes within the system.
Relationships
Piet is in a long-term partnership with his girlfriend, who provides a grounding influence. At work, he collaborates closely with the lead designer and the two product managers whose squads utilize the component library. He has a small circle of trusted colleagues with whom he discusses technical challenges, but generally prefers to work independently on his core responsibilities.
How they decide
Piet is highly methodical and research-driven. He evaluates options thoroughly, weighing pros and cons against the specific needs of his team and the company's long-term goals. He seeks input from trusted colleagues but ultimately relies on data and his own technical judgment. He is risk-averse when it comes to introducing significant changes or adopting new technologies without extensive proof of concept.
How they sound
Speaks with a measured, calm cadence. His tone is generally neutral and informative, avoiding overly casual slang or excessive jargon unless discussing technical specifics with peers. He tends to use precise language and often qualifies his statements. He avoids hyperbole and expresses opinions thoughtfully, often prefacing them with phrases like 'From my perspective...' or 'What I've found is...'.
Personality traits
- meticulous
- detail-oriented
- methodical
- patient
- pragmatic
- reserved
- analytical
- diligent
Goals
- To establish a robust, scalable design system that significantly reduces frontend development time.
- To mentor junior engineers on best practices in component development and design system thinking.
- To achieve a better work-life balance, allowing more time for personal projects and cycling.
- To contribute to open-source projects related to design systems or frontend tooling.
- To see the design system adopted more widely and consistently across all company projects.
Problems & frictions
- Balancing the need for new features with the ongoing maintenance and refactoring of the existing component library.
- Ensuring consistent adoption and understanding of the design system across different product teams with varying priorities.
- The manual effort involved in documenting component variants and design decisions.
- Limited bandwidth for proactive architectural improvements due to urgent feature requests.
- The challenge of keeping the homegrown system up-to-date with the rapidly evolving frontend ecosystem.
Values
- consistency
- maintainability
- team autonomy
- clarity
- efficiency
Interests
- design systems
- TypeScript
- accessibility
- performance optimization
- cycling
Media habits
- reading technical blogs (e.g., Smashing Magazine, CSS-Tricks)
- listening to podcasts on software architecture and frontend development
- following key figures in the design system community on Twitter/X
- watching conference talks on YouTube