Joey Bornscheuer

Why this persona fits the audience

Leads a 4-person IT operations team in Berlin supporting roughly 220 staff across Mac and Windows fleets. He owns Jira Service Management, Okta workflows, and a small set of Python scripts for password resets, onboarding, and basic access tickets.

• Age: 44
• Location: Berlin, Germany
• Occupation: IT operations lead
• Income: €96k
• Education: Master's degree in computer science
• Company size: Mid-sized software consultancy with 250 employees
• Years in role: 8

“The elegance of a system isn't in its complexity, but in its resilience and the clarity of its design. If you can't explain it simply, you haven't understood it deeply enough.”

Joey Bornscheuer, 44, is an IT operations lead deeply rooted in the technical realities of managing IT infrastructure for a mid-sized consultancy in Berlin. His Master's degree in Computer Science provided a strong theoretical foundation, which he has spent the last eight years applying and refining in his current role. He leads a team of four, responsible for the smooth operation of systems supporting around 220 employees, a diverse fleet of Macs and Windows machines. Joey's domain includes the critical tools that keep the company running: Jira Service Management for ticket tracking, Okta for identity and access management, and a suite of custom Python scripts he personally developed for essential tasks like password resets and user onboarding. He views these scripts not as a limitation, but as a testament to his ability to build precisely what's needed. His approach is characterized by an almost obsessive commitment to technical rigor and security; he believes that robust documentation and well-understood processes are the bedrock of reliable IT operations. This philosophy often puts him at odds with faster, less-thorough methods, making him inherently skeptical of solutions that promise automation without transparent, verifiable mechanisms. He lives alone in a comfortable, if somewhat spartan, apartment in Prenzlauer Berg, a reflection of his preference for order and control. His income of €96k allows for financial security, with a significant portion directed towards savings, a pragmatic approach to Berlin's challenging housing market. While he appreciates the efficiency of modern technology, he finds genuine satisfaction in the tangible act of building and maintaining systems himself, preferring the predictable logic of code and configuration over the often-unpredictable nature of human-driven processes or unproven third-party solutions. His recent focus has been on hardening access controls within Okta and ensuring his Python scripts are fully compliant with new data privacy regulations, a task that has consumed considerable time and mental energy, reinforcing his belief that true control comes from understanding every layer of the stack.

Background & daily life

A day in their life

Joey's typical weekday begins with a brisk cycle commute, arriving at the office by 8:00 AM. He immediately checks the Jira dashboard, triages urgent tickets, and reviews overnight system logs. The morning is often spent in team stand-ups, troubleshooting user issues, and refining his Python scripts. Lunch is a quick, healthy meal at his desk while catching up on Heise Online. Afternoons involve deeper dives into security patching, planning minor infrastructure updates, or documenting a recent change. He aims to leave by 6:00 PM, often taking an audiobook with him for the cycle home, where he'll prepare dinner and unwind before reviewing technical articles.

Lifestyle

Joey's routine is a well-oiled machine. He wakes at 6:30 AM, cycles 8km to the office, and spends evenings reading technical journals or listening to cybersecurity podcasts while preparing simple, healthy meals. Weekends are for longer cycling routes through Brandenburg or meticulously organizing his apartment. He's financially prudent, saving consistently for a future down payment on a small house, though he finds Berlin's property market daunting. Social life is limited to a few close friends from university, usually meeting for a quiet beer or discussing tech over dinner.

Work life

Joey's days are a constant juggle of reactive support and proactive, albeit slow, system improvement. He oversees a team of four, ensuring ticket queues in Jira Service Management are managed, Okta workflows are functioning, and his own Python scripts for password resets and onboarding are running smoothly. The pressure comes from the sheer volume of requests from 220 users and the constant threat of security vulnerabilities. He spends a significant portion of his time documenting processes, a task he finds crucial but often rushed by others. He trusts his team but feels the ultimate responsibility for system stability rests squarely on his shoulders.

Relationships

Joey maintains a professional but somewhat distant relationship with his team, valuing competence and diligence above all. His closest confidante is an old university friend, now a senior engineer at another tech firm, with whom he exchanges technical insights and commiserates about industry trends. He has a cordial relationship with his manager, who trusts his technical judgment but sometimes pushes for faster, less-vetted solutions.

How they decide

Joey is a methodical decision-maker. He gathers all available data, researches potential solutions thoroughly, and weighs them against established technical principles and security requirements. He prefers to pilot new tools or processes with a small group before wider rollout and is highly resistant to adopting anything that lacks comprehensive documentation or a clear, demonstrable benefit that outweighs the risks of implementation.

How they sound

Speaks with a measured, precise cadence. Avoids slang and overly casual language, even in informal settings. His tone is generally calm but can become firm when discussing security or technical standards. He uses complete sentences and often employs technical jargon naturally. He tends to pause before answering complex questions, indicating careful consideration. He rarely expresses strong emotional opinions, preferring to frame points around logic and evidence.