Tillmann Hanniske

Why this persona fits the audience

He runs SRE for a 5-person infrastructure group at a Berlin B2B API company, using Alertmanager, Slack, and a shared spreadsheet to route after-hours pages across two time zones.

• Age: 37
• Location: Berlin, Germany
• Occupation: SRE Lead
• Income: €108k salary
• Education: Dipl.-Ing. Computer Engineering
• Company size: 50-100 employees
• Years in role: 4

“The goal isn't just to fix things when they break, but to build systems so resilient that they rarely need fixing in the first place.”

Tillmann Hanniske, a 37-year-old SRE Lead based in Berlin, embodies a blend of technical rigor and practical application. His journey into Site Reliability Engineering began during his Dipl.-Ing. studies in Computer Engineering, where he developed a deep appreciation for robust systems and efficient problem-solving. After graduating, he spent several years at a larger enterprise software company, honing his skills in distributed systems and cloud infrastructure before moving to his current role at a growing B2B API firm. His position requires him to oversee a small but critical infrastructure team, ensuring the high availability and performance of the company's core services. This responsibility is amplified by the company's international reach, necessitating coordination across two time zones. His current operational reality is defined by a reliance on Alertmanager for alerts, Slack for communication, and a somewhat rudimentary shared spreadsheet for managing after-hours pages – a system he finds increasingly inefficient and prone to human error. This manual approach to on-call management is a significant pain point, driving his constant search for more automated and precise solutions. Tillmann is deeply invested in the principles of SRE, valuing automation, precision, and minimizing toil above all else. His personal life is a reflection of this desire for order and control, evident in his passion for woodworking, where he meticulously crafts functional pieces, and his disciplined approach to mountain biking, which demands both physical endurance and strategic planning. He lives alone in a well-organized apartment in Prenzlauer Berg, a testament to his preference for structure and efficiency. Financially, he is responsible, saving diligently, but he doesn't shy away from investing in quality tools or experiences that align with his interests. His career trajectory is focused on advancing system resilience and reducing operational overhead, aiming to create infrastructure that is not only reliable but also inherently maintainable with minimal human intervention. He sees the current paging system not just as an inconvenience, but as a fundamental impediment to achieving true SRE maturity.

Background & daily life

A day in their life

Tillmann's weekday typically begins around 7:30 AM with a strong coffee and a quick scan of Hacker News and overnight alerts. After a brief stand-up with his team, he dives into his primary tasks: refining Kubernetes deployments, optimizing Prometheus queries, or writing automation scripts. Lunch is usually a quick, healthy meal he prepared earlier. The afternoon might involve a deep-dive into a system performance issue, a planning session for an upcoming infrastructure upgrade, or reviewing code for a new monitoring tool. He tries to wrap up by 6 PM, but urgent alerts can easily extend his day. Evenings are for unwinding, perhaps with some woodworking or a short bike ride if the weather permits.

Lifestyle

Tillmann lives a structured but not rigid life in Berlin. His apartment, filled with custom-built wooden shelves and a meticulously organized workshop corner, reflects his woodworking hobby. He prioritizes efficiency, often meal-prepping on Sundays to simplify weekday dinners. Weekends are a mix of intense mountain biking rides in the Brandenburg countryside or losing himself in the rhythmic pulse of a techno club. He’s financially prudent, saving a significant portion of his income, but enjoys investing in quality tools for his hobbies and occasional travel. Socially, he prefers smaller gatherings with close friends over large parties.

Work life

As SRE Lead, Tillmann is the primary architect of reliability for his company's B2B APIs. His team of five navigates the complexities of ensuring uptime across multiple cloud environments, primarily using Kubernetes. The current after-hours paging system, a patchwork of Alertmanager, Slack channels, and a shared Google Sheet, is a constant source of low-level friction. He spends his days optimizing CI/CD pipelines, refining monitoring dashboards, and architecting disaster recovery scenarios. The pressure to maintain near-perfect uptime for critical business APIs is ever-present, often leading to late-night debugging sessions or urgent Slack messages, even when he's technically 'off-duty'.

Relationships

Tillmann maintains a close-knit circle of friends, many from his university days or shared hobbies like mountain biking. His parents, retired engineers living in Bavaria, are proud of his career but don't fully grasp the intricacies of SRE. He has a friendly, professional rapport with his team, valuing their technical input, but his reserved nature means he doesn't socialize extensively with colleagues outside of work.

How they decide

Tillmann is a methodical and research-driven decision-maker. He thoroughly evaluates options, weighing pros and cons against his core values of precision and efficiency. He's not easily swayed by trends or marketing hype, preferring to understand the underlying technical merits and long-term implications. He will often prototype or test solutions in a controlled environment before committing to widespread adoption. Peer recommendations are considered but rarely the sole deciding factor.

How they sound

Speaks with a clear, measured cadence, often using precise technical terminology. His German accent is noticeable but not heavy. He avoids overly casual slang or effusive language, preferring direct and factual communication. When discussing complex issues, he might pause to formulate his thoughts carefully. He tends to use phrases like 'essentially,' 'from a systems perspective,' or 'the primary concern is.'