Why this persona fits the audience
He currently works as a full-stack engineer at a startup with exactly five people total: two founders and three non-founders, including him. His team ships weekly product changes, and he splits time between backend APIs, frontend fixes, and incident follow-up.
- Age: 29
- Location: Berlin, Germany
- Occupation: Full-stack engineer
- Income: €78k-€95k
- Education: Bachelor's degree in computer science
- Company size: 5
- Years in role: 3
“The most satisfying part of my job isn't just building something new, it's seeing it work reliably and knowing I made it robust.”
Konrad Wieser, 29, is a dedicated full-stack engineer deeply embedded in the fast-paced environment of a five-person B2B SaaS startup in Berlin. Holding a Bachelor's degree in Computer Science from a German technical university, he gravitated towards startup culture for its direct impact and the opportunity to work across the entire technology stack. His current role demands constant engagement with both backend development, primarily in Go for their core APIs, and frontend responsibilities using React. He’s been with the company for three years, witnessing its growth from a two-founder idea to a small, functional team shipping weekly updates. Konrad’s approach to his work is characterized by a strong sense of craftsmanship and a commitment to reliability; he meticulously writes code and invests time in thorough testing, often staying late to ensure stability after deployments. He sees the weekly release cycle not just as a deadline, but as a continuous feedback loop that drives incremental improvement. His decision to join this particular startup was driven by the promise of significant autonomy and the chance to learn rapidly from experienced founders. He lives frugally but comfortably, prioritizing experiences and skill development over material possessions. His income, while good for his age and experience, is reinvested into his professional growth through courses and hardware, as well as savings for future stability. The constant need to context-switch between feature development, bug fixing, and urgent incident response is a defining aspect of his professional life, forcing him to develop resilience and sharp problem-solving skills under pressure. He recently championed the adoption of a new observability tool, arguing for its necessity in reducing incident resolution times, a decision that was met with initial skepticism but has since proven its worth.
Background & daily life
A day in their life
Konrad's typical weekday starts around 8:00 AM with a pour-over coffee and a quick scan of tech news. He's at his desk by 9:00 AM, often diving straight into responding to overnight alerts or reviewing the previous day's deployments. Mornings are usually dedicated to coding new features or tackling complex bugs, with frequent context switching between the backend API and frontend components. Lunch is a quick affair, often a simple meal prepared at home. Afternoons might involve a stand-up meeting with the founders, code reviews, writing documentation, or troubleshooting production issues. He usually wraps up around 6:00 PM, sometimes pushing later if a critical incident arises, before heading out for a bike ride or meeting friends.
Lifestyle
Konrad lives in a shared apartment in Friedrichshain, Berlin, opting for affordability and proximity to the city's pulse over solo living. His evenings and weekends often involve cycling through the city's parks or along the Spree, followed by brewing meticulously prepared filter coffee. He's a regular at local board game meetups, enjoying strategic challenges that engage his problem-solving skills. Financially, he's diligent, saving a portion of his income for future investments and potential travel, but isn't overly frugal, enjoying good food and occasional concerts. Socially, he maintains a close circle of long-term friends from university and his startup.
Work life
As a full-stack engineer at a lean B2B SaaS startup, Konrad's days are a dynamic blend of coding, debugging, and system maintenance. The small team means he wears multiple hats, contributing to both the backend services written in Go and the React frontend. Weekly releases are the norm, demanding agility and a constant focus on quality. He spends significant time on incident response, analyzing logs and implementing fixes to ensure system stability, a task he finds both stressful and rewarding due to the direct impact. His direct interaction with the two founders means priorities can shift rapidly, requiring adaptability.
Relationships
Konrad's closest relationships are with his university friends, who understand his career path, and his supportive but geographically distant family. His two founders, while often demanding, are also mentors, and he respects their vision. His interactions with coworkers are primarily professional, leaning towards task-oriented discussions rather than deep personal connection, reflecting his slightly introverted nature.
How they decide
Konrad approaches decisions methodically. He thoroughly researches technical options, weighing pros and cons based on performance, maintainability, and long-term scalability. For personal matters, he's generally cautious, preferring to gather information and consider potential outcomes before committing, often discussing significant choices with his closest friends.
How they sound
Speaks with a clear, measured cadence, favoring precise language. Avoids excessive slang or overly casual phrasing in professional contexts. His tone is generally calm and analytical, even when discussing stressful situations. He might use technical jargon naturally when discussing his work but is capable of simplifying explanations for broader understanding.
Personality traits
- Meticulous
- Pragmatic
- Curious
- Independent
- Resourceful
- Detail-oriented
- Calm under pressure
- Slightly introverted
Goals
- Achieve technical mastery in distributed systems.
- Contribute to a product that demonstrably solves a significant business problem.
- Build a personal side project that gains traction.
- Maintain a healthy work-life balance without sacrificing professional growth.
- Eventually transition into a more senior or lead engineering role.
Problems & frictions
- The constant pressure to deliver features quickly at the startup can sometimes compromise code quality.
- Limited resources and manpower mean he often has to choose between fixing bugs and developing new functionality.
- Feeling isolated when working on complex problems without immediate peer feedback.
- The rapid pace of technological change requires continuous self-directed learning, which can be time-consuming.
- Ambiguity in product direction due to the small founding team's evolving vision.
Values
- craftsmanship
- reliability
- learning
- autonomy
- impact
Interests
- cycling
- indie software
- specialty coffee
- complex board games
- electronics tinkering
Media habits
- Reads tech blogs (Hacker News, Lobste.rs)
- Listens to podcasts (software development, productivity)
- Follows select developers on Twitter
- Watches YouTube tutorials for new tech
- Occasional use of Reddit for niche hobbies