- Age: 29
- Location: Neukölln, Berlin, Germany
- Occupation: Customer Support Lead
- Income: €40,000 gross annually
- Education: Bachelor of Science in Computer Science from Hochschule für Technik und Wirtschaft Berlin
- Company size: Approximately 85 employees; the customer support team has 14 people
- Years in role: 2
“I don't need everything to be perfect; I need to understand what is actually happening so I can make the next sensible move.”
Jonas grew up in Potsdam in a practical, academically comfortable family. His father repairs industrial machinery, and his mother works in municipal administration, so Jonas learned early that both technical skill and patient paperwork can solve surprisingly large problems. At fourteen he built a crude media server from discarded computer parts. It was noisy, unreliable, and deeply satisfying when it finally streamed music to the family laptop. That experience shaped his preference for understanding systems from the inside rather than treating them as sealed objects. He studied computer science at HTW Berlin, choosing applied modules and student jobs over a more theoretical path. During university he worked evenings at a small electronics shop, where he discovered that explaining a confusing technical issue was often harder than fixing it. He joined his current employer as a support agent in 2019, became a senior specialist, and took over team leadership after a manager left unexpectedly. He still answers difficult tickets because he does not want to lose contact with the underlying problems. Jonas's working environment is a patchwork of Zendesk views, Slack channels, Notion pages, spreadsheets, and dashboards. He has written small Python scripts to clean ticket exports and uses browser automation for repetitive checks, though he does not consider himself a proper developer anymore. His recent decisions have mostly involved trade-offs between convenience and maintainability: consolidating documentation, replacing a failing office monitor, and declining a management seminar that conflicted with a long-planned family visit. Time matters to him more than status. He would like a more senior role, but not one that turns him into someone who attends meetings all day and knows less about the work afterward. Money gives him security rather than prestige. He saves consistently, avoids carrying consumer debt, and repairs ordinary household items before replacing them. Still, he is not austere: a well-designed tool, an excellent meal, or an evening with friends feels worth the expense. His central constraint is not ambition but attention; too many open loops follow him from work into his small apartment.
Background & daily life
A day in their life
Jonas wakes around 7:00, feeds Pixel, and checks overnight support volume while making coffee. He cycles through quiet streets to the office, usually arriving before his first meeting. The morning begins with a queue review, staffing adjustments, and a short team check-in about unusual technical cases. Before lunch he handles two escalations, one involving a damaged graphics card and another requiring coordination with the warehouse. His afternoon alternates between coaching sessions, dashboard work, and interruptions from logistics or product teams. He eats at his desk more often than he admits, usually while reading a technology newsletter. After work he stops for groceries, answers a few personal messages, and spends an hour repairing a faulty soldering iron or playing an online game. He usually reads in bed, then remembers one more task at midnight.
Lifestyle
Jonas rents a compact Altbau apartment in Neukölln, where exposed brick, bike parts, and half-finished electronics projects compete for space. He cycles to work most days and cooks simple meals four or five nights a week, usually pasta, curry, or something assembled from supermarket leftovers. He plays PC games with two university friends on Wednesday evenings and attends a monthly repair café when his schedule allows. His health is generally good, although he gets tension headaches during intense work periods and postpones routine appointments. He tracks expenses in a spreadsheet, saves automatically each month, and spends freely only on hobbies, books, and occasional dinners with friends.
Work life
Jonas leads a 14-person support team for an online electronics retailer selling components, peripherals, smart-home devices, and refurbished hardware. His day combines queue monitoring, escalations, coaching, quality reviews, and discussions with logistics, engineering, and warehouse staff. The team uses Zendesk, Slack, Notion, Looker dashboards, and an internal inventory system that Jonas considers powerful but unnecessarily confusing. He handles German and English cases, especially technical troubleshooting and recurring delivery failures. His main pressure is translating vague customer descriptions into actionable information without making agents feel blamed. He enjoys training new hires and improving macros, but dislikes spending hours defending decisions that should be settled by better documentation.
Relationships
Jonas speaks with his mother in Potsdam every Sunday and visits his younger sister, who studies environmental science in Leipzig, several times a year. His closest friends are former university classmates who now work in software, IT security, and games. They exchange excessively detailed messages about hardware failures and apartment problems. At work, newer agents often seek him out because he explains mistakes without humiliating people. His flatmate years are over, but he remains active in a small local repair and cycling community.
How they decide
Jonas is research-heavy and comparison-oriented, but not paralyzed by analysis when the consequences are minor. He starts by defining the actual problem, gathers information from several sources, and prefers tests, documentation, and firsthand evidence over confident opinions. He often makes a provisional choice, observes how it performs, and adjusts later. For decisions affecting other people, he asks for input early and tries to make his reasoning transparent. He is more influenced by technically competent peers than by status, popularity, or polished presentation.
How they sound
Jonas speaks clearly and moderately quickly, with a Berlin-influenced casualness but little theatrical slang. He often says, "Lass uns das einmal sauber auseinandernehmen" when diagnosing a problem. He uses English workplace terms naturally, especially "edge case," "follow-up," and "good enough for now." His humor is dry and usually aimed at systems rather than people. He is comfortable correcting factual errors, but softens the correction with context. He avoids exaggerated enthusiasm, corporate motivational language, and claiming certainty when he has not checked the details.
Personality traits
- Curious but skeptical
- Methodical under pressure
- Dryly funny
- Patient with beginners
- Restless when processes are inefficient
- Technically pedantic in private
- Reliable with follow-through
- Socially warm after an initial reserve
Goals
- Move into a customer operations or service design role with more influence over company processes
- Become genuinely fluent in data analysis and automation rather than relying on copied scripts
- Build a functional electronics workbench and complete several neglected projects
- Maintain enough financial stability to eventually buy a small apartment outside the city
- Stay physically active without turning exercise into another performance metric
Problems & frictions
- Support documentation is scattered across outdated pages, personal notes, and informal Slack messages
- Escalations often arrive without the serial numbers, screenshots, or reproduction steps needed to solve them
- He struggles to protect focused learning time from constant notifications and urgent requests
- His apartment is too small for both comfortable living and a proper electronics workspace
- Management sometimes measures response speed more visibly than resolution quality
- He tends to take responsibility for team problems that should be shared with other departments
Values
- Problem-solving that produces a clear, verifiable result
- Technical accuracy over confident guesswork
- Continuous learning, especially through hands-on experimentation
- Fairness in how policies are applied to customers and coworkers
- Independence and practical competence
Interests
- Consumer electronics and repairable gadgets
- PC gaming and cooperative strategy games
- DIY electronics with Raspberry Pi, Arduino, and salvaged components
- Urban cycling and exploring Berlin's neighborhoods
- Mechanical keyboards and small desk-setup improvements
Media habits
- Reads German and English technology newsletters during breakfast
- Watches long-form repair, engineering, and programming videos on YouTube
- Uses Reddit and specialist forums to troubleshoot obscure technical issues
- Listens to podcasts about software development, digital rights, and games
- Keeps up with local events through Berlin community newsletters and Telegram groups