Why this persona fits the audience
CTO of a 4-person startup in Berlin; coordinates with two engineers, one designer, and nearby open-source contributors through GitHub, Discord, and an Airtable list of people met at events, especially for weekend prototypes and technical introductions.
- Age: 35
- Location: Berlin, Germany
- Occupation: CTO at an early-stage startup
- Income: EUR 110k base + equity
- Education: Master's degree in software engineering
- Company size: 4 people (founder, two engineers, one designer)
- Years in role: 2
“I don't build startups—I build systems that outlive them. The product might die, but the code should keep teaching people.”
Anny Sinnhuber grew up in a Munich suburb, the daughter of a mechanic and an accountant, where she taught herself assembly language on a thrift-store 386. Her first job was at a car factory automation company, where she learned to value systems that just worked. By 24, she was commuting to Berlin for conferences and weekend hackathons—events that became her real education. After a master's in software engineering, she worked at an agency where she realized her talent for organizing chaotic technical projects. Two years ago, she took the CTO role at a pre-seed startup building developer tools, a field she finds satisfyingly niche. Her office vibe is 'chaos organized by coffee stains'—whiteboards covered in architectural diagrams, a shelf of obscure hardware projects, and a coffee machine that brews strong enough to power the servers. She's become known for her weekend hackathons, where she pairs unfamiliar engineers with interesting problems and steps back to let them work. Her current challenge is balancing her team's inexperience with the founder's aggressive timelines. She's quietly building a reputation as someone who can make things work with limited resources, a trait she shares with her father. Her biggest professional regret is not starting her own company sooner, a fear she's now channeling into mentoring other women engineers. When not coding, she's either bouldering or obsessively refining her Airtable system for tracking potential contributors—an ever-growing spreadsheet of Berlin's technical talent, categorized by skills, meetup chatter, and weekend prototype potential.
Background & daily life
A day in their life
Anny's alarm goes off at 6:15, and she's at the bouldering gym by 6:45. By 8:30 she's in the Altbau's loft office, her standing desk raised, staring at three screens: GitHub, Discord, and her Airtable list of potential contributors. First priority is responding to the weekend prototype team's questions—two developers she met at a Rust meetup who've pinged her about an AI side project. The morning is a blur of code reviews, Slack threads, and wading through 18 open PRs. She takes a 90-minute lunch break to bike to an investor meeting in Mitte, returning to find the designer wants to discuss UI components while an engineer needs her to review their complex auth rewrite. By 5:30 she's exhausted from context switching but forces herself to spend 45 minutes writing documentation for the weekend team. The evening is for cooking, a German tech podcast, and an hour coding on her open-source side project before collapsing by midnight.
Lifestyle
Anny rents a top-floor Altbau in Kreuzberg, where she's slowly replacing Ikea furniture with secondhand mid-century pieces. Her mornings begin with matcha and a 6:45am bouldering session at B-Spaces, where she knows half the regulars by first name. She cycles everywhere in Berlin, including the occasional 15km ride to Wannsee when she needs to think through architectural decisions. Weeknights are for cooking elaborate tagines or streaking through GitHub issues. She volunteers one weekend a month for Rails Girls Berlin and has a standing Tuesday night game night with her closest friends—a rotating group of engineers and designers who've all worked in startups that didn't make it. Anny is saving aggressively for a downpayment on a summer house in Mecklenburg-Vorpommern, though she'd never admit how much equity she's liquidating to do it.
Work life
Anny's typical day starts with staring at her Airtable dashboard of nearby developers—color-coded by expertise and contact status—before grabbing her standing desk's copper side handle to pull it up. She spends the first hour triaging GitHub issues and Discord DMs from contributors, often converting promising stranger's pull requests into weekend prototype invites. The morning's rhythm is broken up by the designer's insistently aesthetic brand decisions and the engineers' debates about whether to rewrite the auth system in Rust. Anny has implemented a 'quiet coding' protocol where everyone wears red headbands when they need deep work, which she respects religiously unless there's a production outage. She's currently teaching herself Rust while supervising two engineers who are senior to her but younger than the company's Series A worries. Her biggest frustration is balancing the founders' growth pressure with her own product quality convictions.
Relationships
Anny's closest relationships are with people she's helped grow as engineers. Her core friend group is made up of other startup refugees from failed companies—she trusts them implicitly and meets them monthly for a rotating dinner where they dissect each other's hiring mistakes. She has a younger sister in Hamburg who studies film, which Anny teases for its impracticality but quietly funds with ad-hoc consulting gigs. Her father, a retired mechanic, is her only non-tech confidant and the only person she'll admit to when she's stressed. The Berlin tech scene's casual hierarchy frustrates her, so she's cultivated a smaller network of engineers who measure success by code quality rather than VC terms.
How they decide
Anny makes decisions by testing the water with small experiments and proven patterns. She distrusts big frameworks without evidence and prefers to incrementally grow systems the way she builds teams—by bringing in people who can teach her. She's cautious about technical debt but will make quick calls to unblock her team. When unsure, she'll code a proof-of-concept before discussing it, preferring to show rather than argue.
How they sound
Anny speaks in declarative sentences, often starting with 'We have to...' even when it's just her opinion. She avoids jargon when talking to non-technical people but can't help slipping into GitHub issue lingo with other engineers. Her most common phrases: 'That's not scalable', 'We need to YAGNI this', and 'Let me just check the code.'. She has a slight Bavarian accent that surfaces when she's excited or frustrated. She laughs easily at her own mistakes but bristles at what she considers 'armchair architecture' from people who haven't dealt with production systems.
Personality traits
- The kind of leader who codes alongside her team during crunches
- Preemptively documents technical decisions as rough GitHub gists
- Hates unnecessary meetings but thrives in informal loft spaces with dry-erase walls
- Has a soft spot for junior developers who write clean, modular code
- Will debug a contributor's pull request at 23:47 if they're stuck
- Fond of Berlin's raw tech scene but secretly misses Munich's Bauhaus maintainability
- Treats her equity like a nesting egg (not a get-rich-quick scheme)
- Cynical about buzzwords but keeps a running list of founders to mentor
- Prefers Discord threads over email chains
- Obsessively refactors her own code before merges
Goals
- Build a product Berlin will respect for more than just its funding round
- Mentor three women into CTO roles by 38
- Open-source a small tool that gets 100+ stars
- Own a weekend house where she can host weekend hackathons
- Write a technical book about building reliable systems at pre-seed scale
Problems & frictions
- Her team's skill gaps mean she's still writing 30% of the production code
- The German startup scene expects founders to have prior exits—she doesn't
- Conflict between
- her perfectionist tendencies and the founder's
- ship it' mentality
- Her Airtable list of 237 potential contributors is unwieldy and full of dead leads
- The UX designer keeps fighting over architectural decisions
- Her work-life balance collapses during investment rounds
Values
- speed
- team autonomy
- product quality
- generosity in open source
- hands-on leadership
Interests
- open-source tooling
- startup prototyping
- technical meetups
- minimalist design
- Bouldering
Media habits
- Hacker News
- Tech Twitter
- Lobste.rs
- German tech podcasts
- Occasional Twitch streams of game dev