Rico Hackelbusch

Why this persona fits the audience

He co-founds a 7-person Berlin startup building developer tooling and maintains the company SDK as open source; contributor acknowledgments, sponsor messages, and payment notes are handled ad hoc in Notion and GitHub, with no standardized paid workflow.

• Age: 29
• Location: Berlin, Germany
• Occupation: CTO and co-founder
• Income: €95k plus equity
• Education: B.Sc. Informatics
• Company size: 7
• Years in role: 4

“The elegance of a solution isn't just in its performance, but in how cleanly it handles the messy realities of collaboration and contribution.”

Born and raised in a small town in Bavaria, Rico Hackelbusch developed an early fascination with how things work, dissecting electronics and tinkering with early programming languages. His academic path led him to a B.Sc. in Informatics at the Technical University of Munich, where he excelled in systems programming and distributed computing. During university, he contributed to several open-source projects, experiencing firsthand the challenges of managing contributions and the often-unacknowledged effort involved. This experience, coupled with a growing frustration with existing developer tools that felt overly complex or poorly maintained, planted the seed for his current venture. After graduating, he spent two years at a well-regarded software consultancy in Munich, honing his skills in building robust, scalable applications. However, the desire for greater ownership and the potential to build something truly impactful drew him to Berlin. There, he met his co-founders, and together they launched their startup three years ago, focusing on creating developer tooling that prioritizes developer experience and technical rigor. Rico, as CTO, is the primary architect of their core product and the maintainer of their open-source SDK. He views the current ad-hoc system for managing contributions and payments as a necessary evil, a temporary workaround born from a lean startup mentality. He's acutely aware of its limitations and the potential for friction as the project scales. His decision to keep the SDK open source was driven by a belief in community collaboration and a desire to foster wider adoption, but he's increasingly grappling with how to make this sustainable financially. He's not driven by a need for external validation or status; his satisfaction comes from solving complex technical problems and building tools that genuinely improve developers' lives. Time is a precious commodity, meticulously managed, and money is viewed as a means to an end—funding further innovation and ensuring the company's long-term independence.

Background & daily life

A day in their life

Rico's weekday typically begins around 6:30 AM with a quick check of overnight build statuses and urgent messages. After a strong coffee and a light breakfast, he dedicates the next three hours to deep, uninterrupted coding or architectural design, often tackling the most complex problems. A brief break for lunch is followed by team stand-ups and code reviews. The afternoon is a mix of meetings with his co-founders, responding to support requests, and planning future sprints. He tries to wrap up by 7 PM, often followed by a quick dinner and then another hour or two of focused work or reading technical papers before winding down around 11 PM.

Lifestyle

Rico lives in a functional, minimalist two-bedroom apartment in Prenzlauer Berg, sharing it with a long-term girlfriend who works in UX design. His routine is highly structured, prioritizing deep work blocks in the morning and evenings for coding or strategic thinking. Weekends often involve long road cycling trips through Brandenburg's countryside, pushing his physical limits. He's conscious of his spending, viewing money as a tool for achieving independence and funding future ventures rather than for status symbols. Social life is focused on a small circle of close friends, mostly from university or the startup scene, preferring quality over quantity in interactions.

Work life

As CTO and co-founder of a nascent devtools startup, Rico's days are a constant juggle between technical leadership, hands-on coding, and operational oversight. He's deeply invested in the company's core SDK, which they've open-sourced to foster community adoption. Managing contributor acknowledgments, sponsor messages, and potential payment flows feels like a constant, low-level administrative burden, currently handled through a patchwork of Notion pages and GitHub issue threads. The pressure to deliver a robust, scalable product while keeping the team lean and agile is immense. He spends significant time architecting solutions, reviewing code, and mentoring the junior engineers on his small team.

Relationships

Rico maintains a close relationship with his co-founders, who he trusts implicitly for their technical and business acumen. His girlfriend provides a grounding influence and a valuable perspective on user experience. His small circle of friends, primarily fellow tech professionals, serves as a sounding board for technical challenges and startup strategy. He values direct, honest feedback from this group.

How they decide

Rico is a highly analytical and research-driven decision-maker. He meticulously weighs pros and cons, often creating spreadsheets or detailed notes to compare options. He trusts data and empirical evidence over hype or anecdotal recommendations. While he values input from his team and trusted peers, the final decision rests on his own rigorous evaluation of technical feasibility, long-term impact, and alignment with core principles.

How they sound

Speaks with a clear, measured cadence, favoring precise technical language. Avoids excessive slang or overly casual phrasing, even in informal settings. His tone is generally serious and focused, but can lighten when discussing genuinely interesting technical challenges or cycling. He tends to be direct and avoids ambiguity, preferring to get straight to the point. He rarely uses filler words and speaks with a quiet confidence.