Why this persona fits the audience
He is a Berlin-based DevOps consultant who spends part of each week on client VPS fleets, shell scripts, and deployment fixes. He already works over SSH and keeps a few recurring jobs running for two small SaaS clients, then reviews every agent change carefully before pushing anything live.
- Age: 41
- Location: Berlin, Germany
- Occupation: DevOps consultant
- Income: €108,000
- Education: MSc Informatics
- Company size: Freelance (contracts with 2-3 clients at a time)
- Years in role: 12
“The most dangerous phrase in DevOps isn't 'this will work', it's 'it generally works'. I've seen too many 'generally working' systems fail spectacularly at exactly the wrong moment.”
Mert Piesker's career began with a passion for system administration during his MSc in Informatics at TU Berlin, where his thesis on distributed backup systems gave him an early reputation for reliability in otherwise volatile academic projects. After graduating in 2007, he spent five years at a Berlin hosting provider before striking out on his own in 2012, just as DevOps became a formalized discipline. His consulting practice thrived through steady word-of-mouth referrals, particularly from small SaaS companies that needed production environments that wouldn't embarrass them in front of venture capitalists. His current bread-and-butter work involves maintaining the digital infrastructure for two documentary photography archives and a Berlin-based startup in the EV charging space. Mert's approach to systems architecture is deeply influenced by his cycling hobby—he sees no difference between a poorly maintained bike chain and a server with out-of-date certificates, both needing preventative maintenance. His current professional challenge is finding the right balance between maintaining legacy systems and pushing clients toward modern practices without overwhelming them. Financially, he lives comfortably but not extravagantly, reinvesting most of his steady income into better tools and equipment. Socially, he maintains a small but tight group of friends from university, with whom he shares both technical discussions and board game sessions. His greatest personal project is building a self-hosted platform that can securely process his cycling telemetry data without relying on proprietary apps. Mert's biggest complaint about the industry is the increasing abstraction of infrastructure behind managed services, though he grudgingly admits some of these do solve real problems for developers. His ideal workday involves fixing complex problems with just a terminal, a good cup of coffee, and no interruptions.
Background & daily life
A day in their life
Mert's alarm goes off at 6:15, and he spends the first conscious minutes reviewing his dream journal (kept in plaintext files on a local server). After a breakfast of oatmeal with local honey, he cycles 15 minutes to a client office where he spends the morning debugging a failed Kubernetes upgrade that didn't account for container volume mounts. Between sessions, he checks his home server's performance via SSH tunnel, noting that one of his automated backup scripts timed out overnight. During lunch, he reads about new network routing protocols while repairing his recently punctured bicycle tire. The afternoon is spent writing Ansible playbooks to standardize configurations across three client VPSes, carefully documenting every change. At 18:30, he cycles home, stopping only for fresh bread at a Turkish bakery. The evening is spent brewing a test batch of rye IPA, monitoring fermentation with a Raspberry Pi temperature logger and tweaking his home automation system to adjust lighting based on ambient noise levels. He falls asleep around 23:00 reading about ZFS filesystem tuning, with half a dozen terminal sessions still open.
Lifestyle
Mert rents a top-floor Altbau apartment in Berlin's Prenzlauer Berg, where he's recreated his ideal minimalist workspace with a height-adjustable standing desk, three monitors, and a dedicated workstation for brewing experimental craft beers. His daily routine revolves around early morning cycling (often along the Spree to avoid traffic), followed by coffee at a local café with his self-hosted VPN active. He maintains his fitness through punishing hill climbs on weekends, often using his bike computer to track performance. Financially conservative, he rarely buys expensive equipment, preferring to assemble and tweak his own hardware. Socially, he meets a small group of former university friends for monthly board game nights, though he'd rather stay home debugging scripts on his 2015 ThinkPad.
Work life
Mert's week alternates between on-site client work and remote maintenance. His typical day starts with SSH sessions to check overnight cron jobs before reviewing GitHub pull requests. He spends 30% of his time firefighting deployment issues for small SaaS clients who skipped proper staging environments. His current frustration is a client who insists on using a specific CI/CD tool he finds brittle, forcing him to write custom wrappers. He's currently overhauling a file synchronization system for a documentary photo archive, which requires delicate handling of permissions across distributed servers. His work tools include a custom-configured Vim setup, tmux sessions, and a meticulously organized collection of shell scripts. The biggest pressure is balancing quick fixes with future-proof architecture, especially when clients want 'just this one tweak' that risks technical debt.
Relationships
Mert's closest relationships are with former university classmates from TU Berlin, particularly his old lab partner Jakob, who now works at a renewable energy startup. They meet monthly for board game nights featuring intense discussions about infrastructure-as-code. His parents live in Hamburg and call occasionally, though their understanding of his work extends only to 'you fix computers, right?'. He occasionally contributes to open-source projects but prefers private repositories for his more experimental work. In his cycling community, he's known for his obsessive routing calculations and refusal to use GPS apps that don't respect data privacy.
How they decide
Cautiously analytical. He'll spend hours researching before purchasing hardware, but will make snap decisions about coffee preferences. When evaluating technical solutions, he simulates scenarios in his head before implementing, often seeking second opinions from trusted peers. Financially, he's conservative with big expenses but will splurge on quality tools that save time.
How they sound
Speaks with careful precision about technical matters, but adopts a dry humor when describing client difficulties. Uses German technical terms even when speaking English, especially for infrastructure concepts. Avoids jargon when explaining things to non-technical people but doesn't simplify unnecessarily. His sentences often trail off when he's mentally debugging. When excited about a technical solution, he'll use the phrase 'ah, but you see' before elaborating. Never says 'just' about technical work ('just a quick fix' becomes 'a simple adjustment').
Personality traits
- Analytically meticulous about system architecture
- Slightly cynical about 'cloud-first' trends
- Enjoys quiet working sessions with just a terminal open
- Hoards obscure Linux tools for niche problems
- Routinely double-checks his own scripts for edge cases
- Unwilling to trust automation he hasn't personally tested
- Secretly enjoys writing scripts that outlast their original purpose
- Dislikes phone calls at all hours but tolerates them for clients
- Will spend 2 hours solving a problem that could be fixed in 30 minutes
- Prefers bicycle couriers to Amazon when possible
Goals
- Build a reputation for handling legacy system migrations
- Create a standardized automation toolkit for small SaaS clients
- Finish the 600km Berlin-København bike route next summer
- Perfect his Baltic porter beer recipe
- Reduce screen time in evenings (currently fails at this)
- Simplify his client acquisition process without sacrificing quality
Problems & frictions
- Clients who treat 'it works on my machine' as sufficient testing
- Legacy systems requiring 20th-century troubleshooting approaches
- The eternal conflict between quick patches and proper architecture
- Finding time for personal projects beyond basic home server maintenance
- Mutual fund returns not keeping up with Berlin's rising rents
- Bicycle tires constantly needing patching due to Berlin's awful roads
Values
- reliability
- control
- efficiency
- privacy
- craftsmanship
Interests
- Linux system optimization
- road cycling (computes routes using OpenStreetMap)
- home automation via Raspberry Pi
- minimalist design
- beer brewing (small batches in his apartment)
Media habits
- Reads Linux Weekly News and DevOps blogs during morning coffee
- Listens to Hacker News podcasts on commutes (ebike to client offices)
- Watches bicycle repair YouTube channels during late-night brewing sessions
- Occasionally tweaks his self-hosted Nextcloud for note-taking