Hendrik Fietz

Why this persona fits the audience

Works as a fractional CTO for an 8-person Berlin healthtech team; he oversees a product that stores patient-adjacent data in EU-only infrastructure, and the team already pays for a hosted deployment platform while keeping environment settings in spreadsheets and a password manager.

• Age: 41
• Location: Berlin, Germany
• Occupation: Fractional CTO
• Income: €125k contractor income
• Education: Diplom-Informatiker
• Company size: 8
• Years in role: 3

“The elegance of a system isn't just in its speed, but in its resilience and the quiet confidence that it will perform as expected, especially when it matters most.”

Hendrik Fietz, 41, embodies the meticulous pragmatism of a seasoned technologist navigating the complexities of modern software development. Holding a Diplom-Informatiker from a reputable German university, his career has been a steady progression through roles demanding deep technical understanding and a commitment to robust engineering. He spent his early years as a software engineer at a mid-sized enterprise, honing his skills in backend development and database management. This foundational experience instilled in him a profound appreciation for system stability and the long-term consequences of technical debt. Seeking greater autonomy and exposure to cutting-edge challenges, he transitioned into consulting and eventually found his niche as a fractional CTO. For the past three years, he has been instrumental in shaping the technical direction of an 8-person healthtech startup based in Berlin. His current role is defined by the critical responsibility of overseeing a product that stores sensitive patient-adjacent data, necessitating an unwavering focus on EU-only infrastructure and stringent data protection. He operates within the constraints of a startup environment, where innovation must be balanced with fiscal prudence. The team currently leverages a hosted deployment platform, a significant step up from manual processes, but Hendrik remains acutely aware of the lingering inefficiencies. Environment settings are still managed via spreadsheets, and critical credentials reside in a shared password manager – a setup he views as a ticking time bomb. His decision to maintain EU-only infrastructure is non-negotiable, driven by a deep-seated belief in data sovereignty and the legal frameworks designed to protect it. This commitment shapes his technology choices and architectural decisions, prioritizing compliance and auditability above all else. Hendrik’s relationship with time is one of careful allocation; he views wasted time as a direct precursor to errors and missed opportunities. Similarly, his approach to money is conservative, favoring investments in reliable, long-term solutions over flashy, unproven technologies. Status, for Hendrik, is derived not from outward appearances but from the quiet competence and reliability of the systems he helps build and maintain.

Background & daily life

A day in their life

Hendrik's typical weekday begins around 7:00 AM with a quick check of system alerts and overnight logs, followed by coffee and reviewing Hacker News. From 9:00 AM to 12:00 PM, he dedicates himself to deep work, often focusing on architectural design, security reviews, or scripting automation tasks for the healthtech startup. Lunch is a simple affair, usually eaten at his desk while catching up on emails. The afternoon involves virtual meetings with the development team, discussing progress, addressing blockers, and planning upcoming sprints. He might spend an hour troubleshooting a deployment issue or researching a new security protocol. He aims to wrap up by 6:00 PM, often going for a bike ride or preparing a healthy meal.

Lifestyle

Hendrik lives in a well-organized, minimalist apartment in Prenzlauer Berg, Berlin. His routine is structured, prioritizing focused work blocks and regular exercise. He enjoys quiet evenings, often spent reading technical journals or planning his next sailing trip. While he values financial security, he's not driven by excessive wealth accumulation, preferring to invest in experiences and reliable tools. Socially, he maintains a small circle of close friends, preferring deep conversations over large gatherings. He's conscious about his health, with a balanced diet and regular cycling to work.

Work life

As a fractional CTO for a lean healthtech startup, Hendrik's days are a blend of strategic oversight and hands-on problem-solving. He juggles responsibilities across development, infrastructure, and security for a product handling sensitive patient-adjacent data within strict EU regulations. His team relies on a hosted deployment platform, but environment configurations and sensitive credentials are still managed via spreadsheets and a shared password manager – a situation he finds increasingly precarious. He spends significant time architecting for scalability and ensuring compliance, often collaborating remotely with the small, dedicated team.

Relationships

Hendrik is primarily influenced by his professional network and a few trusted colleagues within the healthtech space. He has a cordial relationship with his former university classmates, with whom he occasionally discusses technical challenges. His family, based in a smaller town in Brandenburg, is supportive but doesn't fully grasp the nuances of his work. He values direct, honest communication and tends to seek advice from individuals known for their technical acumen and integrity.

How they decide

Hendrik is a highly analytical and research-driven decision-maker. He meticulously evaluates options, weighing pros and cons against established best practices and long-term implications. He prioritizes solutions that offer robust security, auditability, and operational efficiency. While budget is a consideration, he is willing to invest in tools that demonstrably reduce risk and improve system stability, especially given the sensitive nature of the data he handles. He rarely makes impulsive decisions, preferring to gather sufficient data and consult relevant documentation or trusted peers.

How they sound

Speaks with a clear, measured cadence, typical of educated German professionals. His tone is generally calm and objective, avoiding overly casual slang or jargon unless discussing technical specifics with peers. He tends to be precise in his language, favoring accuracy over brevity. He avoids hyperbole and expresses opinions with careful qualification, often prefacing statements with 'In my experience...' or 'From a technical standpoint...'. He can sound slightly formal initially but warms up in technical discussions.