Why this persona fits the audience
He is one of three engineers at a Berlin startup and helps cover PostgreSQL backups for production and analytics databases. Their current process is pg_dump plus custom bash scripts, with restore checks done manually to a spare VM and logged in Google Sheets.
- Age: 29
- Location: Berlin, Germany
- Occupation: Backend engineer
- Income: €72k
- Education: B.Eng. Software Engineering
- Company size: Small (startup, <20 employees)
- Years in role: 2
“We're building fast, which is great, but if we can't reliably get our data back when things go wrong, all that speed is built on sand.”
Maddox Thriene, 29, is a backend engineer at a burgeoning Berlin startup, a role he's held for two years. His journey into software engineering began with a B.Eng. from a reputable German technical university, where he developed a strong foundation in computer science principles. He gravitated towards backend systems and infrastructure, finding satisfaction in building robust, efficient solutions. His current role places him at the heart of a small, dynamic team where rapid iteration is paramount. He's one of only three engineers, meaning responsibilities are broad and often spill beyond core development. A significant part of his workload involves ensuring the integrity of the company's PostgreSQL databases, specifically managing backups for both production and analytics environments. The current methodology, a combination of `pg_dump` commands orchestrated by custom bash scripts, feels increasingly precarious to him. He dedicates time each week to manually execute restore checks on a separate virtual machine, meticulously documenting the outcomes in a shared Google Sheet. This process, while functional, highlights a growing technical debt he's keen to address. Maddox values shipping quickly, but not at the expense of fundamental reliability. He's drawn to clean tooling and believes strongly in learning by doing, often diving into new open-source projects to solve immediate problems. His income of €72k allows for a comfortable life in Berlin, though he remains mindful of saving for future goals, such as property ownership. He's not driven by status symbols; his satisfaction comes from solving complex technical challenges and building systems that work dependably. His decision-making process is generally pragmatic and research-oriented, preferring well-documented, stable solutions for critical infrastructure over trendy, unproven technologies. He sees the current backup situation as a ticking clock, a problem that needs a more sustainable, automated solution before it causes a critical failure.
Background & daily life
A day in their life
Maddox's weekday typically starts around 8:00 AM with a quick check of emails and Slack while making coffee. He cycles to the office by 9:00 AM, often listening to a tech podcast. The morning is usually dedicated to coding new features or tackling bugs, interspersed with stand-up meetings. Lunch is a quick affair, often a packed meal or something from a nearby Imbiss. Afternoons involve more development, code reviews, and crucially, monitoring the backup scripts. He might spend an hour verifying a recent restore or updating the Google Sheet log. He usually leaves around 6:30 PM, sometimes later if a deployment is imminent, before cycling home.
Lifestyle
Maddox lives in a shared apartment in Prenzlauer Berg, a compromise to afford living in a desirable part of Berlin. He's disciplined with his finances, saving a good portion of his income, but enjoys occasional weekend trips and good craft beer. His cycling isn't just for commuting; he enjoys longer weekend rides in Brandenburg, often pushing himself on hilly routes. He prioritizes sleep and tries to cook healthy meals, though late-night coding sessions sometimes lead to takeout. Socially, he's comfortable with his close-knit group of friends from university and colleagues, preferring deeper conversations over large gatherings.
Work life
As one of only three engineers at a rapidly growing Berlin startup, Maddox wears many hats. His primary focus is backend development, but he's also deeply involved in maintaining critical infrastructure, including PostgreSQL backups for both production and analytics databases. The current process, a mix of `pg_dump` and custom bash scripts, feels increasingly fragile. He spends a significant chunk of his week ensuring these scripts run, manually verifying restores on a spare VM, and meticulously logging the results in Google Sheets. The pressure to ship new features quickly often clashes with his desire for more robust, automated solutions, creating a constant tension.
Relationships
Maddox maintains strong ties with his university friends, who often share similar career paths and challenges. His relationship with his parents is supportive, though they don't fully grasp the nuances of his tech career. At work, he has a collegial relationship with the other two engineers and the CTO, characterized by direct communication and a shared drive to succeed.
How they decide
Maddox tends to be research-heavy when it comes to technical decisions, especially those impacting stability. He'll explore documentation, read blog posts, and check GitHub issues. However, for operational tasks where time is critical, he relies on established patterns and peer recommendations if available. He values practical, proven solutions over bleeding-edge, unproven technologies, especially for core infrastructure.
How they sound
Speaks with a clear, measured cadence, typical of educated German speakers. Uses precise technical language when discussing work but can switch to more casual phrasing with friends. Avoids overly enthusiastic or sales-y language. Tends to be direct and factual, sometimes a bit dry. Might use phrases like 'essentially', 'the crux of the issue', or 'from a practical standpoint'.
Personality traits
- Pragmatic
- Detail-oriented
- Resourceful
- Methodical
- Independent
- Slightly reserved
- Curious
- Driven by practical results
Goals
- Achieve a senior engineering role with more autonomy
- Contribute to a significant open-source project
- Own a small property in Berlin eventually
- Develop expertise in scalable cloud architectures
- Maintain a healthy work-life balance long-term
Problems & frictions
- The current backup process is manual, time-consuming, and prone to human error.
- Lack of automated restore testing leads to uncertainty about recovery reliability.
- Balancing the urgent need for new feature development with essential infrastructure maintenance.
- Limited budget and resources at the early-stage startup.
- Feeling the technical debt accumulating in critical areas like backups.
Values
- shipping quickly
- clean tooling
- learning by doing
- robustness
- efficiency
Interests
- open-source tooling
- cloud infrastructure
- cycling
- DevOps practices
- database administration
Media habits
- Reads Hacker News daily
- Listens to tech podcasts during commutes
- Follows key figures on Mastodon
- Skims Reddit's r/devops and r/PostgreSQL
- Watches YouTube tutorials for new tools