Why this persona fits the audience
He builds front-end features for SaaS clients and regularly records bug reproductions, UI walkthroughs, and short API demos to share in Slack or issue trackers. His current setup is a mix of OBS, QuickTime, and ad hoc file naming in cloud storage, with cost a constant consideration.
- Age: 29
- Location: Berlin, Germany
- Occupation: Freelance front-end developer
- Income: €74,000 EUR/year equivalent
- Education: Bachelor’s degree in Computer Science
- Company size: solo freelancer with 3-4 regular clients
- Years in role: 5
“I don’t need a fancy tool—just one that doesn’t make me waste hours figuring out why it stopped working.”
Kaan Dengler is a 29-year-old freelance front-end developer based in Berlin, specializing in React and developer tooling. After graduating with a Computer Science degree from TU Dresden, he worked briefly at a Berlin startup before going solo. His freelance career started with small gigs but quickly pivoted to SaaS clients after noticing how poorly documented their APIs were. He now builds front-end features for startups and records screen captures to clarify bugs or demo APIs—a task he finds frustratingly inefficient. His current setup is a mix of OBS, QuickTime, and manual file organization in Notion, a system that works but leaves him annoyed at the loss of time. He’s thrifty with software spending, having been burned by expensive tools with poor UX, but invests in quality hardware. His workstation is a high-end MacBook and ergonomic setup, reflecting his belief that good tools save time. Kaan is deeply autonomous, preferring to solve problems independently but values well-documented tools and communities. He’s currently considering consolidating his workflow but is cautious about lock-in. His side project is a React plugin for better error monitoring, which he hopes to monetize. He’s socially reserved but enjoys Berlin’s tech scene, attending meetups sporadically. His biggest challenge is balancing client work with his own projects, often feeling stretched thin. He’s saving for a new microphone, hoping it will improve his recordings, but debates whether the cost justifies the upgrade.
Background & daily life
A day in their life
Kaan wakes at 7:30 a.m. to his second alarm, brews coffee, and catches up on GitHub notifications while scarfing down overnight oats. By 9 a.m., he’s in his home office, tackling a React refactor for a client. At 11, he records a 2-minute bug repro video for Jira—his third take because OBS crashed. Lunch is a sad desk meal. Afternoon is spent in Slack calls, reviewing PRs, and fixing a CSS conflict. He records an API demo for another client, noting he needs to clean up the ad-hoc file naming. Evening is for open-source contributions or watching a tech talk. He winds down with a podcast, falls asleep reading API docs.
Lifestyle
Kaan lives in a compact but well-organized Kreuzberg loft with exposed brick and a southwest-facing window that lets in sunlight—critical for his seasonal mood regulation. His meal prep consists of weekly batches of lentil curry and quinoa bowls, which he eats while coding. He cycles everywhere in Berlin, even in winter, and has a habit of forgetting his gloves. His social life revolves around occasional meetups at Betahaus or Code.mu, but he’s more likely to be online at night, contributing to open-source or chatting in Reactiflux. He’s frugal with discretionary spending but splurged on a mechanical keyboard with a German layout. His health is generally good except for occasional neck stiffness from bad setup postures, which he ignores until it becomes painful. Money is managed in a spreadsheet, with separate tabs for taxes, client payments, and hardware budgets. His one indulgence is coffee—a fancy Aeropress setup he refinances like a startup.
Work life
Kaan’s workflow is a mix of React development and bug-hunting. He’s currently building a bespoke dashboard for a fintech startup, which requires frequent UI walkthroughs with the product team. His recording setup—a clunky OBS/QuickTime hybrid—is a constant annoyance. He’s tried free tools but finds them either too bloated or missing features. His biggest time sink is renaming screen captures consistently and organizing them in Notion. Clients expect fast turnarounds, so he’s always juggling between coding and documentation. He avoids meetings but tolerates them if they’re well-structured. His coworkers are mostly remote, and communication happens in Slack, GitHub, and occasionally Loom. He’s self-critical about his ad-hoc workflows but hasn’t found a tool that feels worth the cost—yet.
Relationships
Kaan’s family in Hamburg is supportive but doesn’t understand his work. He keeps in touch via WhatsApp family groups, mostly for his mother’s memes. His closest friends are from his university days, now scattered across Europe, and they sync up quarterly for board game nights. He occasionally goes on dates but avoids serious relationships due to work uncertainty. His biggest influence is a senior engineer at SoundCloud, whom he occasionally bounces ideas off. He’s part of a small React Berlin Slack group where he occasionally asks for code reviews but rarely shares personal stuff.
How they decide
Research-heavy but impatient with poor documentation. Prefers tools with free trials or generous refund policies. Trusts word-of-mouth recommendations over ads but dislikes hype. Once convinced, he commits fully but is slow to forgive bad experiences.
How they sound
Speaks in measured, slightly clipped sentences with occasional German words. Avoids jargon unless necessary. Prefers direct questions over small talk. Uses dry humor but rarely laughs. His written communication is terse but thorough. Avoids emojis in professional contexts. Has a habit of saying 'fair point' when acknowledging criticism.
Personality traits
- analytical but prone to over-optimizing workflows
- socially reserved but conversant in tech debates
- thrifty with software spending but invests in good hardware
- meticulous with code but sloppy with file organization
- enjoys deep technical discussions but avoids small talk
- prefers async communication but will troubleshoot over voice
- skeptical of marketing claims but respects well-documented tools
- likes solving problems independently but values good Stack Overflow answers
- pockets money for rare hardware upgrades (currently saving for a new microphone)
- secretly enjoys reading Reddit AMA from industry figures
Goals
- Build a recurring revenue stream from open-source plugins
- Move to a co-living space in Prenzlauer Berg to socialize more
- Contribute to a major React core feature by 2025
- Reduce freelance client dependency by 2024
- Run a Berlin meetup on performance optimization
Problems & frictions
- Constantly re-recording videos when UI changes mid-project
- Disorganized file naming leads to wasted time searching
- Clients nitpick screen recordings despite clear context
- Hardware upgrades feel like a financial stretch
- Burnout from context-switching between coding and documentation
Values
- efficiency
- technical quality
- autonomy
- precision
- minimalist design
- self-reliance
Interests
- React
- developer tooling
- open-source software
- issue triage
- berlin tech meetups
- cybersecurity
Media habits
- reads Indie Hackers and Dev.to
- listens to Syntax.fm and The Changelog
- watches Linus Tech Tips when procrastinating
- checks Twitter for developer memes
- occasionally binge-watches Handmade Heroes