Can Kock

Why this persona fits the audience

Maintains runbooks, shell scripts, and incident postmortems for a 20-person engineering org. Often checks whether filenames, log messages, and ASCII-only automation notes contain the right symbols; keeps a self-made spreadsheet of copied characters and relies on manual searching most days.

• Age: 46
• Location: Berlin, Germany
• Occupation: DevOps engineer
• Income: €78,000/year
• Education: Diploma in information technology
• Company size: 20 engineers in current team, 120 total at Berlin-based SaaS company.
• Years in role: 12

“The most reliable system is the one you understand completely, down to the last character.”

Can Kock, 46, has been a DevOps engineer in Berlin for over a decade, currently working at a mid-sized SaaS company. His journey into IT began with a fascination for how things work under the hood, leading him to pursue a Diploma in Information Technology. He found his niche in system administration and later DevOps, drawn to the challenges of ensuring stability and efficiency in complex systems. Can's approach is deeply rooted in process discipline and a relentless pursuit of reliability; he views minimizing surprises as the ultimate measure of success in his field. This manifests in his meticulous maintenance of runbooks, his extensive collection of shell scripts designed to automate repetitive tasks, and his thorough postmortem analyses following any incident, no matter how minor. He operates with a high degree of conscientiousness, often double-checking configurations and log messages for minute details, including the precise usage of ASCII and Unicode characters, a task he finds surprisingly cumbersome. His self-made spreadsheet of 'useful' characters is a testament to this ongoing struggle. Can's income of €78,000/year allows for a comfortable, stable life in Berlin, which he prioritizes over rapid wealth accumulation. He lives alone, valuing his independence and the quiet control he has over his personal environment. His professional life is characterized by a preference for deep work and problem-solving, often preferring to spend hours debugging a complex issue himself rather than interrupting colleagues. He recently decided to invest more time in documenting the intricacies of the company's legacy systems, recognizing that while tedious, this knowledge is critical for long-term stability, especially as the engineering team grows. He views his role not just as maintaining servers, but as building and preserving the foundational integrity of the company's digital infrastructure, one script and one runbook entry at a time.

Background & daily life

A day in their life

Can's typical weekday begins around 7:30 AM with a strong black coffee and a quick scan of overnight system alerts. After a simple breakfast, he cycles to the office, arriving by 9:00 AM. The morning is usually dedicated to proactive tasks: reviewing logs, updating runbooks, refining automation scripts, and attending a brief stand-up meeting. Lunch is a quick, solitary affair, often eaten at his desk while reading tech news. The afternoon might involve troubleshooting a performance issue, collaborating with a developer on a deployment pipeline, or meticulously documenting a recent incident. He leaves the office around 5:30 PM, cycles home, and spends his evening unwinding with personal projects or a quiet dinner. He avoids unnecessary meetings and prefers asynchronous communication when possible.

Lifestyle

Can lives alone in a functional, uncluttered 70m² apartment in Prenzlauer Berg, Berlin. His evenings are often spent immersed in system administration tasks for personal projects, playing retro video games, or cycling through the city on his well-maintained road bike. He cooks simple, healthy meals most nights, prioritizing efficiency. While not a recluse, his social life is limited to a few close friends from university and occasional tech meetups. He's financially prudent, saving consistently but not aggressively, viewing his income as a means to maintain stability and fund his hobbies rather than a path to ostentatious wealth. He values his quiet routine and the predictability it offers.

Work life

Can's days are a constant balancing act between proactive system maintenance and reactive incident management for his 20-person engineering team. He spends significant time refining shell scripts for automation, meticulously updating runbooks, and dissecting past incidents in postmortems, always striving for clarity and actionable insights. His current focus is on standardizing log message formats across services to improve debugging efficiency. He navigates a landscape of inherited scripts and evolving infrastructure, often feeling like he's patching holes faster than they appear. Coworkers appreciate his reliability but sometimes find his detailed, almost pedantic, approach to documentation a bit overwhelming.

Relationships

Can maintains a small circle of close friends, mostly from his university days, with whom he shares technical discussions and occasional board game nights. He has a cordial but professional relationship with his colleagues, respecting their expertise but preferring to keep interactions focused on work tasks. His family lives in another part of Germany, and they communicate infrequently via phone calls. He is largely self-reliant, with no single individual acting as a primary influencer in his professional or personal life.

How they decide

Can is a cautious, research-heavy decision-maker. He prefers to gather all available information, weigh pros and cons systematically, and often consults technical documentation or community forums before committing to a course of action. He is not easily swayed by trends or peer pressure, valuing proven reliability and efficiency above all else. For operational tools or processes, he will often prototype or test extensively in a staging environment before implementing anything in production.

How they sound

Can speaks with a measured, deliberate cadence, often pausing to formulate his thoughts precisely. His tone is generally calm and factual, with a dry, understated wit that surfaces in written communication more than in spoken words. He avoids hyperbole and overly enthusiastic language, preferring directness and clarity. When discussing technical issues, he uses precise terminology but is patient in explaining complex concepts. He tends to use German sentence structures even when speaking English, occasionally resulting in slightly formal phrasing. He rarely uses slang and actively avoids jargon unless it's standard within his technical domain.